Every founder who has made a bad hire remembers it. Not in an abstract, it-did-not-work-out way, but viscerally. The specific moment they knew. The conversation that confirmed it. The months of hoping it would improve before they finally accepted that it would not.
What most founders do not remember, because they never calculated it, is what the whole episode actually cost. The salary figure sits in the accounts. The real cost does not appear anywhere.
I started thinking about this more precisely after I had seen the same pattern unfold in enough businesses to notice what it actually does to a company. The headline number, the one people quote when the conversation about mis-hires comes up, is roughly one to two times the annual salary of the role. That is the figure the HR consultancies use. It accounts for recruitment fees, onboarding time, management overhead and the cost of doing it all again.
It is accurate as far as it goes. It does not go nearly far enough.
The costs that do not show up in the calculation
The most expensive thing a bad hire produces is not the salary. It is the distraction.
A business running at growth stage has a finite amount of cognitive bandwidth. Every week spent managing a performance issue, wondering whether to have a difficult conversation, hoping the next month will be better, or preparing for the conversation you have been avoiding is a week spent not doing something else. That something else has a value. It is just invisible in the accounts.
For a founder, the arithmetic is particularly brutal. If the founder spends ten hours a week for six months managing a situation that should not exist, that is roughly 260 hours. Put a number on an hour of a founder's time, not the hourly equivalent of their salary but the value of what they could be doing with those hours, and the number is significant. That calculation almost never appears in any mis-hire cost analysis.
Then there is the team effect. A bad hire in a senior or mid-senior role does not underperform in isolation. Good people, the ones who always have options, quietly notice when standards fall. They notice when accountability is uneven. They notice when someone is being managed around rather than managed out. Some of them start updating their CVs. Some of them simply reduce the discretionary effort they were previously putting in, because the implicit contract of "high standards, high reward" no longer feels operative.
This is not dramatic. It is gradual. The attrition and disengagement that follows a poorly managed bad hire often costs the business more than the hire itself.
Why it takes so long
There is a pattern in how founders handle mis-hires that almost always extends the timeline beyond what it should be. It is not stupidity or weakness. It is something more specific: the human reluctance to accept that a decision you made was wrong.
Founders who are decisive, confident and commercially sharp frequently find it genuinely difficult to conclude, six weeks into a hire, that they have made a mistake. The reasoning sounds like this: they need more time to settle in. It is harder than we expected. They were great in the interview. I must be missing something.
By month three, the reasoning shifts: we have invested too much to write this off now. By month six: if I move on this now I will lose another three months recruiting. By month nine: we are nearly at the year mark, maybe they will turn a corner.
The turning corner almost never comes. And each month of hoping costs more than the month before it, because the business is growing and the opportunity cost of carrying a subperforming senior seat grows with it.
In most of the mis-hire situations I have worked through with founders, the decision to exit the individual could have been made at month two or three with roughly the same quality of information as the decision that was eventually made at month eight, nine or ten. The additional months produced very little new information. They produced a great deal of additional cost.
The brief is where it usually goes wrong
The most common source of a bad hire is not the recruitment process. It is what happens before the recruitment process begins.
When founders hire reactively, which is the way most SME hiring gets done, the brief tends to be fuzzy. You need someone in that role. You need them soon. The criteria that come out of that conversation are a combination of what the last person in the role did and what an ideal future version of the role might look like, with not enough clarity about which of those you are actually hiring for.
The result is a brief that attracts a broad range of candidates, generates a long shortlist, and leads to a decision based more heavily on interview chemistry than on a precise assessment of whether this specific person can do this specific job at this specific stage of the business.
Chemistry is not worthless. It is not a proxy for capability. The candidates who perform best in unstructured interviews are not systematically the candidates who perform best in demanding roles. The research on this has been clear for a long time.
What good looks like
A brief that produces the right hire is specific enough to be useful as a screening tool. If you cannot read the brief and make a clear judgement about whether a candidate is likely to succeed in this role, the brief is not yet a brief. It is a wish list.
Beyond the brief, the process should assess the things that most commonly drive failure in a role. Capability is rarely the issue. It is cultural fit, management style, how someone responds to ambiguity, whether they take ownership or operate in a mode of learned helplessness. These things can be assessed if you design the process to assess them.
The cost of getting this right upfront is a few additional weeks and a more disciplined brief. The cost of getting it wrong is twelve months of distraction, a disengaged team, and the whole process again at the end of it. The maths is not complicated. The hard part is being willing to do the work before the urgency takes over.