Virtual Assistant Case Study: One Startup, Real Numbers

This virtual assistant case study for a startup begins at month 18: $15K/month in revenue, $24K/month in burn. One of the two founders was logging 30 hours a week on admin — calendar management, inbox triage, invoice follow-up, expense tracking.

Not strategic work. Not product. Not sales. The kind of tasks that can't be skipped but don't move a startup forward.

One offshore VA hire at $8/hour for 20 hours a week changed the math. This is what that hire looked like — a composite of two-person SaaS companies at 18 months post-launch, patterns drawn from founders who documented the results. Specific enough to be actionable.

---

At $24K/month burn, spending 30 hours on admin is a company-killing problem

The math here is not subtle.

A survey by Time Etc found that the average entrepreneur loses 16 hours a week to administrative tasks — email, scheduling, and operational busywork that someone else could handle. For this startup's co-founder, the number was worse: 30 hours. Nearly an entire second job, running parallel to product and sales.

A two-person startup at month 18 lives in a specific pressure zone. Revenue exists — $15K/month is real traction — but the gap between revenue and burn is still closing slowly. Every hour either builds toward profitability or it doesn't. There is no slack.

Thirty admin hours per week on a co-founder means 75% of one person's work week goes to tasks that aren't building the business.

Scheduling calls. Sorting the inbox. Tracking expenses. Following up on invoices. These tasks aren't optional — they're just not why you started the company.

The admin wasn't clustered into one block. It was threaded through every day, breaking focus and making deep work feel like something you had to carve out rather than something you had. You don't close enterprise deals in the thirty-minute windows between calendar conflicts and expense receipt requests.

---

Why we hired a VA before our first full-time employee

Most startup hiring advice is sequenced around roles: engineer, then sales, then ops. What it misses is execution debt — the admin that piles up on founders before any of those roles exist.

The case for a VA first isn't ideological. It's arithmetic.

Payroll accounts for 60–80% of a typical startup's burn rate. Adding a full-time local hire at this stage would have consumed most of the remaining runway before the hire was up to speed.

A junior ops or admin hire runs $52,000–$65,000 in base salary. Total compensation — payroll taxes, benefits, and equipment — reaches $65–70K per year for a US-based admin role. An offshore admin VA at $8/hour for 20 hours a week costs $640/month. That's $7,680/year.

The gap between those two numbers isn't a nuance. It's two months of runway.

The second argument was flexibility. A full-time hire is a commitment at a stage where the right role isn't fully defined. A VA engagement can start at 10 hours a week and grow. It can also be restructured without a severance conversation.

We ran the full VA vs. employee cost comparison before committing — factoring in taxes, benefits, and overhead. That exercise turned a vague idea into a hire date.

The next question was where to hire. Posting a job cold on a freelance platform means screening dozens of applications yourself — which is a new job on top of the job you're already doing. HireNewTalent.ai surfaces pre-vetted profiles instead: assessed for communication quality, reliability, and the specific skills you're hiring for. For founders with no HR bandwidth, that shortlist is the product.

---

The tasks that moved off the founder's plate in 60 days

Week one was a documentation sprint — before any task handoff.

We logged every recurring admin task and timed it. Twenty-two distinct tasks. Thirty-one hours per week total. Here's what moved first:

• Inbox triage and labeling: 3 hours/week
• Calendar scheduling across time zones: 4 hours/week
• Invoice follow-up and payment tracking: 3 hours/week
• Expense categorization and reporting: 2 hours/week
• Customer support ticket routing: 4 hours/week
• Social media scheduling from pre-approved content: 3 hours/week

That's 19 hours of repeatable, documentable work. The VA owned most of it by day 45.

C3Worx's 2026 analysis of Belay's client data finds that VAs return an average of 13.1 hours per week to executives, with email triage accounting for 4.2 hours and calendar management another 3.8. Those figures matched closely with what this founder recovered in the first 60 days — which suggests the pattern isn't unusual, just underdiscovered.

The handoff wasn't instant. Week one was documentation. Week two was Loom walkthroughs and supervised test runs. Week three, the VA was operating independently on three task categories. By day 60, roughly 18 hours were back in the founder's week.

The onboarding guide on this blog covers this ramp in detail, with templates for the documentation process. The six-week timeline it describes held for this hire. Week two always feels like evidence it isn't working. It isn't — that's just onboarding.

Not all of the recovered hours went immediately to revenue-generating work. Some went to sleep. That matters too.

---

Two offshore VAs cost less than one junior local hire — by $53,000 a year

By month four, the startup had added a second VA. Here's how the cost stack looked.

VA team at month 4:

• VA #1 (admin and ops, started month 1): $8/hour × 20 hrs/week = $640/month
• VA #2 (customer support, started month 3): $10/hour × 15 hrs/week = $600/month
• Monthly total: $1,240, or $14,880/year

Comparable local hire (junior ops/admin):

• Base salary: $55,000
• Payroll taxes: ~$5,000
• Benefits: ~$6,000
• Equipment and onboarding: ~$2,000
• First-year total: ~$68,000

That's a $53,000 gap. At $24K/month burn, that's more than two months of runway.

Philippine-based VAs typically cost $6–$12/hour for experienced admin and operations roles, compared to $3,000–$7,000 per month for a US-based equivalent. Offshore hiring saves 40–70% compared to domestic equivalents when you account for total compensation. The $8/hour figure here sits in the middle of that range — an experienced admin VA with strong English fluency and a documented track record.

HireNewTalent.ai profiles are vetted before they reach a shortlist — screened for communication quality, reliability signals, and role-relevant experience. For a two-person startup with no HR function, that pre-screening compressed the hiring decision from weeks to days. No 47-application pile to sort through.

If you're thinking about sequencing a second or third VA hire, the guide to building a VA team for startups covers how to structure multi-person VA teams at different growth stages.

---

At six months: 22 hours recovered, 34% more customers, $38K saved

At six months, here's what the data showed.

Time returned to the founder:

• Admin hours at baseline: 31/week
• Admin hours at month 6: 9/week
• Hours recovered: 22/week
• Of those 22 hours: 14 reallocated to sales and business development

Financial comparison:

• VA team cost, months 1–6: $7,440
• Comparable local hire cost, months 1–6 (prorated from $68K/year): ~$34,000
• Six-month savings: ~$26,560
• Projected year-one savings vs. local hire: ~$38,000

Output metrics:

• New customer acquisition: +34% in months 4–6 vs. months 1–3
• Average support response time: from 18 hours down to 4 hours
• Invoice collection time: from 14-day average down to 6 days

According to VA Masters' 2026 Industry Report, 78% of businesses see measurable productivity gains within 90 days of hiring a VA. For this startup, month three was the inflection point — the week scheduling fully moved off the founder's plate. The pattern held.

The customer acquisition improvement is the hardest to attribute cleanly. Other things changed in that period. But Gallup research, cited by Inc., found that CEOs who delegate effectively generate 33% more revenue than those who don't. Moving 14 hours per week from inbox management to direct sales outreach is a form of delegation. The correlation is not subtle.

---

What this virtual assistant case study taught us about startup hiring

Document before the hire, not during onboarding.

Writing SOPs during onboarding week is one week too late. The pre-hire documentation exercise forces you to notice which tasks are genuinely ambiguous and which just feel complicated. That distinction changes the job description, which changes who applies, which changes how week one goes. An hour of documentation before hiring saves three hours of rework after.

Start with one task category.

The first handoff covered six task types simultaneously. Too much surface area for week one. The cleaner approach: start with scheduling only. Run it for two weeks until it's tight. Then add one category at a time. This startup found its way to that approach by week five — but not before unnecessary back-and-forth that added friction it didn't need.

Set up a task board on day one.

Slack threads worked for about a week. Then tasks got buried in threads, priorities shifted without anyone noticing, and nobody had visibility into what was actually in progress. A simple Trello board with status columns solved it in fifteen minutes. Not setting it up from the start was a recoverable mistake that cost several hours of clarifying conversations.

For a comparison case — a seven-person service firm, different task mix, same delegation principles applied at a different stage — the offshore VA case study on this blog covers what 90 days looked like there. The specifics differ. The arc is the same.

---

Every virtual assistant case study for a startup is context-dependent. If your admin tasks require real-time judgment calls that shift daily, or your founders' time isn't genuinely blocked by admin work, this hire won't move the needle the same way. Same if you have an urgent technical bottleneck — that hire comes first.

What holds in most cases: the cost gap between offshore VA work and a local hire is real and durable at almost every startup stage. The onboarding friction is front-loaded and predictable. The hours you recover don't stay idle — they go toward the work that actually builds the business.

The hard part is making the first hire. Not because the decision is complicated. Because it's easy to keep waiting until you're less busy.

You won't be less busy. That's the problem you're solving.