The Hire That's Costing You: A 5-Part Guide for Founders
Bad hires don't just cost money. They cost time, momentum, and the trust of everyone watching.
The most expensive person on your team might be the one you're afraid to let go.
Most founders underestimate the cost of a bad hire because they only think about salary. But salary is the smallest part of it.
It's the lost productivity across the team. The manager spending their time managing problems instead of growing the business. The frustration that quietly spreads to your best people. The missed goals and slower execution that compound week after week.
Then comes the replacement cost. Recruiting again. Onboarding again. Rebuilding trust with the team that watched it play out.
A $120K hire that doesn't work out can cost your company $250K or more when you factor in everything. And that's conservative.
But the biggest cost isn't money. It's delay.
The termination itself takes 15 minutes. The decision is what drags on for months.
If you're running a team under 50 and making your first few critical hires, this guide is for you. Below, I walk through the full arc — from recognizing the problem to executing the decision the right way.
Part 1: The Real Cost of a Bad Hire
Most founders I work with aren't avoiding the problem because they don't see it. They're avoiding the conversation they already know they need to have.
That gap between knowing and acting is where time, money, and momentum are lost.
The termination itself takes 15 minutes. The decision is what drags on for months — and every week that passes without a decision costs more than the week before it.
Part 2: Why Most Teams Get Stuck
You already know who it is.
You've known for a while. But you haven't made the decision yet — because you want to be fair, avoid the discomfort, or you're hoping it will somehow get better on its own.
You're not alone. In about 90% of the cases I've worked, the pattern is the same: performance is not where it needs to be, expectations are unclear or inconsistently enforced, and no real decision has been made.
That creates a middle ground where everyone feels the problem but no one addresses it. The team sees it. The individual senses it. And the leader is stuck between action and avoidance.
No one benefits from that limbo. Not the leader. Not the team. And not the person whose performance is in question — they deserve clarity too.
Here's the part most people don't say out loud: keeping the wrong person in a role is often more damaging than hiring them was in the first place.
Your team is watching what you do about it. Not whether you're nice. Whether you're clear.
If you've been going back and forth on a people decision for more than a couple of weeks, that's usually your signal. Not necessarily to fire someone — but to stop avoiding the clarity that situation requires.
Part 3: How to Decide — Fix, Coach, or Exit
Not every performance problem is a termination.
That might be surprising coming from someone who has managed over 200 exits. But it's true — and knowing the difference is what separates a reactive founder from a decisive one.
A founder I worked with hired a senior leader quickly during a growth phase. Within 60 days, the team lacked direction, deadlines were slipping, and morale started to drop. The instinct was to replace them immediately.
Instead, we slowed down and asked three questions before making any move:
Are expectations clearly defined — not just assumed?
Has direct, consistent feedback been given?
Is there a fair opportunity to improve?
Most people think a PIP is only a paper trail toward termination. Sometimes it is. But I've helped people come through a PIP, stay in their role, and become strong contributors. When that happens, it almost always points to something the company missed — unclear expectations or misalignment that was never surfaced.
That's the real insight. Most people are trying their best. The question is whether their effort is aligned with the outcomes the business actually needs, and whether anyone has clearly told them what those outcomes are. That's the decision point.
Fix the environment if expectations were never clear. Coach the individual if the gap is closable. Exit with clarity and fairness if the fit isn't there.
The worst option is staying in the middle and hoping it resolves itself.
Part 4: Termination With Care and Experience
Your team will not remember that you let someone go. They will remember how you did it.
Termination is one of the most avoided and mishandled parts of running a company. I've managed over 200 across my career — layoffs, performance-based exits, executive transitions, misconduct, and more. No two situations are the same. But the principles should be.
Done poorly, it creates legal exposure, erodes trust across the entire team, and disrupts the business far beyond the individual who left. One bad termination can undo months of culture-building.
Done well, it reflects fairness and consistency. Clear documentation. Respect for the individual. And stability for the team moving forward.
You can terminate someone in 15 minutes. Doing it right takes preparation, alignment, and follow-through.
Here's what I've learned after 200 of these conversations: the founders who handle terminations well are not the ones who find it easy. They're the ones who prepare thoroughly, communicate clearly, and treat the person with dignity on the way out. That earns trust from the people who stay.
Part 5: The AI Pressure Test — Run This Before Any Termination
Before you terminate someone, let AI tear your case apart first.
I'm not talking about using AI to draft a termination letter. That saves you 20 minutes. This saves you a lawsuit.
After 200+ terminations, I can tell you the gaps are almost always the same. Feedback that sounds punitive instead of developmental. A timeline that shows no real window to improve. Documentation that proves the founder was frustrated but never proves the employee was clearly told what needed to change.
These are the things an employment attorney will find. These are the things a plaintiff's lawyer will find. The question is whether you find them first.
Most founders have some version of the evidence. Performance notes in a Google Doc. A few Slack messages. Maybe a PIP they put together from a template. They feel confident they have enough.
They usually don't.
Below is the prompt I built — the same scrutiny I'd apply if you hired me to review your case. Paste in your documentation and it tells you what's missing, what's weak, and what needs to be fixed before you move forward.
It's not legal advice. It's the preparation you do before you spend billable hours with an attorney.
The Prompt
Copy this, redact any names, and run it before your next termination conversation. If the output makes you uncomfortable, that's the point — better to feel it now than in a legal proceeding.
You are reviewing a termination case on behalf of the employer. Your job is to be the harshest possible internal reviewer — find every weakness, every gap, and every risk before this case reaches an employment attorney or becomes a legal matter.
Do not reassure me. Do not tell me what I did well. Focus entirely on what is missing, what is weak, and what could be used against me.
I am a startup founder preparing to terminate an employee. Below is all the documentation I have — performance notes, feedback records, PIP documentation, relevant messages, and any other context I could gather.
Review this documentation and evaluate the following areas:
1. DOCUMENTATION GAPS — Is there anything I am claiming happened that has no written evidence to support it? Where does the paper trail go missing? What conversations should have been documented but were not?
2. TIMELINE AND FAIRNESS — Does the timeline show a genuine opportunity for the employee to improve, or does it look like the outcome was predetermined? Are there gaps where nothing was documented for weeks followed by a sudden escalation? Would a reasonable person look at this timeline and believe the process was fair?
3. LANGUAGE REVIEW — Does any of my written feedback, notes, or messages read as personal, emotional, punitive, or retaliatory rather than professional and business-focused? Quote the specific language that is a problem and explain why.
4. CONSISTENCY — Based on what I have provided, is there anything that suggests this employee was held to a different standard than others in a similar role? Are the expectations I reference clearly documented somewhere the employee could have seen them?
5. PROTECTED CLASS RISK — Is there anything in the documentation — even unintentionally — that could suggest the termination is connected to age, gender, race, disability, pregnancy, religious practice, family status, or any other protected characteristic? Look at the language, the timing, and the context.
6. MISSING PROCESS STEPS — What steps appear to be missing from a standard, defensible termination process? Consider whether expectations were formally communicated, whether the employee acknowledged receiving feedback, whether support or resources were offered, and whether there is a record of the employee being given a chance to respond.
7. RETALIATION RISK — Did the employee recently file a complaint, raise a workplace concern, request a reasonable accommodation, take medical or family leave, or engage in any other protected activity? If so, how does the timing of this termination look relative to that activity?
After your review, provide: - A clear risk assessment: LOW, MEDIUM, or HIGH — with a one-sentence explanation of why - The top 3 specific things I need to fix, add, or document before proceeding - One sentence describing how this case would look to an outside observer who knows nothing about my company or this employee
Here is my documentation: [PASTE YOUR DOCUMENTATION HERE — include performance notes, PIP documents, feedback emails, relevant Slack or text messages, and a timeline of key events. Remove all employee names and identifying details before pasting.]
No limbo. Only action.
If you're going back and forth on a people decision right now — whether to act, how to approach it, or what comes after — reach out. That's exactly the kind of situation I work through with founders. 60 minutes is usually enough to understand the situation, work through the decision, and map out a plan to execute it well.
