Runway is the number that governs every major decision a SaaS company makes. Whether to hire, whether to expand into a new segment, whether to start the next fundraise — all of it flows back to how many months of cash remain. Yet the calculation trips up founders more often than it should, because there are two burn rate variants that produce very different answers, and several common inputs that quietly distort the number.
This guide covers how to calculate SaaS runway precisely: the core formula, gross burn vs. net burn, worked examples at pre-revenue and growth stages, three-scenario modeling, investor expectations by round, and the six operational moves that extend runway without touching the cap table.
In This Guide
- ✓The SaaS runway formula and when to use gross vs. net burn
- ✓Worked examples at pre-revenue, $500K ARR, and $2M ARR stages
- ✓Three-scenario tables: optimistic, base, and pessimistic
- ✓Investor benchmarks and what they expect at Seed, Series A, and Series B
- ✓Six operational levers to extend runway without dilution
- ✓The five inputs that distort runway calculations and how to fix each
SaaS Runway. The number of months a company can continue operating at its current cash spending rate before its bank balance reaches zero. It sets a hard deadline on every strategic decision — and should be recalculated every time burn or revenue changes materially.
The Core SaaS Runway Formula
The basic calculation has two inputs: the cash balance and the monthly net burn rate.
A few precision notes before working examples:
- Cash on hand means the actual bank balance — not credit lines, not uncollected receivables, not committed but undrawn venture debt.
- Monthly cash revenue means cash actually received in the month — not recognized revenue, not booked ARR. If a customer signed a $120K annual contract in January, you received $120K in January (not $10K/month), and your runway model should reflect when you actually bank each dollar.
- Monthly operating expenses should be fully loaded — salaries, benefits, software subscriptions, rent, contractor payments, and any other cash outflows, including one-time items you expect to recur.
Gross Burn Rate vs. Net Burn Rate
These are the two burn rate variants you will encounter in board decks, investor conversations, and financial models. They measure different things and are used for different purposes.
The distinction matters most once you have meaningful revenue. A company spending $300,000 per month with $180,000 in monthly cash collections has a $300,000 gross burn and a $120,000 net burn. Using gross burn for the runway calculation understates actual cash longevity by 60%.
Use gross burn to benchmark your cost structure — how lean is your team relative to peers at the same stage? Use net burn to calculate how many months you have left and when to start raising.
Worked Example 1: Pre-Revenue Seed Stage
A pre-revenue SaaS company has just closed a $2M seed round. It has three engineers ($22,000/month loaded cost each), a founder-CEO drawing a $10,000 salary, and approximately $8,000/month in tools, AWS, legal retainers, and office costs.
| Expense Category | Monthly Cost |
|---|---|
| Engineering (3 × $22K) | $66,000 |
| Founder salary | $10,000 |
| Infrastructure, tools, legal | $8,000 |
| Gross Burn (= Net Burn at $0 revenue) | $84,000 |
Runway = $2,000,000 ÷ $84,000 = 23.8 months
Just under 24 months — solidly in the target range. If this team hires one more engineer before closing the books on month one, gross burn rises to $106,000 and runway drops to 18.9 months. A single hire costs the company roughly 4 months of runway at this stage.
Worked Example 2: Revenue-Stage Series A Company
A Series A SaaS company has $4.5M in the bank after raising $6M twelve months ago. It has grown to $1.8M ARR and is burning at $280,000 per month in gross expenses. Cash revenue collections run at $155,000/month — the difference between ARR/12 and collected cash reflects some annual contracts paid in arrears and a small amount of churn-related delays.
36 months is a very comfortable position. This company can afford to invest in growth without immediately optimizing for capital efficiency. If it accelerates hiring and gross burn rises to $380,000 per month while revenue stays flat for three months, net burn increases to $225,000 and runway compresses to 20 months — still above the 18-month floor most investors expect, but worth watching.
Three-Scenario Runway Modeling
A single runway number is not a model — it is a snapshot. Board-ready runway analysis presents three scenarios that bound the range of plausible outcomes: optimistic (things go better than planned), base (the operating plan), and pessimistic (a meaningful miss on revenue and/or a cost surprise). Scenario modeling also surfaces the decisions you need to make now — before a miss forces them.
The example below uses the Series A company from Worked Example 2: $4.5M cash, $280,000 gross burn, $155,000 monthly cash revenue at the time of modeling.
| Scenario | Monthly Revenue Growth | Gross Burn Growth | Net Burn at Month 6 | Estimated Runway | Decision Trigger |
|---|---|---|---|---|---|
| Optimistic | +8% MoM | +2% MoM (modest hires) | ~$68,000 | 40+ months | Accelerate hiring plan; consider Series B timing |
| Base | +4% MoM | +3% MoM (planned hires) | ~$107,000 | 28–32 months | Execute plan; begin Series B prep at month 18 |
| Pessimistic | +1% MoM | +3% MoM (hires proceed) | ~$157,000 | 17–20 months | Freeze discretionary hiring; begin Series B raise immediately |
Optimistic: Revenue grows faster than burn. Net burn contracts naturally, runway extends well beyond the next raise. The risk here is over-confidence leading to premature Series B framing before the business has the metrics to support it.
Base: Plan executes as modeled. 28–32 months is comfortable territory. Begin Series B preparation at month 18 to ensure the process concludes with 12 months of runway remaining as a buffer.
Pessimistic: Revenue near-flat while costs grow. Runway falls below the 18-month floor within a few months. The correct action is not to wait and see — it is to freeze discretionary hiring immediately and begin the Series B process, because a fundraise from a position of 12 months remaining is a much harder conversation than from 20 months.
How to Build the Scenario Model
A functional three-scenario runway model has four components:
- Opening cash balance — actual bank balance as of the model start date, not projected.
- Monthly gross burn forecast — headcount additions by quarter, infrastructure scaling assumptions, and one-time items already committed (lease renewals, planned events, etc.).
- Monthly cash revenue forecast — driven by current MRR, assumed growth rate, churn assumption, and timing of cash collection for annual vs. monthly billing.
- Net burn by month — derived as gross burn minus cash revenue for each forward month, not as a single static figure.
Many founders model runway with a static net burn figure — the current month's number, held constant. That produces a number, but it is not a model. Real runway evolves month-by-month as revenue grows (reducing net burn) and as new hires ramp (increasing gross burn). The static approach systematically overestimates runway in growth phases because it ignores the burn inflation from planned hiring.
Investor Benchmarks by Funding Stage
Investors evaluate runway not just as a raw number but in context of stage, growth rate, and capital efficiency. The benchmarks below reflect what most institutional investors consider minimum acceptable runway at each post-raise checkpoint.
| Funding Stage | Typical Raise Size | Expected Runway Post-Raise | Begin Next Raise When | Investor Concern Threshold |
|---|---|---|---|---|
| Pre-Seed | $250K–$1.5M | 12–18 months | 6–9 months remaining | Below 9 months |
| Seed | $1.5M–$4M | 18–24 months | 9–12 months remaining | Below 12 months |
| Series A | $5M–$20M | 18–24 months | 12 months remaining | Below 15 months |
| Series B+ | $20M–$75M+ | 24–30 months | 12–15 months remaining | Below 18 months |
The 18-to-24-month standard post-raise is close to universal across Tier 1 investors. The logic is straightforward: a fundraise process takes 3 to 6 months from the first LP meetings to wire. You want to start with enough runway that you have genuine optionality — the ability to wait for the right lead, negotiate terms, and not be visibly desperate. Starting a raise with 9 months left means you are raising from a position of urgency. Starting with 18 months means you can afford to be selective.
Post-2022, many investors — including Sequoia and Y Combinator in their public guidance — moved toward 24 months as the new minimum for early-stage companies, reflecting the reality that fundraising timelines lengthened significantly in the tighter capital environment.
Burn Multiple: The Efficiency Context Investors Add
Raw runway tells investors how long you have. Burn multiple tells them how efficiently you are growing. Investors evaluate both together.
A company with 24 months of runway and a 0.8x burn multiple is in a strong position by any measure. A company with 24 months of runway and a 3x burn multiple will face hard questions about whether the growth rate justifies the spend — especially if revenue growth slows. Runway and burn multiple together define whether a company is building toward a strong Series B narrative or heading toward a down round.
Five Inputs That Distort SaaS Runway Calculations
Most runway calculation errors trace to one of five inputs being modeled incorrectly. Each one is fixable once you know to look for it.
1. Using Accrual Revenue Instead of Cash Collections
Revenue is often recognized on an accrual basis — spread evenly over the contract period — while cash arrives on a different schedule. Annual contracts billed upfront create a large cash inflow in month one and nothing thereafter for 11 months. Monthly contracts create even, predictable cash flows. If your model uses monthly recognized revenue (ARR ÷ 12) instead of actual cash received, it understates runway when annual billing is large and overstates it when collections are slow.
Fix: Use a cash-basis revenue schedule. Separate your customer base by billing cadence and model actual collection dates, not recognition dates.
2. Static Net Burn (Not Modeling Planned Hires)
Using this month's net burn as a constant for the next 24 months ignores the reality that most SaaS companies are hiring. If you plan to add six people over the next 12 months at an average fully loaded cost of $150,000 per year, that is $75,000 in additional monthly gross burn by month 12 — a factor that does not appear in your current net burn figure at all.
Fix: Build a headcount plan with hire dates and fully loaded costs (salary + benefits + payroll taxes + equipment, typically 1.2–1.3× base). Roll forward gross burn month-by-month using the hire schedule.
3. Omitting Non-Monthly Cash Outflows
Annual software renewals, insurance premiums, D&O policies, audit fees, and legal retainers are all real cash outflows that do not appear in the monthly operating expenses. A $60,000 annual software renewal creates a one-month spike that reduces runway by half a month more than the base model suggests.
Fix: Maintain a list of annual and quarterly cash commitments. Normalize them to a monthly equivalent in your burn rate, or model them as discrete line items in the month they hit.
4. Including Committed-But-Undrawn Credit
Venture debt commitments, revolving lines of credit, and SAFE notes that have been signed but not yet wired do not belong in the "cash on hand" figure until the cash is actually in your bank account. Including uncommitted capital inflates the runway number and creates dangerous false confidence.
Fix: Run two scenarios: one with current bank balance only, and one with bank balance plus confirmed venture debt draws timed to when you plan to draw them.
5. Ignoring Revenue Churn in the Forward Model
Runway models built on optimistic growth assumptions often bake in best-case new ARR while ignoring churn. If your gross revenue churn is 2% per month and your model assumes flat churn, you will overstate revenue by a compounding amount in each forward period. At a 2% monthly churn, a $150,000 MRR base churns down to $126,000 by month 9 without any new bookings — a $24,000/month swing in net burn that adds up quickly.
Fix: Use historical gross churn data (not net churn) as the baseline churn assumption in your revenue model. Test sensitivity by running the pessimistic scenario with 1.5× your historical churn rate.
Six Operational Levers to Extend SaaS Runway
Extending runway operationally — without raising additional capital — requires either reducing gross burn or accelerating cash revenue. The six levers below are ranked roughly by speed of impact and reliability of outcome.
1. Freeze Discretionary Hiring
Payroll accounts for 60 to 80% of operating expenses in most SaaS companies. Each hire forgone directly reduces gross burn. A hiring freeze does not eliminate headcount cost from existing employees, but it stops the scheduled cost increases from open requisitions. If your plan called for six hires over the next six months at an average fully loaded cost of $180,000 per year, freezing those hires preserves approximately $90,000 per month in gross burn — often worth 6 to 12 months of additional runway depending on your burn rate.
2. Convert Monthly Subscribers to Annual Plans
Customers on monthly billing pay monthly. Customers on annual billing pay 12 months upfront — and their cash hits your account immediately. Offering a 10 to 15% discount for annual prepayment is a net-positive tradeoff in most scenarios: you give up some total contract value in exchange for cash today. A $5K/month customer converting to a $51K annual deal (15% discount) adds $51,000 to your bank balance in month one versus the $5,000 you would have received on the old billing cycle.
3. Accelerate Collections on Outstanding Invoices
Net-30 and net-60 payment terms are common in SMB and mid-market SaaS. Aged receivables — invoices more than 30 days past due — represent cash that is yours but not yet in your bank account. An aggressive collections push can bring 30 to 90 days of revenue forward into the current period. For a company with $500,000 in outstanding receivables, even recovering half within a month meaningfully extends the practical runway horizon.
4. Eliminate Non-Revenue-Generating Software
Most companies carry a software subscription tail that has grown unchecked since the last budget cycle. Tools with zero or low active usage, duplicate functionality, and expired contracts that auto-renewed are all candidates for immediate cancellation. A focused audit of software spend routinely surfaces $10,000 to $50,000 in annual eliminations. That number sounds small, but at a $100,000 net burn rate, eliminating $30,000 in annual software costs adds roughly 3.6 months to runway by reducing monthly gross burn by $2,500.
5. Renegotiate Vendor Contracts
Vendors — cloud providers, data vendors, outsourced services — often have more flexibility on pricing than they initially present, particularly when you signal the alternative is churn. AWS credits programs, renegotiated base-tier pricing for key SaaS tools, and restructuring outsourced support contracts can reduce gross burn by 5 to 15% without eliminating any capability.
6. Add Venture Debt as a Non-Dilutive Bridge
Venture debt — from lenders like Silicon Valley Bank (now First Citizens), Hercules Capital, or Triple Point Ventures — can extend runway by 6 to 18 months without equity dilution beyond the warrant coverage typically attached to the facility. The right time to draw venture debt is when the business fundamentals are strong: growing revenue, acceptable churn, and existing institutional investors willing to support the company. Venture debt used as a last-resort bridge when fundamentals are deteriorating tends to end badly — lenders have covenants, and a covenant breach in a weak position forces a difficult conversation.
The general rule: use venture debt to extend an already-healthy runway, not to rescue a company that is approaching zero.
| Lever | Time to Impact | Typical Runway Extension | Dilutive? | Best For |
|---|---|---|---|---|
| Hiring freeze | Immediate | 3–12 months | No | Any stage with open reqs |
| Monthly to annual conversion | 1–4 weeks | 1–4 months | No | Companies with >50% monthly billing |
| Accelerate collections | 2–6 weeks | 1–2 months | No | Companies with aged receivables |
| Cut unused software | 1–8 weeks | 1–3 months | No | All companies |
| Renegotiate vendor contracts | 4–12 weeks | 1–4 months | No | Companies with $500K+ ARR |
| Venture debt | 4–10 weeks | 6–18 months | Minimal (warrants) | Series A+ with strong metrics |
When to Start Your Next Fundraise
The tactical rule is simple: begin your next fundraise when you have 12 to 15 months of runway remaining. This gives you a 3-to-6-month buffer for the process itself (first meetings to term sheet typically takes 2 to 4 months; due diligence and close takes 1 to 2 months more), plus a 6-to-9-month reserve after close.
A more useful frame is to track the distance between your current runway and your target runway at close. If the goal is 18 months post-close and your current runway is 14 months, you need to close within 2 months or your close-date runway will fall below target. That math tells you when to start, not just when to panic.
"The best time to raise is when you don't need to. The worst time to raise is when you do." — Conventional VC wisdom, borne out in almost every down round story.
One common mistake: founders wait for a cleaner story before starting the process. They want one more quarter of growth, one more logo, one more metric at a threshold. Each delay burns down the negotiating cushion. Start the process with a good story, not a perfect one — because perfect is usually two quarters away and you may not have two quarters to spare.
Monthly Runway Review Checklist
Runway is a living number. It should be updated every time the books close for the month and reviewed against the scenario model. The following checklist captures the essential inputs:
- Update the actual bank balance (cash basis, not accrual).
- Reconcile actual gross burn to the plan — identify any new vendors, unexpected expenses, or lower-than-expected payroll from unfilled seats.
- Update actual cash revenue collected — separate from booked ARR to account for billing timing.
- Recalculate net burn for the current month and compute trailing 3-month average.
- Recompute runway using trailing average net burn as the base case.
- Update the forward model for any planned hires, contract renewals, or known one-time items in the next 90 days.
- Flag the scenario trigger points — at what cash balance does the pessimistic scenario require immediate action?
A monthly cadence for this review is the minimum. Companies with volatile burn or fewer than 15 months of runway should run a weekly cash position update as well — a simpler calculation that tracks the actual bank balance against the model to catch surprises early.