startup-business-analyst-market-opportunity
Generate comprehensive market opportunity analysis with TAM/SAM/SOM calculations
What this skill does
# Market Opportunity Analysis Generate a comprehensive market opportunity analysis for a startup, including Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) calculations using both bottom-up and top-down methodologies. ## Use this skill when - Working on market opportunity analysis tasks or workflows - Needing guidance, best practices, or checklists for market opportunity analysis ## Do not use this skill when - The task is unrelated to market opportunity analysis - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## What This Command Does This command guides through an interactive market sizing process to: 1. Define the target market and customer segments 2. Gather relevant market data 3. Calculate TAM using bottom-up methodology 4. Validate with top-down analysis 5. Narrow to SAM with appropriate filters 6. Estimate realistic SOM (3-5 year opportunity) 7. Present findings in a formatted report ## Instructions for Claude When this command is invoked, follow these steps: ### Step 1: Gather Context Ask the user for essential information: - **Product/Service Description:** What problem is being solved? - **Target Customers:** Who is the ideal customer? (industry, size, geography) - **Business Model:** How does pricing work? (subscription, transaction, etc.) - **Stage:** What stage is the company? (pre-launch, seed, Series A) - **Geography:** Initial target market (US, North America, Global) ### Step 2: Activate market-sizing-analysis Skill The market-sizing-analysis skill provides comprehensive methodologies. Reference it for: - Bottom-up calculation frameworks - Top-down validation approaches - Industry-specific templates - Data source recommendations ### Step 3: Conduct Bottom-Up Analysis **For B2B/SaaS:** 1. Define customer segments (company size, industry, use case) 2. Estimate number of companies in each segment 3. Determine average contract value (ACV) per segment 4. Calculate TAM: Σ (Segment Size × ACV) **For Consumer/Marketplace:** 1. Define target user demographics 2. Estimate total addressable users 3. Determine average revenue per user (ARPU) 4. Calculate TAM: Total Users × ARPU × Frequency **For Transactions/E-commerce:** 1. Estimate total transaction volume (GMV) 2. Determine take rate or margin 3. Calculate TAM: Total GMV × Take Rate ### Step 4: Gather Market Data Use available tools to research: - **WebSearch:** Find industry reports, market size estimates, public company data - **Cite all sources** with URLs and publication dates - **Document assumptions** clearly Recommended data sources (from skill): - Government data (Census, BLS) - Industry reports (Gartner, Forrester, Statista) - Public company filings (10-K reports) - Trade associations - Academic research ### Step 5: Top-Down Validation Validate bottom-up calculation: 1. Find total market category size from research 2. Apply geographic filters 3. Apply segment/product filters 4. Compare to bottom-up TAM (should be within 30%) If variance > 30%, investigate and explain differences. ### Step 6: Calculate SAM Apply realistic filters to narrow TAM: - **Geographic:** Regions actually serviceable - **Product Capability:** Features needed to serve - **Market Readiness:** Customers ready to adopt - **Addressable Switching:** Can reach and convert Formula: ``` SAM = TAM × Geographic % × Product Fit % × Market Readiness % ``` ### Step 7: Estimate SOM Calculate realistic obtainable market share: **Conservative Approach (Recommended):** - Year 3: 2-3% of SAM - Year 5: 4-6% of SAM **Consider:** - Competitive intensity - Available resources (funding, team) - Go-to-market effectiveness - Differentiation strength ### Step 8: Create Market Sizing Report Generate a comprehensive markdown report with: **Section 1: Executive Summary** - Market opportunity in one paragraph - TAM/SAM/SOM headline numbers **Section 2: Market Definition** - Problem being solved - Target customer profile - Geographic scope - Time horizon **Section 3: Bottom-Up Analysis** - Customer segment breakdown - Segment sizing with sources - TAM calculation with formula - Assumptions documented **Section 4: Top-Down Validation** - Industry category and size - Filter application - Validated TAM - Comparison to bottom-up **Section 5: SAM Calculation** - Filters applied with rationale - SAM formula and result - Segment-level breakdown **Section 6: SOM Projection** - Market share assumptions - Year 3 and Year 5 estimates - Customer count implications - Revenue projections **Section 7: Market Growth** - Industry growth rate (CAGR) - Key growth drivers - 5-year market evolution **Section 8: Validation and Sanity Checks** - Public company comparisons - Customer count validation - Competitive context **Section 9: Investment Thesis** - Market opportunity assessment - Key positives and risks - Venture-scale potential - Next steps ### Step 9: Save Report Offer to save the report as a markdown file: - Suggest filename: `market-opportunity-analysis-YYYY-MM-DD.md` - Use Write tool to create file - Confirm file location with user ## Tips for Best Results **Do:** - Start with bottom-up (most credible) - Always triangulate with top-down - Cite all data sources - Document every assumption - Be conservative on SOM - Compare to public company benchmarks - Explain any data gaps or limitations **Don't:** - Rely solely on top-down - Cherry-pick optimistic data - Claim >10% SOM without strong justification - Mix methodologies inappropriately - Ignore competitive context - Skip validation steps ## Example Usage ``` User: /market-opportunity Claude: I'll help you create a comprehensive market opportunity analysis. Let me start by gathering some context. What product or service are you analyzing? → "AI-powered email marketing for e-commerce companies" Who are your target customers? → "E-commerce companies with $1M+ annual revenue in North America" What's your pricing model? → "Subscription: $50-500/month based on email volume, average $300/month" [Claude proceeds with analysis, gathering data, calculating TAM/SAM/SOM, and generating report] ``` ## Integration with Other Commands This command pairs well with: - `/financial-projections` - Use SOM to build revenue model - `/business-case` - Include market sizing in business case ## Notes - Market sizing typically takes 30-60 minutes for thorough analysis - Quality depends on data availability - explain limitations - Update annually as market evolves - Conservative estimates build credibility with investors ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.