pkking/market-sizing
dotfiles/dot_config/skillshare/skills/market-sizing/SKILL.md
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.
tools
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add pkking/dotfiles market-sizingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 9:48 AM30.4s2 files scanned
SKILL.md
- name:
- market-sizing
- description:
- 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.
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)
- Market Definition: Define the market boundaries — what problem space, which customer segments, what geography or constraints apply
- Top-Down Estimation: Start from total industry size and narrow to the relevant slice
- Bottom-Up Estimation: Build from unit economics (customers × price × frequency) to cross-validate
- SAM Scoping: Identify which portion of TAM is realistically serviceable given product capabilities, channels, and constraints
- SOM Estimation: Estimate achievable share in the next 1-3 years based on competitive position and go-to-market capacity
- Growth Projection: Forecast how TAM, SAM, and SOM may evolve over the next 2-3 years
- 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
| Metric | Current Estimate | 2-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
- Market Research: Advanced Techniques
- User Interviews: The Ultimate Guide to Research Interviews
- Crossing the Chasm: The Ultimate Guide For PMs
- Product Innovation Masterclass (video course)
Related Skills
pkking/writing-great-skills
testing
VerifiedTrustedCommunity
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
SKILL.mdUpdated Jul 13, 2026
pkking/webapp-testing
tools
VerifiedTrustedCommunity
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
SKILL.mdUpdated Jul 13, 2026
pkking/web-artifacts-builder
tools
VerifiedTrustedCommunity
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
SKILL.mdUpdated Jul 13, 2026
pkking/wayfinder
data-ai
VerifiedTrustedCommunity
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
SKILL.mdUpdated Jul 13, 2026