Runway planning is not one number. This guide shows how to manage runway as a range with predefined trigger actions tied to burn and revenue variance.
Primary tool: Runway Calculator
What this guide checks
- Base, conservative, and optimistic runway bands.
- Burn drivers with the highest controllable impact.
- Decision trigger points for hiring, spend, and growth bets.
Signals that should trigger a second look
- Runway band narrows below decision comfort window.
- Burn acceleration without matching revenue indicators.
- Leadership decisions rely on outdated cash assumptions.
Common mistakes
- Using one runway number in board reporting.
- Assuming all spend is equally adjustable.
- Delaying trigger-based actions until emergency stage.
Real scenarios
Hiring freeze trigger
Conservative runway dropped below 8 months; predefined hiring freeze prevented panic and preserved strategic roles.
Growth bet validation
Marketing expansion moved from approved to conditional after conservative-case runway breached threshold.
Mistake vs better approach
| Scenario | Common mistake | Better approach |
|---|---|---|
| Board update | Present one runway number. | Show scenario band and key assumption sensitivity. |
| Spending controls | Delay action until cash crisis. | Use predefined triggers tied to conservative runway. |
Decision guidance
Low concern
Runway remains acceptable in conservative case with clear triggers defined.
Medium concern
Runway is manageable but one missed target can force abrupt cuts.
High concern
Runway in conservative case is below operating safety threshold.
Trust workflow (after you get a number)
- Recompute runway weekly during volatile periods.
- Track top three burn drivers separately.
- Define and publish trigger-based actions in advance.
- Review trigger execution discipline monthly.