burn-rate-runway-planner
Skill1 starsChanged 21 days agoMITView on GitHub
Models cash burn, runway, and scenario-based cash flow with explicit triggers, default-alive versus default-dead diagnosis, and a 13-week rolling forecast. Use when planning a fundraise; deciding on layoffs; evaluating hiring plans; modeling a downturn; presenting cash position to the board; or pressure-testing a Chief Financial Officer (CFO) operating plan.
In this repository41 other files it gives its agents.
- ai-activation-optimizerSkill
- ai-content-quality-gateSkill
- ai-feature-experiment-designerSkill
- ai-launch-playbookSkill
- ai-pricing-margin-modelerSkill
- ai-product-positioningSkill
- ai-search-visibility-optimizerSkill
- agent-autonomy-level-mapperSkill
- ai-failure-state-designerSkill
- ai-usability-test-plannerSkill
- ai-ux-auditSkill
- human-in-the-loop-designerSkill
- prompt-surface-designerSkill
- uncertainty-and-explainability-patternsSkill
- ai-agent-financial-analystSkill
- capital-allocation-frameworkSkill
- dcf-valuation-builderSkill
- financial-statement-analyzerSkill
- saas-cohort-analyzerSkill
- competitive-response-modelerSkill
- mechanism-design-plannerSkill
- nash-equilibrium-solverSkill
- negotiation-strategistSkill
- repeated-game-strategistSkill
- ai-decision-engineSkill
- ai-product-strategySkill
- ai-stakeholder-translatorSkill
- customer-interview-synthesizerSkill
- jobs-to-be-done-extractorSkill
- opportunity-solution-treeSkill
- product-discovery-coachSkill
- product-roadmap-prioritizerSkill
- blue-ocean-strategy-canvasSkill
- go-to-market-strategySkill
- gtm-engineeringSkill
- market-sizingSkill
- okr-cascade-plannerSkill
- porters-five-forces-analyzerSkill
- pricing-strategy-analyzerSkill
- strategic-landscape-mapperSkill
- swot-tows-analyzerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
No explicit triggers for when fundraising or cost-cutting starts
- Distinctive: line 75
Always build three scenarios:
- Distinctive: line 120
Default-alive verdict with reasoning
- Distinctive: line 131
Use trimmed-mean growth, not last-month
- Distinctive: line 140
Treat investor commitments as cash until wired
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Burn Rate and Runway Planner
Turns the operating plan into an honest cash narrative - with decision triggers, not just a runway number.
What this skill is
A startup Chief Financial Officer (CFO) instrument that decomposes burn, builds three operating scenarios (base, conservative, stretch), and lays out an explicit lever stack ranked by return per unit of strategic damage. It includes a 13-week rolling cash forecast for tactical liquidity management and a fundraise-trigger calendar tied to runway.
What it solves
- Reporting runway as a single number with no scenario range
- Treating investor commitments as cash before they're wired
- Recommending layoffs as the first lever (instead of last)
- Hiding lumpy disbursements (payroll, tax, insurance) inside an average burn
- No explicit triggers for when fundraising or cost-cutting starts
When to invoke
- Quarterly board preparation for any pre-profitability company
- Pre-fundraise modeling (Series A through pre-Initial Public Offering (IPO))
- Recession or downside scenario planning
- Layoff versus hiring-freeze versus spend-cut deliberation
- 13-week tactical cash management when liquidity is tight
Phase 1: Baseline cash position
- Cash plus equivalents as of date
- Available debt capacity (undrawn lines, available Simple Agreement for Future Equity (SAFE) notes or convertible notes)
- Restricted cash - exclude from runway math
- Net Accounts Receivable (AR) plus Accounts Payable (AP) position (working capital)
Define:
- Gross burn = total monthly cash out
- Net burn = cash out − cash in (revenue plus expansion)
- Cash-zero date at current net burn
Phase 2: Burn decomposition
Break monthly cash out by category as percent of total so the conversation moves to mix, not absolute dollars:
| Category | Monthly $ | Percent of total | Trend (last 3 months) |
| Payroll plus benefits | $X | x% | ↑↓→ |
| Contractors | $X | x% | ↑↓→ |
| Cloud and infrastructure | $X | x% | ↑↓→ |
| Software as a Service (SaaS) subscriptions | $X | x% | ↑↓→ |
| Marketing and paid acquisition | $X | x% | ↑↓→ |
| Office and facilities | $X | x% | ↑↓→ |
| Professional services | $X | x% | ↑↓→ |
| Other | $X | x% | ↑↓→ |
| Total gross burn | $Y | 100% |
Flag any line growing more than 10% month-over-month and the top 3 categories.
Phase 3: Default-alive versus default-dead
Apply the Paul Graham framing:
- Default alive: at current growth, will revenue exceed expenses before cash runs out?
- Default dead: it won't - fundraise or cost cuts required
Compute:
- Revenue month-over-month growth (trailing 6 months, trimmed mean)
- Months until revenue ≥ gross burn at current growth
- Cumulative cash needed to reach break-even
Present the default-alive curve: cash balance over time at current growth.
Phase 4: Scenario planning
Always build three scenarios:
Base - current plan, current sales productivity, current churn Conservative - hiring frozen, sales productivity −20%, churn +25%, no new round Stretch - hiring +30%, sales productivity +15%, new round closes in 4 months
Build the levers table:
| Lever | Cash impact per month | Runway extension | Strategic cost |
| Freeze hiring | +$X | +Y months | Slows roadmap |
| Reduce paid marketing 50% | +$X | +Y months | New Annual Recurring Revenue (ARR) −20% |
| 10% Reduction in Force (RIF) | +$X | +Y months | Morale, severance |
| Defer planned hires one quarter | +$X | +Y months | Mild roadmap slip |
| Negotiate vendor deferral | +$X | +Y months | One-time benefit |
| Draw on credit line | +$X | +Y months | Adds interest |
Stack levers by return per unit of strategic damage - layoffs are rarely the first move if other levers exist.
Phase 5: 13-week rolling forecast
| Week | Beginning cash | Collections | Disbursements | Net | Ending cash |
| W1 | $X | $X | $X | $X | $X |
| ... | |||||
| W13 | $X | $X | $X | $X | $X |
Inputs: Accounts Receivable (AR) aging, Accounts Payable (AP) aging, payroll calendar, tax estimates, insurance, lease. Flag any week where ending cash is less than 30 days of operating expense.
Phase 6: Fundraise trigger calendar
| Runway remaining | Action |
| 18+ months | No pressure; focus on growth metrics |
| 12-18 months | Prepare data room; soft conversations with existing investors |
| 9-12 months | Active fundraise process |
| 6-9 months | Bridge round or extension; activate cost cuts |
| Less than 6 months | Survival mode; aggressive cuts; strategic alternatives |
Tie each trigger to a calendar date based on current burn.
Output
- Cash position memo: balance, gross burn, net burn, runway
- Default-alive verdict with reasoning
- Three scenarios with quantified runway under each
- Recommended levers in priority order with dollar and strategic-cost impact
- Fundraise calendar with trigger dates
- 13-week tactical forecast with liquidity warnings flagged
- 3-5 leading indicators that would shift the plan
Operating rules
Always
- Separate gross burn from net burn
- Use trimmed-mean growth, not last-month
- Build all three scenarios
- Quantify each lever in dollars and strategic cost
- Set fundraise triggers as calendar dates
- Stress-test with lumpy payroll, tax, and insurance disbursements
Never
- Report runway as one number
- Assume revenue grows linearly from one good month
- Treat investor commitments as cash until wired
- Recommend layoffs before exhausting cheaper levers
- Mix restricted cash into runway
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

