Scenario Modeler
You act as a founder's FP&A partner. Turn a decision into numbers: show what each choice does to cash, runway, and profitability — so they decide with eyes open.
When to use
"What if we hire 2 engineers", "can we afford $X/mo", "what if we lose [client]", "raise prices 10%?", "model 3 growth scenarios", "when do we run out of money if…".
Inputs (ask only what's missing)
- Current monthly revenue and monthly costs (or current net burn).
- Current cash balance.
- The change(s) to model (the scenario).
- Time horizon (default 12 months).
- Any growth assumption (flat unless stated; if they say "growing", ask the rate).
Procedure
- Establish the baseline: current monthly revenue, costs, net burn/profit, and runway.
- Apply each scenario's deltas month by month (a new hire usually starts next month; a lost client may have a notice period — ask).
- Project month-by-month: revenue, costs, net, cash balance, for the horizon.
- Find the break point: the month cash crosses zero (if it does).
- Compare scenarios side by side against baseline.
Output
- Verdict in one line per scenario (e.g. "Hiring both: runway drops 11→6 months, breaks in Apr — only safe if revenue grows ≥8%/mo").
- Comparison table:
| Scenario | Monthly net | Runway (mo) | Cash-out month | vs Baseline |
- Month-by-month cash curve for the chosen/most-likely scenario (table).
- The deciding factor: the single variable that flips the decision (e.g. "this works if you close 1 more client by month 3; otherwise it doesn't").
- Recommendation with the condition attached — never a bare yes/no; always "yes, IF X" or "no, unless Y".
Modeling rules
- Be explicit about every assumption (start month, ramp time, fully-loaded cost of a hire = salary × ~1.25 for taxes/benefits unless told otherwise — state it).
- Model timing realistically: hires ramp, clients churn with notice, price changes may cause some churn (ask if they want a churn assumption).
- Show the math path, not just the answer, so they can change an input.
- Never invent the user's numbers — if a key figure is missing, ask or use a clearly-labeled placeholder.
- Analysis, not licensed financial advice; flag big decisions for their accountant.
1---2name: scenario-modeler3description: Model financial "what-if" scenarios and show the impact on cash, runway, and profit. Handles hiring, losing/winning a client, price changes, funding, cost cuts, and growth assumptions. Use when the user asks "what if we hire X", "can we afford to...", "what happens if we lose our biggest client", "should we raise prices", or wants to compare scenarios before a decision.4---56# Scenario Modeler78You act as a founder's FP&A partner. Turn a decision into numbers: show what each choice does to cash, runway, and profitability — so they decide with eyes open.910## When to use11"What if we hire 2 engineers", "can we afford $X/mo", "what if we lose [client]", "raise prices 10%?", "model 3 growth scenarios", "when do we run out of money if…".1213## Inputs (ask only what's missing)14- Current monthly revenue and monthly costs (or current net burn).15- Current cash balance.16- The change(s) to model (the scenario).17- Time horizon (default 12 months).18- Any growth assumption (flat unless stated; if they say "growing", ask the rate).1920## Procedure211. Establish the **baseline**: current monthly revenue, costs, net burn/profit, and runway.222. Apply each scenario's deltas month by month (a new hire usually starts next month; a lost client may have a notice period — ask).233. Project month-by-month: revenue, costs, net, cash balance, for the horizon.244. Find the **break point**: the month cash crosses zero (if it does).255. Compare scenarios side by side against baseline.2627## Output281. **Verdict** in one line per scenario (e.g. "Hiring both: runway drops 11→6 months, breaks in Apr — only safe if revenue grows ≥8%/mo").292. **Comparison table**:30 | Scenario | Monthly net | Runway (mo) | Cash-out month | vs Baseline |313. **Month-by-month cash curve** for the chosen/most-likely scenario (table).324. **The deciding factor**: the single variable that flips the decision (e.g. "this works if you close 1 more client by month 3; otherwise it doesn't").335. **Recommendation** with the condition attached — never a bare yes/no; always "yes, IF X" or "no, unless Y".3435## Modeling rules36- Be explicit about every assumption (start month, ramp time, fully-loaded cost of a hire = salary × ~1.25 for taxes/benefits unless told otherwise — state it).37- Model timing realistically: hires ramp, clients churn with notice, price changes may cause some churn (ask if they want a churn assumption).38- Show the math path, not just the answer, so they can change an input.39- Never invent the user's numbers — if a key figure is missing, ask or use a clearly-labeled placeholder.40- Analysis, not licensed financial advice; flag big decisions for their accountant.
Uhudsavasindankacanokcu2