Runway Forecasting That Updates Itself: Why Spreadsheet Models Drift and Integrated Tools Don't

Runway forecasting is projecting how many months of cash a company has left by modeling future cash in and cash out month by month, instead of dividing today's balance by today's burn. A runway forecast includes planned hiring, revenue growth, contract renewals and one-off payments, so it shows when cash actually runs out.

The simple runway calculation (cash ÷ net burn) assumes the future looks like the recent past. It rarely does. A company that plans to hire, raise prices, or sign a large contract will burn cash at a different rate next quarter than it did last quarter. A forecast captures those changes. A static ratio cannot.

This guide covers the main forecasting methods, a worked example that shows how far a static calculation can drift from a driver-based one, and how to keep the forecast current. For the basics of calculating and tracking today's runway, see our companion guide to cash runway tracking.

Static runway vs. forecast runway

Static runway = cash balance ÷ current monthly net burn. It is a useful snapshot, and the starting point for every forecast.

Forecast runway = the month in which projected ending cash falls below zero (or below your minimum cash threshold). You get there by building month-by-month projections:

Ending cash = opening cash + projected cash in − projected cash out

Repeat for each month until ending cash crosses your threshold. The month it crosses is your forecast runway. If it crosses partway through a month, divide the remaining cash at the start of that month by that month's net burn to get the fraction.

Example: static vs. driver-based runway

Example: a hypothetical 35-person software company has $2,400,000 in cash and a current net burn of $150,000 a month. The static calculation gives $2,400,000 ÷ $150,000 = 16.0 months.

Its operating plan includes two drivers the static number ignores:

• Revenue growth: monthly customer collections are rising, reducing net burn by $5,000 each month.
• Hiring: four engineers start in month 3 at a fully loaded cost of $15,000 a month each, adding 4 × $15,000 = $60,000 a month to burn.

So net burn in month m is $150,000 − ($5,000 × m), plus $60,000 from month 3 onward.

Cash runs out during month 15. At the start of month 15 the company has $105,000 against a net burn of $135,000, so forecast runway is 14 + ($105,000 ÷ $135,000) = 14.8 months.

Now add a downside scenario: collections stop growing and net burn stays at $150,000 until the hires start, then $210,000 a month. Ending cash after month 2 is $2,400,000 − (2 × $150,000) = $2,100,000. That lasts exactly $2,100,000 ÷ $210,000 = 10 more months, so runway is 12.0 months.

Three numbers for the same company on the same day: 16.0 months (static), 14.8 months (plan), 12.0 months (downside). The static figure overstates the plan by more than a month and the downside by four. That gap is the reason to forecast rather than divide.

Three forecasting methods, and when to use each

1. Driver-based monthly forecast (12 to 24 months)

Model cash from the drivers that cause it: headcount and fully loaded cost per role, customer count and average revenue, churn, payment terms, vendor contracts, and debt service. The example above is a two-driver version.

Use it for runway, fundraising timing and hiring decisions. Its strength is that you can change one driver, such as delaying two hires by a quarter, and see the effect on the cash-out date immediately.

Keep the driver list short. Ten well-understood drivers beat fifty you cannot maintain.

2. 13-week cash flow forecast (direct method)

A 13-week forecast projects actual receipts and disbursements week by week: which customer invoices will be collected, which bills and payroll runs will be paid, and when. It is the standard short-term liquidity tool because it shows the low point inside a month that a monthly model averages away.

Use it when runway is under about 12 months, when you have a debt covenant with a minimum liquidity test, or whenever the timing of a few large payments matters. Our free 13-week cash flow starter gives you the structure.

The two methods work together. The 13-week forecast governs the next quarter; the driver-based model governs the next one to two years. Reconcile the first three months of the driver model to the 13-week view each month.

3. Scenarios

A single forecast is a single guess. Build at least three: plan, downside and a severe case. Change only the drivers that are genuinely uncertain, such as new bookings, churn, collection timing, and the start date of planned hires, and keep everything else the same so the scenarios are comparable.

Decide in advance what you will do if the downside case becomes the actual case. For more on structuring scenarios, see stop building one forecast, build three.

Why spreadsheet forecasts drift

Most runway forecasts start accurate and get less accurate every week. The reasons are mechanical.

Actuals don't flow in on their own. Someone has to export the bank balance, the GL and the AR aging, then paste them into the model. When the close is busy, that step slips, and the model runs on last month's starting cash.

Assumptions age. A churn rate, a collection lag, or a hiring start date set at budget time stays in the model until someone changes it. Reality moves on without it.

Cash in is the hardest input to predict. The Federal Reserve's 2025 Report on Employer Firms, drawn from the 2024 Small Business Credit Survey, found that 51% of employer firms cited uneven cash flows as a financial challenge, a category that explicitly includes collecting on receivables. A forecast that assumes customers pay on their terms will be wrong whenever they don't.

Forecasting is hard even for specialists. In the 2026 AFP Treasury Benchmarking Survey, cash and liquidity forecasting was the most frequently cited treasury challenge, named by 49% of respondents. Most growth-stage companies forecast cash without a dedicated treasury team at all.

Version sprawl. A model emailed to the CEO, edited for a board deck, and saved as "v7 final" ends up with several versions in circulation, each with different numbers.

How to keep a forecast current

You do not need a perfect model. You need one that is re-anchored to actuals on a fixed schedule.

1. Re-base after every close. Replace forecast months with actuals as soon as the books close, and roll the forecast forward one month. This is the single most effective habit.
2. Measure forecast accuracy. Each month, compare last month's forecast of cash in, cash out and ending cash with the actuals. Track the variance over time. If you consistently miss collections by 10%, adjust the collection-lag assumption rather than repeating the error.
3. Connect inputs to the source. The fewer manual exports between QuickBooks, the bank and the model, the less the forecast drifts. Even a scheduled sync of the bank balance and AR aging removes the most common error.
4. Document every assumption. Each driver should have an owner, a source and the date it was last reviewed.
5. Report a range. Present plan, downside and severe runway together, and say which assumptions would move the answer most.

For the receivables side of the forecast, collection timing is usually the largest source of error. Our guide to collections management covers how to forecast it from AR aging.

Runway forecasting checklist

• Start from static runway, then build a month-by-month driver-based forecast for 12 to 24 months.
• Add a 13-week direct cash forecast when runway is short or timing matters.
• Build plan, downside and severe scenarios that change only uncertain drivers.
• Re-base the forecast to actual cash after every close.
• Track forecast-to-actual variance and fix the assumptions that miss repeatedly.
• Present runway as a range with its key assumptions, not as one number.

Tech for CFO's RunwayWatch re-bases runway from QuickBooks Online actuals automatically. For a quick static figure without signing up, use the free cash runway calculator.