market-sizing

$npx mdskill add OneWave-AI/claude-skills/market-sizing

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.

SKILL.md

.github/skills/market-sizingView on GitHub ↗
---
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`.

More from OneWave-AI/claude-skills

SkillDescription
accessibility-auditorAudit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
agent-armyDeploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
agent-swarm-deployerDeploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.
agent-team-builderDesigns and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
agent-to-agentAgent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.
ai-readiness-assessmentAssesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.
animateGenerate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.
api-documentation-writerGenerate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.
api-endpoint-scaffolderGenerate REST API endpoints with proper structure, validation, error handling, and types. Use when creating new API routes, endpoints, or backend services.
api-load-testerLoad tests API endpoints with progressive concurrency. Measures response times, error rates, throughput, and identifies breaking points. Generates a detailed report with latency percentiles, throughput curves, bottleneck analysis, and optimization recommendations.