Most SaaS founders know their burn rate number. They don't know what it actually means.
You might say "we burn $50k per month" but that doesn't tell you whether you should hire aggressively, cut costs immediately, or start fundraising next week. The number alone 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 scenario should we plan for?" Because the difference between planning for current trajectory versus aggressive scaling can mean the difference between 18 months of runway and 6.
Most skeleton-crew SaaS teams calculate burn rate wrong. They look at last month's expenses, subtract revenue, and call it done. Decision-making requires more nuanced projections that account for revenue growth, upcoming hiring plans, and seasonal variations.
Here's how to calculate burn rate as a planning tool, not just a metric to report to your board.
Burn rate is your monthly cash outflow minus your monthly cash inflow. But there are two versions that matter. Gross burn is your total monthly expenses, period. Net burn is your expenses minus your revenue. Most of the time when people say "burn rate" they mean net burn, because that's what determines how long your money lasts.
The formula appears straightforward. Total monthly expenses minus monthly revenue equals net burn rate. But the devil lives in the details most founders skip.
First, which month do you use? Last month's numbers don't predict next month's reality if you're growing 20% month-over-month or planning to hire three people. Second, how do you account for one-time expenses versus recurring costs? That $10k annual software renewal hits your burn calculation differently than your monthly payroll.
The biggest mistake is treating burn rate like a fixed number. Your burn rate next month will be different from this month if you're doing your job right. Revenue should be growing. Expenses should be scaling with purpose. The static calculation tells you where you've been, not where you're going.
[NATHAN: Share the specific burn rate calculation method you used at Copy.ai or other companies, including what variables you tracked and how often you updated projections. Include any mistakes you made in early calculations and what you learned.]
Every SaaS founder should calculate burn rate under three scenarios: survival mode, current trajectory, and aggressive scaling.
Survival mode strips your expenses to the absolute minimum. Cancel every non-essential subscription, pause hiring plans, and cut marketing spend to zero if needed. This calculation shows you maximum runway if everything goes wrong. For most early-stage SaaS companies, survival mode cuts burn rate by 40-60%.
Current trajectory assumes you keep doing exactly what you're doing now. This means maintaining your current growth rate, hiring pace, and marketing spend levels. This is your baseline scenario. Use the average of your last three months, adjusted for any known upcoming changes.
Aggressive scaling assumes you invest heavily in growth. Double your marketing budget, hire that engineer and sales person you've been considering, and upgrade your infrastructure. This scenario shows what happens if you bet big on growth.
Here's the math that matters: a company with $100k in the bank, $10k monthly revenue, and $20k monthly expenses has 10 months of runway at current trajectory. But they have 5 months if they scale aggressively to $30k monthly expenses, or 16+ months if they cut to survival mode at $8k monthly expenses.
The SaaS unit economics inform which scenario makes sense. If your unit economics are strong but you need scale to reach profitability, aggressive scaling might work. If your unit economics are weak, survival mode buys you time to fix them.
Most founders only calculate the middle scenario. The other two scenarios are where the real decisions get made.
The goal isn't to minimize burn rate. It's to optimize it for your timeline and growth potential.
Start with the easy wins that don't impact growth: audit your software subscriptions and cancel anything unused in 30 days, negotiate annual payment terms with vendors for discounts, and optimize your cloud hosting bill by rightsizing server capacity.
Then look at your team structure. Consider outsourcing instead of hiring full-time, delaying that senior hire to promote internally, or sharing resources across functions. A skeleton crew that's organized well can outperform a larger unorganized team.
Revenue optimization extends runway better than cost cutting. Implement usage-based pricing if your product supports it. Offer annual payment discounts to improve cash flow. Focus sales efforts on higher-value deals that close faster. A 20% increase in average deal size has the same runway impact as cutting 20% of your expenses, but it compounds differently because higher revenue per customer improves your unit economics permanently while cost cuts provide only one-time benefits.
The warning signs you're cutting too deep: customer satisfaction drops, product development stalls, or team morale crashes. Smart cost management preserves growth potential. Desperate cost cutting kills it.
According to Battery Ventures Operating Manual, 60% of SaaS companies extend runway primarily through revenue growth rather than cost cuts. The companies that grow through economic downturns focus on efficiency, not just conservation. ProfitWell's 2023 SaaS Metrics Report shows that companies maintaining growth investments during cash crunches recover 3x faster than those that cut aggressively.
Your burn rate calculation determines your fundraising timeline. However, it shouldn't determine your fundraising decision.
If your net burn rate is trending toward zero (revenue growth exceeding expense growth), bootstrapping to profitability might work. Run the numbers: how many months until net burn hits zero? How much total capital do you need to get there? If the answer is less than your current runway, you might not need outside funding.
If your burn rate is stable or increasing but your growth metrics are strong, fundraising makes sense. VCs want to see efficient burn: how much revenue growth you generate per dollar spent. Bessemer's 2024 State of the Cloud shows median burn multiples of 2-3x for early-stage SaaS companies (meaning $2-3 of ARR growth per dollar of net burn).
The timing calculation works backward from your target close date. If you need to raise in 6 months and your current burn rate gives you 8 months of runway, you're cutting it close. Fundraising takes longer than founders expect, and you need buffer time for due diligence and negotiation.
Your financial model should show multiple scenarios with different funding amounts. How does your burn rate change if you raise $500k versus $2M? What milestones can you hit with each amount?
The decision framework: raise if you need capital to reach the next value inflection point. Bootstrap if you can reach profitability or significant milestones with current runway, and avoid raising capital simply because other companies are raising.
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 separate functions, SLG creates 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 scratch each time. For skeleton-crew SaaS teams managing burn rate, SLG maximizes output without adding headcount. Learn more about the complete framework.
Your burn rate isn't just a number to track. It's a planning tool that helps you make decisions about hiring, spending, and fundraising.
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.
Update your burn rate calculations monthly, not quarterly. Include upcoming changes to revenue and expenses. Model at least three scenarios. Use the scenarios to make decisions about resource allocation and timeline planning.
The question isn't "what's our burn rate?" It's "what's our burn rate under different scenarios, and which scenario gives us the best chance of hitting our next milestone?" That's the calculation that actually matters.
Calculate burn rate monthly, not quarterly. Revenue and expenses change too quickly in early-stage SaaS for quarterly calculations to be useful for planning. Update your projections whenever you make significant hiring decisions or see unexpected revenue changes.
Gross burn is your total monthly expenses regardless of revenue. 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 identifying areas to cut if needed.
Include one-time expenses in the month they occur for cash flow tracking, but exclude them from your baseline burn rate projections. Track them separately and factor them into your runway calculations as discrete events rather than recurring monthly costs.
Model seasonal patterns separately if they're significant to your business. For example, if you typically see 30% higher expenses in Q4 due to conference season or holiday bonuses, build that into your projections rather than using a flat monthly average.
Target a burn multiple of 2-3x (meaning $2-3 of ARR growth per dollar of net burn) according to Bessemer's benchmarks. Better than 3x is excellent efficiency, worse than 2x suggests you're burning capital without sufficient growth to justify it.
Start modeling path to profitability when your net burn rate is consistently decreasing month-over-month and you can see a clear timeline to reaching break-even within your current runway. This typically happens when monthly recurring revenue growth exceeds expense growth rate.