rlaope/oh-my-hermes / skills/omh-market-research
omh-market-research
Verified[omh] Market sizing or customer/competitive analysis: investigate a scoped market with TAM/SAM/SOM sensitivity, attributed customer evidence, and comparable competitor/pricing profiles before a decision brief. Use when the user says: market-research, market sizing, tam sam som, bottom up market sizing, market size sensitivity, customer evidence analysis, jtbd evidence matrix, competitor pricing profiles.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.5 KB |
| references/competitive-pricing.md | markdown | 2.5 KB |
| references/customer-evidence.md | markdown | 2.4 KB |
| references/findings-template.md | markdown | 2.8 KB |
| references/full-contract.md | markdown | 3.5 KB |
| references/market-sizing.md | markdown | 3.3 KB |
| references/procedure.md | markdown | 7.1 KB |
references/market-sizing.md
View on GitHub# Market sizing method and worksheet
Use only for a scoped addressable-market question. Do not supply default figures.
1. Freeze buyer versus user, geography, product/use-case boundary, period,
currency/base year, count unit and revenue denominator. Exclude substitutes
only with a reason. Distinguish annual revenue, annual spend, installed stock,
transactions and potential buyers; never sum incompatible measures.
2. Register each operand before calculation: `I1 | value or unknown | unit |
population/denominator | observation period | S1 or A1 | applicability`.
`S1` names a retrieved source; `A1` names an explicit assumption with owner,
rationale, plausible bounds and validation need. A source pointer is not a read.
3. Build top-down TAM from the broad eligible population or spend, applying
documented segment filters without double-counting overlapping categories.
Build bottom-up TAM from eligible buyer counts times annual spend per buyer
(or annual units times price per unit). If inputs are unavailable, show the
symbolic formula and unknown, never a fabricated estimate.
4. Derive SAM by product, geography, channel, regulatory and service constraints
within TAM. Derive SOM for an explicit horizon from reachable accounts,
evidenced conversion assumptions, sales capacity, onboarding capacity and
retention. Do not select an arbitrary share of TAM. Require SOM <= SAM <= TAM
only when all three use the same currency, period and denominator.
5. Run formulas with a calculator or code tool and retain command/expression,
input IDs, result and unit. Record exchange-rate/date and inflation/base-year
adjustments separately; unknown operands must not silently become zero.
6. Reconcile top-down and bottom-up results: inspect taxonomy, overlap, time
period and spend-versus-revenue definitions. Never average incompatible
estimates. If only one method is feasible, say why the other is unavailable.
7. Use bounded low/base/high scenarios with source-based or labeled assumed
ranges. Vary each uncertain driver once (one-way sensitivity), state what was
held fixed and identify the driver changing the decision most. Do not call
these statistical confidence intervals or attach invented probabilities.
## Fillable output
Scope: [buyer, geography, period, currency/base year, denominator, cutoff]
| Layer | Population and exclusions | Formula with I/A IDs | Tool result + unit | Source coverage / limitation |
| --- | --- | --- | --- | --- |
| TAM top-down | [eligible universe] | [sourced formula] | [unknown until run] | [S IDs] |
| TAM bottom-up | [buyer count] | [count x annual spend] | [unknown until run] | [S/A IDs] |
| SAM | [serviceable constraints] | [nested filter] | [unknown until run] | [exclusions] |
| SOM | [horizon and capacity] | [reachable x conversion, capped by capacity] | [unknown until run] | [A IDs to test] |
| Driver | Low / base / high + units | Why bounded | Fixed inputs | Result range | Decision sensitivity |
| --- | --- | --- | --- | --- | --- |
| [I/A ID] | [unknown until supported] | [source or assumption] | [IDs] | [tool receipt] | [threshold crossed or unresolved] |
Close with reconciliation, contrary estimates, missing inputs, and the next
verification that could change the range. No market-size figure proves demand.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |