Your board meeting is in eleven days. The CFO slides a single number across the table: nine months of runway. Nobody says the word "layoffs" out loud, but it's sitting in the room like a chair nobody wants to acknowledge. You already know what the easy move is. You also know it's the one that will cost you your best engineer, the one who just closed the biggest deal of her career, and half the team that made the last two quarters work.
Reducing your burn rate without cutting people is harder than cutting people. That's the honest version. It requires you to look at every line of your expense sheet as if you were an outsider auditing your own company, and to make decisions you've been avoiding for months because they felt small. They aren't small. Here's how to actually do it.
Key takeaways
- Payroll is usually the biggest line item, but it is rarely the only one with slack. SaaS, cloud, office space, and contractor spend typically hide 15–30% of recoverable cost.
- Renegotiating existing contracts almost always beats cancelling and re-signing. Vendors would rather keep 80% of the deal than lose 100% of it.
- A hiring freeze is not a layoff, but it only works if you freeze it for everyone, including the two roles you were "definitely" going to fill.
- Salary deferrals and voluntary reduced-hours programs beat forced pay cuts because they preserve trust—the single asset that's hardest to rebuild.
- Cutting growth spend is seductive and usually wrong. Cut fixed costs first, then look at variable spend with unit economics in mind.
- You have more runway-levers than you think: payment terms, subletting, deferred capex, and renegotiated insurance renewals.
Why reducing burn without layoffs is a different problem
Layoffs are the fastest lever. They're also the most expensive one once you account for the second-order effects: severance, recruiting costs when you rehire in eighteen months, and the morale hit that shows up quietly in your next two quarters of output. Most founders I've talked to who went through a layoff round describe the same thing—the number on the spreadsheet improved, and the team never quite came back to the same operating rhythm.
So the real constraint isn't "how do I cut 20% of costs." It's "how do I cut 20% of costs without touching the people who generate the revenue." That constraint changes what you look at first. It pushes you toward fixed costs, vendor contracts, and everything that isn't a salary.
What the burn rate actually measures
Your burn rate is how much cash leaves the business in a month, net of what comes in. Gross burn is total spend; net burn subtracts revenue. Runway is cash divided by net burn. If you're at $400,000 in the bank and burning $50,000/month net, you have eight months. That's the arithmetic. The strategic question is which of those $50,000 you can remove without breaking the machine that produces the revenue on the other side.
Which is why the first move is not "cut." It's "audit."
The 90-day expense audit that actually finds money
I ran this exercise on a project where the founders were convinced the only path to a lower burn was a headcount reduction. Three weeks later, we'd found $37,000/month in savings that had nothing to do with salaries. Here's the order I use now.
Start with the boring fixed costs
Pull every recurring charge from the last 90 days. Not the annual ones—the monthly ones that have been quietly renewing since before you had a finance person. Sort them by amount and by "when did we last actually use this."
- SaaS subscriptions: a mid-size team I worked with was paying for eleven tools that overlapped in functionality. Two of them nothing had logged into in four months.
- Cloud compute: idle staging environments, over-provisioned instances, log retention set to "forever" because nobody changed the default. This is often the second-largest recoverable line after payroll.
- Office space: if you signed your lease before 2023, you're likely paying for a floor plan that assumed a headcount you never hired.
- Insurance and professional services: renewal letters that get auto-approved every year because they look administrative.
None of these are dramatic. Together they add up. On that project, the recurring-charge audit alone recovered roughly $12,000/month—annualized, that's close to one junior salary, without losing anyone.
Then go after the big contracts
Your cloud provider, your CRM vendor, your data warehouse, your legal firm—these are the contracts with room. Most of them will not discount on a phone call. What works is a written request that lays out the situation plainly: you're committed to the relationship, you need to reduce the annual commitment, and here are the terms that would let you stay. Vendors hate churn more than they hate a smaller invoice.
A pattern I've seen repeat: ask for a 12-month commitment at a lower rate rather than a month-to-month at the current rate. You trade flexibility for a smaller number, and if you're confident in the vendor, that's a good trade.
Growing your way out vs cutting your way down
There's a version of this where you cut so aggressively that you hit profitability on paper and lose the growth that made the company investable. The framework I use to avoid that mistake is simple: cut fixed costs hard, protect variable costs tied to revenue, and be surgical about everything in between.
| Cost category | Cut priority | Why |
|---|---|---|
| Idle SaaS & unused licenses | Immediate | Zero impact on output, instant savings |
| Office footprint | High | Fixed cost, often renegotiable or sublettable |
| Cloud over-provisioning | High | Engineering-led, no headcount effect |
| Paid acquisition | Medium | Cut only if CAC payback is already long |
| Contractor / agency spend | Medium | Reduce scope, not relationships |
| Payroll | Last | Only after every other lever is exhausted |
Notice that paid acquisition is above payroll but below the boring stuff. That ordering matters. Cutting marketing when your CAC payback is healthy is the most common mistake founders make under pressure—they confuse "spend" with "waste," and it costs them the next two quarters of pipeline.
How to keep paying people when you can't keep paying them the same
If you've exhausted the non-payroll levers and you still need more runway, you have options that aren't layoffs. None of them are painless, and none of them work without transparency.
- Hiring freeze: freeze every open role, including the ones you've already interviewed for. Announce it, don't let it leak.
- Voluntary reduced hours: offer a 4-day week at 80% pay for anyone who wants it. Some people will take it. The ones who don't, stay whole.
- Salary deferral: deferred compensation paid back after a set milestone, with interest. Founders should defer first and the most.
- Contractor conversion: move roles that don't need full-time coverage to part-time or project-based arrangements, with the person's consent.
- Internal redeployment: before you cut a role, ask whether that person can absorb work from another function that you were about to hire for.
The mistake I see most often is doing these in private and announcing them as facts. That reads as a dress rehearsal for layoffs. Doing them with the team—explaining the runway math, showing the levers you've already pulled—turns them into a shared decision. And a shared decision survives the quarter.
What not to cut
Some spending looks like fat and is actually muscle. Be careful with these, because the savings are real but the cost is invisible until it isn't.
- Customer support headcount: the first thing to feel a cut is churn, and churn takes two quarters to show in the numbers.
- Engineering velocity: cutting dev tooling to save $2,000/month while slowing the team by 10% is a bad trade every time.
- Onboarding and enablement: if you freeze hiring, you still have people joining from offers already signed. Don't strand them.
- Anything that produces revenue: if a line item has a measurable, positive payback, it's not a cost, it's an investment.
Real talk: the cuts that feel heroic are often the ones that hurt most. The cuts that feel boring are the ones that actually extend runway.
The part nobody puts in the deck
Reducing burn without layoffs isn't a single decision, it's a stack of them—each one small, each one requiring you to ask someone for something they'd rather not give. A vendor to renegotiate. A team to hold off on hiring. A landlord to talk to. A board to walk through the math with.
What makes it work is doing all of them, in order, before you touch the thing you were told was the only leverage you had. The founders who come out the other side of a tight year without losing their team aren't the ones who found a clever trick. They're the ones who did the boring work first.
Which leaves one question worth sitting with: if you had to cut 20% of your burn tomorrow without losing a single person, what's the first thing you'd actually look at? If you know the answer, you already know where to start. If you don't, that's the audit talking.
