agentleFS
teodstrteodstr/boardroom/skills/market-sizing/SKILL.md

market-sizing

Skill0 starsChanged 3 days agoMITView on GitHub

Estimate the size of a market (TAM, SAM, SOM) with transparent top-down and bottom-up calculations, explicit assumptions, scenarios and a sanity check. Use for business plans, pitch decks, market entry, "how big is the market for X", or case-interview estimates. Triggers: "market size", "TAM SAM SOM", "market sizing", "how big is the market", "taille de marché", "marché potentiel", "estimer le marché", "tamaño de mercado", "mercado potencial", "dimensionar el mercado".

32 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • skytiger6724Skill

    prioritize-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

  • skytiger6724Skill

    brainstorm-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

  • miovragSkill

    strategy-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-devSkill

    interview-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-IntelligenceSkill

    beachhead-segment

    Identify the first beachhead market segment for a product launch.

    Also in 4 projects that use this

  • nandanosqlSkill

    customer-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

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 28 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
  1. Distinctive:

    Top-down: start from a published total (with its source) and apply successive filters, each one sourced or labeled as an assumption.

    line 35
  2. Distinctive:

    Every input is labeled Source (with a reference) or Assumption (with its reasoning).

    line 75

“Common” is measured: kept by at least 6 in 10 of the 28 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Market sizing

Estimate how big an opportunity is, in a way anyone can check: every number has a source or a stated assumption, and every step of the calculation is visible.

When to use

  • Business plans, pitch decks, market entry decisions, investment memos.
  • Case-interview estimates ("How many coffees are sold in Paris each day?").
  • For the profitability of each customer, use unit-economics.

Inputs

  1. The product, the customer, the geography and the unit (value per year in a currency, or volume).
  2. Any data the user has: industry reports, statistics, prices, customer counts.

Method

  1. Define the market precisely: what is sold, to whom, where, over what period. Most errors come from a vague definition.
  2. Define the three levels:
    • TAM (total addressable market): total demand for the category in the geography, at 100% market share.
    • SAM (serviceable available market): the part the company can actually serve with its offer, channels and geography.
    • SOM (serviceable obtainable market): the share it can realistically win in 3–5 years, given competition and resources.
  3. Top-down: start from a published total (with its source) and apply successive filters, each one sourced or labeled as an assumption.
  4. Bottom-up: number of target customers × adoption rate × purchases per year × average price. Prefer it for the SOM: it is what investors trust.
  5. Triangulate: compare both results. If they differ by more than about 2×, revisit the assumptions.
  6. Run scenarios: low, base and high on the two most uncertain assumptions.
  7. Round the results. False precision ruins credibility.

For case interviews without data: break the population into segments, use round numbers, say each assumption aloud, and check the result against common sense.

Output

### Market definition
<Product, customer, geography, unit, period.>

### Top-down
| Step | Value | Source or assumption |
|---|---|---|

### Bottom-up
| Driver | Value | Source or assumption |
|---|---|---|
Customers × adoption × frequency × price = …

### Results
| Level | Value | How |
|---|---|---|
| TAM | … | … |
| SAM | … | … |
| SOM | … | … |

### Scenarios
| Scenario | Key assumptions | SOM |
|---|---|---|

### So what
<What the size means for the decision.>

Quality bar

  • Every input is labeled Source (with a reference) or Assumption (with its reasoning). No figure is presented as a fact without a source.
  • Units and periods are consistent at every step, and the formulas are visible.
  • Top-down and bottom-up are both done and compared.
  • The SOM is realistic compared with the shares that competitors hold.
  • Results are rounded and end with what they mean for the decision.
  • Written in the user's language, with the standard terms below.

Terminology

EnglishFrançaisEspañol
Total addressable market (TAM)Marché total adressableMercado total direccionable
Serviceable available market (SAM)Marché adressable accessibleMercado disponible
Serviceable obtainable market (SOM)Part de marché atteignableMercado obtenible
Top-down / bottom-upApproche descendante / ascendanteEnfoque descendente / ascendente
AssumptionHypothèseSupuesto

Sources

  • Blank, S., & Dorf, B. (2012). The Startup Owner's Manual. K&S Ranch.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.