business
Startup Pitch Deck
Slide-by-slide pitch deck guide covering problem, solution, market size, business model, traction, team, financials, and ask — with investor-ready structure and common red flags to avoid.
pitch-deckfundraisingstartupinvestorspresentation
Works well with agents
Works well with skills
$ npx skills add The-AI-Directory-Company/(…) --skill startup-pitch-deckSKILL.md
Markdown
| 1 | |
| 2 | # Startup Pitch Deck |
| 3 | |
| 4 | ## Before you start |
| 5 | |
| 6 | Gather the following from the user: |
| 7 | |
| 8 | 1. **What stage?** (Pre-seed, seed, Series A, Series B+) |
| 9 | 2. **How much are you raising?** (Target amount and intended use of funds) |
| 10 | 3. **What is the product?** (One-sentence description a non-expert would understand) |
| 11 | 4. **Do you have traction?** (Revenue, users, growth rate, key metrics) |
| 12 | 5. **Who is the audience?** (VC firm, angel investors, accelerator, corporate partnership) |
| 13 | 6. **How will this be presented?** (Live pitch with Q&A, sent cold via email, both) |
| 14 | |
| 15 | If the user wants to start with the solution slide, push back: "Investors fund problems, not solutions. Start with a problem so painful that the audience is already nodding before you show what you built." |
| 16 | |
| 17 | ## Deck structure — slide by slide |
| 18 | |
| 19 | A standard investor pitch deck is 10-14 slides. Every slide has one job. Below is the recommended order and content for each. |
| 20 | |
| 21 | ### Slide 1: Title |
| 22 | ``` |
| 23 | [Company Name] — [what you do in 10 words or fewer] |
| 24 | [Presenter name, title] | Raising $X at [stage] |
| 25 | ``` |
| 26 | |
| 27 | ### Slide 2: Problem |
| 28 | ``` |
| 29 | - Who has this problem (specific persona, not "everyone") |
| 30 | - How they solve it today (status quo) |
| 31 | - Why the status quo is painful (quantify: time, cost, error rate) |
| 32 | - Include one data point: "X% of [audience] report [problem]" |
| 33 | ``` |
| 34 | |
| 35 | ### Slide 3: Solution |
| 36 | ``` |
| 37 | - What your product does (one paragraph, no jargon) |
| 38 | - How it solves the problem differently from the status quo |
| 39 | - One screenshot or diagram — show outcome, not feature list |
| 40 | ``` |
| 41 | |
| 42 | ### Slide 4: Market size |
| 43 | ``` |
| 44 | TAM: Total Addressable Market — everyone who could theoretically buy |
| 45 | SAM: Serviceable Addressable Market — segment you can reach with current model |
| 46 | SOM: Serviceable Obtainable Market — realistic capture in 3-5 years |
| 47 | |
| 48 | Present as: TAM $XB → SAM $YB → SOM $ZM |
| 49 | Cite sources for each number. "We estimated" is not a source. |
| 50 | ``` |
| 51 | |
| 52 | ### Slide 5: Business model |
| 53 | ``` |
| 54 | - How you make money (subscription, usage, marketplace, licensing) |
| 55 | - Pricing: what the customer pays and how (per seat, per transaction, tiered) |
| 56 | - Unit economics: CAC, LTV, LTV:CAC ratio, gross margin |
| 57 | - If pre-revenue: planned pricing model with comparable benchmarks |
| 58 | ``` |
| 59 | |
| 60 | ### Slide 6: Traction |
| 61 | ``` |
| 62 | Show a chart. Investors scan for slope, not absolute numbers. |
| 63 | - Revenue or MRR over time (best) |
| 64 | - User growth over time (acceptable at pre-seed/seed) |
| 65 | - Key milestones: launch date, notable customers, partnerships |
| 66 | |
| 67 | Include 2-3 specific numbers: |
| 68 | "$X MRR, growing Y% month-over-month" |
| 69 | "Z paying customers including [notable name]" |
| 70 | ``` |
| 71 | |
| 72 | ### Slide 7: Go-to-market |
| 73 | ``` |
| 74 | - How you acquire customers today (channel, cost) |
| 75 | - Top 2-3 channels you will scale |
| 76 | - Sales motion: self-serve, inside sales, enterprise sales, PLG |
| 77 | - Current CAC and target CAC at scale |
| 78 | ``` |
| 79 | |
| 80 | ### Slide 8: Competitive landscape |
| 81 | ``` |
| 82 | Use a 2x2 matrix or comparison table. Position yourself in the best quadrant. |
| 83 | - Choose axes that highlight your differentiation |
| 84 | - Include direct competitors and the status quo |
| 85 | - One sentence on why your position is defensible |
| 86 | |
| 87 | Never say "we have no competitors." |
| 88 | ``` |
| 89 | |
| 90 | ### Slide 9: Team |
| 91 | ``` |
| 92 | - 2-4 founders/key hires with one-line bios |
| 93 | - Relevant experience: what in their background makes them the right team for THIS problem |
| 94 | - Notable: prior exits, domain expertise, technical depth |
| 95 | - Advisory board (if notable names) |
| 96 | |
| 97 | Skip generic bios. "10 years of experience" means nothing. "Built the payments system at Stripe" means everything. |
| 98 | ``` |
| 99 | |
| 100 | ### Slide 10: Financials |
| 101 | ``` |
| 102 | - 3-year projection: revenue, expenses, headcount |
| 103 | - Key assumptions stated explicitly (growth rate, conversion rate, churn) |
| 104 | - Current burn rate and runway |
| 105 | ``` |
| 106 | |
| 107 | ### Slide 11: The ask |
| 108 | ``` |
| 109 | - Amount raising: $X |
| 110 | - Use of funds breakdown (product, hiring, GTM — percentages) |
| 111 | - Milestones this capital will achieve |
| 112 | |
| 113 | Example: "Raising $3M seed to reach $1M ARR in 18 months" |
| 114 | "60% product, 30% GTM, 10% ops" |
| 115 | ``` |
| 116 | |
| 117 | ### Slide 12: Appendix (optional) |
| 118 | |
| 119 | Backup slides for Q&A: detailed financial model, product roadmap, customer testimonials, technical architecture. |
| 120 | |
| 121 | ## Quality checklist |
| 122 | |
| 123 | Before delivering the deck, verify: |
| 124 | |
| 125 | - [ ] Every slide has one clear point — no slide tries to do two jobs |
| 126 | - [ ] Problem slide quantifies the pain with real data |
| 127 | - [ ] Market size uses TAM/SAM/SOM with cited sources |
| 128 | - [ ] Traction slide has a chart showing growth direction |
| 129 | - [ ] The ask states the amount, use of funds, and milestones |
| 130 | - [ ] No slide has more than 30 words of body text (slides are visual, not documents) |
| 131 | - [ ] The deck tells a story: problem, solution, proof, team, ask |
| 132 | - [ ] Competitive slide does not claim "no competitors" |
| 133 | |
| 134 | ## Common mistakes |
| 135 | |
| 136 | - **Too many words per slide.** If you have to read the slide to the audience, it's a document, not a deck. Use visuals, charts, and short phrases. Save detail for the appendix. |
| 137 | - **Market size without bottom-up validation.** "The global SaaS market is $200B" tells investors nothing. Build market size bottom-up: number of target customers times price per customer. |
| 138 | - **Traction slide without a trend.** A single number ("we have 500 users") is a snapshot. A chart showing 500 users growing 15% month-over-month is a story. Always show trajectory. |
| 139 | - **Burying the ask.** Some decks spend 12 slides on the product and one rushed slide on the raise. The ask is the purpose of the deck — give it a dedicated slide with clear numbers. |
| 140 | - **Generic team bios.** "Jane has 15 years of experience in technology" does not explain why Jane is the right person to solve this specific problem. Connect each team member's background to the company's mission. |
| 141 |