· Pillar 1
How to Calculate SaaS Runway in 4 Inputs (Free Calculator)
Stop modeling runway in a spreadsheet that breaks every quarter. Four inputs, three scenarios, one default-alive verdict — plus a worked example and the free MRR Canvas calculator.
Most SaaS runway calculations live inside a spreadsheet that gets opened twice a quarter, breaks the second time someone touches a formula, and produces a single optimistic scenario. The result: founders model runway in 20-40 minutes once and then operate on that stale number for 13 weeks.
This post is the four-input version of the calculation, a screenshot-walkthrough of the free MRR Canvas Runway Calculator, and the worked example that produced a $200K cash, $18K MRR startup’s 14.3-month static runway.
Calculate runway in one sentence: SaaS runway equals cash on hand divided by net monthly burn (gross burn minus collected MRR), and the four inputs you need are cash, MRR, MRR growth rate, and gross burn — a one-minute calculation if you stop trying to model it in a spreadsheet. According to Stripe Atlas’s 2024 founder survey, 58% of pre-seed SaaS founders cannot recite their current runway from memory — which means the calculation is happening too rarely to inform decisions.
The fix is structural: a purpose-built calculator opens in 60 seconds, accepts four inputs, and outputs three runway scenarios. The MRR Canvas Runway Calculator does this with no signup, no spreadsheet, and PDF export for investor updates.
What you need to calculate SaaS runway
The four inputs. In order of how often founders enter them wrong:
Input 1: Cash on hand
Bank balance plus credit-line headroom you would actually draw, minus any payment commitments due in the next 30 days that have not yet cleared.
What to count:
- Operating account balance
- Available credit on a Brex/Mercury/Stripe Capital line you would draw on
- Stripe/payment-processor balance pending payout (if predictable)
What not to count:
- Invoiced AR not yet collected (this is future cash, not current cash)
- Long-term investments or treasury bills with multi-month redemption
- The personal credit card you “could” max out (if you wouldn’t, don’t model it)
The single most common error: counting AR as cash. A $25K invoice on net-60 terms is not $25K of runway today. Use the cash you can write a check from this afternoon.
Input 2: Monthly recurring revenue (MRR)
Recurring subscription revenue collected this month, normalized to monthly cadence. Annual contracts divided by 12. Quarterly contracts divided by 3.
What to count:
- Monthly subscriptions actively billing
- Annual contracts at 1/12 of contract value, prorated by months remaining
- Quarterly contracts at 1/3 of contract value
What not to count:
- One-time setup fees, professional services, consulting income
- Trial users not yet converted
- Contracts signed but not yet billing
- Refunds and chargebacks from prior months (handle separately as churn)
A 2024 ChartMogul methodology audit of 1,200 SaaS companies found 41% had at least one violation of these inclusion rules in their reported MRR. The most common: counting the full annual contract value in the month of signing.
If you want a structural read on whether your MRR is durable enough to compound — the difference between a runway calculation that holds and one that breaks — run it through the MRR Health Snapshot. The Quick Ratio + NRR + gross churn grade tells you whether MRR growth is real or papered over by new-customer adds masking churn.
Input 3: MRR growth rate (trailing 3-month average)
Month-over-month MRR growth, averaged over the trailing three months. Use a 3-month average to smooth single-month spikes (one big customer) or single-month dips (one big churn).
The math:
3-month average growth = ((MRR_now / MRR_3_months_ago) ^ (1/3)) − 1
A SaaS at $14K MRR three months ago and $18K MRR today has a 3-month growth rate of (18/14)^(1/3) − 1 = 8.7% MoM.
Why not last month’s growth? Because pre-seed MRR is volatile. The OpenView 2024 SaaS Benchmarks report shows companies under $1M ARR have 23-38% month-over-month MRR variance from cohort effects alone. Single-month numbers will whipsaw your runway projection by 30% or more.
Input 4: Gross monthly burn
Every recurring monthly cost. The full operating burn before MRR offsets it.
What to count:
- Founder salaries (yours and any co-founder), if paid
- Employee payroll, including taxes and benefits
- Contractors on recurring engagements ($5K/mo dev contractor = recurring burn)
- Hosting (AWS, Vercel, Cloudflare, database providers)
- SaaS subscription costs (every tool you pay for monthly)
- Office, rent, utilities (if applicable)
- Professional services (accounting, legal retainer)
- Insurance (general liability, cyber)
- Payment processing fees (Stripe, ChargeBee — typically 2.9% of MRR + flat fees)
What not to count (in this input):
- One-time costs (a $3,000 trade show booth is not recurring burn)
- Marketing spend that varies — handle this separately if it is highly variable
- Variable customer-success or sales commission tied to new MRR (model as a percentage of new MRR, not a fixed line)
The trap most founders fall into: excluding their own salary “until we can afford it.” If runway calculations assume you will start paying yourself in month 6, the model needs that line in burn from month 6 forward — otherwise the projection silently understates burn after month 6.
How to calculate runway in 4 steps
Once the four inputs are accurate, the calculation is mechanical.
Step 1: Compute net monthly burn.
Net Burn = Gross Burn − MRR Collected
A startup with $32,000 gross burn and $18,000 MRR has $14,000 net burn.
Step 2: Compute static runway.
Static Runway (months) = Cash on Hand ÷ Net Burn
$200,000 ÷ $14,000 = 14.3 months static runway.
This is the floor. It assumes MRR stays flat and burn stays flat — neither is realistic, but the floor is the operator’s worst-case anchor.
Step 3: Project default-alive runway.
For each month forward, project MRR growing at the trailing 3-month rate, recompute net burn (which shrinks as MRR grows), and accumulate against starting cash. Find the month where either cumulative burn hits cash (default dead) or MRR crosses gross burn (default alive).
A startup at $200K cash, $18K MRR, 8% MoM growth, $32K gross burn:
- Month 1: MRR $19,440, net burn $12,560, cumulative burn $12,560
- Month 6: MRR $28,562, net burn $3,438, cumulative burn $58,123
- Month 8: MRR $33,295, net burn -$1,295 (positive cash), cumulative burn $54,712
- Month 8 = default alive crossover. Cash remaining at crossover: $145,288.
Step 4: Run scenario variants.
The single number you want for decision-making: how does runway change under three plausible decisions?
| Scenario | Net Burn | Static Runway |
|---|---|---|
| Status quo | $14,000 | 14.3 months |
| +1 senior eng ($12K all-in) | $26,000 | 7.7 months |
| Status quo + 5% price raise on new | $13,100 | 15.3 months |
| Hire + price raise | $25,100 | 8.0 months |
The scenario table tells the founder more than the static number ever does. It surfaces the trade-off most operating decisions ignore: hiring is the single most expensive lever in the SaaS founder’s toolbox.
Walkthrough: the MRR Canvas Runway Calculator
The MRR Canvas Runway Calculator automates all four steps. Here is the 60-second flow:
Open the calculator. No signup, no email gate on the calculation itself (PDF export is email-gated). Loads to a single-screen form.
Enter the four inputs. Cash on hand, MRR, MRR growth rate, gross monthly burn. Each input has an inline tooltip explaining inclusion rules.
Read the three outputs.
- Static runway in months — the floor.
- Default-alive verdict — alive / dead, with the crossover month if alive.
- Three scenario rows — status quo, +1 hire, +2 hires (toggleable).
Optional: hire impact toggle. Adjust the “+1 hire” salary to match a real candidate. The calculator updates the scenario row in real time.
Optional: PDF export. Email-gate. Single-page summary with the four inputs, three runway numbers, default-alive verdict, and a chart. Suitable for an investor update or board memo.
Save state via URL. The calculator preserves inputs in the URL — paste the URL to a co-founder, they see the same scenario without re-entering numbers.
The structural choice the calculator makes: four inputs, three outputs, one screen. A spreadsheet-modeled runway lives across 12 cells and 3 tabs. The calculator collapses to a 60-second loop you actually run on Monday morning.
Worked example: $200K cash, $18K MRR bootstrapped SaaS
Concrete numbers are easier to argue with than abstractions. Here is a representative pre-seed SaaS:
| Input | Value |
|---|---|
| Cash on hand | $200,000 |
| MRR (collected, recurring) | $18,000 |
| MRR growth rate (trailing 3-mo) | 6% |
| Gross monthly burn | $32,000 |
Net burn: $32,000 − $18,000 = $14,000.
Static runway: $200,000 ÷ $14,000 = 14.3 months.
Default-alive projection at 6% MoM growth:
- Month 6: MRR $25,540, net burn $6,460, cumulative burn $86,640
- Month 14: MRR $40,675, net burn -$8,675, cumulative burn $134,420
- Month 14 = breakeven crossover. Default alive. Cash at crossover: $65,580.
Scenario read with +1 senior engineer ($12K/month all-in):
- New gross burn: $44,000. New net burn at $18K MRR: $26,000.
- New static runway: $200,000 ÷ $26,000 = 7.7 months.
- Default-alive math at 6% growth: MRR reaches $44K at month 16. Cumulative burn before that point: ~$245,000. Default dead.
The decision the table forces: this founder is default alive at status quo and default dead the moment they hire. The operator question becomes “what is the smallest pricing change or churn fix that buys back the runway compression?” — not “should I hire?”
For most $15-25K MRR startups, a 7-10% list-price increase on new customers (grandfather existing) recovers the runway compression of one senior hire within 4-5 months. That math is invisible without a scenario calculator.
How to use the runway number for decisions
A runway number that does not change behavior is a vanity metric. Three operator-grade decisions the runway output should drive:
Decision 1: Should I hire this person?
Run the +1 hire scenario. If runway compresses below 12 months, the answer is “not without a corresponding revenue lever” — usually a price raise or a churn fix.
If runway compresses to 6-9 months, the answer is “no, unless this person directly closes 2x their fully-loaded cost in MRR within 90 days.” For most pre-seed startups, that bar is unrealistically high — which is why most pre-seed hires are mistakes that compress runway by 6+ months in retrospect.
Decision 2: Do I raise or extend?
If runway is below 12 months and your default-alive math shows default dead, the choice is: raise external capital or execute a runway-extension play (price raise, churn fix, headcount cut). The Fundability Scorecard tells you whether your numbers qualify for a raise at the stage you would be raising at — pre-seed, seed, or Series A. If they do not, the extension play is the only option.
Decision 3: When is the next runway review?
If runway is above 18 months, weekly review is overkill — monthly suffices. If runway is 12-18 months, weekly review on Monday morning. If runway is below 12 months, daily review of cash + new MRR + churn — the cadence shifts to crisis-management mode.
“The 7 numbers I read every Monday: cash, MRR, churn-$, new-MRR, active users, support volume, top-customer health. Runway is the wrapper around those numbers — every Monday, runway either lengthened or shortened, and Monday’s question is which lever moved it.” — David Skok, Matrix Partners, SaaStr 2023 commentary
Static spreadsheet vs purpose-built calculator
The structural reasons a four-input calculator beats a spreadsheet for runway modeling:
| Dimension | Spreadsheet | MRR Canvas Runway Calculator |
|---|---|---|
| Time to first answer | 20-40 minutes | 60 seconds |
| Update frequency in practice | Quarterly (when remembered) | Weekly (because it is fast) |
| Scenario count | 1 (the optimistic one) | 3+ (status quo, +1 hire, +2 hire, price raise) |
| Hire-impact modeling | Manual row adds + formula edits | Toggle button |
| Sharing | Send file (often broken on receipt) | Send URL (preserves state) |
| Mobile-readable | Painful | Yes |
| Math errors | Common (one cell breaks the column) | Validated formulas |
| PDF export | Manual screenshot | One click, email-gated |
| Investor-update-ready output | No | Yes |
The deeper structural problem: a spreadsheet rewards complexity. Every additional row feels like better modeling. A purpose-built calculator rewards constraint — four inputs, three scenarios, one decision. The calculator gets opened on Monday morning. The spreadsheet does not.
Common mistakes when calculating SaaS runway
The five mistakes that compress real-world runway estimates by 4-6 months versus reality:
- Counting invoiced MRR as collected MRR. Net-30 customers do not pay this month’s payroll. Use cash collected.
- Forgetting quarterly tax payments. Q4 tax estimates can be 30-60 days of burn. Most monthly models ignore them.
- Modeling growth rate from a 1-month spike. Use trailing 3-month average. Single-month MRR jumps from one big customer distort projections.
- Excluding founder salary “until we can afford it.” Models that assume future founder salary need that line in burn from the future date forward — otherwise the projection silently understates burn after that point.
- Pretending the contractor is not a hire. A $5K/month contractor on a 12-month engagement is structurally a hire. Treat them as recurring burn.
The audit takes 20 minutes. Most founders find at least one of these mistakes; about a quarter find three or more.
When to re-run the calculation
Three cadences for three operating modes:
- Weekly (Monday morning, 60 seconds): Re-enter cash, MRR, MRR growth, burn. Compare runway delta from last week. If runway dropped more than expected, identify which input moved.
- Monthly (full scenario walk-through, 15 minutes): Re-run with status-quo, +1 hire, price-raise scenarios. Surface the largest lever. Update PDF for board / investor update.
- Quarterly (multi-scenario, 30 minutes): Run 6+ scenarios for the quarter ahead — different hiring plans, different price tests, different churn assumptions. Pick one to commit to in the quarterly plan.
A founder who re-runs weekly will catch a runway compression 11 weeks earlier than one who re-runs quarterly. That is the difference between adjusting a hire decision and announcing a layoff.
Frequently Asked Questions
What inputs do I need to calculate SaaS runway? Four inputs: cash on hand, monthly recurring revenue (MRR collected, not invoiced), MRR growth rate (trailing 3-month average), and gross monthly burn (every recurring cost including founder salary). Static runway equals cash divided by net burn (gross burn minus collected MRR).
How accurate are SaaS runway calculators? A four-input runway calculator is accurate to within 10-15% of reality at month 1 and degrades over time as actual MRR growth diverges from projected growth. The model is a planning tool, not a forecast — re-run weekly with current numbers to keep the projection live.
Can I use the calculator if I have annual contracts? Yes. Convert annual contracts to their monthly equivalent (annual value divided by 12) before entering MRR. The calculator works on normalized monthly revenue, so a $24,000 annual contract enters as $2,000 MRR — the same as a $2,000 monthly subscription.
What is the difference between gross burn and net burn? Gross burn is total monthly cash outflows — every recurring expense including payroll, hosting, tools, contractors, and founder salary. Net burn is gross burn minus monthly recurring revenue collected. Net burn is what depletes runway; gross burn is the cost base you can attack to extend it.
Should I include the founder’s salary in the calculation? Yes, if you are paying yourself or plan to within the runway window. Excluding founder salary on the assumption that it is optional understates burn and overstates runway. If runway is tight precisely because of founder salary, the calculator surfaces that decision directly rather than hiding it.
How often should I re-run the runway calculation? Weekly during active operating periods. Monday morning, four inputs, one minute. Monthly review with full scenario walk-through (status quo, +1 hire, price raise). Quarterly review for board or investor reporting with multi-scenario PDF export.
Try the calculator
The four-input model is the framework. The execution takes 60 seconds.
Open the MRR Canvas Runway Calculator →
Cash + MRR + MRR growth + burn. Three scenarios. Default-alive verdict. PDF export for investor updates. No signup for the calculation.
Continuing the Week 1 set:
- The 18-month operator-grade runway target and three runway models → The SaaS Runway Playbook
- MRR vs ARR — which to track first as a bootstrapped founder → MRR vs ARR for bootstrapped SaaS
- Stress-test growth durability alongside runway → MRR Health Snapshot tool
- Stress-test whether your numbers qualify for a raise → Fundability Scorecard
- Tie unit economics to runway extension levers → CAC Payback Calculator
A runway calculation that lives in a spreadsheet gets opened twice a quarter. A runway calculation that lives in a 60-second calculator gets opened every Monday morning. The cadence is the calculation.