Market Sizing Agent Skill
Estimate market size using TAM, SAM, and SOM with top-down and bottom-up approaches. Use when sizing a market opportunity, estimating addressable market, preparing for investor pitches, or evaluating market entry.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/phuryn/pm-skills --skill market-sizingThe instruction itself
8 sections, as written by the authorEstimate 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)
- Market Definition: Define the market boundaries — what problem space, which customer segments, what geography or constraints apply
- Top-Down Estimation: Start from total industry size and narrow to the relevant slice
- Bottom-Up Estimation: Build from unit economics (customers × price × frequency) to cross-validate
- SAM Scoping: Identify which portion of TAM is realistically serviceable given product capabilities, channels, and constraints
- SOM Estimation: Estimate achievable share in the next 1-3 years based on competitive position and go-to-market capacity
- Growth Projection: Forecast how TAM, SAM, and SOM may evolve over the next 2-3 years
- 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
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take phuryn/market-sizing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.