market-sizing
Skill0 starsChanged 38 days agoMITView on GitHub
Builds a defensible TAM/SAM/SOM market-sizing model with bottom-up and top-down triangulation and a low/base/high sensitivity range. Use when someone asks "how big is the market", "calculate my TAM", "size this opportunity", is preparing an investor deck market slide, or needs to defend a market number under diligence. Do NOT use for revenue projections of an existing business - use revenue-modeling instead.
31 other projects use a version of this.
Adopted by
Most recently taken up by
- solanabr/startup-builder-skilltheir own version, first seen Nov 1, 2026
- writer/skillstheir own version, first seen Nov 1, 2026
- Insightful-Pipe/marketing-strategy-skillstheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- daviszhen/agent-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use prioritize-features, brainstorm-okrs and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
skytiger6724Skillprioritize-features
Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations. Use when prioritizing a feature backlog, making scope decisions, or ranking product ideas.
Also in 4 projects that use this
skytiger6724Skillbrainstorm-okrs
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.
Also in 4 projects that use this
miovragSkillstrategy-red-team
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
Also in 3 projects that use this
launchapp-devSkillinterview-script
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
Also in 4 projects that use this
About-IntelligenceSkillbeachhead-segment
Identify the first beachhead market segment for a product launch.
Also in 4 projects that use this
nandanosqlSkillcustomer-journey-map
Map the complete customer experience across all touchpoints using the NNGroup framework. Identifies pain points, emotions, and opportunities at every stage of the user journey.
Also in 5 projects that use this
- +5 more from skytiger6724
Other versions31 projects use a version of this.
Word for word · 2
- SkillMedev/founder-fundraising-os★ 0100% same
- SkillMedev/startup-fundraising★ 0100% same
Edited · 0
None found.
Wrote their own version · 29
- openai/plugins★ 7.8ksame name
- OneWave-AI/claude-skills★ 378same name
- explorium-ai/gtm-skills★ 346same name
- hamzafarooq/claude-code-starter★ 145same name
- AlphaMao1/AlphaMao_Skills★ 130same name
- z1993/AlphaMao_Skills★ 130same name
- Mehdibargach/claude-code-pm-skills★ 97same name
- atypica-ai/marketing-skills★ 44same name
- raphaelxiao/mck_skills★ 32same name
- writer/skills★ 9same name
19 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- cold-email-craftSkill
- competitive-intelligenceSkill
- go-to-market-plannerSkill
- landing-page-copySkill
- pricing-strategySkill
- unit-economicsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Use your actual or expected ACV, not an aspirational one.
- Distinctive: line 72
If you are creating a category, size the adjacent budget you displace and the problem's current cost (including the cost of doing nothing).
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Market Sizing
A market size number is only useful if it is defensible. Investors have seen a thousand "100B TAM" slides and discount all of them. This skill builds a number you can defend under questioning by showing your work.
The Three Layers
- TAM (Total Addressable Market): total spend if everyone who could buy, did, at your price. The ceiling.
- SAM (Serviceable Addressable Market): the slice you can actually reach given product, geography, and segment.
- SOM (Serviceable Obtainable Market): what you can realistically win in 3-5 years given competition and execution. The number that matters for planning.
Build Bottom-Up First
Bottom-up is the credible method; build it before you ever cite a top-down analyst report.
TAM = (number of potential customers) × (annual contract value)
- Count customers from a real source: company databases, license counts, industry registries - not a guess.
- Use your actual or expected ACV, not an aspirational one.
- Segment the customer count by size; a mid-market customer and an enterprise pay very differently.
Bottom-up forces you to state your assumptions, which is exactly what a sharp investor will probe.
Triangulate Top-Down
Cross-check with top-down: take a credible total-spend figure from analyst reports and narrow it by the addressable fraction. If bottom-up and top-down land within ~2x of each other, you have a defensible range. If they diverge wildly, your assumptions are wrong somewhere - find out where.
SAM and SOM
- SAM: apply realistic filters - the segments your product actually serves, the geographies you operate in, the buyers you can reach.
- SOM: model market share capture over time against named competition. A 1-3% share of a large SAM in five years is more credible than 30% of a tiny one.
Show the Math
The number is worthless without the assumptions. Always present:
- The customer count and its source.
- The ACV and its basis.
- The narrowing logic from TAM to SAM to SOM.
- A sensitivity range (low / base / high) on the key assumptions.
Common Mistakes
- "1% of a huge market" - lazy and instantly discounted.
- Confusing market size with revenue opportunity for you specifically.
- Citing a single analyst report as the whole case.
- A SOM that implies implausible market share.
When the Market Is New
If you are creating a category, size the adjacent budget you displace and the problem's current cost (including the cost of doing nothing). New-category sizing is about the pain, not an existing line item.
Deliverable
Produce a sizing model with bottom-up TAM, top-down cross-check, SAM and SOM with explicit filters, a low/base/high sensitivity, and a one-paragraph defense of the SOM as the planning number.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

