The Real Cost of a Bad Hire vs. a Nearshore Mismatch (And How to Avoid Both)

Most founders budget for a hire's salary. Few budget for what happens if the hire is wrong.

According to the Recruitment & Employment Confederation, a poor hire at mid-manager level on a £42,000 salary can end up costing a business more than £132,000 once training, lost productivity, and departmental disruption are factored in. That's more than three times the salary that first got board sign-off.

For a startup or scale-up, that isn't a rounding error. It's a chunk of runway. And it's exactly the number that makes "let's outsource this instead" feel like the safer option, right up until the outsourcing relationship goes wrong too.

The honest answer is that both paths carry risk. The difference is what that risk looks like, how fast it compounds, and how expensive it is to reverse. Here's how to actually compare them.

What a bad engineering hire costs

The REC figure isn't scare-mongering; it's additive, and each line item is easy to recognise:

Recruitment cost

The CIPD puts average cost-per-hire at £3,000–£5,000 for standard roles, rising to £5,000–£15,000 for senior or specialist positions once agency fees are included. For a senior engineer, expect the top of that range.

Ramp time

Research from Oxford Economics and Unum found it takes an average of 28 weeks for a new hire to reach full productivity. That's over half a year of partial output before you even find out whether the hire was right.

Legal and severance exposure

The Employment Rights Act 2025, rolling out through 2026, raises the stakes further: statutory sick pay now applies from day one, and the redundancy pay cap has risen to £751 a week, with maximum payouts up to £22,530. Letting a bad hire go is no longer just awkward, it's a defined cost on the balance sheet.

The invisible cost

This is the one that doesn't show up in any of the above, and it's usually the most damaging for a small team: a senior engineer quietly double-checking a struggling colleague's work, a sprint that slips because one person can't be trusted with the critical path, a founder spending management time on a performance conversation instead of the roadmap.

At a 200-person company, one underperforming mid-level hire is a nuisance. At a 15-person startup, it can stall an entire product line, because there's no bench strength to absorb it.

What a nearshore or outsourcing mismatch costs

This is where it's tempting to say "so outsource instead” but a bad outsourcing engagement has its own failure modes, and they deserve equally honest treatment:

Timezone and communication friction

A delivery team that's nominally "nearshore" but effectively unreachable during your working hours creates the same drag as a disengaged in-house hire, just with an extra layer of distance to diagnose it through.

Turnover on "your" team

Some providers rotate developers between clients without much warning, so the person who understood your codebase in month one isn't the person writing code in month four.

Unclear ownership and IP terms

Contracts that don't explicitly assign code and IP to you are a real risk, not a formality.

Vetting theatre

Plenty of providers claim to vet candidates and then send whoever's on the bench that week.

Where this genuinely differs from a bad permanent hire is the downside curve. A mismatched engagement can be flagged and swapped out within weeks, without notice periods, redundancy consultation, or Employment Rights Act exposure. The cost of getting it wrong is real, but it's bounded and reversible in a way a UK employment contract isn't.

A framework for choosing between them

Rather than treating this as outsourcing-versus-hiring in the abstract, the more useful question is: how reversible do I need this decision to be?

Situation	Better fit
Role is niche or the market rate has spiked (e.g. DevOps, platform engineering)	Augmentation: reduces mis-hire risk on a hard-to-assess specialism
Role is founding/culturally load-bearing and long-term	Permanent hire, but invest heavily in upfront vetting. This is where the REC's £132k risk is highest if you get it wrong
Need is experimental; new product line, MVP, unproven roadmap	Augmentation: keeps the decision reversible while the bet is unproven
You need 24/7 or follow-the-sun coverage	Augmentation: a UK-only hire can't cover this without an expensive on-call rota anyway

Put in pounds: a permanent mid-level hire that doesn't work out carries roughly £132,000 of exposure by the time you've accounted for recruitment, ramp time, and departure. A six-month augmented engagement with a clean exit clause caps your downside at whatever you'd have paid over those six months, with no severance, no redundancy consultation, and no eighteen-month tail of a CIPD or REC case study with your company's name on it.

The fix is the same either way

Whichever path you take, the underlying discipline doesn't change: rigorous vetting before day one, and a cheap way out if you got it wrong. The REC's own guidance on calculating the cost of a bad hire exists precisely because most businesses only do this maths after the fact.

If you're weighing up a permanent senior hire against bringing in vetted capacity to de-risk the decision, that's exactly the conversation we have with founders every week. Get in touch and we'll talk through what fits your stage.