Latest / Sales Leadership with Fexingo: Quota Carriers, Sales Managers, and Revenue Teams / The Real Cost of a Bad Sales Hire
Transcript
- Lucas: Let me start with a number that still makes me wince. A client of mine — mid-market SaaS company, about sixty million in ARR — hired a senior account executive in January of last year. By the time they finally let her go in September, the total cost of that hire was around three hundred and forty thousand dollars. Luna: That's not just her salary, I assume. Lucas: Right. Salary was maybe a hundred and ten of that. The rest is recruiter fees — they used an agency, paid twenty-five percent of first-year comp — plus ramp costs, fully loaded benefits, sales enablement tools she barely used, and the biggest hidden one: the deals she lost because she was mismanaging relationships. Luna: And the deals she never even got into because her pipeline hygiene was terrible. Lucas: Exactly. Her manager spent roughly four hours a week in coaching and firefighting — that's opportunity cost. Plus the cultural drag. Two junior reps on her team started interviewing elsewhere because they felt her sloppiness was hurting team morale. Luna: So you're saying that three hundred and forty K is probably an underestimate. Lucas: I think it's conservative. The real number, if you include lost pipeline the team never recovered, is probably closer to half a million. And the thing is — this is not a unique horror story. It's a pattern I see in maybe one out of every three sales organizations I work with. Luna: So what went wrong? How did they end up hiring someone who clearly wasn't a fit? Lucas: A few things. First, they over-indexed on her resume. She had a great pedigree — worked at a well-known enterprise software company, had a track record of hitting quota three years in a row. But her last role was very different: she was a farmer, not a hunter. Her job was to manage existing accounts, not open new logos. They needed a hunter. Luna: So they basically hired the wrong archetype. Lucas: Exactly. Second, they skipped the role-play portion of the interview. They did three rounds of behavioral questions — 'tell me about a time you overcame a tough objection' — which everyone rehearses for. But they never put her in a simulated discovery call with their actual product. If they had, they would have seen she couldn't ask good follow-up questions. Luna: We always talk about the importance of discovery, but leaders are often too busy or too confident in their gut to actually test it. Lucas: And the third thing: they relied heavily on one glowing reference from her former manager, who had since left that company. That manager gave a rave review, but when they finally checked a peer reference — from a colleague who'd worked with her on a deal — the feedback was lukewarm. By then, the offer was already signed. Luna: It's like they wanted to find a reason to say yes. Lucas: Desperation. They'd been trying to fill the role for five months. The VP of Sales was under pressure from the board to grow revenue. So they convinced themselves the fit was there. Luna: I see this a lot. The 'first ninety days' mindset actually works against us. If a new hire doesn't deliver immediately, leaders panic. But sometimes, the real problem is that the first ninety days are wasted on the wrong metrics. Lucas: That's a great point. In her case, the onboarding was two weeks of product training and then straight into cold calling. No shadowing, no joint calls with a senior rep, no gradual ramp. She was set up to fail. Luna: So what should a better onboarding look like? Give me one concrete element. Lucas: I like the 'ten-call rule' — before a new rep makes their first solo call, they have to listen to ten recorded calls from top performers and write down what they noticed. Then they have a debrief with their manager. It forces pattern recognition before they open their mouth. Luna: That's smart. And it doesn't cost anything. Lucas: Exactly. The other thing: have a thirty-day checkpoint that's not about pipeline number. It's about process fidelity. Can they log a call correctly? Do they use the CRM the way the team does? Are they asking good discovery questions in role-play? If those things aren't there by day thirty, you probably have a problem. Luna: And if they are there, but the numbers aren't coming yet, you can be more patient. Lucas: Right. But here's the uncomfortable truth: most sales leaders wait too long to cut bait. The average time to termination for a mis-hire in my data set is seven months. That's seven months of lost productivity, bad customer interactions, and team frustration. Luna: So what's the right timeline? When should you start getting nervous? Lucas: I think you need to differentiate between regrettable and non-regrettable attrition. Non-regrettable is when someone just isn't a fit — they're not going to make it. For that, the decision should come by day sixty if you have a good onboarding process. If by day sixty they still can't pass a basic discovery call role-play, you're not doing them or yourself any favors. Luna: That's aggressive. Most companies give at least a full quarter. Lucas: And that quarter costs them hundreds of thousands. Let me put it this way: if you knew a rep had a twenty percent chance of working out, would you hire them? Probably not. But that's essentially what happens when you don't have a real gate in the first sixty days. Luna: So the solution is better gates, not just better interviews. Lucas: Exactly. The interview is just the first gate. The real test is how someone performs when they're actually in your environment, with your product, your customers, your culture. You need a structured onboarding that creates multiple data points early. Luna: It reminds me of the concept of 'hire slow, fire fast.' But most companies do the opposite. Lucas: They hire fast because they're desperate, and they fire slow because they're hopeful. Both instincts are wrong. The cost of a bad hire is orders of magnitude higher than the cost of an empty seat. Luna: Before we go further, I want to say something about these conversations. We spend a lot of time here digging into real numbers and real cases — and we deliberately don't run ads on the show. If these episodes have helped you think differently about your team or your career, and you want to support that, there's a simple way: buy me a coffee dot com slash fexingo. No pressure, just a way to keep it ad-free. Lucas: Yeah, and honestly, we've heard from listeners who say that one framework from an episode saved them a bad hire or a lost deal. That's why we do it. So if that's you, we'd appreciate it. Luna: Alright, back to hiring. You mentioned the 'ten-call rule' — any other practical tools? Lucas: One more: the 'reverse reference' check. Before you make an offer, ask the candidate for a reference from a former peer — someone who wasn't their manager. Then ask that person specifically: 'On a scale of one to ten, how much did you learn from working with them?' That's a different signal than the standard reference question. Luna: Because peers see the collaborative reality, not just the managed narrative. Lucas: Exactly. And one more: have a 'day zero' meeting. Before the candidate accepts, have their future manager walk them through the first thirty days in detail — what success looks like, what the learning milestones are. If the candidate seems surprised or hesitant, that's a red flag. They should be excited about the structure. Luna: So essentially, you're trying to create a transparent contract upfront. Lucas: Yes. And that transparency is what allows you to have a tough conversation at day thirty. You're not blindsiding them. You both agreed on what success looked like. Luna: What about the cost of the wrong manager? That's a whole other conversation. Lucas: It is, and it's related. A bad manager can make even a good hire fail. But we'll save that for another episode. Luna: Deal. So the takeaway: hire with a process, not a gut feeling. Onboard with gates, not just hope. And cut fast if the gates aren't met. Lucas: And remember, the cost of a bad hire isn't just the salary. It's the lost pipeline, the team morale, the manager's time, and the deals that never close. That three hundred and forty thousand dollars? That's cheap compared to what it could have been. Luna: Alright, let's leave it there. Thanks for listening, and we'll see you next time.