You get:
- reading entire reports to find the one table you need
- missing key forecast data because it’s buried in methodology
- inconsistent numbers across reports because different base years
- no easy way to compare market size estimates across sources
- spending hours formatting numbers for presentations
But market reports have predictable structure:
- current market size: TAM in $ (base year)
- CAGR: projected growth rate
- forecast year: projected market size
- segment splits: by region, product type, customer size
- methodology note: primary vs. secondary research
Without extraction, you waste time and risk using wrong numbers.
This prompt pulls the essential market sizing numbers from any industry report.
Assume the role of a market analyst who extracts sizing data from industry reports. Your task is to pull current and forecast market numbers from the source. Generate: 1. MARKET SIZE (CURRENT) - Base year: [YYYY] - Global market size: [$X billion/million] - Regional split (if available): [North America: $X, EMEA: $X, APAC: $X] 2. MARKET FORECAST - Forecast year: [YYYY] - Projected market size: [$X billion/million] - CAGR (forecast period): [X%] 3. SEGMENT BREAKDOWNS - By product/service type: [Segment A: X%, Segment B: Y%] - By customer size: [Enterprise: X%, SMB: Y%] - By vertical/industry: [Most relevant verticals] 4. METHODOLOGY NOTE - Data sources: [Primary surveys / Secondary research / Both] - Sample size (if primary): [N=X] - Confidence level (if reported): [X%] 5. LIMITATIONS - What the report acknowledges it missed - What you should be skeptical about 6. CITATION-READY SUMMARY (one sentence) - "According to [Source/Year], the [Market Name] market was valued at $X in [Base Year] and is projected to reach $Y by [Forecast Year], growing at X% CAGR." INPUTS: Industry report content (relevant sections): [PASTE OR DESCRIBE] Market/industry name: [E.G., "Global Project Management Software Market"] Report publisher: [E.G., "Gartner, Forrester, IDC, Statista, internal"] Your use case: [E.G., "Investor pitch deck — need TAM, SAM, SOM"] RULES: - Always include the base year (market size without a date is useless) - Distinguish between TAM (total addressable), SAM (serviceable addressable), and SOM (serviceable obtainable) if reported - Flag forecast uncertainty — longer forecasts are less reliable - Note if numbers are inflation-adjusted or nominal - If multiple scenarios (optimistic/base/pessimistic), extract all three
- Run this on every industry report you read — build a database of market numbers by source.
- When forecasts conflict, cite the most recent report with the most transparent methodology.
- Always report the base year alongside market size — “$10B in 2025” not just “$10B.”
- For investor decks, lead with TAM, then show SAM and SOM to demonstrate realism.
- Update your numbers annually — markets change faster than reports are published.
Industry report content:
“The global AI software market was valued at $62.5 billion in 2024. By 2028, it is expected to reach $187.5 billion, representing a 31.6% CAGR. North America leads with 42% market share, followed by Europe (28%) and Asia-Pacific (24%). The fastest-growing segment is generative AI (38% CAGR). Methodology: survey of 2,000 enterprise IT decision-makers and analysis of public financial data.”
Market/industry name:
“Global AI Software Market”
Report publisher:
“IDC”
Your use case:
“Investor pitch deck for an AI startup”
This framework improves outcomes by forcing:
- current size extraction (with base year)
- forecast extraction (with CAGR)
- segment breakdowns (where the growth is)
- methodology awareness (how trustworthy are these numbers?)
- citation-ready summary (plug and play into decks)
Great market sizing extraction doesn’t just give you numbers — it gives you numbers you can trust and cite.
Build Better AI Systems
Subscribe for advanced prompt engineering, AI coding tools, debugging frameworks, and practical strategies for developers and engineers.