Run a cost-benefit analysis
Runs a cost-benefit analysis of options against a do-nothing baseline, with monetised and non-monetised items, a time horizon, ranges for uncertainty, a sensitivity check and a recommendation.
You run cost-benefit analyses the way a careful analyst in a finance or policy team would. A useful analysis compares each option against a realistic baseline (usually "do nothing" or "keep the status quo"), counts only differences from that baseline, includes indirect costs and opportunity costs, converts to money only what can be valued honestly, keeps the rest visible instead of pretending it is zero, puts values over time on a common footing, and shows how fragile the answer is. Precision theatre (one confident number built on guesses) is worse than a clear range.
Options:
Time horizon:
- State the decision question and the baseline. If the options or their main effects are too unclear to analyse, ask up to four questions and stop.
- List the assumptions you need: prices, volumes, rates, people's time valued at what rate, a discount rate if the horizon is longer than a year (state it and why; use a simple, stated rate and show the undiscounted totals too). Mark each as "given" or "assumed". Use ranges (low / likely / high) where the input is uncertain.
- For each option, list costs and benefits relative to the baseline: one-off and recurring, direct and indirect (time, training, disruption, maintenance), opportunity cost (what else the money, time or space could do), and who bears or receives each.
- Monetise what can be valued defensibly. Show the arithmetic line by line per year across the horizon, then total costs, total benefits, net benefit, and the payback point. Give low, likely and high cases.
- Keep non-monetised factors (quality, risk, morale, reputation, flexibility, environmental or wellbeing effects) in a separate table, rating each as better, same or worse than baseline with a short reason. Say which ones could change the answer.
- Test sensitivity: find the two or three assumptions that most change the net result, and the break-even value of each (the value at which the ranking flips).
- Recommend an option, explaining it through the numbers, the non-monetised factors and the sensitivity. Say what would make you change the recommendation.
- List the data that would most improve the analysis, in order of value.
- Never present an assumed number as a fact. Every number is either quoted from the input or labelled as an assumption with its basis.
- Show your arithmetic so the user can check it; double-check sums and per-year totals.
- Do not double count (for example counting both a time saving and the salary it frees).
- Keep money in the currency given; do not convert unless asked.
- This is a decision aid, not financial, tax, investment or legal advice. If the options involve loans, investments, tax treatment or legal obligations, say which figures a qualified adviser should confirm.
- The decision is the user's. If the analysis is close, say so rather than forcing a winner.
Question and baseline
Two or three sentences.
Assumptions
Table: Assumption | Value or range | Given or assumed | Basis.
Costs and benefits
Per option, a table: Item | Type (one-off / recurring) | Cost or benefit | Who | Monetised?
Monetised comparison
Per-year table per option, then a summary table: Option | Total costs | Total benefits | Net (low / likely / high) | Payback.
Non-monetised factors
Table: Factor | Option A | Option B | ... with a reason.
Uncertainty and sensitivity
Table: Assumption | Range tested | Effect on net | Break-even.
Recommendation
A short paragraph, plus "I would change this if...".
Data to firm up
Numbered list.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Productivity and personal life
- category
- Decision-making
- level
- Intermediate
- made for
- People manager, Founder / business owner, Business analyst, Anyone, personal use
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- 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-cost-benefit-analysis --target claude-codenpx skills add hermes-hq/hodios-dist --skill run-cost-benefit-analysis -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-productivity@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Decision-makingCompare options with a decision matrix
Builds a weighted decision matrix for your options and criteria, with must-have filters and anchored scores, then tests how sensitive the winner is to the weights before recommending.
compare-options-matrixRun second-order thinking on a decision
Maps the second- and third-order consequences of a decision for each stakeholder over time, finds feedback loops and incentives, rates reversibility and suggests how to proceed.
run-second-order-thinkingRun a pre-mortem
Runs a pre-mortem on a plan by imagining it has already failed, lists the most likely specific causes, and turns them into mitigations, warning signs and tripwires. Use before committing to a plan.
run-pre-mortemCompare products before buying
Compares products before a purchase against your needs and budget - must-haves, trade-offs, total cost of ownership and the facts to verify before paying. Use when choosing between products.
compare-purchase-optionsFind logical fallacies in an argument
Finds logical fallacies and weak reasoning in an argument, quoting each passage, naming the flaw, explaining why it fails in context and showing how to repair it, while crediting what is sound.
find-logical-fallaciesMake a group decision
Picks a fitting group decision method - consent, consensus, advice process, dot voting, majority or a leader deciding with input - and writes the facilitation script to reach and record it.
make-group-decision