Roberta Piket performs as a jazz pianist and owns Geek Girls IT Services, a managed IT provider in Teaneck, New Jersey. She runs both brands from a single login in RecurPost social media management software, across six social accounts on four networks. No account carries content from both brands. This page documents how that setup runs, and the rule that decides whether an operator like her needs one content library or two.
Two Brands That Share an Owner and Share No Accounts
Jazz performance career and a managed IT provider
New York, and Teaneck, New Jersey
6 social accounts on 4 networks, one RecurPost login
Roberta Piket is a jazz pianist, organist and composer based in New York. She also owns Geek Girls IT Services, a managed IT provider she founded in 2005 and runs from Cedar Lane in Teaneck, New Jersey, serving small businesses and nonprofits across New Jersey and New York.
Roberta’s two businesses share nothing except an owner. Jazz listeners follow her for gig dates and recordings. IT clients follow Geek Girls for security advice and service updates. Neither audience wants the other’s posts in its feed.
Her account set makes that separation concrete.
| Brand | Network | Account |
|---|---|---|
| Roberta Piket Jazz | Facebook Page | facebook.com/TheRealRobertaJazz |
| Roberta Piket Jazz | X | x.com/robertajazz |
| Roberta Piket Jazz | YouTube | youtube.com/user/rpiket |
| Geek Girls IT Services | Facebook Page | facebook.com/GeekGirlsIT |
| Geek Girls IT Services | LinkedIn company page | linkedin.com/company/geek-girls |
| Geek Girls IT Services | X | x.com/geekgirls_IT |
Roberta publishes to six accounts across four networks. Not one of those accounts receives both streams. That zero overlap decides everything else on this page.
Posting by Hand for Two Brands Multiplies by Account, Not by Brand
Roberta’s manual publishing load scaled with her account count, not her brand count. One gig announcement was never one post.
A gig announcement is a Facebook Page post, an X post shaped to fit 280 characters, and a video upload with its own title and description. An IT blog update is another three pieces of work: a Facebook Page post, a LinkedIn company page post, and a second X post. One announcement on each side of the business meant six separate acts of publishing.
Roberta’s two content streams also run on different clocks. Gig announcements are dated. They matter for a week and then they are worthless, because the show already happened. IT blog posts carry no expiry and stay useful months after publication. RecurPost runs those two rhythms on two schedules, which only works because the content sits in two places.
An operator running one brand across two accounts does not have this problem and does not need this setup.
How RecurPost Keeps Two Brands’ Posting Separate
RecurPost attaches one posting schedule to one content library. Two libraries therefore give two brands two independent schedules, each pointed at its own accounts.
Roberta runs a jazz library and an IT library inside one RecurPost login. The jazz library publishes only to her three jazz accounts. The IT library publishes only to the three Geek Girls accounts. Neither library can reach the other brand’s audience, because RecurPost sets the destination accounts on the library’s schedule rather than on the individual post.
In RecurPost, the destination account set decides library structure, not the brand count.
Roberta’s two libraries work because each one owns its own accounts. One library is the better build where both streams would publish to the same accounts. One schedule attaches to one library, so two libraries aimed at the same accounts compete for the same posting slots. A social media manager running two service lines from a single Facebook Page and a single LinkedIn page is in that second case, not Roberta’s.
You can repeat Roberta’s test on your own accounts in half a minute. Open the list and check whether any single account would carry posts from both brands. If none would, two libraries are safe.
Inside each library, RecurPost’s evergreen recurring libraries refill slots from posts still worth publishing, and one-time-use posts publish once and drop out of the rotation. Roberta uses both types, which matters more than it sounds. A gig announcement set to recur would republish a date that has already passed. See RecurPost publishing features for how libraries and schedules fit together.
What Actually Happens When a Blog Post Enters Through RSS
RecurPost’s RSS-based content import moves a feed item into a content library. It does not publish the item. The library’s schedule publishes it.
RecurPost’s two-step path is the part most descriptions skip. Roberta connected the Geek Girls blog feed at geekgirlsit.com/blog. When a new post appears there, RecurPost picks it up on its next fetch and places it in the IT library. The IT library’s schedule then sends it to the Geek Girls Facebook Page, the LinkedIn company page and the IT X account at the next open slot.
RecurPost gives each feed an approval setting, and that setting decides whether a person stands between the feed and the library. RecurPost’s add to library after approval setting holds every imported item for review. The add to library without approval setting sends items into the library on their own. With the second setting and a schedule already attached, a new blog post reaches all three Geek Girls accounts without Roberta touching anything.
RecurPost’s RSS import fits a brand that already publishes long-form on someone else’s schedule, so the feed does the noticing. It does not fit an operator who wants to edit every headline before it goes anywhere, though that operator can set the feed to require approval and accept the extra step.
Every Account in Roberta’s Setup Publishes Without Her
RecurPost publishes automatically to all six of Roberta’s accounts. Facebook Pages, LinkedIn company pages, X accounts and YouTube channels all accept scheduled posts through their platform APIs, so nothing in her setup waits on a person.
RecurPost cannot publish to every destination that way. Meta retired automatic Group posting in April 2024, and no scheduler can post to a Facebook Group or a personal Facebook profile without someone tapping a notification in a mobile app. Roberta has neither. Both of her Facebook destinations are Pages, which is why her queue runs unattended. See Facebook publishing constraints for the full split.
RecurPost’s unattended queue matters most when nobody is watching it. A gig announcement scheduled on Tuesday goes out on Friday while Roberta is on a bandstand. RecurPost handles more than 850 documented platform error conditions behind that queue, including image size mismatches and access tokens that report a false expiry, so a post that fails gets flagged instead of disappearing quietly.
If Roberta added a Facebook Group for a students’ community, that one destination would need the notification tap. The constraint is Meta’s, not RecurPost’s.
One Announcement, Four Networks, Four Sets of Rules
RecurPost holds a separate version of each post per network rather than sending one block of text everywhere. That is the difference between announcing a gig and announcing it four times.
X gives Roberta 280 characters, and a link counts as 23 of them however long the URL runs. Her Facebook Page post has room for the full personnel list and the venue address. LinkedIn takes the Geek Girls posts framed for a business audience. YouTube wants its own title of up to 100 characters, a description of up to 5,000, and one of 17 categories.
YouTube also decides the format itself. A vertical clip up to three minutes publishes as a Short. A 16:9 export publishes as a regular video. That is YouTube’s rule rather than a RecurPost setting, so a trio recording shot wide always lands as a standard video.
RecurPost’s per-network customization earns its keep when one event has to appear on networks with incompatible limits. An operator posting the same short line everywhere gains little from it.
What Changed for Roberta
Roberta’s publishing trigger moved from her to the schedule. Before RecurPost, every gig announcement and every blog update meant stopping work and posting to three accounts by hand. Now each library publishes on its own cadence to its own accounts.
Roberta reports more social engagement and better gig attendance since the switch. Those are her figures rather than measured ones, and results in social publishing depend heavily on where an account started.
Roberta’s setup is verifiable even where her results are not. Six accounts publish from one login. Two libraries never collide, because they never share a destination. Gig announcements run as one-time-use posts so a past date never resurfaces, while IT content recurs.
RecurPost does not build an audience. It keeps a schedule. An operator with nothing in the pipeline gets an empty queue on a timer.
Who This Two-Brand Setup Fits, and Who It Does Not
Roberta’s setup fits an operator running two or more brands whose social accounts do not overlap. Freelancers with a side practice, consultants who also speak or perform, and agency owners marketing both the agency and a second product line all land in that shape. At least one brand should carry a blog or feed worth importing, and the content should either repeat or arrive on a schedule.
Roberta’s setup is the wrong shape in four situations. One library beats two where both brands publish to the same accounts, because two schedules aimed at one account fight for the same slots. A queue adds nothing to an operator whose posts are same-day commentary on something that just happened. Roberta’s unattended publishing also breaks down if a brand’s only Facebook presence is a Group or a personal profile, since those destinations need a notification tap on a phone. The fourth case is softer. An operator who wants every imported item reviewed can set the feed to require approval and live with the extra step.
RecurPost’s approval workflow is not one of those limits. Roberta works alone, so she never used RecurPost’s post approval workflow, where a writer sends a post to the workspace owner or named teammates and reviewers approve, reject or edit it before it publishes. RecurPost sets approval per post rather than locking it to a role. A two-brand operator who later hires a writer has the workflow waiting.
Try RecurPost
RecurPost prices by social account, not by user seat. Roberta’s six accounts run on the Personal plan at $25 per month for five accounts plus $4 per month for the sixth, which is $29 per month for both brands together. She is the only person in the account, so she pays nothing for seats.
5 social accounts. Roberta’s sixth account adds $4 per month, so both brands run for $29 per month.
20 social accounts and 3 team members included, with extra members at $20 per month each.
RecurPost backs every plan with a 30-day money-back guarantee, and the free trial runs 14 days.
RecurPost’s pricing structure holds as brands multiply. See RecurPost plans and pricing for every plan and add-on with its unit price, read the other RecurPost customer case studies for different operating setups, or start a 14-day free trial.
Roberta Piket Case Study FAQs
Common questions about running more than one brand from a single RecurPost account:
How often does RecurPost check an RSS feed for new posts?
RecurPost checks each connected RSS feed every 6 hours on a fixed daily cycle. A blog post published just after one fetch waits for the next before it reaches your content library, and the library’s schedule then places it in the next open slot. Roberta’s Geek Girls posts therefore appear on her IT accounts within hours of publication rather than minutes.
Can RecurPost post to more than one YouTube channel?
RecurPost connects the primary channel of the Google login that authorizes it. A second channel needs its own sign-in and counts as its own connected account against your plan limit. Roberta publishes to one channel, so YouTube uses one of her six accounts. A creator running three channels needs three connected accounts, not one.
Does posting a link on X cost extra in RecurPost?
RecurPost charges $0.20 for each X post that carries a link, drawn from a prepaid wallet on your account. Text-only X posts cost nothing. RecurPost reserves the fee before publishing and refunds it automatically if the post fails. Roberta posts gig links and blog links from two separate X accounts, and both draw on the same wallet.
Where does a one-time-use post go after it publishes?
A one-time-use post in RecurPost publishes once and then moves into a library named Expired Content instead of returning to the rotation. That behaviour is what keeps a dated gig announcement from resurfacing a month after the show. Posts in regular libraries work the opposite way and cycle back around on the schedule.