Share
You built the business, and now the business runs on your hours. Report-outs, onboarding, invoices, vendor emails. None of it grows the company, and all of it lands on you. This virtual assistant case study shows what happened when one founder, Sean O'Brien of HeadTop Performance, stopped absorbing that work and handed seven recurring workstreams to a single Jarvis Specialist. The result: 5-10 hours a week back, redirected to client development and growth. Below is the full breakdown, in the order it actually happened: the challenge, exactly what got delegated, the result, and why the pattern works so you can copy it.
Why This Virtual Assistant Case Study Is Worth Your Time
Most VA case studies are useless. They lead with a revenue number you can't verify ("$2M added in 6 months!") and skip the only part you can actually use: the task list. What got delegated, in what order, and what the founder did with the time.
Here is a contrarian take most VA companies won't say out loud: a virtual assistant does not grow your revenue. You do. What a good Specialist does is buy back the hours you were burning on admin so you can do the two things only a founder can do, sell and build. If a case study claims the VA "generated" the growth, be skeptical.
So this one sticks to what Sean reported himself, through our testimonial form, in his own words. One founder. One Specialist. Seven workstreams. 5-10 hours a week returned. No inflated dollar claims, and where we do math on his time later in this article, we label it as illustrative math, not client-reported results.
If you want more examples in this format after reading, the full library is on our case studies page. But start with this one, because the pattern here is the one most service-business founders need first.
The Challenge: A Founder Still Doing Everything
Sean O'Brien runs HeadTop Performance. Like most founders of client-service businesses, he hit the stage where the company had real clients, real events, real vendors, and one bottleneck: him.
Monthly report-outs sat on his plate. Client onboarding sat on his plate. Client events, admin, chasing third-party vendors, all of it routed through the founder. Not because he lacked a team mindset. Because that is the default state of every owner-operated business. Work flows to the person who cares most, and nobody cares more than the founder.
In his own words:
"As a founder, I realized I was still trying to do everything within the business. It was likely taking away 5-10 hrs a week from me that were invaluable to be deployed to client-facing times or client development and growth work."
Notice what he calls those hours: invaluable. Not because the tasks were hard. Because of what the hours should have been doing instead, client-facing work and growth. That is the real cost of founder admin. It is not the task, it is the trade.
If that paragraph reads like your calendar, the problem is not discipline or time management. It is that recurring operational work has no other place to land. The fix is to build that place, which is exactly what Sean did.
What His Jarvis Specialist Handles Now
This is the part most case studies blur, and it is the part worth stealing. Sean's Jarvis Specialist now runs seven recurring workstreams:
- Monthly newsletter
- Weekly client preparation
- Weekly client follow-ups and check-in reminders
- Invoice follow-ups and build-outs
- Client onboarding and communications
- Third-party vendor coordination
- Onsite event scheduling setup
Look at the shape of that list. Nothing on it is a one-off project. Every item is a loop: it happens weekly or monthly, it follows a repeatable process, and it used to interrupt the founder on a schedule. That is what makes it delegable. One Specialist, one owner for all seven loops.
Look also at what the list touches: client communication, money (invoices), vendors, events. This is not "inbox cleanup." These are trust-heavy workstreams that founders usually insist on keeping, and they run fine without him because they were handed off as owned processes, not tossed over the wall as favors. If you are wondering what else falls in the delegable category, we keep a running breakdown in what virtual assistants can actually do and a full list of roles we source.
Seven workstreams, off his plate, run by one person. That is the whole mechanism.
The Result: 5-10 Hours a Week Back, Every Week
The headline number in this virtual assistant case study is simple: 5-10 hours a week returned to the founder, every week. Sean redirected that time to the two things only he can do, client development and growth work.
Now the math. To be clear, this is illustrative math, not a client-reported dollar figure. If you value founder time at a conservative $200 an hour, then 10 hours a week is $2,000 a week, roughly $8,000 a month of founder capacity moved from admin to growth. Even at the bottom of the range, 5 hours at $200, that is $4,000 a month of reallocated attention. Run the same numbers at your own hourly value; the point survives any reasonable rate.
And that math undercounts, because hours are not fungible. An hour spent chasing a vendor is not just a lost hour, it is a context switch that bleeds focus from the sales call after it. Harvard Business Review has written for years about why leaders systematically fail to delegate work that others should own. The pattern Sean broke is the most common one: competence becomes a trap, and the founder stays the default owner of everything he happens to be able to do.
Steal the structure before you book anything Sean's seven workstreams are a template. Open our use cases library, list every task in your business that repeats weekly or monthly, and mark the ones that do not require you personally. That list is your version of this case study, and it usually takes 15 minutes to write.
Why This Works: The Pattern Behind the Result
Three things made this outcome boring and repeatable instead of lucky.
1. He delegated loops, not chores. Every item on Sean's list recurs. Recurring work compounds: hand it off once, get the hours back every single week after. One-off tasks save you an afternoon. Workstreams change your calendar permanently.
2. One Specialist owns the whole system. Seven workstreams went to one person, not seven gig workers. That matters because the workstreams touch each other: onboarding feeds client communications, client prep feeds follow-ups, invoices feed vendor coordination. A single owner sees the whole picture and catches what falls between the lanes.
3. The handoff was a process, not a dump. The fear every founder has here is losing control of client-facing work. That fear is legitimate when delegation means "forward the email and hope." It goes away when each workstream is handed off with a defined process and a feedback loop, which is how our process is built and why we train every Specialist before they touch your business. If control is your sticking point, read how to delegate without losing control before you hire anyone, including us.
Sean's advice to founders still on the fence covers this exact fear:
"You already know it, you're spending way too much time on daily/weekly tasks that should be handled by someone else. It is not the headache you think it is to integrate someone to take those for you, and you are going to feel so much better and have so much more impact on your business and in your personal life when you get those things off your plate."
Read that first line again. You already know it. The bottleneck is rarely information. It is the founder giving themselves permission to let go of work they are competent at but should not be doing.
What Most Founders Get Wrong When They Copy a Case Study
Two failure modes show up constantly when founders try to replicate a result like this.
Failure mode one: delegating randomly. The founder hires help, then feeds them whatever task is annoying that day. No recurring workstreams, no ownership, no compounding. Three months later they conclude "a VA didn't work for me." The assistant never had a system to run, so there was no system to improve. The fix is Sean's structure: pick workstreams that repeat, hand over the whole loop, and let one person own it end to end.
Failure mode two: waiting until the process is perfect. Founders tell themselves they will delegate "once I document everything." They never do, because documentation is exactly the kind of non-urgent work that loses to client fires every week. Sean did not wait for a perfect ops manual. The documentation gets built during the handoff, with the Specialist doing the writing. Your job is to talk through the workstream once, not to become a technical writer first.
There is a third, quieter mistake: benchmarking against the wrong number. Founders compare a Specialist's cost against "what admin work is worth" instead of against what their own reclaimed hours produce. Sean's hours went to client development and growth. That is the correct comparison, and it is why the investment page frames packages against founder time, not task time.
How to Run the Same Play in Your Business
You do not need a special business model to replicate this virtual assistant success story. You need the same three moves:
- 1. List your loops. Every task that recurs weekly or monthly. Newsletter, client prep, follow-ups, invoicing, onboarding, vendor chasing, scheduling. If Sean's seven look familiar, start with those.
- 2. Mark what does not require you. Be honest. "I'm faster at it" is not the same as "it requires me." Most founder admin fails that test.
- 3. Hand the loops to one owner. Not five freelancers. One trained Specialist who runs the system and reports on it, matched to your business through our process.
Jarvis packages start from $1,733/month, and every match comes with training and a structured handoff, so you are not onboarding a stranger from a job board and hoping. The founders this works best for are the ones like Sean: real clients, real recurring ops, and a calendar that proves the founder is still the default owner of everything.
Frequently Asked Questions
What does a virtual assistant case study actually prove?
It proves a pattern, not a promise. This one shows that seven recurring, client-facing workstreams can be run by one trained Specialist, returning 5-10 founder hours a week. Your numbers will differ, but the mechanism, delegating recurring loops to a single owner, transfers to almost any client-service business.
Can one virtual assistant really handle newsletters, invoicing, and vendor coordination at the same time?
Yes, when they are handed off as owned processes. Sean's Specialist runs seven workstreams because each one is a defined loop with a cadence, not a pile of random requests. The mix of communication, admin, and coordination work is normal for one full-scope Specialist.
How long does it take to hand off this many workstreams?
Hand them off in sequence, not all at once. Start with the loop that costs you the most hours, stabilize it, then add the next. Jarvis structures this transition deliberately: every Specialist is trained first, then integrated workstream by workstream with check-ins, so nothing client-facing drops during the switch.
How much does a virtual assistant like this cost?
Jarvis packages start from $1,733/month, with the Specialist trained and matched to your business before day one. Compare that against the founder hours you get back, not against the admin tasks themselves. Full details are on the investment page.
What should I delegate first?
The recurring task that interrupts you most often, not the one that is easiest to explain. Weekly loops beat one-off projects because the time savings repeat. For most service businesses that means client follow-ups, scheduling, invoicing, or onboarding, four of the seven items on Sean's list.
Get Your Own 5-10 Hours Back
Sean's words, not ours: you already know you're spending too much time on tasks someone else should handle. The only question left is which seven workstreams come off your plate first. Book a free 15-minute call, bring your task list, and we will map it against what a Jarvis Specialist can own in your business.