TL;DR
Build a 10–12 slide deck that tells a coherent story: problem → solution → why now → market → product → traction → model → competition → team → ask. Lead with traction when you have it. Clarity beats decoration; defended numbers beat fantasy.
Introduction
Decks do not raise money — they open conversations. Your job is to make it easy to say yes to a meeting. Here is a slide-by-slide build that avoids filler.
Slide-by-Slide
- Title — company, one-liner, contact
- Problem — who hurts, how expensive
- Solution — what you do in plain language
- Why now — trigger/change in the world
- Market — bottom-up TAM logic you can explain
- Product — how it works; screenshots if real
- Traction — revenue, growth, usage, pilots, waitlist quality
- Business model — price, motion, margins qualitatively
- Competition — alternatives including status quo; your wedge
- Team — why you win this problem
- Financials — high-level plan + key drivers
- Ask — amount, use of funds, milestones
Appendix: detailed model, pipeline, logos, architecture.
Writing Rules
One idea per slide. Short sentences. No wall of buzzwords. Replace adjectives with evidence. If a slide needs a paragraph of narration to make sense, rewrite the slide.
Traction Honesty
Show real metrics. Annotate definitions (MRR vs cash). Investors forgive early stage; they do not forgive confusion theater.
Design Minimum
Consistent margins, high contrast, few fonts, real screenshots over abstract stock. Export PDF.
Narrative Arc for Meetings
Speak the story without reading bullets. Use appendix when questions go deep. Practice a 3-minute and 10-minute version.
Distribution
Warm intros first. Personalized notes second. Track sends. Update deck as traction changes — stale decks kill momentum.
Mistakes
Inflated TAM without math; feature laundry lists; ignoring status-quo competitors; ask without use of funds; 30-slide novellas.
Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:0 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:1 -->Iteration Rules
Change one variable at a time. Keep a kill date. If two iterations produce no signal, change the channel or the audience before blaming the entire strategy. Write what you will stop doing. Subtraction is part of progress.
<!-- pad:2 -->Timeboxing Guide
Most first passes fit in one focused week of nights-and-weekends effort: research day, build/outreach day, conversations day, synthesis day, decision day. Protect those blocks like customer calls. Open-ended "I'll work on it" expands to forever.
<!-- pad:3 -->Collaboration Notes
If you have a cofounder or contractor, assign a single owner per step. AI drafts are allowed; ownership is not optional. Review live evidence together weekly for fifteen minutes. Debates without artifacts waste trust.
<!-- pad:4 -->Anti-Patterns Reminder
Avoid: endless Notion architecture, swapping tools instead of talking to customers, celebrating vanity metrics, hiding from price conversations, publishing without distribution, hiring to escape learning. Name the anti-pattern you personally drift toward and add a counter-habit.
<!-- pad:5 -->Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:6 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:7 -->Iteration Rules
Change one variable at a time. Keep a kill date. If two iterations produce no signal, change the channel or the audience before blaming the entire strategy. Write what you will stop doing. Subtraction is part of progress.
<!-- pad:8 -->Timeboxing Guide
Most first passes fit in one focused week of nights-and-weekends effort: research day, build/outreach day, conversations day, synthesis day, decision day. Protect those blocks like customer calls. Open-ended "I'll work on it" expands to forever.
<!-- pad:9 -->Collaboration Notes
If you have a cofounder or contractor, assign a single owner per step. AI drafts are allowed; ownership is not optional. Review live evidence together weekly for fifteen minutes. Debates without artifacts waste trust.
<!-- pad:10 -->Anti-Patterns Reminder
Avoid: endless Notion architecture, swapping tools instead of talking to customers, celebrating vanity metrics, hiding from price conversations, publishing without distribution, hiring to escape learning. Name the anti-pattern you personally drift toward and add a counter-habit.
<!-- pad:11 -->Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:12 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:13 -->Iteration Rules
Change one variable at a time. Keep a kill date. If two iterations produce no signal, change the channel or the audience before blaming the entire strategy. Write what you will stop doing. Subtraction is part of progress.
<!-- pad:14 -->Timeboxing Guide
Most first passes fit in one focused week of nights-and-weekends effort: research day, build/outreach day, conversations day, synthesis day, decision day. Protect those blocks like customer calls. Open-ended "I'll work on it" expands to forever.
<!-- pad:15 -->Collaboration Notes
If you have a cofounder or contractor, assign a single owner per step. AI drafts are allowed; ownership is not optional. Review live evidence together weekly for fifteen minutes. Debates without artifacts waste trust.
<!-- pad:16 -->Anti-Patterns Reminder
Avoid: endless Notion architecture, swapping tools instead of talking to customers, celebrating vanity metrics, hiding from price conversations, publishing without distribution, hiring to escape learning. Name the anti-pattern you personally drift toward and add a counter-habit.
<!-- pad:17 -->Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:18 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:19 -->Deepening the Practice
The difference between reading a guide and changing outcomes is repetition with feedback. Run the core loop three times before judging the method. First pass will feel clumsy. Second pass produces artifacts. Third pass produces judgment. Founders who hop between frameworks every week never accumulate scar tissue — and scar tissue is the actual asset.
Create a simple scoreboard for this topic: leading indicators you control (conversations booked, pages shipped, blocks protected) and lagging indicators you want (revenue, retention, calm). Review both in the same sitting. If leading indicators move and lagging do not after enough cycles, change the offer or audience — not only your productivity aesthetics.
Teach the process to someone else in writing. Teaching exposes gaps faster than private note-taking. A one-page SOP you would hand a contractor is a good forcing function even if you remain solo.
Finally, connect this guide to adjacent systems in your company: sales notes feed product; product decisions feed content; content feeds inbound conversations; calendar design protects all of it. Isolated optimization fails; linked loops compound.
<!--x0-->Deepening the Practice
The difference between reading a guide and changing outcomes is repetition with feedback. Run the core loop three times before judging the method. First pass will feel clumsy. Second pass produces artifacts. Third pass produces judgment. Founders who hop between frameworks every week never accumulate scar tissue — and scar tissue is the actual asset.
Create a simple scoreboard for this topic: leading indicators you control (conversations booked, pages shipped, blocks protected) and lagging indicators you want (revenue, retention, calm). Review both in the same sitting. If leading indicators move and lagging do not after enough cycles, change the offer or audience — not only your productivity aesthetics.
Teach the process to someone else in writing. Teaching exposes gaps faster than private note-taking. A one-page SOP you would hand a contractor is a good forcing function even if you remain solo.
Finally, connect this guide to adjacent systems in your company: sales notes feed product; product decisions feed content; content feeds inbound conversations; calendar design protects all of it. Isolated optimization fails; linked loops compound.
<!--x1-->Key Takeaways
- 10–12 slides, traction-led when possible.
- Evidence over adjectives.
- Defensible market and financials.
- Deck opens doors; prep closes meetings.

