borghei/Claude-Skills / personal-productivity/pitch-deck-reviewer
pitch-deck-reviewer
VerifiedScore a pitch deck's structure and content against YC, Sequoia, and a16z heuristics. Use before sending a deck to investors, practicing a pitch, or reviewing a seed or Series A fundraising deck.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.8 KB |
| assets/deck_summary_template.md | markdown | 941 B |
| references/pitch_deck_heuristics.md | markdown | 5.4 KB |
| scripts/deck_structure_scorer.py | script | 9.3 KB |
references/pitch_deck_heuristics.md
View on GitHub# Pitch Deck Heuristics
Public guidance from YC, Sequoia, a16z, and others converges on a similar deck structure. This guide synthesizes them.
---
## Common Structure (Seed Deck — 10-12 slides)
1. **Title / vision** — Company name + 1-line "what you do" statement
2. **Problem** — The pain you're solving, in customer language
3. **Solution / product** — How you solve it (visuals, not words)
4. **Why now** — What recent shift makes this newly possible / urgent
5. **Market size** — Bottoms-up TAM, ideally with growth rate
6. **Business model** — How you make money + unit economics teaser
7. **Traction** — Hard numbers (or, pre-revenue: signups, LOIs, usage)
8. **Competition** — Honest landscape; your differentiation
9. **Team** — Why you specifically can do this
10. **Ask** — How much, what milestones, what timeline
Some decks add: roadmap, vision-end-state, customer quotes.
---
## Series A Deck — 12-15 slides
Series A buys traction, not promise. Structure shifts:
1. **Title / vision**
2. **What we do** (one-line clarity — investors won't know your category)
3. **Traction (deep)** — 12-24 months of metrics, MoM/YoY growth
4. **Unit economics** — CAC, LTV, payback, gross margin, contribution margin
5. **Customer evidence** — Case studies, named logos, quantified outcomes
6. **Market size** — Validated bottoms-up using your customer data
7. **Competitive position** — Honest map, including incumbent threats
8. **Why us / unfair advantage** — Founder-market fit, insight, moat
9. **Roadmap (next 12-18 months)**
10. **Team & key planned hires**
11. **Ask / use of funds** — Specific milestones the round buys
12. **Vision** — Where this goes long-term
---
## Heuristics from Each Source
### Y Combinator (Demo Day deck)
YC's published guidance emphasizes:
- One idea per slide
- Clear problem framing (most decks fail here)
- Specific traction numbers
- Founder-team relevance to the problem
- Honest competition framing
- Ask + use of funds
YC famously uses concise pitch decks (often 10-12 slides max) and a strict "could you describe the company in 1 sentence?" exercise.
### Sequoia ("Writing a Business Plan")
Sequoia's classic guidance covers:
- Company purpose (1 declarative sentence)
- Problem and customer pain
- Solution (value prop)
- Why now
- Market size (bottoms-up)
- Competition / alternatives
- Product (with roadmap)
- Business model
- Team
- Financials (for later stage)
- Vision
Sequoia emphasizes the **discipline of clarity** — every slide must be readable in a few seconds and stand alone.
### Andreessen Horowitz (a16z)
a16z published "16 Slides for Startup Pitch":
- Title
- Vision
- The problem
- The solution
- Why now
- Market size
- Competition
- Product (live demo if possible)
- Business model
- Strategic relationships
- Team
- Traction
- Financials (if applicable)
- Ask
- Backup slides (for likely questions)
a16z emphasizes the **vision slide as a separate slide** — what does the world look like if you succeed?
---
## Common Mistakes
### Problem-slide failures
- Stating a fact rather than a pain ("there are 100M people with X" — so what?)
- Using your category's language rather than the customer's
- Talking about competitor failures rather than user pain
### Solution-slide failures
- Buzzword salad
- No screenshots
- Describing features rather than what becomes possible
### Why-now failures
- Skipping it entirely
- Vague "AI is hot" — what specifically about your product is newly possible?
### Market-size failures
- Top-down only ("$5T healthcare market") with no bottoms-up
- Conflating addressable with capturable
- Inflated numbers that get challenged in diligence
### Traction failures
- Vague "strong growth" without numbers
- Cherry-picked time windows
- Hiding churn
### Competition failures
- "We have no competition" (red flag)
- Only listing competitors you can beat
- Listing 50 and missing the 2 that matter
### Team failures
- LinkedIn dump
- No relevance to the specific problem
- Hiding gaps without naming them
### Ask failures
- "Raising $X" without milestones
- Use-of-funds that doesn't match the ask amount
- Skipping or downplaying the ask
---
## Format Heuristics
- Slide count: seed 10-12, Series A 12-15. Not 30.
- One idea per slide.
- Numbers > adjectives.
- Screenshots > screenshots-of-screenshots.
- Brand template, not generic Office.
- Plays well at 1366×768 (still common projector resolution).
- PDF version available.
---
## What to Optimize For
**Seed:** Optimize for getting a meeting. The deck rarely closes; the conversation does.
**Series A:** Optimize for surviving 30-60-90 day diligence. Numbers must hold up.
**Beyond:** Optimize for clarity of strategic narrative; metrics matter but so does the question of where this is heading.
---
## What Decks Don't Solve
A deck doesn't make a bad business fundable. It does ensure a fundable business doesn't get passed for structural reasons.
The decks that get funded are 80% great business + 20% great deck. Don't confuse the order.
---
## Resources
- **Y Combinator Library:** ycombinator.com/library — public guidance on deck construction
- **Sequoia "Writing a Business Plan":** sequoiacap.com/article/writing-a-business-plan
- **a16z "Startup Pitch Decks":** a16z.com — search for the deck guides
- **Pitch.com / DocSend** — published example decks (Airbnb seed deck is a famous reference)
- **Forerunner Ventures / Bessemer Memo** — published memos giving structural insight
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |