The True Cost of a Bad Early Hire

Most founders, when they think about the cost of a bad hire, think about salary. They calculate three or four months of wasted compensation, add recruiting fees, and call it a day.

That number is almost always less than $50,000. And it's almost always wrong by a factor of three to five.

The visible costs (the part everyone calculates)

Let's say you hire a senior engineer at $180,000/year. They don't work out after five months. The visible math:

• 5 months of salary: $75,000
• Recruiting costs (if agency): $27,000–$36,000
• Severance (if applicable): $15,000–$30,000
• Re-hiring costs: another $27,000–$36,000

Total visible cost: roughly $144,000–$177,000. Painful, but survivable.

Now here's the part nobody puts on a spreadsheet.

The invisible costs (the part that actually kills you)

Founder time

How long did you spend sourcing, screening, and interviewing this person? Realistically, 40–60 hours for a senior role. Then onboarding: weekly 1:1s, context transfers, code reviews, coaching. Another 20–30 hours over the first month. Then managing the performance problem: documentation, hard conversations, HR consultation. Another 20–30 hours.

You spent roughly 100 hours of your time on this person. At an early-stage startup, founder time is the scarcest resource. What else could you have built in those 100 hours?

Team morale and output

A bad hire doesn't exist in isolation. They interact with your team. If they're underperforming, your other engineers are picking up slack — and they notice. They lose respect for leadership's judgment. They start questioning whether you know what you're doing. Morale dips compound faster than you expect.

Research from the University of Iowa found that a single "bad apple" employee can reduce team performance by 30–40%. On a five-person engineering team, that's effectively losing 1.5 to 2 engineers worth of output — while still paying the bad hire's salary.

Velocity loss on the roadmap

The feature that didn't ship. The technical debt that got introduced. The architecture decision that went sideways because the wrong person made it. These aren't abstract costs — they compound directly into your competitive position.

At the early stage, six months of velocity loss can be the difference between winning a market and watching a competitor pull ahead. You can quantify this in terms of delayed revenue, extended runway requirements, or lost pilots.

Direction risk

This is the one nobody talks about. At the seed stage, your first technical hire shapes your architecture. Your first marketing hire shapes your positioning. Your first sales hire shapes your ICP. These decisions have two-to-three-year compounding effects.

A bad early hire doesn't just waste months of salary. They can send the company in the wrong direction for years.

The real number

When you add up direct costs, founder time, team velocity loss, and morale impact, a bad senior hire at a Seed-stage startup typically costs between $300,000 and $500,000 — and that's a conservative estimate that doesn't account for direction risk.

For context: at $150K MRR, that's 2–3 months of total revenue. At a $3M Seed round, it's 10–17% of your runway, gone.

Why this matters for how you evaluate candidates

If a mis-hire truly costs $400,000, how much should you invest in evaluating candidates properly?

Even a 10% reduction in mis-hire risk is worth $40,000 in expected value. A proper evaluation process — with work sample tests, structured scoring, and behavioral signal analysis — costs a fraction of that. The math isn't close.

The founders who treat hiring as a cost center and rush it to save time are the ones who end up paying the real bill six months later. The ones who treat evaluation as an investment are the ones who build durable teams.

You now know what the actual investment is worth. The question is whether your current process is designed to justify it.