Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / The Hidden Cost of a Bad Hire
Transcript
- Lucas: A mid-level hire in tech costs about a hundred and fifty thousand dollars in salary and benefits in year one. That's the obvious number. But get that one wrong, and the real hit is closer to six times that. Luna: Six times. So we're talking nearly a million dollars for one bad hire. Where does that number come from? Lucas: It's a rule of thumb that's been around for a while — and it's surprisingly durable. The U.S. Department of Labor has historically pegged the cost of a bad hire at thirty percent of the employee's first-year earnings — that's just the direct stuff. But a lot of research, including work from the Society for Human Resource Management, says the indirect costs blow that up. Luna: Right — the indirect costs. That's where it gets fuzzy. What are we actually including? Lucas: Onboarding time from managers and peers — that's hours of lost productivity. Then there's the hit to team morale. If the hire is a bad cultural fit, it can drive turnover among the people who have to work with them. And the big one: opportunity cost. Every project they touch is delayed or botched while you figure out they're not the right person. Luna: I've seen that play out. There was a SaaS company — I think it was around a hundred employees — that brought in a VP of Sales from a big enterprise software firm. On paper, stellar resume. But the culture was completely different. Fast-moving, scrappy, founder-led. Lucas: And what happened? Luna: Within six months, the sales team's retention dropped by forty percent. Four of the ten reps quit. They said the VP was micromanaging, running long forecast meetings, demanding rigid pipeline reports. The CEO told me they lost about two million dollars in pipeline that quarter because the reps who left were the top performers. Lucas: That's exactly the kind of domino effect that doesn't show up on a P&L. The VP's salary was probably two hundred thousand, maybe two-fifty. But the real cost? Easily over a million, maybe two, when you factor in lost deals, recruiting fees to replace the reps, and the time the CEO spent firefighting instead of closing clients. Luna: So how do you catch this early? The 'hire slow, fire fast' mantra is popular, but it's hard to execute. Especially when you've already invested months in recruiting someone. Lucas: It is hard. But there's a practical hack. I've seen companies implement what they call a 'thirty-day triage check.' Not a formal performance review — more like a structured conversation at the end of the first month. The manager and the new hire sit down and go through three questions. Luna: What are the three questions? Lucas: One: Is the role what you expected? Two: Are you getting the support you need? Three: Is there anything that's surprising you in a bad way? The key is to ask it in a way that gives the new hire permission to be honest. You want them to say, 'Actually, the sales cycle here is much shorter than I'm used to, and I'm struggling to adapt.' Luna: So you're not waiting for the ninety-day review. By then, the damage could be done. Lucas: Exactly. And the triage check isn't just a touchy-feely exercise. You can track the answers. If the same patterns keep coming up across different hires — like 'I'm not getting enough training' — that's a signal about your onboarding process, not the individual. But if one hire consistently says they feel misled about the role, you might have a bad fit. Luna: I like that it's structured but low-stakes. No one's getting fired in the first thirty days. But you can decide to invest extra coaching or, in some cases, start documenting performance issues early. Lucas: Right. And if you do need to let someone go early, it's cheaper. The rule of thumb I've heard from some HR leaders is that the cost of a bad hire multiplies by ten after the first quarter. Because by then, they've built relationships, influenced projects, and maybe even hired people under them. Luna: That's a scary thought. So the thirty-day check is really about avoiding that ten-times multiplier. Lucas: Exactly. And it's not just about the cost. It's about fairness. The longer you keep someone who's a clear mismatch, the worse it is for them too. They're stressed, underperforming, and eventually they'll be fired. Better to have that conversation early and give them a chance to course-correct or find a better fit elsewhere. Luna: I want to go back to the six-times number. Is that really accurate for every role? What about a frontline customer support agent versus a senior engineer? Lucas: Good point. The multiplier scales with seniority and impact. For an entry-level role, the cost might be two to three times salary. But for a senior leader, it can easily be ten to fifteen times. Because they're making decisions that affect the whole strategy. The VP of Sales we talked about — his bad hire cost was probably twenty times his salary, when you add it all up. Luna: That's sobering. So the takeaway isn't just 'be careful who you hire.' It's 'build a system to detect misalignment fast.' Lucas: Exactly. And a lot of companies don't have that system. They rely on gut feel and hope. But hope isn't a strategy when the cost of failure is half a million dollars or more. Luna: I'm curious — are there any industries that are particularly bad at this? I feel like startups are notorious for hiring too fast. Lucas: Startups are definitely susceptible. They're under pressure to grow, and the founders are often optimists by nature. They'll overlook red flags because they want to believe. But I've also seen it in large enterprises where the onboarding process is so bureaucratic that it takes six months to realize someone isn't working out. By then, the damage is done. Luna: So the opposite extreme — hiring slow but firing even slower — can be just as costly. Lucas: It can be worse. Because in a large company, a bad hire can fly under the radar for a year. They're in a silo, they're producing mediocre work, and nobody wants to have the uncomfortable conversation. The cost compounds silently. Luna: What about the role of the hiring manager? How much of the bad hire is actually a failure in the hiring process itself versus poor management? Lucas: It's often both. But I think a lot of bad hires happen because the job description wasn't clear, or the interview process didn't test for the skills that actually matter. You can hire a brilliant person for the wrong role. That's not their fault. That's a process failure. Luna: So one way to reduce bad hires is to tighten up the job description and the interview rubrics. Lucas: Exactly. And include some kind of work sample test. For the VP of Sales, maybe have them run a mock forecast meeting. See how they actually behave. Because a resume can tell you they have the experience. But it can't tell you if they'll fit the culture. Luna: I want to talk about one more thing: the emotional cost. We talk about dollars and cents, but there's also the hit to team morale, the loss of trust. How do you quantify that? Lucas: You can't easily. But you can measure turnover rates on the team. If you see a spike in departures within six months of a new hire, that's a red flag. And you can do stay interviews — asking current employees why they're staying — to see if the new person is driving people away. Luna: So the hidden cost of a bad hire is that it's not just one mistake. It's a cascade. Lucas: It is. And that's why the thirty-day triage check is worth doing. It's a low-cost way to catch the cascade before it becomes a waterfall. Luna: Alright. So for anyone listening who's in a hiring role, what's one concrete thing they can do differently starting next week? Lucas: Implement a thirty-day triage check for every new hire. Make it a calendar reminder. Block thirty minutes for week four. Have a simple conversation. Ask the three questions. And then document the answer. It's a small habit that could save your company hundreds of thousands of dollars. Luna: That's actionable. And if the answer to question one is 'No, the role isn't what I expected' — you have a problem, and you can fix it early. Lucas: Exactly. And if all three answers are positive, great. You've just validated your hiring process. That's useful data too. Luna: I think that's a good place to leave it. A bad hire is expensive, but it's not inevitable. You just need the right checkpoints. Lucas: And the courage to act on what you find.