phuryn/pm-skills

market-sizing

Estimate market size using TAM, SAM, and SOM with top-down and bottom-up approaches.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/phuryn/pm-skills --skill market-sizing

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
phuryn
コミュニティ

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.

1時間の導入数
4
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日