The Real Cost of a Bad Hire in 2026 (and How Much of It Traces Back to AI)

Agencies have gotten reasonably good at pricing the obvious costs of a bad hire — the placement-fee refund, the re-run search, the client relationship damage. What's less priced in is a newer contributor to that number: a hire who got through the interview on answers that weren't entirely their own.

What "£180K" is actually made of

The commonly cited figure — roughly £180K lost per agency, per year, to bad hires — isn't one line item. It's the sum of several:

• The direct refund or re-placement cost owed to the client under most contingency and retained agreements
• The sunk recruiter time across sourcing, screening, and multiple interview rounds that produced a hire who didn't work out
• The client relationship cost — a bad placement is exactly the kind of thing that makes a client quietly start talking to a competing agency
• The re-run cost of doing the entire search again, usually under more time pressure the second time

Most of this was already true before AI-assisted interviewing existed. What's changed is one of the inputs.

The AI-assisted layer on top of it

With roughly 1 in 3 interviews now including some form of AI-assisted answer, a meaningful share of "bad fit" hires aren't actually fit problems — they're screening problems. A candidate who leaned on a stealth copilot to sound more technically fluent than they actually are doesn't just risk underperforming; they were never accurately screened in the first place, which means every downstream cost above traces back to an interview that should have been flagged and wasn't.

Why this is easy to miss after the fact

A bad hire rarely gets a clean postmortem that traces back to "the interview answers were suspiciously polished." It gets chalked up to culture fit, changed priorities, or bad luck — because without evidence from the actual interview, there's nothing to point to. This is exactly why evidence matters more than instinct here: a flag tied to the specific line in the transcript that triggered it is something a hiring manager can actually act on in the moment, not a vague unease that only makes sense in hindsight.

The threshold that actually matters

Not every polished answer means the same thing. Good preparation and reading from a live copilot can sound alike in the moment, which is why a flag should prompt a follow-up question, not a rejection. The follow-up is where the difference shows: a well-prepared candidate can go a layer deeper, while someone reading answers usually can't. Catching that before the offer is the difference between an awkward interview and that £180K bad-hire cost.

Pricing the fix against the cost

Catching one bad hire before an offer goes out is worth roughly what the average bad hire already costs. That's the whole case for vetting candidates properly, right down to the interview, before anyone gets near an offer.

That's how we hire for startups. Every candidate is checked before you meet them: ID and right to work, employment history, references through work email, and a live interview read by our anti-cheat, with a follow-up on anything that doesn't add up. A flag is a prompt for a question, never a verdict. Book a call, or if you already have candidates, we'll check them.