On this page
- What burn rate actually measures (and what it doesn’t)
- How to model three burn rate scenarios that actually help you plan
- Survival mode
- Current trajectory
- Aggressive scaling
- How to extend your runway without killing growth
- When to raise versus bootstrap to profitability
- Where Systems-Led Growth fits
- The burn rate calculation that actually helps you plan
Most SaaS founders know their burn rate number. They don’t know what it actually means.
You might say “we burn $50k a month.” Fine. That tells you nothing about whether you should hire aggressively, cut costs this week, or start fundraising next month. The number on its own is useless without the context around it.
The real question isn’t “what’s our burn rate?” It’s “what’s our burn rate under different scenarios, and which one should we plan for?” Because the gap between planning for your current trajectory and planning for aggressive scaling is the gap between 18 months of runway and 6.
Most skeleton-crew teams calculate burn the lazy way. They take last month’s expenses, subtract revenue, and call it done. That gives you a rear-view mirror. Real decisions need projections that account for revenue growth, upcoming hires, and seasonal swings.
Here’s how to treat burn rate as a planning tool instead of a number you report to your board.
What burn rate actually measures (and what it doesn’t)
Burn rate is your monthly cash outflow minus your monthly cash inflow. There are two versions that matter.
Gross burn is your total monthly expenses, full stop. Net burn is expenses minus revenue. When people say “burn rate,” they almost always mean net burn, because that’s what determines how long your money lasts.
The formula looks simple: total monthly expenses minus monthly revenue equals net burn. The problem lives in the details founders skip.
First, which month do you use? Last month doesn’t predict next month if you’re growing 20% month-over-month or about to hire three people.
Second, how do you handle one-time costs versus recurring ones? That $10k annual software renewal hits your math differently than payroll. Smear it across twelve months and you understate this month’s reality. Drop it in raw and you spook yourself.
The biggest mistake is treating burn rate like a fixed number. If you’re doing your job, next month’s burn won’t match this month’s. Revenue should be climbing. Expenses should be scaling with purpose. A static calculation tells you where you’ve been, not where you’re going.
How to model three burn rate scenarios that actually help you plan
Every founder should run burn under three scenarios: survival mode, current trajectory, and aggressive scaling.
Survival mode
Strip expenses to the bone. Cancel every non-essential subscription. Pause hiring. Cut marketing to zero if you have to. This shows your maximum runway if everything goes sideways. For most early-stage SaaS companies, survival mode drops burn by 40-60%.
Current trajectory
Assume you keep doing exactly what you’re doing. Same growth rate, same hiring pace, same marketing spend. This is your baseline. Use the average of your last three months, adjusted for any known changes you’ve already committed to.
Aggressive scaling
Assume you bet on growth. Double marketing. Hire the engineer and the salesperson you’ve been circling. Upgrade infrastructure. This shows what happens when you push the gas.
Here’s the math that makes it real. A company with $100k in the bank, $10k monthly revenue, and $20k monthly expenses has 10 months of runway at current trajectory. Scale aggressively to $30k in expenses and you have 5 months. Cut to survival mode at $8k in expenses and you have 16+ months.
Same bank balance. Wildly different futures.
Your unit economics tell you which scenario makes sense. Strong economics that just need scale to hit profitability? Aggressive scaling might be the right bet. Weak economics? Survival mode buys you time to fix them before you pour fuel on a leaky engine.
Most founders only ever calculate the middle scenario. The other two are where the actual decisions get made.
How to extend your runway without killing growth
The goal isn’t to minimize burn. It’s to optimize it for your timeline and your growth potential. Those are different things.
Start with the easy wins that don’t touch growth. Audit your software subscriptions and kill anything unused in the last 30 days. Negotiate annual terms with vendors for a discount. Rightsize your cloud bill instead of paying for capacity you don’t use.
Then look at team structure. Consider outsourcing instead of a full-time hire. Delay a senior hire and promote internally. Share resources across functions. A skeleton crew that’s organized well beats a bigger team that isn’t. That’s the entire premise of Systems-Led Growth.
Then optimize revenue, because it extends runway better than cost cutting. Implement usage-based pricing if your product supports it. Offer annual payment discounts to pull cash forward. Point sales at higher-value deals that close faster.
A 20% increase in average deal size has the same runway impact as cutting 20% of expenses, but it compounds differently. Higher revenue per customer improves your unit economics permanently. Cost cuts are a one-time benefit.
The warning signs you’re cutting too deep: customer satisfaction drops, product development stalls, morale crashes. Smart cost management protects growth potential. Desperate cost cutting torches it. The companies that grow through downturns focus on efficiency, not just conservation.
When to raise versus bootstrap to profitability
Your burn rate sets your fundraising timeline. It shouldn’t set your fundraising decision.
If net burn is trending toward zero (revenue growth outpacing expense growth), bootstrapping to profitability might work. Run it: how many months until net burn hits zero? How much total capital to get there? If that number is less than your current runway, you may not need outside money at all.
If burn is stable or rising but your growth metrics are strong, raising makes sense. Investors want to see efficient burn, how much revenue growth you generate per dollar spent.
The timing works backward from your target close date. If you need to raise in 6 months and you have 8 months of runway, you’re cutting it close. Fundraising always takes longer than founders expect, and you need buffer for due diligence and negotiation.
Your model should show multiple funding amounts. How does burn change if you raise $500k versus $2M? What milestones can you hit with each?
The framework is simple. Raise if you need capital to reach the next value inflection point. Bootstrap if you can hit profitability or a meaningful milestone on your current runway. Never raise just because everyone else is.
Where Systems-Led Growth fits
Systems-Led Growth is the practice of building AI-augmented workflows that connect your entire go-to-market motion. Instead of treating content, sales, and customer success as three separate functions, you build systems where one input produces outputs across the full funnel.
A sales call becomes a follow-up email, a one-pager, and content for your next campaign. One webinar becomes ten assets without starting from a blank page every time.
For a skeleton-crew team watching its burn, that matters. SLG is how you grow output without growing headcount, which is the single biggest lever you have on net burn. You can see how we think about it or book a call if you want to talk through your own setup.
The burn rate calculation that actually helps you plan
Your burn rate isn’t a number to track. It’s a tool to make decisions with about hiring, spending, and raising.
The static calculation, last month’s expenses minus revenue, tells you where you’ve been. The scenario-based calculation, modeling different growth and spending assumptions, tells you where you’re going. Most founders need the second one and only run the first.
So do this:
- Update your burn calculations monthly, not quarterly.
- Include upcoming changes to revenue and expenses, not just history.
- Model at least three scenarios: survival, current, aggressive.
- Use those scenarios to make actual decisions about resource allocation and timing.
The question isn’t “what’s our burn rate?” It’s “what’s our burn rate under different scenarios, and which one gives us the best shot at hitting our next milestone?”
That’s the calculation that actually matters.
Related reading: score yourself with the matching audit · start with an audit · read the manifesto · I deleted 140,000 visitors a month on purpose
Frequently asked questions
How often should I recalculate my burn rate?
Monthly, not quarterly. Revenue and expenses move too fast in early-stage SaaS for a quarterly number to be useful for planning. Update your projections whenever you make a significant hiring decision or see an unexpected revenue change.
What's the difference between gross burn and net burn rate?
Gross burn is your total monthly expenses, period. Net burn is expenses minus revenue. Most investors care about net burn because it determines runway, but gross burn matters for understanding your cost structure and spotting where to cut if you have to.
Should one-time expenses be included in burn rate calculations?
Include them in the month they actually hit your cash for cash flow tracking, but keep them out of your baseline burn projections. Track them as discrete events in your runway model rather than smearing them across every month as if they were recurring.
What burn multiple should I target as an early-stage SaaS company?
A burn multiple of 2-3x is a reasonable target, meaning $2-3 of ARR growth per dollar of net burn, per Bessemer's benchmarks. Better than 3x is strong efficiency. Worse than 2x usually means you're spending capital without enough growth to justify it.
When should I focus on path to profitability instead of net burn?
Start modeling path to profitability once net burn is consistently decreasing month over month and you can see a clear break-even within your current runway. That usually happens when recurring revenue growth outpaces expense growth.