Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Market Sizing

ASecurity

Walks through both top-down and bottom-up market sizing methodologies with explicit assumption tracking. Produces investor-ready estimates with transparent reasoning.

7 stars
0 votes
0 copies
0 views
Added 10/3/2026
businessrustgo

Security Analysis

A100/100

Scanned 10/3/2026

$npx -y skills add EdgeCaser/shipwright --skill market-sizing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Market Sizing?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Market Sizing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/edgecaser-market-sizing-shipwright/badge)](https://www.skillsdirectory.com/skills/edgecaser-market-sizing-shipwright)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: market-sizing
description: "Walks through both top-down and bottom-up market sizing methodologies with explicit assumption tracking. Produces investor-ready estimates with transparent reasoning."
category: discovery
default_depth: standard
---

# Market Sizing (TAM / SAM / SOM)

Read `docs/workflow-contract.md` once per session before applying this skill. Resolve it from the nearest ancestor of this file containing `manifest.json`; all Shipwright paths are relative to that root.

## Description

Walks through both top-down and bottom-up market sizing methodologies with explicit assumption tracking. Produces investor-ready estimates with transparent reasoning.

## When to Use

- Evaluating a new market opportunity
- Preparing investor decks or business cases
- Prioritizing between multiple market segments
- Sanity-checking revenue projections

## Depth

| Scope | Use When | Sections to Include |
|---|---|---|
| **Light** | Quick sanity check on whether a market is worth exploring | Top-Down Sizing only, single-source TAM/SAM/SOM |
| **Standard** | Business case or investor deck preparation | All sections |
| **Deep** | Board-level investment decision or new market entry | All sections + scenario modeling (bull/base/bear), sensitivity analysis on top 3 assumptions, comparable company benchmarks |

**Omit rules:** At Light depth, skip Bottom-Up Sizing, Triangulation, and the full Assumption Register. Retain citations, calculation steps and inline assumptions for each TAM/SAM/SOM estimate.

## Key Definitions

- **TAM (Total Addressable Market):** The total revenue opportunity if you captured 100% of the market
- **SAM (Serviceable Addressable Market):** The portion of TAM your product can realistically reach given current product scope, geography, and go-to-market
- **SOM (Serviceable Obtainable Market):** The realistic share of SAM you can capture in a defined timeframe given competition, resources, and brand awareness

## Framework

### Method 1: Top-Down Sizing

Start from a known market size and narrow down.

```markdown
## Top-Down Estimate

### TAM
Source: [Industry report / analyst estimate]
Total market value: $[X]B
Basis: [What's included, e.g., "global project management software spending"]
Year: [year of estimate]

### SAM
Narrowing factors:
- Geography: [e.g., North America only → 40% of TAM]
- Segment: [e.g., SMB only → 25% of remaining]
- Product scope: [e.g., only collaboration features → 60% of remaining]
SAM = TAM × [factor1] × [factor2] × [factor3] = $[Y]B

### SOM
Capture assumptions:
- Year 1 market share target: [X]%
- Basis: [comparable company benchmarks or bottoms-up capacity]
SOM = SAM × [capture rate] = $[Z]M
```

### Method 2: Bottom-Up Sizing

Build from unit economics upward.

```markdown
## Bottom-Up Estimate

### Unit Economics
- Target customer: [persona / company profile]
- Average annual contract value (ACV): $[X]
- Basis for ACV: [pricing model × expected usage]

### Addressable Customer Count
- Total companies in target segment: [N]
- Source: [Census data / LinkedIn / industry report]
- Filter 1: [e.g., 10-500 employees → N1]
- Filter 2: [e.g., uses [category] tools → N2]
- Filter 3: [e.g., in target verticals → N3]
- Addressable customers: [N3]

### Market Size
- TAM = [Total potential customers] × ACV = $[X]
- SAM = [Reachable customers] × ACV = $[Y]
- SOM = [Capturable in timeframe] × ACV = $[Z]
```

### Step 3: Triangulate & Validate

Always produce both top-down and bottom-up estimates and compare:

```markdown
## Triangulation
| Method | TAM | SAM | SOM |
|---|---|---|---|
| Top-Down | $[X]B | $[Y]B | $[Z]M |
| Bottom-Up | $[X]B | $[Y]B | $[Z]M |
| Delta | [%] | [%] | [%] |

## Reconciliation
[Explain why the estimates differ and which you trust more for each tier]
```

### Step 4: Assumption Register

Every market sizing exercise must include an explicit assumption log:

```markdown
## Assumption Register
| # | Assumption | Value Used | Sensitivity | Source |
|---|---|---|---|---|
| A1 | ACV | $[X] | HIGH, ±20% changes SOM by $[Y]M | [source] |
| A2 | Segment penetration | [X]% | MEDIUM | [source] |
| A3 | Market growth rate | [X]% CAGR | LOW | [analyst report] |
```

**Sensitivity:** HIGH = changes the conclusion, MEDIUM = shifts magnitude, LOW = minor impact.

## Minimum Evidence Bar

**Required inputs:** Target market definition (industry, geography, or customer segment) and at least one of: pricing model, comparable company data, or industry report reference.

**Acceptable evidence:** Analyst reports (Gartner, IDC, CB Insights), government/census data, public company filings, industry association statistics, comparable company revenue disclosures, or primary research with documented sample sizes.

**Insufficient evidence:** If no credible source exists for the TAM base figure, state "Insufficient evidence for TAM estimate" and stop and recommend sourcing an industry report (Gartner, IDC, CB Insights) or running a bottom-up count from public data (e.g., LinkedIn, Census Bureau) before attempting this skill.

**Hypotheses vs. findings:**
- **Findings:** TAM base figures and customer counts must cite a specific source with publication year.
- **Hypotheses:** Narrowing factors (segment penetration, capture rate) and ACV assumptions may be estimated, label each as "assumed" with sensitivity rating in the Assumption Register.

## Output Format

Produce a market sizing document with:
1. **Executive Summary**, TAM/SAM/SOM headline numbers with confidence ranges
2. **Top-Down Analysis**, with sources and narrowing factors
3. **Bottom-Up Analysis**, with unit economics and customer counts
4. **Triangulation**, comparison and reconciliation
5. **Assumption Register**, all assumptions with sensitivity ratings
6. **Visualization**, nested TAM > SAM > SOM summary

**Shipwright Signature (required closing):**
7. **Decision Frame**, Whether the market justifies investment given SOM range, trade-off between market size confidence vs. speed to decision, confidence in estimates with evidence quality, owner, decision date, revisit trigger
8. **Unknowns & Evidence Gaps**, Assumptions with HIGH sensitivity that lack primary sources, segments with no bottom-up validation
9. **Pass/Fail Readiness**, PASS if both top-down and bottom-up estimates are present with cited sources and deltas are reconciled (at Light depth: PASS if top-down TAM/SAM/SOM is present with at least one cited source; bottom-up and triangulation not required); FAIL if only one method used or TAM source is undocumented (at Light depth: FAIL if TAM source is undocumented)
10. **Recommended Next Artifact**, Which Shipwright skill to run next and why

## Common Mistakes to Avoid

- **Conflating TAM with opportunity**, TAM is theoretical; SOM is what matters for planning
- **Cherry-picking favorable estimates**, Show both methods and reconcile honestly
- **Hidden assumptions**, Every number should have a source or a labeled assumption
- **Ignoring growth rates**, Static sizing misses trajectory; include CAGR estimates
- **Precision theater**, A range ($800M-$1.2B) is more honest than a false-precision point estimate ($943M)

## Weak vs. Strong Output

**Weak:**
> "TAM is $50B based on the global SaaS market."

Unsourced, uses an overbroad category, no narrowing logic, makes any SOM look artificially large.

**Strong:**
> "TAM is $8.2B (Gartner 2025, global spend on employee onboarding software). SAM = $2.5B after filtering to North America (40%) and mid-market 100-1000 employees (76% of segment). Source: LinkedIn company count cross-referenced with BLS data."

Cited, narrowed with explicit factors, uses two independent sources for triangulation.

Attribution

EdgeCaserEdgeCaser
View sourceSee grades on GitHubMore from EdgeCaser →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Email Composer

Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.

304952 votes

Solution Architect

Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.

192 votes

Akorchak:Venture Assessment

Generate a comprehensive VC investment assessment report for a company

72 votes

Telegram Compose

Compose rich, readable Telegram messages using HTML formatting via direct Telegram API. Use when: (1) Sending any Telegram message beyond a simple one-line reply, (2) Creating structured messages with sections, lists, or status updates, (3) Need formatting unavailable via Clawdbot's Markdown conversion (underline, spoilers, expandable blockquotes, user mentions by ID), (4) Sending alerts, reports, summaries, or notifications to Telegram, (5) Want professional, scannable message formatting wit...

6511 votes

Just Fucking Cancel

Find and cancel unwanted subscriptions by analyzing bank transactions. Detects recurring charges, calculates annual waste, and helps you cancel with direct URLs and browser automation. Use when: 'cancel subscriptions', 'audit subscriptions', 'find recurring charges', 'what am I paying for', 'save money', 'subscription cleanup', 'stop wasting money'. Supports CSV import (Apple Card, Chase, Amex, Citi, Bank of America, Capital One, Mint, Copilot) OR Plaid API for automatic transaction pull. Out...

6511 votes
View all in business →