tam-sam-som
Skill0 starsChanged 5 months agoMITView on GitHub
Size a market with TAM / SAM / SOM using both top-down and bottom-up methods. Use when the user asks "how big is this market", needs market sizing for a pitch deck or business case, or is validating whether an opportunity is worth pursuing. Produces defensible numbers with stated assumptions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- bwfnx/sbdc-toolkittheir own version, first seen Aug 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- bwfnx/sbdc-toolkit★ 1same name
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 repository9 other files it gives its agents.
- cold-outreachSkill
- competitor-analysisSkill
- fundraising-narrativeSkill
- growth-experimentsSkill
- landing-page-copySkill
- market-researchSkill
- mvp-specSkill
- pricing-experimentsSkill
- pricing-strategySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 36
Don't inflate TAM to look big — a huge TAM with no bottom-up path reads as naive.
- Distinctive: line 37
Don't confuse "market size" with "revenue you'll get" (that's SOM, and smaller).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
tam-sam-som — market sizing
When to use
The user wants a credible market size for a deck, memo, or go/no-go decision, or asks "is this market big enough?". Investors expect a bottom-up number they can sanity-check — not a "1% of a $X trillion market" hand-wave.
Process
- Define the unit of demand precisely (who pays, for what, how often).
- TAM (Total Addressable Market) — everyone who could ever buy.
- SAM (Serviceable Addressable Market) — the slice you can reach with your product, geography, and channel today.
- SOM (Serviceable Obtainable Market) — what you can realistically win in 3–5 years given competition and capacity.
- Compute it two ways and reconcile:
- Top-down: industry report figure × filters (segment, region, ICP %).
- Bottom-up: (# target customers) × (annual contract value) × (capture %). Bottom-up is the one investors trust; lead with it.
- State every assumption and its source. Show the formula, not just the result.
What to produce
- A short table: TAM / SAM / SOM with the number, method, and key assumptions.
- One bottom-up formula written out (e.g.,
120,000 SMB dental clinics × $3,600 ACV × 3% = $13M SOM). - A sensitivity note: how the SOM moves if capture or ACV is ±50%.
Pitfalls
- Don't inflate TAM to look big — a huge TAM with no bottom-up path reads as naive.
- Don't confuse "market size" with "revenue you'll get" (that's SOM, and smaller).
- Cite the year and source of any top-down figure; stale numbers get challenged.
Report back
Give the three numbers, the bottom-up formula, the assumptions, and a one-line judgement: is the SOM large enough to support the business the user wants?
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.