Run a what-if analysis
Builds a scenario and sensitivity analysis for a decision (best, base and worst cases, a tornado chart and breakevens) as a spreadsheet layout with exact formulas. Use before committing to a plan.
A what-if model is useful when it shows which assumptions the decision actually depends on. That takes three views: coherent scenarios (best, base and worst cases built from assumptions that would plausibly happen together, not every input at its extreme at once), one-way sensitivity (swing each input from low to high with the others at base, sorted by impact in a tornado chart), and breakevens (the value of each key input at which the decision flips). The model must keep inputs separate from calculations, so changing an assumption never means editing a formula.
Build a what-if analysis in for this decision:
Uncertain inputs:
- Define the output metric and the decision rule (for example "go if 3-year profit is above zero").
- Write the model as a short chain of formulas from inputs to output, and state every structural assumption (time horizon, what is fixed versus variable, timing of cash flows, discounting).
- Lay out an Inputs sheet: one row per input with name, unit, low, base, high, source, plus a scenario selector cell. Give each input a named range.
- Lay out a Calculation sheet that references only the live input cells, with exact cell addresses and formulas.
- Scenarios: define best, base and worst as coherent sets of input values, explain why each set hangs together, and drive the live inputs from the selector (for example with
CHOOSEorINDEXon the scenario number). In Excel, also mention Scenario Manager as an option. - Sensitivity: for each input, compute the output at its low and high value with the others at base, and the swing. In Excel, use a one-variable Data Table or a LAMBDA of the model; in Google Sheets, which has no Data Table feature, wrap the model in a named function or LAMBDA, or give one row per input that recomputes the output with the overridden value. Sort by swing and describe how to chart it as a tornado (a bar chart of low and high deltas from base).
- Breakevens: for the two or three most sensitive inputs, solve for the value at which the decision rule flips, algebraically where possible, or with Goal Seek (built into Excel; an add-on in Google Sheets).
- Compute the base, best and worst outputs and the sensitivity table from the numbers given, showing the arithmetic.
- Use only the user's numbers. If an input has no low or high value, propose a range, label it "[assumed range]" with the reasoning, and list it under How to read it.
- If an important input seems to be missing from the list (for example taxes, ramp-up time or one-off costs), name it and ask whether to add it rather than silently inventing a value.
- Every formula must work in as written; use function names and separators for an English-locale setup and say so.
- Present the model as a decision aid, not a recommendation: the decision belongs to the user, and the model is only as good as its ranges.
- Keep it auditable: no hard-coded numbers inside formulas, and no circular references.
Model
The output metric, decision rule, formula chain and structural assumptions.
Inputs sheet
A table: cell | name | unit | low | base | high | source.
Calculation sheet
A table: cell | label | formula.
Scenarios
A table: input | worst | base | best, then the output for each scenario and the selector formula.
Sensitivity
A table sorted by swing: input | output at low | output at high | swing; then the formulas and the tornado chart steps.
Breakevens
Each input's breakeven value and how it was found.
How to read it
Three to five bullets: which assumptions matter most, which ranges were assumed, and what to verify before deciding.
2 required values still a placeholder; the assistant will ask for them.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Data analysis
- category
- Spreadsheets
- level
- Intermediate
- made for
- Business analyst, Financial analyst, Founder / business owner, Data analyst
- risk
- read-only
- version
- v1.0.0 · experimental
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install run-what-if-analysis --target claude-codenpx skills add hermes-hq/hodios-dist --skill run-what-if-analysis -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-data-analysis@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of SpreadsheetsBuild a KPI driver tree
Decomposes a top-line metric into a driver tree with exact formulas, definitions and owners, so a change in the metric can be traced to the input that moved. Use for metric design and reviews.
build-kpi-treeExtract tables from a PDF
Extracts tables from PDF or scanned text into clean CSV, Markdown or JSON, keeps values exactly as printed, flags likely OCR errors and validates totals against the source. Use before analysis.
extract-tables-from-pdfAudit a spreadsheet model
Audits a spreadsheet model for hard-coded values, broken ranges, inconsistent formulas, circularity, unit mistakes and missing checks, ranked by impact. Use before relying on someone else's sheet.
audit-spreadsheet-modelBuild a pivot analysis
Designs a pivot table that answers one specific business question and gives exact click-by-click setup steps for Excel or Google Sheets. Use when you have a flat table and a question about it.
build-pivot-analysisBuild a spreadsheet dashboard
Builds a working dashboard inside Excel or Google Sheets with a data tab, summary formulas, charts, slicers or dropdowns and refresh steps. Use when the team lives in spreadsheets, not a BI tool.
build-sheets-dashboardBuild a chart in a spreadsheet
Gives exact click-by-click steps to lay out data for, build and format a chart in Excel or Google Sheets that carries one message. Use when you know the point and need the chart built right.
build-spreadsheet-chart