Cash Runway Planning With Base, Downside, and Hiring Cases

Simple runway equals unrestricted cash divided by net monthly burn. It is a useful snapshot: $1.2 million divided by $100,000 suggests 12 months. A planning model must go further because collections, payroll, annual renewals, taxes, and hiring rarely arrive in smooth monthly amounts.

The practical model

Treat cash runway planning with base, downside, and hiring cases as a system with four review points: start with bankable cash, build monthly cash movements, create decision-linked scenarios, set trigger dates before distress. Give each point an owner, a measurable acceptance condition, and a rollback trigger. Thresholds should come from observed workloads, contracts, or risk tolerance rather than an unexplained default.

Start with bankable cash

Separate unrestricted cash from restricted deposits, customer funds, and undrawn credit. Reconcile the opening balance to actual bank accounts. Model cash receipts by expected collection date rather than invoice date, and apply realistic delay and default assumptions.

Build monthly cash movements

List payroll with start dates and employer costs, contractors, cloud bills, rent, debt service, taxes, insurance, and annual subscriptions. Include one-time purchases and severance. Calculate ending cash each month from opening cash plus receipts minus payments; the lowest point matters more than an annual average.

Create decision-linked scenarios

A base case reflects the current plan. A downside case can lengthen sales cycles, reduce renewals, and raise collection delays. A hiring case shifts named roles by month. Avoid a vague percentage haircut across every line; connect assumptions to operational drivers the team can observe.

Set trigger dates before distress

Choose a minimum cash floor and work backward from financing or profitability lead time. If fundraising requires six months and diligence needs two more, a 12-month headline runway is not eight months of optionality. Define triggers for hiring pauses, vendor renegotiation, and board review.

Common pitfalls

• Counting unsigned contracts as cash.

• Using EBITDA in place of cash burn.

• Forgetting annual payments and tax dates.

• Assuming a credit line remains available during a downside case.

A focused test plan

1. Start with bankable cash: verify that separate unrestricted cash from restricted deposits, customer funds, and undrawn credit. Then introduce the failure case “counting unsigned contracts as cash” and confirm that the system fails visibly, stays within its safety boundary, and has a documented recovery action.

1. Build monthly cash movements: verify that list payroll with start dates and employer costs, contractors, cloud bills, rent, debt service, taxes, insurance, and annual subscriptions. Then introduce the failure case “using ebitda in place of cash burn” and confirm that the system fails visibly, stays within its safety boundary, and has a documented recovery action.

1. Create decision-linked scenarios: verify that a base case reflects the current plan. Then introduce the failure case “forgetting annual payments and tax dates” and confirm that the system fails visibly, stays within its safety boundary, and has a documented recovery action.

1. Set trigger dates before distress: verify that choose a minimum cash floor and work backward from financing or profitability lead time. Then introduce the failure case “assuming a credit line remains available during a downside case” and confirm that the system fails visibly, stays within its safety boundary, and has a documented recovery action.

Conclusion

Runway is a calendar, not a quotient. Model dated cash flows, maintain several operational scenarios, and attach actions to thresholds while the company still has choices.