tam-sam-som-calculator
Calculate TAM, SAM, and SOM with explicit assumptions, methods, and caveats. Use when sizing a market for a product idea, business case, or executive review.
What this skill does
## Purpose Guide product managers through calculating Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) for a product idea by asking adaptive, contextually relevant questions. Use this to build defensible market size estimates backed by real-world citations, economic projections, and population data—essential for pitching to investors, securing budget, or validating product-market fit. This is not a back-of-napkin guess—it's a structured, citation-backed analysis that withstands scrutiny. ## Key Concepts ### TAM/SAM/SOM Framework The three-tier market sizing model: **Total Addressable Market (TAM):** - The total market demand for a product or service - "If we captured 100% of the market, what's the revenue?" - Broadest possible market (no constraints) **Serviceable Available Market (SAM):** - The segment of TAM your company can realistically target - Narrowed by geography, firmographics, demographics, or product constraints - "Who can we actually reach with our product?" **Serviceable Obtainable Market (SOM):** - The portion of SAM you can realistically capture - Accounts for competition, market constraints, go-to-market capacity - "What can we capture in the next 1-3 years?" ### Why This Works - **Top-down validation:** TAM → SAM → SOM ensures estimates are grounded in reality - **Investor-friendly:** Standard framework VCs and execs understand - **Citation-backed:** Real data sources (Census, Statista, World Bank) add credibility - **Adaptive:** Questions adjust based on context (B2B vs. B2C, US vs. global, etc.) ### Anti-Patterns (What This Is NOT) - **Not a single-number guess:** "The market is $10B" without supporting data - **Not static:** Markets evolve—reassess annually - **Not a substitute for customer validation:** Market size ≠ product-market fit ### When to Use This - Pitching to investors or execs (need market size in deck) - Validating product ideas (is the market big enough?) - Prioritizing product lines (which has bigger opportunity?) - Setting growth targets (what's realistic to capture?) ### When NOT to Use This - For internal tools with captive users (no external market) - Before defining the problem (market sizing requires clear problem space) - As the only validation (pair with customer research) --- ### Facilitation Source of Truth Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill. It defines: - session heads-up + entry mode (Guided, Context dump, Best guess) - one-question turns with plain-language prompts - progress labels (for example, Context Qx/8 and Scoring Qx/5) - interruption handling and pause/resume behavior - numbered recommendations at decision points - quick-select numbered response options for regular questions (include `Other (specify)` when useful) This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic. ## Application Use `template.md` for the full fill-in structure. This interactive skill asks **up to 4 adaptive questions**, offering **enumerated context-aware options** at each step. The agent adapts questions based on previous responses. --- ### Step 0: Gather Context (Before Questions) **Agent suggests:** Before we begin, it's helpful to have product context. If available, please share: **For Your Own Product:** - Website copy (homepage, product pages, value prop statements) - Marketing emails or landing pages - Product descriptions or positioning statements - Case studies or customer testimonials - Sales deck or pitch materials **If You Don't Have a Product Yet:** - Find a similar or adjacent product (competitor or analog) - Copy their website homepage, product description, or landing page - We'll use this as a reference point for market sizing **You can paste this content directly, or we can proceed with a brief description.** **Why this helps:** - Marketing materials already contain target audience, pain points, and value props - Analyzing real content (yours or competitors') grounds the analysis in reality - You can benchmark against similar products' market positioning --- ### Optional Helper Script (Deterministic Math) If you already have population and ARPU numbers (or a TAM estimate), you can run a deterministic helper to compute TAM/SAM/SOM and generate a Markdown table. This script does **not** fetch data or write files. ```bash python3 scripts/market-sizing.py --population 5400000 --arpu 1000 --sam-share 30% --som-share 10% ``` --- ### Question 1: Problem Space **Agent asks:** "Based on the context you've provided (or will describe), what problem space are you exploring for market sizing?" **Offer 4 enumerated examples (user can select by number or write custom):** 1. **B2B SaaS productivity** — E.g., "Workflow automation for small business operations" (like Zapier, Integromat) 2. **Consumer fintech** — E.g., "Personal budgeting app for Gen Z users" (like Mint, YNAB) 3. **Healthcare/telehealth** — E.g., "Mental health support for remote workers" (like BetterHelp, Talkspace) 4. **E-commerce enablement** — E.g., "Payment processing for online sellers" (like Stripe, Square) **Or write your own problem space description based on the marketing materials you shared.** **Tip:** If you provided website copy or marketing materials, the agent can extract the problem space from phrases like: - "We help [target] solve [problem]" - "The #1 solution for [use case]" - Customer pain points in testimonials or case studies **User response:** [Selection or custom description] --- ### Question 2: Geographic Region **Agent asks:** "What geographic region are you targeting?" **Offer 4 enumerated options (adapted based on problem space):** 1. **United States** — Best for detailed Census Bureau data, BLS stats, robust industry reports 2. **European Union** — Use Eurostat, local statistical agencies; note GDPR/compliance considerations 3. **Global** — World Bank, IMF data; broader but less granular 4. **Specific country/region** — E.g., "Canada," "Southeast Asia," "Latin America" **Or specify your own region.** **User response:** [Selection or custom] **Adaptation logic:** - If user selected B2B SaaS (Question 1, Option 1) → Emphasize US/EU markets (mature SaaS adoption) - If user selected Consumer fintech (Question 1, Option 2) → Mention emerging markets (higher mobile adoption) --- ### Question 3: Industry/Market Segments **Agent asks:** "What specific industry or market segments does this problem space relate to?" **Offer 4 enumerated options (adapted based on problem space + geography):** **Example (if Question 1 = B2B SaaS, Question 2 = US):** 1. **SMB services sector** — 5.4M businesses, $1.2T revenue (US Census, 2023) 2. **Professional services (legal, accounting)** — 1.1M firms, $850B revenue (IBISWorld, 2023) 3. **Healthcare providers** — 900K practices, $4T industry (BLS, 2023) 4. **Tech/software companies** — 500K firms, $1.8T revenue (Statista, 2023) **Or describe your own industry segment.** **User response:** [Selection or custom] **Adaptation logic:** - If Question 1 = Consumer fintech, offer consumer segments (e.g., "Gen Z 18-25," "Millennials 25-40") - If Question 1 = Healthcare, offer segments (e.g., "Primary care physicians," "Therapists/counselors") --- ### Question 4: Potential Customers (Demographics/Firmographics) **Agent asks:** "Who are the potential customers affected by this problem?" **Offer 4 enumerated options (adapted based on previous answers):** **Example (if Question 1 = B2B SaaS, Question 3 = SMB services sector):** 1. **SMBs with 10-50 employees** — 1.2M businesses, $400B revenue (Census Bureau, 2023) 2. **SMBs with 50-250 employees** — 600K businesses, $800B revenue (Census Bureau, 2023) 3. **Solo entrepreneurs/freelancers** — 3.5M self-employed, $200B revenue (BLS, 2023) 4. **Service businesses with online presence** — 2M businesses, $600B e-com
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.