hermes

Make a Fermi estimate

Makes a Fermi estimate by decomposing a quantity, stating assumptions with ranges, cross-checking from another angle and naming the data that would tighten it. Use for sizing when no data exists.

context

You make Fermi estimates the way good consultants and physicists do: break a quantity nobody knows into factors people can reason about, put an honest range on each, combine them, and then attack the answer from a different direction. The value is the reasoning, not the number: a transparent estimate within a factor of two or three is useful, and a precise-looking number with hidden assumptions is not.

task

Estimate the following:

question

  1. Pin down the quantity: unit, place, time period, and what counts (for example "practising dentists, not all licensed", "per year"). If the question allows very different readings, choose the most useful one, say so, and note how the answer changes under the other reading.
  2. Decompose it into three to six factors that multiply or add to the answer, choosing factors that can each be reasoned about or looked up.
  3. For each factor give a low, central and high value (a range you are about 90% confident in) and the reasoning. Mark each as one of: given by the user, a widely known fact recalled from memory (to be verified), or an assumption.
  4. Combine: compute the central estimate with the arithmetic shown. For the range, do not just multiply all the lows and all the highs (that range is far too wide); combine in log space, multiplying the central values and widening by the root-sum-of-squares of each factor's log-range, or state a sensible range and say how you derived it.
  5. Cross-check with an independent decomposition (bottom-up versus top-down, supply versus demand, or a known benchmark). If the two disagree by more than a factor of three, find which assumption is likely wrong and revise.
  6. Name the one or two factors that drive most of the uncertainty, and the specific data that would narrow them.
constraints
  • Show every multiplication; round inputs and results to one or two significant figures.
  • Never present a recalled statistic as precise or current; label it "from memory, verify" and keep it inside a range.
  • Do not use a published figure for the answer itself as one of the factors; that is looking it up, not estimating. If the user wants the real figure, say where to find it after the estimate.
  • Keep the answer in one unit with a clear period; give the order of magnitude explicitly (for example "tens of thousands").
  • If the question is not a quantity (for example "Is my business idea good?"), say so and offer the quantities that would help decide it.
output format

Answer

The central estimate, the range and the order of magnitude, in one sentence.

The question pinned down

One or two sentences.

Decomposition

The formula in words (for example population x share who ... x frequency).

Calculation

Table: Factor | Low | Central | High | Basis (given, recalled, assumed) | Reasoning. Then the arithmetic for the central estimate and the range.

Cross-check

The second approach with its arithmetic, and how it compares.

Biggest uncertainties

One or two bullets.

Data that would tighten it

Bullets naming specific sources or measurements.

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
Data analysis
category
Statistics
level
Beginner
made for
Business analyst, Founder / business owner, Consultant / freelancer, Student
risk
read-only
version
v1.0.1 · 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

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install make-fermi-estimate --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill make-fermi-estimate -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the data-analysis plugin
claude plugin install hodios-data-analysis@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Statistics
PromptBusiness strategy

Estimate market size (TAM, SAM, SOM)

Estimates TAM, SAM and SOM bottom-up with explicit assumptions and low-base-high ranges, then cross-checks top-down. Use for a pitch, a business plan or a go/no-go on a new market.

estimate-market-size
PromptStatistics

Explain a statistics concept

Explains a statistics concept such as a p-value, confidence interval or power, with intuition, a worked example, a simulation and common misreadings. Use to finally get it.

explain-statistical-concept
PromptSpreadsheets

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.

run-what-if-analysis
PromptStatistics

Analyse A/B test results

Analyses A/B test results with a sample-ratio-mismatch check, effect sizes, confidence intervals and guardrail metrics, ending in a ship, iterate or stop call. Use when an experiment ends.

analyze-ab-test-results
PromptStatistics

Calculate sample size

Computes the sample size or statistical power for an experiment or survey, shows the formula and assumptions, and gives a sensitivity table. Use before launching an A/B test, study or survey.

calculate-sample-size
PromptStatistics

Check an analysis for pitfalls

Reviews an analysis for statistical pitfalls such as Simpson's paradox, p-hacking, survivorship, base rates and causal over-claims before it is shared. Use as a pre-publication review.

check-analysis-for-pitfalls