market-sizing
TAM/SAM/SOM market sizing with top-down and bottom-up estimation methods, cross-validation of assumptions, and divergence reconciliation. Generates investor-ready materials with growth projections and confidence intervals. Use when estimating addressable markets, validating opportunity size, or preparing pitch deck market slides.
What this skill does
# Market Sizing TAM/SAM/SOM framework for estimating addressable market and validating opportunity size. ## Definitions | Metric | Definition | Question It Answers | |--------|------------|---------------------| | **TAM** | Total Addressable Market — everyone who could possibly buy | "What's the theoretical ceiling?" | | **SAM** | Serviceable Addressable Market — segment you can actually reach | "What can we realistically target?" | | **SOM** | Serviceable Obtainable Market — realistic share in 3 years | "What will we actually capture?" | ``` +-------------------------------------------------------+ | TAM | | +---------------------------------------------------+ | | | SAM | | | | +-----------------------------------------------+| | | | | SOM || | | | +-----------------------------------------------+| | | +---------------------------------------------------+ | +-------------------------------------------------------+ ``` ## When to Use Top-Down vs. Bottom-Up | Method | Use When | Risk | |--------|----------|------| | **Top-Down** | Industry reports exist; investor pitch; quick estimate | Overestimates SOM | | **Bottom-Up** | Sales capacity known; pricing validated; more credible | More work; requires assumptions | | **Both (recommended)** | High-stakes decisions; fundraising; board decks | Cross-validate to build confidence | Always cross-validate both methods and reconcile within 20%. If they diverge by more than that, revisit your assumptions. ## Quick Formulas ``` Top-Down TAM = (# potential customers) × (annual value per customer) SAM = TAM × (% your solution can address) SOM = SAM × (realistic market share % in 3 years) Bottom-Up SOM = (# customers you can acquire) × (average deal size) SAM = SOM / (your expected market share %) TAM = SAM / (your segment as % of total market) ``` ## Example: AI Code Review Tool ```markdown ## Market Sizing: AI Code Review Tool ### Top-Down TAM - Global developers: 28M - Using code review tools: 60% → 16.8M - Average annual spend: $300/developer - TAM = $5.04B SAM - Enterprise only (>500 employees): 8M developers - Willing to pay premium: 40% → 3.2M - SAM = $960M SOM - Sales capacity supports ~$15M ARR (Year 3) - Realistic market share: 2% - Unconstrained SOM = $960M × 2% = $19.2M - Constrained SOM = min($19.2M, $15M) = $15M ### Bottom-Up - Target accounts Year 1: 50 enterprise deals - Average ACV: $100K - Year 1 ARR: $5M - Year 3 (3× growth): $15M ARR → SOM = $15M ### Reconciled SOM: $15M (confirmed by both methods) ``` ## SOM Constraint Model Do not report an unconstrained SOM. Always apply real-world limits: ``` SOM constraints: Sales capacity: supports $15M ARR max Competitive pressure: 5 strong incumbents → −20% market share Go-to-market reach: 70% of SAM reachable with current channels Conservative SOM = min( SAM × target_share%, sales_capacity_ceiling, SAM × gtm_reach% × target_share% ) ``` ## Confidence Levels | Confidence | Evidence Required | |------------|------------------| | HIGH | Multiple corroborating sources, data < 2 years old | | MEDIUM | Single authoritative source, 1-2 years old | | LOW | Extrapolated, heavy assumptions, data > 2 years old | Always label each number with its confidence level in deliverables. ## Common Mistakes | Mistake | Correction | |---------|------------| | TAM = "everyone on earth" | Define a specific, bounded customer segment | | SOM = 10% of a billion-dollar market | Apply actual sales capacity and GTM constraints | | Single method only | Cross-validate top-down and bottom-up | | Old data | Use sources < 2 years old; flag if older | | Ignoring competition | SOM must account for incumbents' share | ## References - [TAM/SAM/SOM Rules](rules/market-tam-sam-som.md) — Calculation methods, SOM constraint model, cross-referencing - [TAM/SAM/SOM Guide](references/tam-sam-som-guide.md) — Detailed guide with data source recommendations ## Related Skills - `ork:competitive-analysis` — Understand competitive dynamics that constrain SOM - `ork:business-case` — Build financial justification once opportunity is sized - `ork:product-frameworks` — Full product strategy toolkit --- Version: 1.0.0
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".