Build a support team or outsource? What it really costs

Sooner or later most growing businesses ask the same question: should we build our own support team, or outsource customer support? The first answer often comes from comparing the wrong two numbers — a salary on one side, an outsourcing quote on the other.

Neither number tells you what support actually costs. Here's how to work out both properly, where each option hides costs, and how to decide which is cheaper for your business. If you're still working out whether your support needs to change at all, start with the signs your company has outgrown it.

Why a salary versus a quote is the wrong comparison

A salary is what you pay a person. An outsourcing quote is what you pay for a service, which usually bundles in cover for absence, management, tools and replacement staff. Put the two side by side and an in-house support team nearly always looks cheaper, because most of its costs never appear on a payslip.

The option that looks cheapest on paper is often the one with the most costs left off it.

What it really costs to build a support team

To compare fairly, add up everything a support hire costs you — not just their pay:

• Salary — the visible part, and the only part most comparisons include.
• Employer taxes and contributions — payroll taxes, pension or superannuation, and insurance. They vary by country, but they're never zero.
• Recruitment — job ads, agency fees, or your own hours screening and interviewing. Spread it over how long you expect the person to stay.
• Onboarding and ramp-up — the weeks a new agent is paid in full but not yet productive, plus the time colleagues spend training them.
• Tools — a helpdesk seat, chat or phone licences, a laptop, and any quality or knowledge base software.
• Management time — someone schedules, coaches, reviews quality and handles escalations. If that someone is you, it's still a cost; it's just paid in your time.
• Cover for absence — annual leave, public holidays and sick days all leave gaps that someone else has to fill.
• Replacement — when a support hire leaves, you pay for recruitment and ramp-up all over again.

None of these are unusual. They're just easy to leave off a spreadsheet — and together they make a support hire cost noticeably more than their salary.

The coverage question: why hours change everything

One full-time person covers one working week: roughly 40 of the 168 hours in a week. That's enough if your customers only need you during business hours, in one time zone.

The moment you need more, the arithmetic changes fast:

• Longer days or a second time zone mean a second person, or shifts that run into overtime.
• Weekend cover adds another rota to staff.
• Genuine 24/7 support needs about 168 ÷ 40 ≈ 4.2 full-time people for a single seat — before anyone takes leave.

This is where many plans to build a tech support team quietly break. Hiring one person doesn't buy you coverage. It buys you one person's working hours.

How outsourced customer support is priced

Outsourcing providers usually charge in one of a few ways:

• Per agent, per month — a dedicated person, or a share of one, working on your account. Predictable, and the closest thing to having your own team.
• Per ticket or contact — you pay for the volume handled. Flexible, but costs rise with volume, and it can reward speed over actually solving problems.
• Per hour — common for overflow and after-hours cover.
• Setup or onboarding — the time a provider spends learning your product, tools and processes before going live.

The useful question isn't which model sounds cheapest. It's what's included: cover for leave, management and quality checks, tools, and a replacement if someone leaves.

The costs of outsourcing people forget

Outsourcing has hidden costs too, and a fair comparison counts them:

• Knowledge transfer — your team's time documenting the product and answering the provider's questions while they get up to speed.
• Oversight — someone on your side still needs to review quality and own the relationship.
• Less direct control — changes to process or tone of voice go through another team.
• Product feedback — what support learns has to cross a company boundary, and gets lost unless you build a route for it.
• Contract terms — notice periods and minimum commitments limit how quickly you can change course.

None of these rule outsourcing out. They're the mirror image of the in-house costs, and a good provider should raise them before you have to ask.

So is it cheaper to build a support team or outsource?

It depends — but on specific, knowable things rather than gut feel:

• Building in-house tends to win when volume is steady, support needs deep product knowledge, business hours in one time zone are enough, and someone has real time to manage the team.
• Outsourcing tends to win when you need longer hours or several time zones, volume is uneven or seasonal, you'd otherwise be hiring your first support manager, or the people who would run support are already stretched.

Plenty of businesses land in between: a small in-house core that owns the product knowledge, escalations and key customer relationships, with outsourced cover for routine questions, extended hours or overflow. It's the same principle as pairing AI with people — each part does the work it's best at — provided the handoff between them is designed properly.

How to compare the two properly

1. Work out your fully loaded cost per support agent — every line from the list above, not just salary.
2. Decide which hours genuinely need covering, and turn that into the number of people it takes.
3. Get outsourcing quotes for the same hours and volume, and ask exactly what's included.
4. Compare cost per resolved contact, not cost per person. You're buying problems solved, not time spent — a cheaper option that resolves less costs more per result.
5. Add the cost of switching to whichever option means change.

The bottom line

Building a support team isn't automatically cheaper, and neither is outsourcing. The honest answer comes from comparing fully loaded costs, the hours you actually need covered, and what each option resolves — not a salary against a quote. Do that comparison once, carefully, and the decision usually makes itself.