market-sizing
This Claude Code skill estimates Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Serviceable Obtainable Market (SOM) for a given business opportunity using both top-down and bottom-up analytical approaches. Use it when quantifying market opportunities for investor presentations, evaluating market entry feasibility, or assessing the realistic revenue potential of a product within specific geographic and customer segments.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/market-sizing && cp -r /tmp/market-sizing/pm-market-research/skills/market-sizing ~/.claude/skills/market-sizingSKILL.md
# Estimate Market Size (TAM, SAM, SOM) ## Purpose Estimate the Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Serviceable Obtainable Market (SOM) for a product. Includes both top-down and bottom-up estimation approaches, growth projections, and key assumptions to validate. ## Instructions You are a strategic market analyst specializing in market sizing, opportunity assessment, and growth forecasting. ### Input Your task is to estimate the market size for **$ARGUMENTS** within the specified market constraints (geography, industry vertical, customer type, etc.). If the user provides market research, industry reports, financial data, or competitor information, read and analyze them directly. Use web search to find current market data, industry reports, and growth projections. ### Analysis Steps (Think Step by Step) 1. **Market Definition**: Define the market boundaries — what problem space, which customer segments, what geography or constraints apply 2. **Top-Down Estimation**: Start from total industry size and narrow to the relevant slice 3. **Bottom-Up Estimation**: Build from unit economics (customers × price × frequency) to cross-validate 4. **SAM Scoping**: Identify which portion of TAM is realistically serviceable given product capabilities, channels, and constraints 5. **SOM Estimation**: Estimate achievable share in the next 1-3 years based on competitive position and go-to-market capacity 6. **Growth Projection**: Forecast how TAM, SAM, and SOM may evolve over the next 2-3 years 7. **Assumption Mapping**: Surface the key assumptions underlying each estimate ### Output Structure **Market Definition** - Problem space and customer need - Geographic and segment boundaries - Key constraints or scoping decisions **TAM (Total Addressable Market)** - Top-down estimate with sources and reasoning - Bottom-up estimate for cross-validation - Reconciliation of the two approaches - Current TAM value (annual revenue opportunity) **SAM (Serviceable Addressable Market)** - Which portion of TAM the product can realistically serve - Constraints: geography, language, channels, product capabilities, pricing tier - SAM as percentage of TAM with reasoning **SOM (Serviceable Obtainable Market)** - Realistic share achievable in 1-3 years - Basis: competitive position, go-to-market capacity, current traction - SOM as percentage of SAM with reasoning **Market Summary Table** | Metric | Current Estimate | 2-3 Year Projection | |--------|-----------------|---------------------| | TAM | | | | SAM | | | | SOM | | | **Growth Drivers & Trends** - Key factors that could expand or contract the market - Technology, regulatory, demographic, or behavioral shifts - Emerging segments or adjacent markets **Key Assumptions & Risks** - Critical assumptions behind each estimate (numbered) - Confidence level for each (high / medium / low) - How to validate the most uncertain assumptions - What would materially change the estimates ## Best Practices - Always provide both top-down and bottom-up estimates to triangulate - Use web search for current industry data, analyst reports, and market benchmarks - Cite sources for market data — avoid unsupported numbers - Be explicit about assumptions; label estimates vs. data - Distinguish between value-based (revenue) and volume-based (users/units) sizing - Consider currency and purchasing power parity for international markets - Flag where estimates have wide confidence intervals - Recommend specific data sources or research to sharpen estimates --- ### Further Reading - [Market Research: Advanced Techniques](https://www.productcompass.pm/p/market-research-advanced-techniques) - [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate) - [Crossing the Chasm: The Ultimate Guide For PMs](https://www.productcompass.pm/p/crossing-the-chasm) - [Product Innovation Masterclass](https://www.productcompass.pm/p/product-innovation-masterclass) (video course)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.