The real cost of a bad hire for a 10-person startup
There’s a number that gets quoted a lot in HR circles: a bad hire costs between 30% and 150% of the person’s annual salary. It’s a wide range, which tells you that the people making these estimates aren’t very confident in them. The reason the range is so wide is that the real costs are mostly invisible — they don’t show up on a balance sheet, and you usually can’t see them clearly until after the person has left.
At a large company, a bad hire is painful but survivable. The team is big enough to absorb it. The person can be managed into a corner. The impact stays contained.
At a 10-person startup, it’s a different situation entirely.
The numbers you can actually calculate
Let’s start with what’s visible. Say you hire a senior engineer at ₹28 lakhs per year. They’re not working out — maybe the skills aren’t what was represented, maybe it’s a culture problem, maybe the role wasn’t defined clearly enough. You give it six months before you accept the situation isn’t fixable.
Direct costs in that six months: ₹14 lakhs in salary and benefits. Recruiting fees if you used an agency — typically 8–12% of CTC, so another ₹2.5–3.5 lakhs. Equipment, tools, software licences. Then the cost of the replacement hire — same fees again.
You’re somewhere between ₹20–25 lakhs in direct costs for a single hire that didn’t work out. And you still don’t have the person you need.
That’s the easy part of the calculation.
The cost of the work that didn’t get done
A senior engineer who isn’t performing isn’t just neutral — they’re often actively creating problems. Code that has to be rewritten. Architectural decisions that get made badly and have to be undone. Features that get “built” but shipped with enough bugs that the product team has to spend the next two months fixing them rather than shipping new things.
The opportunity cost of six months of one person’s delayed output at a 10-person startup is enormous. At that stage, a single good senior engineer can move the product forward by six months in six months. A bad one can set it back by three. That’s a nine-month swing in product progress from one hiring decision.
For a startup racing to hit a milestone before the next fundraise, that nine months is not abstract. It’s the difference between having a compelling story to tell investors and not.
The management tax
This is the cost most founders underestimate. A struggling employee doesn’t just underperform — they require time from the people around them.
The hiring manager starts having difficult weekly check-ins. The CTO gets pulled into debugging sessions that shouldn’t require their involvement. HR time goes into documentation and performance management. The team has conversations after hours about whether this person is going to work out.
In a 10-person company, the hiring manager is often also building the product, running customer calls, and managing three other things. Diverting 30–40% of their attention to managing a struggling employee is not a small thing. It’s a meaningful reduction in the output of one of the most valuable people in the company, for months.
A founder told me last year that they knew within eight weeks that their head of growth hire wasn’t working. It took them another four months to act on it. In that time, they estimated they’d personally spent 6–8 hours a week managing the situation — coaching sessions, difficult conversations, trying to restructure the role. That’s roughly 100 hours of a founder’s time, on top of everything else the failed hire cost.
What it does to the team
At ten people, everyone knows everyone. There’s no hiding a performance problem from the rest of the team. And how you handle it — or don’t handle it — sends a signal to the rest of the company about what standards mean.
If the team sees someone who isn’t performing get managed gently for months with no consequences, the high performers notice. They start to question whether the company has the judgment to build a team worth being part of. Some of them — quietly, without drama — start taking calls from recruiters.
Losing a high performer because a bad hire made them feel like the bar was dropping is one of the most expensive things that can happen to an early-stage company. It’s also nearly impossible to directly attribute to the original hiring mistake, which is why it never shows up in the cost estimates.
Why it happens more than it should
Most bad hires aren’t the result of bad luck. They’re the result of a few predictable mistakes:
Hiring for skills and ignoring fit. Someone can be technically excellent and still be the wrong person for a specific team at a specific stage. Early-stage companies need people who are comfortable with ambiguity, who can work without much structure, and who don’t need a lot of hand-holding. These things don’t show up on a CV.
Rushing because the need feels urgent. The pressure to hire quickly is real — there’s work to do and not enough people to do it. But making a hire you’re not confident in because you need someone now is almost always more expensive than waiting another four weeks to find the right person.
Ignoring early signals in the process. Most bad hires show red flags during interviews that get rationalised away. References that are warm but vague. Answers that are impressive-sounding but don’t quite answer the question. A gut feeling that something is off. These signals are worth taking seriously.
Not being honest about what the role actually is. A candidate who joins expecting one thing and finds another isn’t necessarily a bad hire — they’re a bad fit for the role as it actually exists. Accurate role descriptions and honest conversations about the messy reality of early-stage work prevent a lot of these situations.
Acting faster once you know
One of the hardest things for first-time founders is acting decisively when a hire isn’t working. There’s always a reason to wait another month. Maybe it’s a communication issue that can be fixed. Maybe the person needs more time to find their feet. Maybe it’ll sort itself out.
Sometimes that’s true. But usually, the founders who look back on a difficult hire say the same thing: they knew earlier than they acted, and waiting made everything worse — for the company, for the team, and often for the person themselves.
This isn’t about being harsh. It’s about being clear. If someone isn’t working out, the kindest thing — for them and for the company — is to have that conversation directly and early, rather than letting a difficult situation drag on for half a year.
The best way to avoid the cost of a bad hire is to get the hire right in the first place. That sounds obvious, but it requires slowing down at the front end — being clear about what you need, running a proper process, and not letting urgency push you into a decision you’re not confident in.
If you’re about to make a hire and want to think through the process, or if you’re looking for someone to run the search for you, reach out. It’s the kind of conversation we have every week.
The best way to avoid a bad hire is to screen properly before the offer. See how Albatronix vets engineering candidates — or explore fractional hiring to reduce the risk of a long-term commitment before you’re ready.
