Forecast movements rather than one growth rate
Begin with reconciled opening MRR and forecast new, expansion, contraction and churn separately. Each driver should connect to an operating mechanism: sales capacity and win rate for new revenue, product adoption for expansion, downgrades for contraction and renewal behavior for churn. A single compound percentage hides these mechanisms and cannot tell a team what to change when the forecast misses.
Separate contracted backlog from uncommitted pipeline. Apply implementation dates and probability only where supported. Annual contracts, usage revenue and services may create billing or recognition schedules that differ from MRR movement, so maintain a bridge from recurring forecast to invoicing and cash collection.
Build explicit operating scenarios
A base case should represent the current operating plan, not the midpoint between optimism and fear. A downside case should name specific stresses such as lower win rate, delayed hiring productivity, higher churn or slower collections. An upside case should identify the capacity and spend required to deliver the additional growth.
Change linked drivers coherently. Lower sales can reduce commissions but may not reduce payroll immediately. Higher churn can lower support usage but may increase save activity and refunds. Scenario logic should reflect timing and dependencies rather than changing each line independently.
Translate operations into monthly cash
Start with unrestricted bank cash. Schedule customer collections using actual billing terms and payment behavior, then schedule payroll, taxes, vendors, debt and capital purchases when cash leaves the account. Accounting expense, invoice date and payment date are different events. Runway depends on the cash event.
Normalize exceptional receipts and payments when calculating burn, but do not delete them from the cash schedule. Annual software renewals, tax installments, insurance and severance can create a minimum cash point that an average monthly burn calculation misses.
Set buffers and decision dates
Define a minimum operating cash buffer based on payroll, critical vendors and collection volatility. Runway should end when forecast cash reaches that buffer, not necessarily zero. Then work backward for decisions with lead time: fundraising, hiring freezes, contract renegotiation and cost reductions cannot begin on the day cash reaches the threshold.
Assign trigger measures to each action. For example, a hiring phase may require both a sales-pipeline threshold and a minimum downside runway. This makes the plan responsive to evidence rather than dependent on a single forecast produced months earlier.
Reforecast with actual variance
After every close, replace forecast revenue movements, collections and expenses with actuals. Explain variance by driver and update the remaining months. Preserve prior forecast versions so accuracy and bias can be reviewed. A forecast process improves when errors change assumptions, not when history is silently overwritten.
- Connect revenue movements to invoicing and collection timing.
- Use a minimum cash buffer and named downside scenario.
- Assign action dates before the forecast threshold.