No founder starts a company planning to lay people off. But market conditions shift, a funding round takes longer than expected, or a growth bet does not pay off on the timeline the budget assumed, and at some point the math stops working. When that happens, how a founder handles the next thirty days shapes the company's culture, its ability to hire well again, and often its own reputation, for years afterward.
This is not a guide about whether to cut. That decision usually becomes obvious once the runway math is done honestly. This is a guide about doing it in a way that treats departing employees fairly, protects the people who remain, and leaves the company in a position to rebuild rather than limp forward with a demoralized team.
Founders who have never done this before often underestimate how much planning a layoff needs. It touches legal compliance, payroll, benefits administration, equipment recovery, access revocation, internal communication, external communication, and the emotional reality of telling people their job is ending. Treating it as a single afternoon conversation, rather than a coordinated process planned over one to two weeks beforehand, is where most of the avoidable damage comes from, both to departing employees and to the company's ability to operate smoothly afterward.
Consider a common scenario: a twenty-five person startup realizes eighteen months into a two-year runway plan that the next funding round is going to take longer to close than expected, possibly six months longer given how the market has shifted. The founder has two honest choices: cut costs now to buy time, or run the risk of running out of cash before the round closes and having no choice at all.
The founders who handle this well start from the product roadmap, not from a headcount spreadsheet. They ask which parts of the roadmap are still core to the next milestone that matters for fundraising or revenue, and size the team to that scope rather than applying an across-the-board percentage cut that leaves every team understaffed for what it is still expected to deliver. This usually means some functions shrink more than others, and being able to explain that logic to both departing and remaining employees is part of what keeps the process fair rather than arbitrary.
The most damaging mistake is announcing a cut before the details are ready. Founders under pressure sometimes tell the company "layoffs are coming" to relieve their own anxiety about the decision, without having severance terms, a final list, or a communication plan ready. This creates weeks of uncertainty where the entire team wonders who will be affected, which tanks morale and productivity far more than the layoff itself eventually does.
A second mistake is cutting evenly across every team regardless of the roadmap. An across-the-board ten percent cut feels fair on a spreadsheet, but it often leaves some teams unable to deliver what is still expected of them while other teams end up overstaffed relative to a shrinking scope. The better approach, as described above, is to decide what the company will and will not attempt to build over the coming months first, and let team sizing follow from that.
A third mistake is letting the manager of a departing employee find out at the same time as the employee, or worse, after. Managers need to be briefed and prepared before their direct reports are, both so they can support their team through the transition and so they are not blindsided in front of the person they manage.
A fourth, subtler mistake is treating the remaining team's questions as a distraction from getting back to work. Employees who just watched colleagues lose their jobs need space to process it, ask questions, and hear directly from leadership more than once. Founders who try to move past it too quickly, out of a desire to restore normalcy, often find that unaddressed anxiety resurfaces as attrition a few months later instead.
Founders navigating this decision often benefit from revisiting how the company's equity and cash obligations were structured in the first place. Startups that got their cap table and equity commitments right early tend to have more flexibility during a downsizing, because they are not also untangling messy vesting or advisor equity disputes in the middle of an already difficult process.
It is also worth acknowledging that the founder's own capacity to lead through this matters; the toll a downsizing takes is closely related to the broader theme of sustainable founder pace, and founders who are already running on empty tend to make worse decisions under this kind of pressure.
It also helps to remember that a downsizing is rarely a single event in the life of a company; it is a moment that gets referenced for years afterward, in how alumni talk about the company, in how remaining employees describe leadership to future recruits, and in how the founder personally reflects on the decision. Treating the process with the same rigor given to a fundraising close or a major product launch, rather than as an unpleasant task to get through quickly, tends to produce outcomes the founder does not regret revisiting later. Founders who have been through this once often say the second time, should it ever come, is handled with far more calm and clarity, simply because the process itself is no longer unfamiliar, and because they already know which parts of the checklist matter most in the first forty-eight hours.
A downsizing is one of the hardest decisions a founder makes, and there is no version of it that feels good. What separates a downsizing that damages a company from one that sets it up to recover is preparation: honest runway math, a principled org shape, fast and dignified execution, and a credible plan communicated quickly to the people who remain. For example, a company that spends an extra week planning the process properly, rather than rushing to cut costs the same week the problem becomes clear, often comes out the other side with a team that trusts leadership more, not less, because they watched the company handle a genuinely hard moment with integrity.