How do you fire someone at a small startup?

At a small startup, every seat matters — a poor-fit employee doesn't just underperform, they slow everyone else down and quietly erode the culture you're trying to build. The right move is to act faster than feels comfortable, communicate directly without hedging, and treat the person with genuine respect throughout. Delaying a necessary firing is one of the most common and costly mistakes early-stage founders make.

Why founders wait too long — and what it costs

The impulse to delay is understandable. Early hires feel like co-conspirators, not employees. You hired them when nobody believed in the company, and letting them go feels like betrayal. But the math of a five-person team is brutal: one person operating at 60% isn't a 20% drag, it's a drag on every meeting, every decision, and every person who has to compensate for the gap.

Founders also tend to rationalize. They tell themselves the person is improving, that next quarter will be different, or that the role just needs to be redefined. Sometimes that's true. More often, it's a way of deferring a painful conversation. A useful diagnostic: if you've had the same performance concern for more than 60 days and it hasn't materially changed, the situation is unlikely to resolve itself. What you're really doing by waiting is paying full cost — in salary, morale, and your own attention — for partial output.

Paul Graham's observation about bad founders extending to bad hires is instructive here. In his writing on what makes founders fail, Graham notes that exploitative or low-integrity behavior tends to begin with cofounders and spread outward. The same dynamic applies to culture more broadly: the behaviors you tolerate in any team member signal what's acceptable to everyone else. A founder who doesn't act on a clear problem is, in effect, endorsing it.

How to know it's time: the criteria that actually matter

There are two distinct firing scenarios at a startup, and they require different thinking. The first is a performance issue: the person is trying but not delivering at the level the role demands. The second is a values or integrity issue: the person is capable but dishonest, politically corrosive, or actively undermining trust. The second category should be acted on immediately, with no performance-improvement process. The first deserves a short, explicit intervention first — but only one.

For performance issues, the intervention should be a direct conversation with three components: a specific description of what isn't working (not vague feedback, but concrete examples), a clear statement of what success looks like over the next 30 days, and an honest acknowledgment that the role may not be the right fit if things don't change. This isn't a PIP in the corporate HR sense — it's a frank adult conversation. If the person improves, great. If they don't, you've already had the honest conversation, which makes the final decision easier for both parties.

For values or integrity problems — lying to customers, undermining colleagues, hiding bad news — don't wait. In a small company, trust is infrastructure. One person who corrodes it costs more than they contribute, no matter how technically skilled they are. The question to ask is: if I found out today that this person behaved this way, would I still hire them? If the answer is no, the decision has already been made.

The mechanics of the actual conversation

The termination conversation itself should be short, clear, and kind — in that order of priority. Founders often get this backwards: they lead with kindness, bury the clarity, and leave the other person confused about whether they've actually been let go. The conversation should happen in person when possible, in private, and at the start of the day (not Friday afternoon, which traps someone in a bad weekend).

Open by stating the conclusion, not working up to it. Something like: 'I've decided to let you go, and today is your last day.' Then briefly explain why — one or two honest sentences, not a catalog of grievances. The explanation should be real, not HR-softened to the point of meaninglessness. 'This role needs someone with more experience in X than you currently have' or 'We've had ongoing issues around Y that haven't changed' is honest. 'We're restructuring priorities' when you're not is a lie that makes the person feel manipulated and leaves them without useful feedback.

After the explanation, shift to logistics: what they'll receive in severance, how you'll handle references, the timeline for returning equipment or access. Have these details decided before you walk into the room. Being unprepared in the logistics phase signals that you haven't thought this through, which makes a hard moment worse. Keep the whole conversation under 20 minutes. Longer doesn't make it more compassionate — it just makes it more uncomfortable for everyone.

Severance, references, and what you owe early employees

Startup employment is inherently asymmetric: early employees take real risk, often accepting below-market salaries in exchange for equity and the opportunity. When you let someone go, especially in the first two years of the company, acknowledging that risk with a fair exit is both the right thing to do and protects your reputation as a founder who treats people well.

For an employee who has been with you less than a year, two to four weeks of severance is a reasonable floor. For someone who has been there longer or made meaningful sacrifices, be more generous — a month or two is not unusual. Accelerating cliff-based equity vesting for someone who was clearly trying and simply didn't fit is a powerful gesture that costs you relatively little but means a great deal to them. Consult your startup attorney before making commitments, but don't let legal process become a reason to be ungenerous.

References are often left ambiguous, which is worse than either option. If you can genuinely recommend the person for certain types of roles, say so explicitly and offer to be a reference for those. If you can't, be honest about what you can say — something like 'I can speak to their technical skills and the work they did on X, but I'd be less able to speak to fit for a senior leadership role' is more useful to them than a vague non-answer. Early hires talk to other founders. How you treat people on the way out will define whether good people want to join you on the way in.

After the firing: talking to the team

What you say to the remaining team matters almost as much as the firing itself. Don't pretend it didn't happen or be vague in a way that breeds rumor. A brief, honest statement — that day or the next morning — is better than silence. You don't need to share every detail, but the team deserves to know the role no longer exists in its current form and that you wish the person well.

Resist the urge to justify the decision by cataloging the person's failures to the team. Even if some team members already knew there was a problem, hearing you speak badly about a departed colleague tells them exactly how you'll speak about them if things go wrong. The signal you want to send is that you make hard decisions thoughtfully, treat people with respect throughout, and move forward.

Finally, use the moment to reassess the role itself, not just the person. A forced departure is often a chance to reconsider what you actually need. Early startups frequently hire for what they needed six months ago, not what they need now. Before backfilling the position reflexively, spend a week asking whether the role should exist in the same form, or whether the work could be distributed differently. The gap left by a departure is often smaller than it looked, and sometimes the team moves faster without needing to coordinate around someone who wasn't contributing fully.

“Founders want so much to seem big that they imitate even the flaws of big companies, like indifference to individual users.”

— Paul Graham, source

The one thing to do

Decide clearly, act quickly, tell the truth in the room, and treat the person's exit with the same care you gave their hire — your reputation as a founder depends on it.

Frequently asked questions

Should you use a performance improvement plan (PIP) before firing someone at a startup?

A formal PIP is usually unnecessary and often backfires — it signals the person is already out the door, which can poison the team dynamic. Instead, have one direct, explicit conversation that names the problem and sets a clear 30-day benchmark. If nothing changes, act. Reserve immediate termination for values or integrity issues, where no improvement process is appropriate.

How do you fire a cofounder versus a regular employee?

Cofounder separations are legally and emotionally more complex because they typically involve equity, board seats, and investor relationships. You'll need legal counsel to structure the exit properly — vesting acceleration, buybacks, and board changes all need to be handled formally. The conversation itself follows the same principles: direct, honest, and respectful, but expect it to take longer and involve more negotiation.

What if the employee gets emotional or argumentative during the termination conversation?

Stay calm and don't get drawn into a debate about the decision itself, which has already been made. Acknowledge their feelings briefly — 'I understand this is hard to hear' — then redirect to logistics. If the conversation becomes unproductive, it's acceptable to pause and reschedule the logistics discussion for the next day. Don't reverse the decision in the moment because of an emotional reaction.

How do you handle the fired employee's system access and data?

Revoke access to company systems, email, and code repositories on the day of termination — ideally within the hour after the conversation ends. This isn't punitive; it's standard security hygiene and protects both parties. Brief your IT or ops person in advance so it happens cleanly without the appearance of being reactive or hostile.

Sources

More playbook answers · Growth Prophet home