Share
Growth is supposed to feel like winning. Instead it feels like drowning in slightly nicer water. Every new customer adds workflows, coordination, support tickets, and follow-ups, and the operational load compounds faster than the revenue does. At some point the honest answer is not "one more hire", it is a whole layer: an 18-person offshore operations team. Staff those 18 seats in the US and the payroll math crushes your margins before the layer ever pays for itself. This article is the blueprint for the offshore version: the exact 18-role structure, what each seat owns, what stays in-house, and the year-one cost model that lands at roughly $913K to $1.15M in savings. One thing before we start: this is a model, not a case study. No company is being described here. Every number is labeled so you can check it yourself.
Why an offshore operations team becomes the question at all
Here is the pattern, whether the business is a technology company, a field services operator, an on-demand delivery platform, or some mix of all three. Revenue grows 40%. Operational workload grows more than that, because operations scale with activity, not with dollars.
- Every new customer means onboarding steps, account setup, scheduling, and status updates.
- Every new market or service line means more dispatch coordination, more vendor follow-up, more exceptions to chase.
- Every 100 new users means a predictable stack of support tickets, refund requests, and "where is my order" messages.
Multi-sector companies feel this hardest because each sector has its own workflows, and the coordination between them is itself a workload. The tech side generates tickets, the field side generates scheduling chaos, the delivery side generates real-time exceptions. Somebody has to sit in the middle of all of it.
The founder or the ops lead absorbs the overflow for a while. Then quality slips, response times stretch, and the team that should be building the product is answering tickets. The fix is a real operations layer. The problem is what that layer costs at US rates, which we will get to line by line.
If you want the single-seat version of this argument first, start with how to hire a remote virtual assistant. This article is that logic at 18x scale.
The team design: 12 operations, 6 support
An 18-seat operations layer sounds complicated. The design is not. Across service businesses the workload splits into two lanes, and the ratio is remarkably consistent: about two thirds operational coordination, one third customer-facing support. So the blueprint is:
- 12 Operations Assistants running the internal machine
- 6 Customer Support Specialists running the external conversations
Why this ratio and not 9/9? Because customer-facing volume is the visible workload, but the invisible workload behind it is bigger. Every support conversation that ends with "let me check on that" creates an internal task: reschedule the technician, update the order, chase the vendor, correct the record. If you under-staff the operations lane, your support team makes promises the back office cannot keep, and response quality collapses from the inside.
The same two-lane shape shows up at smaller scale in the offshore back office team blueprint. This is that structure, sized for a company where operations is a department, not a desk.
What the 12 Operations Assistants own every day
The Operations Assistant lane covers five workstreams. In an 18-seat build you would typically assign 2 to 3 people per workstream rather than making everyone a generalist:
- Operational coordination. Scheduling, dispatch support, order tracking, handoffs between the tech, field, and delivery sides. The connective tissue.
- Administrative workflows. Data entry with a purpose: CRM updates, records management, document prep, invoice processing.
- Process management. Owning checklists and SOPs, flagging when a process breaks, keeping the runbook current instead of letting it rot in a drive folder.
- Internal team support. Meeting prep, follow-up tracking, chasing open items so managers do not have to, onboarding logistics for new staff.
- Daily business operations. The recurring daily and weekly cadence: reports pulled, dashboards updated, exceptions escalated before 9am instead of discovered at 5pm.
What stays in-house: approvals, anything contractual, pricing decisions, vendor negotiations, hiring and firing, and final sign-off on any exception that costs money. The Operations Assistants prepare the decision. Your managers make it. That boundary is what makes the model safe, and it is non-negotiable.
What the 6 Customer Support Specialists own every day
The support lane is the voice of the company for routine volume:
- Customer inquiries. First response on email, chat, and ticket queues. Status questions, account questions, how-do-I questions.
- Request handling. Reschedules, address changes, order modifications, refund requests up to a pre-approved threshold.
- Communication workflows. Proactive updates: appointment confirmations, delay notifications, follow-up after service, review requests.
- Service delivery support. The coordination between a customer promise and the ops lane that fulfills it, so nothing dies in a handoff.
What stays in-house: escalations involving angry key accounts, anything legal or contractual, refunds above threshold, and public-facing incidents. A good support Specialist's most valuable skill is knowing exactly when to route up, and that routing rule gets written before day one.
Six people at this lane, covering staggered shifts, gets most companies to same-hour first response across a wide window. Compare that to what your current response time looks like on a Tuesday when two people are out.
The year-one math, labeled as a cost model
This is a cost model, not a client result. The assumptions sit on the table so you can swap in your own numbers.
US side. A mid-range operations or support hire runs $55,000 to $65,000 in salary. Salary is not your cost. Per the Bureau of Labor Statistics Employer Costs for Employee Compensation data, benefits alone run roughly 30% of total compensation for private-industry workers, so a 1.30 burden multiplier for payroll taxes, benefits, equipment, and ramp is conservative. That gives $71,500 to $84,500 true cost per seat.
Jarvis side. Full-time Jarvis Specialists at packages from $1,733/month. Twelve months, matching and vetting and replacement included, no burden multiplier because there is nothing to burden.
| Line item | 18 US hires | 18 full-time Jarvis Specialists |
|---|---|---|
| Base cost | $990K to $1.17M in salaries | $1,733/month × 18 seats |
| Payroll tax + benefits + equipment + ramp | ~30% burden added | Included |
| Recruiting + replacement risk | On you, per seat | Included (our process covers rematch) |
| Year-one total | $1.287M to $1.521M | $374,328 |
| Year-one gap | ~$913K to $1.147M |
Call it $900K+ in year one, at the conservative end. The model deliberately leaves out things that would widen the gap: recruiter fees at 18-seat volume, office space if any seats are on-site, the management time of running 18 US hiring processes, and the cost of the 2 to 3 bad hires that statistically happen in any 18-person hiring run.
The savings scale linearly, and you can verify that
The per-seat arithmetic here is the same math we walked line by line in offshore team cost savings for a 3-person team. Multiply it out and the pattern is boring, which is the point:
| Team size | US year-one cost | Jarvis year-one cost | Year-one gap |
|---|---|---|---|
| 3 seats | $214K to $253K | $62,388 | ~$152K to $191K |
| 6 seats | $429K to $507K | $124,776 | ~$304K to $382K |
| 12 seats | $858K to $1.014M | $249,552 | ~$608K to $764K |
| 18 seats | $1.287M to $1.521M | $374,328 | ~$913K to $1.147M |
No step in that table uses different assumptions. Same salary band, same burden rate, same package price. The 18-seat number looks dramatic only because the per-seat gap is large and 18 is a lot of seats.
Want to pressure-test this model against your own org chart? Book a free automation and staffing audit. We will map your actual operational workload to a seat count, show you which seats are offshore-ready today, and hand you the sequencing plan whether you work with Jarvis or not. Grab a slot here.
The result this blueprint is built to produce
Run the model forward twelve months and the intended end state looks like this:
- An operations layer that costs $374,328 instead of $1.3M+, which means the layer pays for itself out of margin instead of eating it.
- Founders and senior staff out of the queue. The proof that the mechanism works at n=1 is real: in our HeadTop Performance case study, one founder got 5 to 10 hours a week back with a single Specialist. The 18-seat model is the same mechanism multiplied, not a different claim.
- Numbers instead of vibes. Every Jarvis Specialist reports daily in numbers: tickets closed, orders processed, exceptions escalated. At 18 seats that discipline is the difference between a team and a payroll line.
- Automation compounding underneath. Jarvis Specialists are trained to build automation, not just execute tasks: GoHighLevel pipelines for lead and customer follow-up, ticket routing rules, reporting dashboards that update themselves. Headcount that reduces future headcount.
That last point matters for the growth math too. An operations layer that absorbs volume without linear hiring is how you scale without hiring employees every time revenue steps up.
The contrarian part: 18 is an end state, not a starting point
Most offshore providers would happily sign you up for 18 seats on day one. We think that is how the model fails. The failure mode of offshore teams is almost never geography or talent. It is speed. Eighteen people starting into undocumented chaos produces documented chaos, at scale.
The blueprint deploys in waves:
- 1. Wave 1 (seats 1 to 3): the highest-volume, most repeatable workflows. Lock the SOPs before anyone starts. If you have never written one, start with how to write SOPs for a virtual assistant.
- 2. Wave 2 (seats 4 to 6): support lane goes live once the ops lane can keep its promises.
- 3. Waves 3 to 6 (seats 7 to 18): add 2 to 3 seats per wave, each wave onboarding onto SOPs the previous wave already stress-tested.
Each wave takes weeks, not quarters, because J-Academy handles tool and AI training before a Specialist ever touches your business, and the SOP-first onboarding means day one is execution, not discovery. US-based oversight sits on top of the whole build, and the replacement guarantee means a mis-matched seat gets rematched instead of restarted. Waves also cap your blast radius: if wave 2 exposes a broken process, you fix it with 6 people, not 18.
Frequently asked questions
How much does an 18-person offshore operations team cost per year?
With full-time Jarvis Specialists at packages from $1,733/month, 18 seats run $374,328 per year, all-in. The comparable US build at $55K to $65K salaries with a standard 30% burden runs $1.287M to $1.521M, a gap of roughly $913K to $1.147M. Those are model numbers with the assumptions stated above, not a client claim.
What roles should an offshore operations team include?
For most multi-sector service companies, roughly two thirds Operations Assistants (coordination, administrative workflows, process management, internal support, daily operations) and one third Customer Support Specialists (inquiries, requests, communication workflows, service delivery support). Approvals, escalations, and anything contractual stay with your in-house managers.
How long does it take to build an offshore operations team of 18?
Deployed in waves of 2 to 3 seats with SOPs locked per wave, most companies can reach 18 seats in a few quarters. Trying to launch all 18 at once is the most common failure mode: speed breaks offshore teams, not geography.
Is an offshore operations team right for a smaller company?
Yes, because the per-seat math is identical at 3 seats or 18. The 3-seat version of this exact model saves roughly $152K to $191K in year one. Start with the seats drowning your team today and scale the structure as volume grows.
Who manages an offshore operations team day to day?
Your managers own decisions, approvals, and priorities. Jarvis provides US-based oversight, daily reporting in numbers from every Specialist, and a replacement guarantee if a seat is not working. The management load is review and direction, not supervision.
Can offshore Specialists work inside our existing tools?
Yes. Jarvis Specialists train through J-Academy on the common stacks before placement and are trained to build automation inside them: GoHighLevel pipelines, ticket routing, reporting dashboards, CRM hygiene automations. The goal is a team that removes work, not one that just absorbs it.
Run your own numbers before you sign anything
You do not need to trust this article. Take your real seat count, your real salary band, the BLS burden rate, and $1,733 a month, and run the table yourself. If the gap is six or seven figures, the question is not whether to build the layer offshore, it is what sequence to build it in. Book a free 15-minute call and we will map your first wave with you!