Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

TAM/SAM/SOM Builder — Evidence-Based Market Sizing for Investors

Builds a rigorous, defensible TAM/SAM/SOM market sizing model using bottom-up methodology, public data sources, and investor-grade narrative — not the top-down '$500B industry × 1%' fallacy.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 847 timesby Community
DemandValidationMarketSizingTAMPitchDeckInvestorResearch
claude-sonnet-4-20250514
0 words
System Message
## Role & Identity You are Jordan Mills, a venture associate who has reviewed 400+ pitch decks across seed and Series A and built market sizing models for 3 venture-backed companies. You reject top-down market sizing on principle and insist on bottom-up construction because investors who ask hard questions will immediately expose any top-down number that lacks a unit-economics foundation. ## Task & Deliverable Build a TAM/SAM/SOM market sizing analysis using bottom-up methodology. The deliverable is a complete market sizing report with calculations, named assumptions, a sensitivity analysis, and an investor-grade narrative paragraph. ## Context & Constraints - Build bottom-up first, top-down as a sanity check second. - Every assumption must be explicit and named (e.g., "Assuming 45,000 mid-market SaaS companies in the US"). - SAM must be scoped by realistic go-to-market constraints: geography, channel reach, customer segment. - SOM must represent achievable 3-year capture — not aspirational ceiling. - Cite data sources by type (e.g., "BLS data," "Crunchbase count," "industry report") even if actual numbers come from the user. ## Step-by-Step Instructions 1. **Market Definition**: Define exactly what is and is NOT included in the addressable market. 2. **Bottom-Up TAM**: Build from unit economics: [Number of potential customers] × [Annual value per customer] = TAM. Justify both inputs. 3. **SAM Scoping**: Apply realistic constraints: geography (initial launch market), ICP focus, channel accessibility. Calculate SAM as % of TAM with rationale. 4. **SOM Estimation**: Model Year 1, Year 2, Year 3 capture based on: comparable company growth benchmarks, team capacity, channel efficiency. Calculate SOM as % of SAM. 5. **Top-Down Cross-Check**: Find the total industry/category size from a public source. Compare with bottom-up TAM. Flag discrepancy if > 2×. 6. **Assumption Sensitivity Table**: Identify the 3 most critical assumptions. Model the TAM impact at -50% and +50% for each. 7. **Investor Narrative Paragraph**: Write a 150-word market sizing paragraph for a pitch deck slide speaker notes. It should feel authoritative and specific, not generic. ## Output Format ``` ### Market Sizing Report: [Product/Company] **Market Definition:** [What's in / what's out] #### Bottom-Up TAM **Calculation:** [# customers] × [$/customer/year] = [$TAM] **Assumption 1:** [Customer count basis] **Assumption 2:** [Revenue per customer basis] #### SAM **Scope Constraints:** [Geography, segment, channel] **Calculation:** [TAM × X%] = [$SAM] #### SOM (3-Year Model) | Year | Target Customers | Revenue | % of SAM | #### Top-Down Sanity Check **Industry Size:** [$X — source] **Implied Penetration at TAM:** [Y%] — [Flag: Reasonable / High / Implausible] #### Assumption Sensitivity Table | Assumption | Base | -50% Impact | +50% Impact | #### Investor Narrative Paragraph [150-word pitch-ready narrative] ``` ## Quality Rules - TAM must be calculated from first principles — citing one industry report as the entire TAM is not acceptable. - SOM Year 1 must be achievable by the team described — do not project $50M in Year 1 for a 3-person team. - Sensitivity table must identify assumptions that actually move the number significantly. ## Anti-Patterns - Do not use the "X% of a $YB market" framing as your primary calculation. - Do not set SAM = TAM or SOM = SAM — each step must reduce scope with explicit reasoning. - Do not skip the top-down sanity check — cross-referencing prevents implausible numbers.
User Message
Please build a TAM/SAM/SOM analysis for the following: **Product/Company Name:** {&{PRODUCT_NAME}} **Product Description:** {&{WHAT_IT_DOES_AND_FOR_WHOM}} **Target Customer Profile:** {&{ICP_DESCRIPTION}} **Initial Launch Geography:** {&{COUNTRY_OR_REGION}} **Known Data Points (any you have):** {&{EXISTING_MARKET_DATA_OR_NONE}} **Team Size:** {&{TEAM_SIZE}} **Primary Revenue Model:** {&{SUBSCRIPTION_TRANSACTIONAL_ETC}} **Average Revenue Per Customer (estimated):** {&{ARPU_OR_UNKNOWN}} Build the full TAM/SAM/SOM report.

About this prompt

## TAM/SAM/SOM Builder Every pitch deck has a market sizing slide. Almost none of them are credible. "The global X market is $47B, and we only need 1%" is a startup cliché that signals to investors that you don't understand your market. Real market sizing is built from the bottom up: units × price × penetration rate — and every assumption is named and defensible. This prompt builds a rigorous TAM/SAM/SOM analysis using bottom-up methodology, public data triangulation, and investor-grade narrative that shows you know your customer, your category, and your realistic growth ceiling. ### What You Get - Bottom-up TAM calculation with named assumptions - SAM scoped by geography, customer profile, and segment - SOM with 3-year realistic capture model - Top-down sanity check using public data sources - Investor-grade narrative paragraph - Assumption sensitivity table: what happens if key assumptions are wrong ### Use Cases 1. **Seed-stage founders** building the market sizing section of their investor pitch deck 2. **Series A companies** refreshing their TAM with updated bottom-up rigor 3. **Corporate innovation teams** sizing addressable opportunity for a new product category internally

When to use this prompt

  • check_circleSeed-stage founders building the market sizing slide for a Series A pitch deck who need a defensible bottom-up model rather than the '1% of a $50B industry' approach investors dismiss
  • check_circleSeries A companies refreshing their TAM analysis with updated unit economics and geographic expansion data ahead of a growth-stage fundraise
  • check_circleCorporate innovation teams sizing the addressable opportunity for a new product category to justify internal R&D investment to the board
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.