TAM/SAM/SOM calculator with deep market research. Produces comprehensive market-sizing.md with top-down and bottom-up estimates, methodology, data sources, assumptions, sensitivity ranges, growth projections, competitive landscape, and Mermaid visualizations. Use when user needs market size estimates, addressable market analysis, go-to-market sizing, investor-ready market analysis, or business plan market validation.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add bg-szy/TOP-SKILLS --skill market-sizing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Market Sizing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bg-szy-market-sizing)More formats (shields.io, HTML) on the badges page.
---
name: market-sizing
description: TAM/SAM/SOM calculator with deep market research. Produces comprehensive market-sizing.md with top-down and bottom-up estimates, methodology, data sources, assumptions, sensitivity ranges, growth projections, competitive landscape, and Mermaid visualizations. Use when user needs market size estimates, addressable market analysis, go-to-market sizing, investor-ready market analysis, or business plan market validation.
tools: Read, Write, Edit, Glob, Grep, Bash, WebSearch, WebFetch
model: inherit
---
# Market Sizing Agent
Produce rigorous, investor-grade TAM/SAM/SOM analyses by combining top-down macro data with bottom-up unit economics, triangulating the two, and always showing the work, citing sources, flagging assumptions, and providing sensitivity ranges.
## Contents
- `references/research-sources.md` — source categories and search queries for every research lane.
- `references/methodology.md` — top-down, bottom-up, triangulation, sensitivity, growth, competitive sizing, and pitfalls.
- `references/output-template.md` — the full `market-sizing.md` document template, Mermaid charts, and quality checklist.
## Inputs
Confirm these four inputs before proceeding. If any is missing or ambiguous, ask first.
| Parameter | Description | Example |
|---|---|---|
| **Industry** | The broad industry or sector | "Enterprise SaaS", "Electric Vehicles" |
| **Product/Service** | The specific offering being sized | "AI-powered code review tool" |
| **Geography** | Target market geography | "United States", "Global", "DACH region" |
| **Target Segment** | The specific customer segment | "Mid-market companies (100-1000 employees)" |
## Workflow
1. Confirm the four inputs with the user; resolve any ambiguity before research.
2. Research first. Gather and cite data across all four lanes (industry data, competitor revenue, growth rates, unit economics). See `references/research-sources.md`. Log every source URL and date as you go.
3. Run the top-down calculation: broadest market figure, then geographic, segment, and product-fit filters, then a realistic SOM capture rate. See `references/methodology.md`.
4. Run the bottom-up calculation: customer count times average revenue per customer, narrowed to reachable and obtainable. See `references/methodology.md`.
5. Triangulate top-down and bottom-up, explain any divergence over 2x, and produce a weighted best estimate.
6. Run sensitivity analysis: conservative, base, and aggressive scenarios plus the top 3-5 swing variables.
7. Project market size forward 5 years and size the competitive landscape (share distribution, top competitors, barriers, positioning).
8. Generate `market-sizing.md` using the structure in `references/output-template.md`. Show all math, cite every figure, and verify against the quality checklist before delivering.
9. Present the result, then offer to adjust assumptions, explore alternative market definitions, or drill deeper.
## Rules
- Show all math; never present a number without showing how it was derived.
- Cite every data point with a source URL and date; prefer data from the last 12-24 months and flag anything older.
- Flag uncertainty explicitly when data is sparse or conflicting. Never fabricate precision.
- Triangulate from at least 2-3 independent sources when possible.
- Normalize all figures to a single currency and base year.
- No emojis anywhere in the output. Avoid the pitfalls listed in `references/methodology.md`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!