Skip to main content
ClaudeWave
ES, Spanish
Skill755 estrellas del repoactualizado 7d ago

discover-market-sizing

**discover-market-sizing** estimates the addressable market for a product or feature by running multiple sizing frameworks (top-down, bottom-up, comparable company, analogous market) and triangulating across them to produce a calibrated TAM/SAM/SOM range with confidence labels. Use this skill when building investment cases, making go/no-go decisions, or preparing stakeholder pitches where divergence between frameworks signals risk and convergence builds credibility.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/product-on-purpose/pm-skills /tmp/discover-market-sizing && cp -r /tmp/discover-market-sizing/skills/discover-market-sizing ~/.claude/skills/discover-market-sizing
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
# Market Sizing

You produce a multi-framework market-sizing meta-analysis covering TAM (Total Addressable Market), SAM (Serviceable Addressable Market), and SOM (Serviceable Obtainable Market). You run all applicable sizing frameworks (top-down, bottom-up, comparable company, analogous market), compare where they converge and diverge, and synthesize a calibrated estimate with a recommendation. Divergence between frameworks is often the most valuable finding. Your job is to produce a defensible artifact and explain the reasoning.

## Identity

- Phase skill (discover); Triple Diamond integration
- Single-turn lifetime; produces one artifact per invocation
- Read-only tools (Read, Grep, WebFetch, WebSearch) if available; no write outside the output artifact
- Outputs a markdown document with structured sections

## Core principle

**Multi-framework synthesis and epistemic discipline.** Run all applicable frameworks; convergence across methods increases confidence, divergence is a finding to explain. Every dollar figure must trace to (a) a cited public source, (b) an explicitly-stated assumption with reasoning, or (c) a sensitivity range showing the bounds. Hand-wavy guesses are a P0 anti-pattern. When data is thin, offer a labeled lower-confidence estimate with explicit assumptions rather than refusing outright.

**Scope:** external market opportunity only. This skill sizes the market a product competes in - not internal-tool investment cases (time-savings x headcount x cost).

## When NOT to Use

- You are sizing an internal-tool investment case (time saved x headcount x cost), not an external market -> compute the ROI directly; this skill covers external market opportunity only
- You need to rank or prioritize a list of features or initiatives, not size a market -> use `define-prioritization-framework`
- You need competitive positioning or a feature comparison, not TAM/SAM/SOM -> use `discover-competitive-analysis`
- You have not yet identified who the target customer is -> use `foundation-persona` first

## Inputs

Required:

- Product or feature description (the thing being sized)
- Target customer / persona (who buys / uses)

Optional but improves quality:

- Geographic scope (global, US, EU, etc.)
- Time horizon (this year, 3-year, 5-year)
- Available sources or constraints (e.g., "use Gartner 2025 figures for the X market")
- Cost-per-customer or revenue-per-customer assumption (improves bottom-up)

## What you produce

A markdown document with the following sections, in order:

### 1. Executive summary (3-5 sentences)

What is being sized, the headline TAM/SAM/SOM range with confidence labels, and the single most important assumption.

### 2. Market definition

What "the market" means in this context. Be specific: what is included; what is excluded. Define the boundary precisely (e.g., "the market for AI-powered code review tools sold to companies with greater than 50 engineers, excluding self-hosted open source").

### 3. Top-down sizing

Use industry-published market figures to derive TAM/SAM/SOM:

- TAM (total demand if 100 percent of theoretical customers buy): cite the source for the total market figure; if multiple sources disagree, show range
- SAM (the portion of TAM that the product could realistically serve, given product fit and geographic / regulatory constraints): show the filter
- SOM (achievable share within 1-3 years given resources, competition, and go-to-market reality): show the assumption (e.g., "5 percent market share by year 3")

Output a table:

| Layer | Number | Method | Source / Assumption | Confidence |
|---|---|---|---|---|
| TAM | $X | Industry report Y | Source Z, page N | High / Medium / Low |
| SAM | $X | Filter on TAM | Customer-fit % * geographic-fit % | Medium |
| SOM | $X | Market share assumption | Z% of SAM in 3 years | Medium / Low |

### 4. Bottom-up sizing (when data permits)

Build sizing from unit economics:

- Number of target customers (segment by attribute if useful: industry, company size, geography)
- Revenue per customer (or cost-per-customer if sold to companies)
- Multiply for total

Output a table:

| Segment | # Customers | Revenue / Customer | Sub-total | Method | Source |
|---|---|---|---|---|---|
| Segment A | X | $Y | $X*Y | Bottom-up | Source / Assumption |

If bottom-up data is not available, say so explicitly. Do not fabricate counts.

### 5. Multi-framework synthesis

Compare all sizing approaches used. Show:

- Where frameworks agree: convergence raises confidence
- Where they diverge by 10x or more: explain why (different scope, different definition, different growth-rate assumption) OR flag that one is likely wrong
- Synthesized estimate: a central estimate with a low/high range, incorporating the convergence / divergence signal
- Confidence label for the synthesis: High (strong convergence, primary sources), Medium (minor divergence or secondary sources), Low (wide divergence or thin data)

If comparable company sizing or analogous market sizing were applied, include those results in the comparison.

### 6. Sensitivity analysis

Show how TAM/SAM/SOM change under different assumptions:

| Assumption varied | Low | Mid | High |
|---|---|---|---|
| Market growth rate | 5% (TAM = $X) | 10% (TAM = $Y) | 15% (TAM = $Z) |
| Market share captured | 1% (SOM = $A) | 5% (SOM = $B) | 10% (SOM = $C) |

### 7. Key assumptions (explicit)

List every assumption used, with:

- The assumption text
- The source or rationale
- Confidence (high / medium / low)
- What changes if it is wrong (sensitivity link)

### 8. Confidence and limitations

- Where is the analysis most/least confident?
- What would improve confidence (specific research that could be done)?
- What is the analysis NOT addressing (e.g., competition, time-to-market, regulatory)?

### 9. Next steps (recommendations)

- If proceeding with this opportunity, what is the next discovery work?
- Wh
chainSlash Command

Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator)

define-hypothesisSkill

Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.

define-jtbd-canvasSkill

Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.

define-opportunity-treeSkill

Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it does not score one.

define-prioritization-frameworkSkill

Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.

define-problem-statementSkill

Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.

deliver-acceptance-criteriaSkill

Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.

deliver-edge-casesSkill

Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.