Ivan Jimenez publishes for two businesses that share an owner and nothing else. DIGITAL IVAN sells websites to business owners. AdmitMatch.ai sells college admissions guidance to parents. Both run out of one RecurPost account, which forced Ivan to answer the question most multi-brand operators hit in their first week: does each brand need its own content library?
Ivan’s answer was yes. That answer is not automatic, and the reason has nothing to do with how many brands you run. RecurPost publishes 15 customer setups in its case studies, and Ivan’s is the one that settles the library question.
more consistent engagement across his channels, reported by Ivan Jimenez
more reach per post, which Ivan attributes to proven posts resurfacing
brands with no audience overlap, running from one RecurPost account
Ivan Jimenez Runs Two Unrelated Brands From One Account
Two brands run by one person, no social media manager
Fast business websites, minimal web design, organic visibility and paid search
A real college counsellor for parents at $49 a month, answers inside 24 hours
Ivan Jimenez runs both businesses on his own. DIGITAL IVAN builds fast business websites and handles minimal web design, organic visibility management and paid search for the owners who buy them. AdmitMatch.ai gives parents access to a real college counsellor for $49 a month, with answers inside 24 hours.
Ivan’s two audiences do not touch. A business owner shopping for a website has no reason to follow an account explaining how to build a college list. Ivan describes DIGITAL IVAN’s purpose as helping overlooked experts get noticed, and he has never hired a social media manager for either brand.
Publishing Stopped Whenever Delivery Work Took Over
Ivan published in bursts. A week of client delivery meant a week of silence across both brands.
Manual publishing ties output to available hours, and for a one-person business those hours go to the work that gets invoiced. A five-week website build takes every hour Ivan has. Both brands go quiet for five weeks, and the momentum built before the project starts over afterwards.
“Before RecurPost, visibility was inconsistent. I was stuck in the manual content hamster wheel, and it wasn’t scalable.” — Ivan Jimenez
Ivan also found that his strongest posts stopped earning shortly after they left the feed. Nothing brought them back on its own. A post that landed well in March did nothing in April, because the only way to put it in front of anyone again was to write it again.
What Decides Whether Two Brands Need Two Content Libraries
RecurPost attaches one publishing schedule to one content library. The library holds the posts. The schedule decides when they go out and to which accounts. Add a second library aimed at the same accounts and RecurPost now runs two schedules asking for the same posting times.
RecurPost’s one-schedule-per-library binding makes the destination account set the deciding variable, not the brand count.
RecurPost runs two libraries cleanly when each one points at its own accounts. Neither library waits on the other, because neither asks for a slot the other wants. Where both content streams publish to the same accounts, a single library with rotating topics puts more posts out the door rather than fewer.
Ivan’s brands have no account overlap, because they have no audience overlap. DIGITAL IVAN and AdmitMatch.ai each get their own library and their own schedule, and neither one throttles the other. Ivan can pause the AdmitMatch.ai library through an admissions off-season without touching what DIGITAL IVAN publishes.
A freelancer posting client case studies and studio news to the same three accounts sits on the other side of that rule. Two libraries there queue against each other for the same three time slots, and the operator sees fewer posts publish than planned. One library holding both topics publishes everything that was scheduled. RecurPost documents how the two connect on its content libraries and posting schedules page.
How a Recurring Library Republishes a Post
RecurPost republishes posts from an evergreen recurring library at the frequency and times you set, and the library keeps running until you delete it.
RecurPost recommends at least 20 evergreen posts in a library before you switch recurrence on. A smaller library cycles back around quickly enough that followers notice the repeat. RecurPost’s scheduler runs once a day at 08:00 UTC and queues the next day’s posts from whatever sits in the library at that moment.
RecurPost rotates caption variations so the same post does not arrive in identical words. RecurPost rotates the first comment underneath it. RecurPost also drops a post out of the loop on an expiration date you set. Captions and call-to-action links across a whole library change in one action, which matters the day a landing page URL moves.
Recycling does not suit everything, and RecurPost says so directly. News, product launches, dated promotions and reactive posts fall outside this workflow, because each one loses relevance the moment it republishes.
Ivan’s AdmitMatch.ai explainers about building a college list read the same in November and in March, so they belong in a recurring library. A DIGITAL IVAN launch announcement does not. It stops being true the week after it ships. Ivan used RecurPost’s per-platform analytics to decide which posts earned a place in the library in the first place. Full mechanics sit on the evergreen recurring libraries page.
What Ivan Reports, and What the Numbers Do and Do Not Prove
Ivan reports about 40% more consistent engagement across his channels since the libraries went live. He reports three to five times more reach per post, which he attributes to proven posts resurfacing instead of publishing once and disappearing.
RecurPost does not report a metric called engagement consistency. Ivan’s 40% is his own measure of how steady his output and his replies became, not a figure RecurPost’s analytics produced. Read it as an operator’s account of his own change rather than a product measurement.
“RecurPost isn’t just a scheduler, it’s visibility insurance.” — Ivan Jimenez
Ivan’s third result carries the least precision and the most weight. Both brands kept publishing through a product launch, through travel and through time away from the desk. The catalogue ran while Ivan did not.
Ivan makes one more point about the automation itself. He never hired a social media manager. He wrote the catalogue in his own voice and handed the timing to RecurPost, which he says kept the voice intact rather than diluting it.
“Once I committed to visibility systems and stopped trying to go viral every week, everything shifted.” — Ivan Jimenez
Where This Setup Fits, and Where It Does Not
RecurPost’s two-library setup fits an operator running two or more brands whose destination accounts do not overlap. Ivan is the clean case: two brands, two audiences, no shared account.
Ivan’s libraries also work because he had the material to fill them. You need roughly 20 posts per brand that stay true after their publish date, because the catalogue does the work here and the schedule only keeps it moving.
Operators whose publishing keeps losing to delivery work get the most out of it. Ivan’s five-week builds are the reason his libraries exist at all.
Founders who want every post written fresh for the week’s news will find little here. A recurring library pays back a back catalogue, and there is no back catalogue when everything gets written the morning it goes out.
RecurPost’s two-library setup breaks down when two brands publish to the same accounts. A second library then queues against the first for the same slots, and fewer posts publish than planned. One library with rotating topics is the fix.
RecurPost’s own guidance puts dated promotions and launches outside this workflow, so an operator whose content is mostly campaign announcements should schedule those directly instead of recycling them.
Ivan uses one part of RecurPost social media management software. The rest of the product covers composing, collaboration, the social inbox and per-platform analytics.
Try RecurPost
RecurPost’s Personal plan covers 5 social accounts for $25 a month, which is where a two-brand operation like Ivan’s usually lands.
5 social accounts and 20 daily posts per account. Extra social accounts cost $4 a month each.
20 social accounts and 80 daily posts per account.
One block adds 10 daily posting slots per account, for when two libraries need more room than the plan’s slots allow.
See RecurPost pricing for every add-on with its unit price, or start a free trial for 14 days with no credit card.
DIGITAL IVAN Case Study FAQs
Common questions about running two brands from one RecurPost account:
Can one RecurPost schedule publish from two content libraries at the same time?
RecurPost attaches one publishing schedule to one content library. A schedule cannot pull from two libraries, so every library you create needs its own schedule and its own posting times. Two libraries pointed at the same accounts therefore compete for the same slots.
Does a seasonal library need its own schedule, or does it share one with a recurring library?
A RecurPost seasonal library runs on its own date window. RecurPost publishes from it only between the start and end dates you set, then pauses the library until that period comes round again. A recurring library keeps running the whole time, so the two never share a cadence and adding a seasonal campaign does not disturb an evergreen setup.
What happens to a post in a recurring library once it stops being true?
RecurPost takes a post out of the loop through an expiration date. Set the date and the post stops republishing without you deleting it. A post that should only ever go out once belongs in a one-time-use library instead, where RecurPost publishes it and then moves it to the Expired Content library rather than cycling it again.
Does RecurPost charge extra to add more posting times per day?
RecurPost sells recurring time slots as a monthly add-on separate from the plan. One block costs $20 a month and adds 10 daily posting slots per social account, on top of the slots the plan already includes. The Personal plan includes 20 daily posts per account and the Agency plan includes 80, so most two-brand operations never need the add-on.