bundles/startup/skills/market-sizer/SKILL.md
Use this skill when users need to calculate market size (TAM/SAM/SOM), assess market opportunity, validate market potential, or determine if a market is big enough to pursue. Activates for "how big is the market," "TAM," "market sizing," or market opportunity questions.
npx skillsauth add shipshitdev/library market-sizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Market sizing specialist applying Hexa's practical market assessment methodology. Help founders determine if their target market is big enough using rigorous bottom-up AND top-down analysis.
Hexa's Core Principle: "Make sure you can approximate how big the market is—ideally by confronting bottom-up and top-down analysis."
| Term | Definition | What It Means | |------|------------|---------------| | TAM | Total Addressable Market | Everyone who could theoretically buy | | SAM | Serviceable Available Market | The segment you can actually reach | | SOM | Serviceable Obtainable Market | What you can realistically capture in 3-5 years |
Market Size = Bottom-Up Analysis + Top-Down Analysis + Timing Assessment
TAM = Total Potential Customers × Annual Revenue Per Customer
SAM = TAM × Percentage You Can Reach
SOM = SAM × Realistic Market Share (1-5% years 1-3)
Start with industry reports, narrow to your slice.
Common Sources: Gartner, Forrester, Statista, IBISWorld, CB Insights
| Your Goal | Required SOM | Required SAM | |-----------|--------------|--------------| | Lifestyle ($500K-2M/year) | $500K-2M | $10M+ | | Venture-scale ($10M+ ARR) | $10M+ | $100M+ | | Unicorn potential ($100M+) | $100M+ | $1B+ |
The 10% Rule: If you captured 10% of SAM, would that be interesting?
The two methods should be within 2-3x of each other.
| Variance | Meaning | Action | |----------|---------|--------| | < 50% | Good alignment | Proceed with confidence | | 50-200% | Reasonable | Investigate discrepancy | | > 200% | Major misalignment | One method is wrong |
| Stage | Characteristics | Implication | |-------|-----------------|-------------| | Emerging | < $100M, few players | High risk, high reward | | Growing | 20%+ growth, new entrants | Good timing | | Mature | < 10% growth, clear leaders | Need strong wedge | | Declining | Negative growth | Avoid unless transforming |
| Skill | When to Use |
|-------|-------------|
| idea-validator | Validate the idea for this market |
| startup-icp-definer | Define ideal customer in this market |
| competitive-intelligence-analyst | Deep dive on competitors |
| fundraise-advisor | Present market size to investors |
For complete bottom-up/top-down worksheets, market dynamics assessment, timing analysis framework, output format template, market size benchmarks by business type and ACV, and common mistakes to avoid, see: references/full-guide.md
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.