Published by the Uniflow AI editorial team
SaaS Runway Calculator: Model Hiring, Pricing, Burn, and Fundraising Scenarios
A SaaS runway calculator estimates how long a software company can operate before its cash balance reaches a defined minimum. The useful version is a monthly, driver-based model that connects opening cash, customer collections, churn, pricing, hiring, expenses, debt, taxes, and fundraising.
A simple cash-divided-by-burn calculation is only reliable when receipts and expenses remain stable. For a growing SaaS company, the real question is more practical:
Which decisions will cause cash to fall below its minimum reserve, and when?
This guide provides the formula, required inputs, a worked example, scenario rules, and a framework for deciding when to hire, change pricing, reduce spending, or raise capital.
How does a SaaS runway calculator work?
A SaaS runway calculator projects monthly cash inflows and outflows, then identifies the first month in which closing cash falls below the company’s minimum operating balance. The model should show both the cash-out month and the assumptions that caused it, rather than returning only one average number of runway months.
Use this monthly equation:
Closing cash
= Opening cash
+ Cash collected
+ Financing proceeds
- Payroll and benefits
- Operating expenses
- Taxes, interest, and debt repayments
- Financing fees
Runway ends when closing cash reaches the minimum cash threshold—not necessarily when the bank account reaches zero. The threshold may need to cover:
- Payroll and benefits
- Tax liabilities
- Debt service
- Customer refunds
- Committed vendor expenses
- A board- or lender-required reserve
A calculator should return at least these outputs:
| Output | What it tells you |
|---|---|
| Closing cash by month | Whether cash remains above the operating threshold |
| Gross burn | The company’s total monthly cash cost before receipts |
| Net burn | The monthly cash reduction after receipts |
| Cash-out month | When cash falls below the minimum threshold |
| Minimum projected cash | The lowest point in the forecast |
| Hiring deadline | The latest safe date for a planned hire |
| Fundraising deadline | When financing preparation must begin |
| Sensitivity ranking | Which assumptions have the greatest effect on runway |
Y Combinator’s financial-modeling guidance recommends building a monthly financial model and defines net burn as cash outflows minus cash inflows. That monthly view is essential when collections, hiring, or financing events occur at different times.
Why is runway a cash-timing problem rather than an ARR problem?
Runway is a cash-timing problem because ARR measures recurring-revenue run rate, while cash depends on invoices, payment terms, collections, prepayments, refunds, taxes, and expenses. A SaaS company can grow ARR and still lose runway if customers pay slowly or headcount grows before revenue arrives.
Consider a £120,000 annual contract:
- An annual prepayment may create a £120,000 receipt in one month.
- Quarterly billing may create £30,000 receipts every three months.
- Net-60 terms may delay cash until two months after invoicing.
The contract’s ARR is the same in all three cases, but the cash curve is different. A runway calculator must place receipts in their expected collection months rather than treating booked ARR as immediately available cash.
What is the SaaS runway formula?
The basic SaaS runway formula divides available cash by average net burn, but a monthly cash model is more accurate when burn or collections change. Use the simple formula for an initial estimate and the monthly equation for hiring, pricing, fundraising, or downside decisions.
Estimated runway in months
= Cash available above minimum reserve
÷ Average monthly net burn
For example:
Cash available = £500,000
Minimum reserve = £100,000
Average monthly net burn = £50,000
Estimated runway = (£500,000 - £100,000) ÷ £50,000
Estimated runway = 8 months
This estimate assumes net burn remains constant. It will be misleading if a planned hire begins in month three, a customer pays annually, a fundraise closes in month six, or churn changes materially.
Use the monthly model whenever any of these conditions apply:
- Headcount changes during the forecast
- Collections vary by customer or billing term
- Revenue is growing or declining
- A financing event is expected
- The business has debt or significant tax payments
- The company must preserve a specific cash reserve
- Management is comparing operating scenarios
What inputs should a SaaS runway calculator include?
A useful SaaS runway calculator needs opening cash, a minimum cash threshold, revenue and collection assumptions, fully loaded workforce costs, operating expenses, taxes, debt, financing events, and scenario variables. Each input should include a period, owner, source, and confidence level so assumptions can be replaced with actuals during the monthly reforecast.
What belongs in a minimum viable runway model?
A minimum viable runway model needs six layers: cash, collections, workforce, operating expenses, financing, and scenarios. This version is sufficient for an early-stage company with relatively few customers and limited contributors, provided the assumptions are reviewed monthly.
| Model layer | Minimum inputs | Decision supported |
|---|---|---|
| Cash baseline | Opening unrestricted cash and minimum reserve | How much cash is actually available |
| Revenue and collections | Existing MRR, new bookings, churn, payment timing | When revenue becomes cash |
| Workforce | Employees, contractors, start dates, fully loaded cost | Whether a hire is affordable |
| Operating expenses | Software, hosting, marketing, professional fees, insurance | Which costs are committed or discretionary |
| Financing | Debt, interest, proceeds, fees, close date | Whether a financing event changes runway |
| Scenarios | Base, downside, and upside assumptions | What action is required under uncertainty |
What belongs in a CFO-grade runway model?
A CFO-grade model adds customer cohorts, billing schedules, collection probabilities, workforce planning, departmental ownership, actual-versus-forecast variance, version control, and sensitivity analysis. It is designed for repeated operating decisions rather than a one-time estimate.
A more advanced model may include:
- Customer-level or cohort-level churn
- Expansion, contraction, and net revenue retention
- Invoice dates and expected collection dates
- Annual prepayments and deferred revenue considerations
- Fully loaded employee costs by employing entity
- Committed versus discretionary expenses
- Departmental budgets and owner submissions
- Debt covenants and repayment schedules
- Scenario versions with approval history
- Accounting, payroll, billing, and CRM data
- Sensitivity rankings by cash impact and timing
The distinction is not primarily company size. A solo founder may need a CFO-grade model if the company has international payroll, long sales cycles, annual contracts, or an imminent financing decision.
What does a 12-month SaaS runway example look like?
A worked example shows why a monthly model is more informative than dividing cash by one burn figure. The fictional company below starts with £500,000, maintains a £100,000 minimum reserve, hires an engineer in month three, and receives no financing during the initial forecast.
| Month | Opening cash | Collections | Gross burn | Financing | Closing cash | Status |
|---|---|---|---|---|---|---|
| 1 | £500,000 | £60,000 | £110,000 | £0 | £450,000 | Above reserve |
| 2 | £450,000 | £65,000 | £125,000 | £0 | £390,000 | Above reserve |
| 3 | £390,000 | £55,000 | £155,000 | £0 | £290,000 | Hiring impact |
| 4 | £290,000 | £70,000 | £160,000 | £0 | £200,000 | Above reserve |
| 5 | £200,000 | £60,000 | £165,000 | £0 | £95,000 | Below reserve |
| 6 | £95,000 | £75,000 | £165,000 | £0 | £5,000 | Below reserve |
| 7 | £5,000 | £80,000 | £170,000 | £0 | -£85,000 | Cash shortfall |
The company reaches its £100,000 minimum reserve in month five and experiences a cash shortfall in month seven. A simple average calculation could hide the timing effect of the month-three hire and changing collections.
The management response could include:
- Delaying or restructuring the hire
- Reducing discretionary marketing or software costs
- Improving collection timing
- Increasing prices for new customers
- Starting fundraising before month five
- Testing a combined downside case with higher churn
The output is not a recommendation by itself. It identifies the month when a decision becomes urgent.
How should hiring plans affect SaaS runway?
Hiring affects runway through salary, employer payroll taxes, benefits, commissions, recruiting, equipment, onboarding, and the time required for an employee to become productive. Model every planned hire as a dated cash event with a fully loaded cost and ramp period instead of using only an average headcount assumption.
A hiring schedule should include:
- Role and department
- Recruitment start date
- Expected start date
- Base salary or wages
- Employer payroll taxes
- Benefits and pension contributions
- Commission or bonus eligibility
- Recruiting fees
- Equipment and software
- Onboarding and training
- Ramp period
- Expected revenue or productivity contribution
A useful hiring decision rule is:
Approve a hire only when the downside case preserves the minimum cash reserve through the expected productivity or financing milestone, unless the hire is required to prevent a more significant operational risk.
This rule is deliberately stricter than asking whether the company can afford the first month of salary. A hire can be affordable today but unsafe if it moves the cash-out month ahead of a fundraise or profitability milestone.
A delayed hire may preserve cash but also delay product delivery, sales capacity, or customer support. Include both the cost of the employee and the operating consequence of not hiring.
What payroll assumptions matter in UK and US hiring scenarios?
UK and US hiring scenarios require separate payroll assumptions because employer taxes, wage rules, benefits, and filing requirements differ. Treat statutory figures as dated inputs, verify them before use, and model employees, contractors, benefits, and local obligations according to the employing entity and work location.
Examples of dated inputs include:
- UK employer National Insurance: The employer rate increased to 15% from April 6, 2025, and the secondary threshold was reduced to £5,000 per year. See the UK government guidance on employer National Insurance changes.
- UK National Living Wage: The rate for workers aged 21 and over increased to £12.21 per hour from April 1, 2025. See the UK National Minimum Wage rates.
- US Social Security wage base: The 2025 wage base was $176,100. See the Social Security Administration wage-base information.
These are dated examples, not universal 2026 planning rates. Recheck current official guidance before approving payroll, preparing a tax forecast, or comparing UK and US employment costs.
How do churn, pricing, NRR, and collections change runway?
Revenue assumptions should separately model churn, contraction, expansion, new bookings, pricing, discounts, invoicing, and collections. NRR explains how an existing customer cohort changes, but it does not show when new revenue becomes cash or whether acquisition spending is economically justified.
SaaS Capital defines net revenue retention as the percentage of beginning recurring revenue retained from the same customer cohort after churn, contraction, and expansion.
NRR
= (Beginning recurring revenue
+ Expansion
- Contraction
- Churn)
÷ Beginning recurring revenue
Keep these variables separate:
| Variable | Meaning |
|---|---|
| Gross churn | Recurring revenue lost from cancellations |
| Contraction | Reduced spend from existing customers |
| Expansion | Additional spend from existing customers |
| New bookings | Revenue from newly acquired customers |
| Pricing | List-price, packaging, discount, or usage changes |
| Collections | Cash actually received |
| NRR | Change in the existing customer cohort before new business |
A price increase may improve revenue per customer but reduce conversion, increase churn, or lengthen negotiations. Model those effects independently instead of applying the price increase to all revenue.
How do CAC and CAC payback fit into runway planning?
CAC and CAC payback help determine whether growth spending is likely to improve runway over time, but neither metric replaces a cash forecast. Test acquisition cost, gross-margin contribution, payment timing, and ramp period together before increasing sales or marketing spend.
CAC
= Sales and marketing acquisition cost
÷ New customers acquired
CAC payback period
= CAC
÷ Monthly gross-margin contribution per customer
For example, a £12,000 CAC and £1,000 monthly gross-margin contribution imply a 12-month payback before considering churn, expansion, or delayed collections. If the company has only six months of downside runway, the spending decision requires financing capacity or a shorter payback path.
Bessemer Venture Partners discusses the Rule of 40, commonly expressed as revenue growth percentage plus profit-margin percentage. It can provide performance context, but it is not a substitute for runway analysis.
What should base, downside, and upside SaaS scenarios contain?
A credible scenario model changes the operating assumptions that drive cash rather than arbitrarily changing the final runway number. At minimum, vary bookings, churn, collections, hiring pace, operating costs, pricing, and fundraising timing across base, downside, and upside cases.
| Dimension | Conservative case | Base case | Upside case |
|---|---|---|---|
| New customer acquisition | Lower, evidence-based conversion | Expected pipeline conversion | Higher conversion supported by capacity |
| Gross churn | Higher churn | Recent historical expectation | Lower churn supported by retention evidence |
| Expansion and NRR | Lower retention and expansion | Expected cohort behavior | Stronger retention and expansion |
| Hiring pace | Delayed or reduced hiring | Approved hiring plan | Accelerated hiring |
| Fundraising timing | Delayed, smaller, or unsuccessful raise | Expected close date | Earlier or larger raise |
| Pricing | No increase or greater discounting | Planned pricing | Successful price increase |
| Collections | Slower payment timing | Expected payment timing | Faster payment timing |
| Result | Earlier cash-out and required cuts | Expected runway and milestones | Higher growth with potentially higher burn |
The most useful downside case often combines several plausible pressures:
- Slower bookings
- Higher churn
- Slower collections
- Delayed hiring productivity
- Higher operating costs
- A delayed financing close
Use company-specific evidence to set ranges:
- Historical bookings and churn
- Customer cohort retention
- Sales pipeline conversion
- Average payment terms
- Collection history
- Hiring plans and offer-stage data
- Vendor commitments
- Financing conversations
How should a company rank runway sensitivities?
Rank sensitivities by the change in cash-out month or minimum cash caused by changing one assumption while holding the others constant. This identifies the assumptions most worth managing instead of treating every forecast input as equally important.
A practical sensitivity process is:
- Establish the base case.
- Change one driver by a defined amount.
- Recalculate the cash-out month and minimum cash balance.
- Record the change in months and cash.
- Rank the drivers by impact.
- Repeat with combined downside assumptions.
Typical high-impact sensitivities include:
- Hiring start dates
- Collection delays from large customers
- Churn among high-value accounts
- Financing close dates
- Annual prepayment assumptions
- Sales and marketing spend
- Pricing changes with uncertain conversion effects
A connected planning workflow such as Uniflow can keep hiring, bookings, collections, and expenses in the same scenario model, making it easier to compare the effect of an operating decision before it is finalized.
When should a SaaS company raise capital?
A SaaS company should begin fundraising early enough to reach its next financing or profitability milestone with an adequate cash buffer in the downside case. Model the expected close, delayed close, smaller round, and no-round outcomes instead of treating financing as guaranteed.
Include these financing inputs:
- Preparation start date
- Expected close month
- Gross proceeds
- Financing fees
- Debt repayment
- Interest expense
- Investor conditions
- Minimum cash balance
- Dilution or repayment implications
- Operating milestone funded by the round
Fundraising should be treated as a dated cash event:
Net financing cash
= Gross proceeds
- Financing fees
- Debt repayment
- Other closing costs
If the downside case reaches the minimum reserve before the expected close date, the company has a financing timing problem even if the proposed round is large enough on paper. Start earlier, reduce burn, increase collection certainty, or test a smaller bridge or other financing structure with qualified advisers.
“A startup is an organization formed to search for a repeatable and scalable business model.” — Steve Blank, “What’s a Startup? First Principles”
Capital should be connected to a milestone. If the raise funds a sales team, product launch, or new market, the model should show the required spend, expected timing, milestone owner, and downside result if the milestone is missed.
How should UK and US assumptions be handled?
UK and US runway models should use separate assumptions for payroll, corporation tax, wage requirements, interest rates, benefits, and financing structures. Do not apply one country’s employer-cost percentage to an international workforce or present dated statutory rates as permanent planning assumptions.
| Input | United Kingdom | United States |
|---|---|---|
| Employer payroll | National Insurance rules and thresholds vary by tax year and employee circumstances | Federal payroll taxes, state requirements, benefits, and wage rules apply |
| Wage floor | National Minimum Wage and National Living Wage depend on age and category | Federal, state, and local wage rules may apply |
| Corporation tax | Treatment depends on profits, associated companies, accounting periods, and marginal relief | Federal corporate tax is supplemented by state and local rules |
| Interest rates | Use the applicable Bank Rate and lender terms at the forecast date | Use the applicable Federal Reserve environment and lender terms |
| Fundraising | EIS and other UK structures have eligibility conditions | SAFEs and convertible instruments have specific legal and tax implications |
Verify current information through official sources such as HM Revenue & Customs, the UK Department for Business and Trade, the US Internal Revenue Service, the Social Security Administration, and the Federal Reserve.
Planning note: statutory tax, payroll, wage, and financing rules change. Confirm the applicable rates and treatment with qualified payroll, tax, legal, and financing advisers before relying on the forecast.
Should a startup use a spreadsheet or FP&A tool?
A spreadsheet is often sufficient for a small company with few drivers and contributors. An FP&A tool or financial operating system becomes more valuable when the company needs controlled inputs, repeatable scenarios, workforce planning, actual-versus-forecast reporting, data connections, or shared ownership across departments.
| Option | Best fit | Strengths | Limitations |
|---|---|---|---|
| Uniflow | Solo founders and finance leaders who need connected financial planning | Centralized planning workflow, driver-based forecasts, cash visibility, and scenario comparison | Confirm required integrations, permissions, and plan scope for your company |
| Spreadsheet | Early-stage teams with simple models and few contributors | Flexible, inexpensive, and fast to customize | Manual updates, version-control risk, and limited auditability |
| Workday Adaptive Planning | Larger organizations with structured planning requirements | Workforce, financial, and scenario planning capabilities | More implementation effort and enterprise-oriented administration |
| Anaplan | Complex organizations with multi-department planning | Connected planning across functions and scenarios | Requires configuration, governance, and ongoing administration |
| QuickBooks or Xero | Accounting actuals and basic financial records | Useful source data for cash, expenses, and payroll | Not necessarily a complete driver-based runway model |
| Stripe or Chargebee | Billing and recurring-revenue data | Supports subscription, invoice, and collection analysis | Billing data alone does not model hiring, expenses, or financing |
Uniflow is relevant when the company needs to connect operating assumptions—such as hiring, bookings, collections, and spending—to a shared forecast. It does not replace accounting, payroll, tax, legal, or treasury systems; its value is in making planning and scenario decisions more repeatable.
| Decision factor | Spreadsheet | FP&A or financial operating system |
|---|---|---|
| Model complexity | Best for limited drivers | Better for interconnected operating drivers |
| Contributors | Works with one or a few users | Better for controlled departmental inputs |
| Scenario frequency | Occasional analysis | Repeated planning and sensitivity analysis |
| Data updates | Often manual | Can be connected to approved business data |
| Governance | Depends on file discipline | Supports permissions, versioning, and repeatability |
| Implementation | Fast to start | Requires tool selection and configuration |
How can Uniflow support SaaS runway planning?
Uniflow can help founders and finance leaders organize runway planning around a shared operating forecast rather than disconnected spreadsheet versions. The workflow is most useful when hiring, bookings, collections, expenses, and financing assumptions must be compared before a decision is approved.
A practical Uniflow workflow can include:
- Establish the cash baseline and minimum reserve.
- Record revenue, collections, hiring, and expense assumptions.
- Create base, downside, and upside cases.
- Compare the effect of a hire, pricing change, or financing delay.
- Assign owners to assumptions and review dates.
- Compare actual results with the forecast.
- Reforecast when operating conditions change.
For a solo founder, this can create a repeatable planning habit without requiring a large finance team. For a CFO, it can provide a shared structure for departmental inputs, scenario review, and management communication.
Uniflow does not determine which decision is correct. Founders and CFOs still need to validate data, document assumptions, review sensitivities, and obtain professional advice where appropriate.
Explore Uniflow for startup financial planning or compare a modern financial operating system with traditional FP&A workflows in Uniflow’s financial planning guide.
What is the most reliable way to use a SaaS runway calculator?
Use a monthly, driver-based SaaS runway calculator with documented assumptions, at least three scenarios, actual-versus-forecast reporting, and a regular reforecast process. The calculator should report cash-out month, minimum cash balance, gross burn, net burn, milestone dates, and the assumptions with the greatest runway impact.
Use this operating cadence:
- Build the model from bank, accounting, payroll, billing, and operating data.
- Assign owners to bookings, churn, collections, hiring, expenses, and financing.
- Run scenarios before approving major hires or spending commitments.
- Compare actuals with forecast every month.
- Update assumptions when pipeline, customer behavior, headcount, or funding conditions change.
- Escalate early when a downside case reaches a financing, hiring, or cost-reduction trigger.
The most important output is not a single runway number. It is a decision schedule showing when management must act to preserve cash, reach a milestone, or secure financing.
Frequently asked questions about SaaS runway calculators
How is SaaS runway calculated?
SaaS runway is calculated by projecting monthly cash inflows and outflows until closing cash falls below a defined minimum reserve. A simple estimate divides cash above the reserve by average net burn, but a monthly model is more accurate when collections, hiring, expenses, or fundraising change during the forecast.
Should runway use gross burn or net burn?
Runway normally uses net burn because net burn reflects cash outflows after cash inflows. Gross burn remains important because it shows the company’s total cost base and the savings available if revenue declines. Show both figures to distinguish structural cost growth from temporary collection timing.
What inputs does a SaaS runway calculator need?
A calculator needs opening unrestricted cash, a minimum cash threshold, collections, churn, bookings, pricing, hiring, fully loaded payroll, operating expenses, taxes, debt, financing events, and scenario assumptions. It should also record the timing and owner of each input so assumptions can be reviewed and replaced with actual results.
How does hiring affect SaaS runway?
Hiring reduces runway through salary, payroll taxes, benefits, recruiting, equipment, onboarding, and delayed productivity. Model each employee by start date and fully loaded monthly cost. Include the expected operating contribution and ramp period because delaying a hire may preserve cash but also delay revenue, product delivery, or customer support.
How should fundraising appear in a runway model?
Fundraising should appear as a dated cash event with an expected close month, gross proceeds, fees, debt repayment, interest, and the possibility of a delayed, smaller, or unsuccessful round. Start fundraising before the downside case reaches its minimum cash reserve, not when the bank account is nearly empty.
How does ARR differ from cash?
ARR is a recurring-revenue run-rate measure, while cash depends on invoice timing, billing terms, collections, annual prepayments, refunds, taxes, and expenses. A company can grow ARR while its cash position worsens. A runway calculator should therefore model expected collections rather than treating ARR as cash.
Is a spreadsheet or dedicated FP&A tool better?
A spreadsheet may be adequate when the company has few drivers and contributors. A dedicated FP&A tool or financial operating system becomes more valuable when the company needs controlled inputs, version history, workforce planning, scenario comparisons, and repeatable actual-versus-forecast reporting. Choose based on complexity and decision frequency, not company size alone.