Why CEOs Call Me After a Bad Hire, Never Before

Most CEOs call after the project has slipped, after the team member pulls them aside to say they're thinking about leaving, after the client email arrives with a tone that used to be warmer. By then, the hire has been in place for five or six months. The damage is real and the options are limited. The call always starts the same way: "I think we made a mistake."

This is not unusual. It's the most common pattern we see. And it's almost entirely avoidable.

Understanding the Real Cost of a Bad Hire

When CEOs calculate the cost of a bad hire, they usually land on something manageable: a few months of salary, maybe a severance payment, the time spent re-posting the role. It stings, but it feels finite. This calculation is almost always wrong.

Consider a head of client success brought into a 25-person company. She's technically capable, interviewed well, and came with strong references. By month four, the two most experienced members of her team have quietly started looking elsewhere. One leaves. The client accounts she was meant to deepen have stalled - not dramatically, just a degree or two cooler than they used to be. The CEO eventually parts ways with her at month six. The replacement search takes three months. The team member who left takes institutional knowledge about two clients that no one thought to document.

The salary cost was real. But the actual cost - the team disruption, the client relationship cooling, the knowledge that walked out the door, the three months of productivity lost while the team recalibrated around someone who wasn't quite right - that's the cost most CEOs never fully tally.

There's also a hidden timeline that compounds the problem. The first 30 days of almost any hire are misleadingly positive. The new person is engaged, asking questions, making good impressions. Leadership feels vindicated. Between 60 and 90 days, the cracks begin to show - small ones, usually. A meeting where the tone was off. Feedback from a peer that doesn't quite land. A task that took longer than expected, with an explanation that felt slightly evasive. Individually, none of these are flags. Together, they're a pattern.

By month six, that pattern is undeniable to almost everyone except the person who made the hire. They're usually the last to say it out loud.

Why CEOs Don't Call Until It's Too Late

There's a specific kind of silence that settles in around a struggling hire. The CEO has already spent real capital on this person - interview time, onboarding hours, introductions to clients, the internal announcement that framed this hire as a step forward. Admitting the hire was a mistake means admitting the decision was a mistake. For many founders and CEOs, especially those who made the call themselves, that's genuinely painful.

Sunk-cost thinking is so common in hiring it's almost a cliché, but it's worth naming plainly: the time and money already spent are gone regardless of what happens next. The only question is what the next six months cost. Staying with a bad hire because you've already invested in them is one of the more expensive ways to protect your own sense of judgment.

The calls we tend to receive come at one of three moments. The first is when a key person on the team - often the most respected one - quietly signals they're done. The second is when a client relationship fractures in a way that feels connected to the hire. The third is when a deadline gets missed and the explanation from the hire doesn't quite hold together. Any one of these events creates enough pain to override the discomfort of admitting the mistake. But by then, the intervention required is much larger than it would have been at month two.

Part of what keeps CEOs from calling earlier is the belief that asking for help signals weakness or uncertainty. In practice, the opposite tends to be true. The founders who build the strongest teams are usually the ones who treat hiring as a due diligence exercise, not a test of their own instincts. They ask. They check. They consult. Not because they lack confidence, but because they understand the stakes.

Spotting Red Flags During the Hiring Process

The warning signs are usually there. They're just easy to rationalise in the moment.

In a hiring conversation, technically strong answers can mask real misalignment. A candidate describes their last role fluently and impressively, but when you ask how they handled a disagreement with their manager, the answer goes vague. "We worked through it," they say, or "I always try to find common ground." These aren't terrible answers, but they're not revealing ones either. A candidate who's genuinely good at navigating conflict usually has a specific story - something with texture, where they didn't get exactly what they wanted but the outcome was constructive. Evasion about team dynamics during interviews is one of the clearest early signals of difficulty ahead.

Reference checks are where many hiring processes fall apart, not because references lie, but because the questions are too safe. "What were their strengths?" will get you a polished answer. Try this instead: "Tell me about a time this person disagreed with you or pushed back on a decision. How did they handle it?" Or: "Is there a context where you think they'd struggle?" A genuine reference will engage with these questions thoughtfully. A polite brush-off - short answers, enthusiasm without specifics, a quick pivot to positives - is its own kind of signal.

After final-round interviews, before any offer is made, there's a conversation worth having with the people who'll work most closely with this person. Not a formal debrief, just an honest read. If someone hesitates and can't quite say why, pay attention to that. Hesitation without clear cause isn't nothing. It's often pattern recognition that hasn't yet found its words.

Building a Hiring Culture That Asks for Help

Some of the most effective hiring processes we've seen are built around a simple norm: no offer goes out before someone outside the hiring team has reviewed the candidate. Not to override the decision - to pressure-test it.

Framing matters here. Bringing a finalist candidate to a trusted advisor or a small panel of colleagues before making an offer isn't a sign of doubt. It's what due diligence looks like in hiring. You'd do it before signing a lease or approving a significant vendor contract. The same instinct applies to the people who'll shape your team's culture and output for the next several years.

Unilateral hiring decisions - especially in smaller companies - carry a specific risk: they rely entirely on the pattern recognition of one person, filtered through one set of incentives and one set of blind spots. A CEO who's excited about a candidate because they remind her of herself at an earlier career stage, or because the interview happened on a particularly good day, may not be the most calibrated judge. A second or third perspective, from someone who won't feel the hire's reflected glory if it goes well, tends to surface things that get missed.

A simple version of this: final-round candidates meet with two or three people outside the direct hiring manager. Each person asks one question designed to reveal character or approach - not credentials. Something like: "Describe a project that didn't go the way you expected. What did you learn from how you handled it?" The answers aren't evaluated against a rubric. You're looking for self-awareness, honesty, and whether the story the candidate tells sounds like the kind of person who'd fit this particular team. Afterwards, each person shares one observation. That's it. Small ritual, real signal.

What to Do When You Realise You've Made a Mistake

If you've landed here - the hire is in place, the doubts are real, and you're not sure how to proceed - there's a useful decision tree to work through. First: is this a skills gap or a misalignment? Skills gaps can sometimes be closed with clearer expectations, better support, or a role adjustment. Misalignment - between how this person operates and what the team actually needs - rarely resolves on its own. Time usually makes it clearer, not better.

If it's misalignment, the conversation with the hire is difficult but often less surprising to them than CEOs expect. People who aren't thriving in a role usually know it. The discomfort tends to be mutual. A direct, honest conversation - "This doesn't seem to be the right fit for either of us, and I'd like to talk about how we handle that" - gives the person their dignity and opens a path forward. Framing it as a shared reality rather than a verdict tends to produce better outcomes for both sides.

There's a cost to acting quickly: severance, the time and expense of re-hiring, the awkward team communication. These are real. But they are almost always lower than the cost of six more months of a hire who isn't working. Team morale compounds slowly in both directions. Every week a misaligned person stays in a role, the team around them is quietly recalibrating - working around them, compensating, becoming a little more cautious. That's expensive in ways that don't show up in any single line item.

When to Seek Support

There are three moments where an outside conversation pays for itself many times over. The first is before the offer - when you have a finalist and something about the decision feels uncertain. Not because you're second-guessing yourself, but because another set of eyes on the pattern is simply good practice. The second is during the first 90 days, if early signals feel off. Not alarming, just off. A trusted advisor can help you distinguish between normal adjustment friction and something that deserves closer attention. The third is before you're about to make a significant hire - a first head of sales, a new engineering lead, a COO - where the stakes are high enough that the downside of a mistake is genuinely disruptive.

Who you call matters. The most useful person is someone who has actually hired and fired, who knows your industry or your stage of growth, and who can ask the questions you're too close to ask yourself. This might be a board member, a mentor, a founder who's been through the same scale-up, or an HR consultant with early-stage experience. The credential is less important than the pattern recognition.

One honest comparison: a pre-hire conversation costs a few hours and, sometimes, a consulting fee. A post-hire mistake - the kind that costs you a team member, a client relationship, and a replacement search - costs months. The arithmetic isn't complicated. The hard part is making the call before the pressure is unbearable, rather than after.