agentleFS
daviszhendaviszhen/agent-skills/skills/phuryn-pm-skills-pm-market-research-market-sizing/SKILL.md

market-sizing

Skill1 starsChanged 26 days agoMITView on GitHub

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.

32 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 5

    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:

    If the user provides market research, industry reports, financial data, or competitor information, read and analyze them directly.

    line 18
  2. Distinctive:

    Top-Down Estimation: Start from total industry size and narrow to the relevant slice

    line 23
  3. Distinctive:

    Always provide both top-down and bottom-up estimates to triangulate

    line 74
  4. Distinctive:

    Use web search for current industry data, analyst reports, and market benchmarks

    line 75
  5. Distinctive:

    Consider currency and purchasing power parity for international markets

    line 79

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

Estimate 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)

  1. Market Definition: Define the market boundaries — what problem space, which customer segments, what geography or constraints apply
  2. Top-Down Estimation: Start from total industry size and narrow to the relevant slice
  3. Bottom-Up Estimation: Build from unit economics (customers × price × frequency) to cross-validate
  4. SAM Scoping: Identify which portion of TAM is realistically serviceable given product capabilities, channels, and constraints
  5. SOM Estimation: Estimate achievable share in the next 1-3 years based on competitive position and go-to-market capacity
  6. Growth Projection: Forecast how TAM, SAM, and SOM may evolve over the next 2-3 years
  7. 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

MetricCurrent Estimate2-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

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.