IndexGuide

Building a deck. The long, technical, cited guide.

Field notes from inside a fundraise practice. Read top to bottom, this is one continuous argument: what a deck is for, the order it should land in, what each slide must do, what the model behind it must show, how to ship it, and what to do the morning after you send it. Slide-by-slide, with visual examples, a working financial model, and citations to DocSend, Sequoia, YC, a16z, Bessemer, and First Round.

Read this as one argument, not eleven posts.

Most "how to build a deck" content is a pile of slide tips. This one isn't. It is a single, sequential thesis about how a round actually closes — and the deck is only the most visible artifact of that work. The arc runs in eight beats: what a deck is for(§01), the order that survives a partner room (§02), what each of the twelve slides has to do (§03), the design and density that keep it readable on a laptop (§04), the model underneath (§05), the mistakes that kill rounds (§06), the writing process (§07), and what happens after you send(§08–11).

Each section opens with the principle, gives a concrete example from a recent founder I worked with (anonymized), and closes with a checklist or model you can lift directly. Where I take a position that contradicts published VC advice, I say so and cite both sides. The goal is not a deck that looks like a deck. The goal is a deck that earns the second meeting.

"A great deck is the visible 10% of an invisible 90%: a clear ask, a credible model, a real customer, and a team who has practiced the Q&A out loud. Skip any of those four and the slides cannot save you."
The thesis of this guide
§01–02
What a deck is, and the order
§03
The twelve slides, in technical detail
§04–05
Design, density, and the model behind it
§06–07
Mistakes, and how to actually write it
§08–09
Tracking opens; the appendix as a second deck
§10–11
Q&A drill; the final pre-send checklist
Reading time
~52 min
Sections
11
Field notes
6
References
10
Section 01

What a deck actually is

A pitch deck is not a document. It is an artifact passed around a partnership Slack channel by an associate at 11pm on a Sunday.

The most-cited public dataset on investor reading behavior is DocSend's Pitch Deck Interest Metrics work, which has tracked investor sessions across tens of thousands of founder decks. The headline finding has been stable across vintages: a successful investor session lasts roughly three to four minutes, and the time is spent disproportionately on team, traction/financials, and product[1]. Every design decision in this guide proceeds from that fact.

The deck has two jobs and only two. The first is to get the meeting. The second, once the meeting happens, is to be the shared reference document the partner uses to repeat your bet to the rest of the room when you are not there. That is it. It is not a business plan, a product spec, or a vision statement. It is the minimum viable shared mental model of your company.

"The job of the pitch is not to convince. The job of the pitch is to earn the right to a longer conversation."
Mike Maples Jr., Floodgate

Most founders build the wrong thing because they imagine a careful reader. There is no careful reader. There is a tired reader, a skeptical reader, and a reader who already half-passed before they opened the file. Write for those three.

The reader's mental funnel


   open file
       │
       ▼
  ┌────────────┐  ~11s   "is this a category I touch?"
  │  Title +   │ ───────►  if no  ──► close
  │  Problem   │
  └────────────┘
       │ yes
       ▼
  ┌────────────┐  ~24s   "is the why-now real?"
  │ Why now +  │ ───────►  if no  ──► skim, pass
  │   Wedge    │
  └────────────┘
       │ yes
       ▼
  ┌────────────┐  ~38s   "do the numbers exist?"
  │ Traction + │ ───────►  if no  ──► skim, pass
  │  Market    │
  └────────────┘
       │ yes
       ▼
  ┌────────────┐  ~52s   "do I believe this team?"
  │   Team +   │ ───────►  if yes ──► reply within 24h
  │    Ask     │
  └────────────┘
Figure 1.1 — How an investor actually reads a cold deck. Times are illustrative, anchored to DocSend's published per-slide medians [1].

The funnel above is not a literal sequence; investors jump around. But the gating questions are real, and they are answered in roughly that order. If any one of them gets a "no", the rest of the deck is irrelevant. Build for the gates, in order.

Section 02

Structure: how many slides, in what order

The canonical pitch deck has between ten and fifteen body slides. DocSend finds that decks that successfully raise are most often between 14 and 19 slides total, with a median around 19 when an appendix is included[1]. Sequoia's own template runs about ten[2]. Y Combinator's recommended structure is similarly tight at around ten to twelve slides[3]. Andreessen Horowitz publishes a sixteen-slide guide[4]. The variance is real but the band is narrow: build for roughly twelve body slides plus an appendix.

SourceBodyAppendixNotable rule
Sequoia Capital [2]10openWhy now is the most important slide
Y Combinator [3]10–12limitedOne idea per slide
Andreessen Horowitz [4]16structuredLead with team for repeat founders
First Round Capital [5]12–14openProblem before product, always
DocSend dataset [1]14–19commonDecks 14–19 slides raise fastest
Bessemer (cloud) [8]12heavyBottom-up TAM only
Table 2.1 — Recommended deck structures from major published sources. Numbers indicate slide counts in the body, excluding appendix. Aggregated from primary sources cited.

The order I use

Twelve body slides, in this sequence:

  • 1. Title. Company, one-liner, round, contact.
  • 2. Problem. One painful, expensive, or growing problem. Quantified.
  • 3. Why now. The specific shift that makes this possible today and not five years ago.
  • 4. Wedge. The narrow first product. Not the platform.
  • 5. How it works. A picture of the product in use.
  • 6. Traction. Numbers, or proof of insight if pre-revenue.
  • 7. Market. Bottom-up TAM, never top-down.
  • 8. Business model. One sentence and one chart.
  • 9. Competition. Including "do nothing" and "spreadsheets".
  • 10. Team. Why this team wins this race.
  • 11. Ask. Amount, instrument, milestones, runway.
  • 12. Vision. The platform the wedge becomes. One paragraph.

 ┌─Title─┐
 │  who  │
 └───┬───┘
     ▼
 ┌─Problem─┐    ┌─Why now─┐    ┌──Wedge──┐
 │  pain   │──► │  shift  │──► │  narrow │
 └─────────┘    └─────────┘    └────┬────┘
                                    ▼
                              ┌─Product──┐
                              │ workflow │
                              └────┬─────┘
                                   ▼
 ┌─Traction─┐  ┌──Market──┐  ┌──Model───┐  ┌──Comp──┐
 │  slope   │─►│ bottom-up│─►│  $/unit  │─►│  vs.   │
 └──────────┘  └──────────┘  └──────────┘  └────┬───┘
                                                ▼
                                           ┌─Team─┐
                                           │ why  │
                                           │  us  │
                                           └──┬───┘
                                              ▼
                                         ┌──Ask──┐
                                         │ $, mo │
                                         └──┬────┘
                                            ▼
                                       ┌─Vision─┐
                                       │  10y   │
                                       └────────┘
Figure 2.1 — A canonical 12-slide narrative arc. Each box is a single argumentative beat.

A16z's seed-stage deck guide proposes a similar shape with a slightly different ordering and gives the structural reasoning for each slide[4]. First Round's research adds an interesting twist: founders who lead with a clear problem statement raise faster than those who lead with the product[5]. Lead with the problem. Always.

Section 03

Slide by slide, in technical detail

Slide 1 · Title

Quality checklistSlide 1 · Title
Include
  • Company name in plain type, large.
  • One-line descriptive summary in the customer's language.
  • Round size and instrument: e.g. "Raising $2.5M Seed on a SAFE @ $20M post."
  • Founder name, email, and the date of this version of the deck.
Cut
  • Taglines ("Reimagining the future of work").
  • "Confidential — Do Not Distribute" watermarks.
  • Logo wall of press, customers, or schools.
  • Stock-photo backgrounds and gradient overlays.
Common failure modes
  • !Investor cannot tell what category you are in within 5 seconds.
  • !No round size, so the partner cannot scope fit at a glance.
  • !No date, so old copies in inboxes are mistaken for the current pitch.
  • !File name is "Deck Final v7.pdf" instead of Company_Round_Date.pdf.
Per-slide checklist · Slide 1 · Title

Company name, a single descriptive line in plain English, the round ("Raising $2.5M Seed"), founder name, email, date. That is the entire payload. No tagline. No logo wall. No "Confidential" in red — decks get forwarded, and pretending otherwise reads as naive.

Slide 1 · Working
Lattice
HRIS for distributed engineering teams.
Raising $2.5M Seed · SAFE @ $20M post
jane@lattice.co · Mar 2026
A working title slide. Plain, dense, repeatable verbatim by an associate.
Slide 1 · Broken
Lattice
Reimagining the future of work.
Confidential — Do Not Distribute
✗ Antipattern
A broken title slide. Tagline says nothing. No round, no contact, no date.

Slide 2 · Problem

Quality checklistSlide 2 · Problem
Include
  • One sentence stating the problem in the customer's own words.
  • Two or three quantified bullets: who, how often, how much it costs them.
  • A specific, dated reference point if you have one (a regulation, a cost curve, a survey).
  • Implicit answer to: who is paying for this pain today?
Cut
  • "Imagine a world where…" and any other generic opener.
  • Trillion-dollar industry stats with no link to your customer.
  • Long quotes from McKinsey, Gartner, or Forrester reports.
  • Personal anecdotes longer than one line.
Common failure modes
  • !Problem is too generic to test ("data is siloed").
  • !Problem describes a feature gap, not a customer pain.
  • !No quantification, so partner has no anchor for severity.
  • !Problem is real but boring; the partner moves on at 11 seconds.
Per-slide checklist · Slide 2 · Problem

One sentence at the top stating the problem in the customer's own language. Underneath, two or three bullets that quantify it: how many people, how much money, how often. DocSend's per-slide data consistently shows the problem slide gets only a sliver of session time[1], and that sliver decides whether the rest of the deck gets read. If your problem is generic, you have lost them by slide three.

Slide 3 · Why now

Quality checklistSlide 3 · Why now
Include
  • A specific shift in the last 18–36 months: regulation, cost curve, platform, behavior.
  • Citable source for the shift — a date, a number, a public ruling.
  • One sentence on why this shift makes the company possible today and not five years ago.
  • An implicit timer: why this window will close if it isn't acted on.
Cut
  • "AI is everywhere" or "COVID accelerated digital."
  • Generic megatrend slides ("the future of work," "web3," "sustainability").
  • Anything that would have been equally true five years ago.
  • Three different shifts pretending to be one argument.
Common failure modes
  • !Cites the platform (ChatGPT, AWS) instead of what the platform unlocked in your segment.
  • !Trends are real but reversible; partner discounts the urgency.
  • !Confuses "market growing" with "window opening."
  • !No tailwind that you, specifically, ride better than incumbents.
Per-slide checklist · Slide 3 · Why now

The single most underwritten slide in seed-stage decks. Sequoia calls it the most important slide in the deck because it forces the founder to articulate the non-obvious tailwind[2]. A good "why now" answers: what changed in the last 18 to 36 months that makes this company possible, valuable, or urgent? Cost curves, regulatory change, platform shifts, new model capability, new data availability.

Bad "why now" slides cite ChatGPT or COVID as if those were arguments. They are background. The argument is what specifically changed in your sub-segment.

SectorWeak (background)Strong (specific)
AI infraGPT changed everythingFrontier-model inference cost per million tokens fell ~10x between 2023 and 2025, making fine-tune economics positive for sub-$10M-ARR companies
FintechCOVID accelerated digitalSection 1033 final rule (Oct 2024) made consumer-permissioned data portability mandatory by Apr 2026
ClimateESG is a megatrendIRA §45V hydrogen credit became claimable in 2025, opening a $3/kg subsidy stack we underwrite into pricing
B2B SaaSRemote work is here to stayBuying-committee size has compressed post-2023 (Gartner: ~6.8 → ~5 stakeholders), shortening enterprise cycles materially
Table 3.1 — Examples of strong vs. weak 'why now' arguments observed in seed-stage decks.

Slide 4 · Wedge and product

Quality checklistSlide 4 · Wedge and product
Include
  • The narrow first product, named clearly.
  • One identifiable first customer profile, by title and segment.
  • A real screenshot or short workflow diagram of the product in use.
  • One sentence on the durable advantage the wedge creates.
Cut
  • Platform diagrams with five concentric circles.
  • Future modules and roadmap bubbles.
  • Generic "AI-powered" labels with no specifics.
  • Pretending Figma mocks are shipped product.
Common failure modes
  • !Wedge is too broad — "all of HR" instead of "onboarding for distributed eng teams."
  • !Wedge is too small to grow into the vision shown later.
  • !No screenshot, so the partner cannot tell if the product is real.
  • !Workflow shown is a UI tour, not a customer outcome.
Per-slide checklist · Slide 4 · Wedge and product

The wedge is the first painful problem you solve for the first identifiable customer. It is narrow on purpose. Investors fund wedges, not platforms, because wedges are testable in 18 months and platforms are not. Bill Gurley's well-known framing is that the best businesses look small at first and only become obvious in hindsight[6]. Show the small thing. Talk about the platform on the vision slide.

"The next big thing will start out looking like a toy."
Chris Dixon, a16z

The product slide is the one place a screenshot or short workflow diagram is non-negotiable. Investors want to see that the thing exists. If it does not exist yet, show the highest-fidelity mock you have and label it as a mock. Pretending a Figma is shipping product is a tell partners catch immediately.

Slide 5 · How it works

Quality checklistSlide 5 · How it works
Include
  • A linear three-to-five-step workflow from input to outcome.
  • Real interface fragments at each step, not abstract icons.
  • The unit of work the product replaces (a meeting, a spreadsheet, a vendor).
  • One before/after time or cost number, sourced from a real customer.
Cut
  • Architecture diagrams with databases, queues, and a cloud icon.
  • Concentric-circle 'platform' diagrams.
  • Feature lists masquerading as a workflow.
  • Screens redacted so heavily that nothing is legible.
Common failure modes
  • !Diagram explains the system, not the customer's job.
  • !Workflow shown is the demo path, not the production path.
  • !No clear hand-off — partner can't tell who does what, when.
  • !Slide reads like internal engineering documentation.
Per-slide checklist · Slide 5 · How it works

The "how it works" slide answers the question the partner cannot ask out loud: what is the customer actually doing inside this software, and what would they have done without it? A working version is a sequence — input, action, output — illustrated with real screen fragments. The wedge slide tells the partner what you sell. This slide tells them what using it feels like.


   ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐
   │  Trigger │ →  │  Capture │ →  │  Decide  │ →  │  Resolve │
   │  (event) │    │ (in-app) │    │  (model) │    │ (action) │
   └──────────┘    └──────────┘    └──────────┘    └──────────┘
       0 min          ~30s            ~5s            ~10s

   Replaces:  a 45-minute weekly meeting + a shared spreadsheet
   Anchor:    Acme Co., Q1 2026 pilot, n=1,420 events
Figure 3.0 — A workflow slide as a left-to-right sequence. Each box is a state of the customer's job, not a system component.

Slide 6 · Traction

Quality checklistSlide 6 · Traction
Include
  • One chart: time on x-axis, key metric on y-axis, last 6–12 months.
  • Retention next to growth: dollar and logo, or DAU/MAU.
  • One efficiency callout (CAC payback, burn multiple, or magic number).
  • If pre-revenue: design partners signed, LOIs, pilots in flight.
Cut
  • Cumulative metrics that hide a flat MoM line.
  • Vanity counts (page views, app installs, newsletter subs) without conversion.
  • Logos of "interested" customers who haven't paid.
  • Three charts on one slide.
Common failure modes
  • !Showing growth without retention reads as a leaky bucket.
  • !Y-axis truncated to make a 4% gain look like a hockey stick.
  • !Mixing free and paid users into a single "users" line.
  • !Calling pilots "revenue" without disclosing whether they convert.
Per-slide checklist · Slide 6 · Traction

Traction is the slide investors spend the most time on[1]. In DocSend's published per-slide breakdowns, the traction/financials block consistently absorbs the largest share of session time — multiples of the title slide. If you have revenue, show ARR or MRR with the monthly trajectory for the last six to twelve months. If you have users, show actives and retention curves. If you have a waitlist, show conversion to paid where possible.


   ARR ($k)
   400 ┤                                            ●
   350 ┤                                       ●
   300 ┤                                  ●
   250 ┤                            ●
   200 ┤                       ●
   150 ┤                  ●
   100 ┤             ●
    50 ┤        ●
     0 ┤  ●  ●
       └──┬──┬──┬──┬──┬──┬──┬──┬──┬──┬──┬──┬──
         M1 M2 M3 M4 M5 M6 M7 M8 M9 10 11 12

   Net retention: 142% · Logo retention: 96% · CAC payback: 7.1 mo
Figure 3.1 — A slope-and-shape traction chart. The story is in the second derivative, not the absolute number.

The Mosaic effect: a single chart showing time on the x-axis and a metric going up and to the right is worth more than ten bullets. Founders consistently underrate how much investors care about the slope of the line versus the absolute number. A small absolute number with a steep slope often outperforms a large flat number[7].

Slide 7 · Market

Quality checklistSlide 7 · Market
Include
  • Bottom-up TAM with the arithmetic visible: accounts × ACV.
  • SAM defined by your reachable GTM channels.
  • 5-year SOM with a stated penetration assumption.
  • Citation for the account count (industry body, public filing, dataset).
Cut
  • Top-down TAM ("$400B global market").
  • Three nested concentric circles labelled TAM/SAM/SOM with no math.
  • Adjacent markets included to inflate the number.
  • Forecasts stretched out to 2035.
Common failure modes
  • !TAM is so large it is obviously fabricated; partner stops trusting the rest of the deck.
  • !SAM is undefined — no clear answer to "who can you actually reach."
  • !Penetration assumption is implausible (>20% in 5 years).
  • !No source for the underlying account count.
Per-slide checklist · Slide 7 · Market

Always bottom-up. Top-down TAM slides ("the global X market is $400B") are almost universally dismissed by professional investors[8]. The defensible bottom-up model is: number of target customers × realistic ACV × realistic penetration. Show the arithmetic. If the number is small, do not lie about it; instead, show how it grows.

TAM  = Σ (target accounts in segment_i  ×  realistic ACV_i)
SAM  = TAM × % reachable through your GTM channels
SOM  = SAM × % win rate against incumbents in 5 years

Worked example (vertical SaaS for US dental practices):

  target accounts        =   142,000  US dental practices       [ADA, 2024]
  realistic ACV          =     $4,800  ($400/mo, 1.5 seats avg)
  TAM                    =     $682M
  SAM (reachable via PLG)=     $410M  (60% of TAM, urban/suburban)
  SOM (5-year, 12% pen.) =      $49M
Formula 3.1 — Bottom-up TAM. SAM is the slice you can reach. SOM is the slice you intend to win in 5 years.

Slide 8 · Business model

Quality checklistSlide 8 · Business model
Include
  • One sentence: who pays you, how much, how often.
  • Pricing tiers with realistic ACV per tier.
  • Gross margin with a one-line explanation if unusual for the category.
  • Net revenue retention if you have it; expansion path if you don't.
Cut
  • Five-year revenue projections from a pre-revenue company.
  • "Multiple revenue streams" pies with imaginary slices.
  • Made-up benchmarks ("industry standard 90% gross margin").
  • Take-rate diagrams without a number on them.
Common failure modes
  • !Gross margin is materially below category norm and goes unaddressed.
  • !Pricing is below value delivered, with no path to expansion.
  • !Revenue model and product wedge contradict each other.
  • !Unit economics are confused with company economics.
Per-slide checklist · Slide 8 · Business model

One sentence: who pays you, how much, how often. One simple unit economics chart if you have one. If your gross margin is unusual for the category, explain why. Investors at this stage care less about precision than about whether you understand your own economics.

MetricSeed (median)Series A (top quartile)
Gross margin65–75%78–85%
Net revenue retention100–110%120%+
CAC payback (months)12–18<12
LTV:CAC3.0x5.0x+
Magic number0.71.2+
Burn multiple<2.0<1.0
Table 3.2 — Unit economics benchmarks for SaaS at seed/Series A. Adapted from OpenView and Bessemer SaaS benchmarks.

Slide 9 · Competition

Quality checklistSlide 9 · Competition
Include
  • A feature comparison table, not an empty-quadrant 2x2.
  • Real incumbents named, plus "spreadsheets" or "do nothing."
  • A row where you honestly lose today (e.g. SOC 2, integrations, headcount).
  • One row that captures the strategic moat in two years.
Cut
  • 2x2s with you alone in the top right.
  • "We have no competition."
  • Vague capability words ("powerful," "flexible," "intelligent").
  • Logos of competitors you've never lost a deal to.
Common failure modes
  • !Slide implies you win on every axis, which destroys credibility.
  • !Competitors listed are not the ones partners think of in your category.
  • !No mention of the status quo, so partner assumes the buyer doesn't actually need this.
  • !Moat row reads like marketing copy, not a defensible advantage.
Per-slide checklist · Slide 9 · Competition

Do not use a 2x2 with you alone in the top right. It is a meme[9]. Use a feature comparison table or a positioning map that includes "the status quo" and "spreadsheets" as competitors. The honest competitive slide says: here is what customers do today, here is why it is bad, here is why we are better, and here is what we are not yet better at.


                       │ Spreadsheets │ Incumbent A │ Incumbent B │   Us
   ────────────────────┼──────────────┼─────────────┼─────────────┼────────
   Time to first value │     5 min    │   3 weeks   │   6 weeks   │  9 min
   Price/seat/mo       │      $0      │    $48      │    $72      │   $19
   API-first           │      ✗       │     ✗       │     ✓       │   ✓
   SOC 2 Type II       │      —       │     ✓       │     ✓       │   ✗ ← admit
   Multi-entity ledger │      ✗       │     ✓       │     ✗       │   ✓
   AI workflows        │      ✗       │     ✗       │     ✗       │   ✓
Figure 3.2 — A more honest competitive frame than the empty-quadrant 2x2: a feature ledger that admits where you lose.

Slide 10 · Team

Quality checklistSlide 10 · Team
Include
  • Founders, with one specific prior outcome each.
  • An "unfair advantage" line per founder, in concrete terms.
  • Why this team, working together, wins this race.
  • One critical hire you are making with this round.
Cut
  • Headshot row with logos and no narrative.
  • Ten advisors with no specific contribution.
  • Generic credentials ("deep domain expertise").
  • School names doing the work of accomplishments.
Common failure modes
  • !Team slide is the most-read slide, and yours is the thinnest.
  • !Unfair advantage is unverifiable ("sold a previous company," no name, no exit).
  • !Founders' backgrounds don't match the wedge.
  • !Advisor wall outweighs founder accomplishments visually.
Per-slide checklist · Slide 10 · Team

The team slide is the second most-read slide in the deck after financials[1]. Show the founders, their relevant prior work, and the specific reason this team wins. The unhelpful version is a row of headshots with logos underneath. The useful version answers: why this team, why now, what you have built or shipped together before.

Slide 11 · The ask

Quality checklistSlide 11 · The ask
Include
  • Amount, instrument, and post-money cap ("$3M on SAFE @ $20M post").
  • Runway in months and what milestones the round buys.
  • Hiring plan: roles and number per function.
  • Stated trigger and target for the next round.
Cut
  • "Raising a seed round" with no number.
  • Five-year financial forecast slides.
  • Use-of-funds pie with vague slices like "growth."
  • Vanity dilution targets ("raising 10%").
Common failure modes
  • !Ask isn't tied to specific, dated milestones.
  • !Round size doesn't survive a sensitivity check (CAC up 30% breaks the plan).
  • !Hiring plan front-loads sales before product-market fit.
  • !Next-round trigger is a metric the deck doesn't show a credible path to.
Per-slide checklist · Slide 11 · The ask

Be specific. "Raising $3M on a SAFE at $20M post" is more investable than "Raising a seed round." State the milestones the round buys: revenue, hires, product, geography. State the runway in months. DocSend data is unambiguous that decks with a clearly stated ask close faster[1].

Raising:  $3.0M  on a post-money SAFE  @ $20M post
Runway:   22 months
Buys us:
  • $1.5M ARR  (from $240k today)
  • 8 hires    (4 eng, 2 GTM, 1 design, 1 ops)
  • SOC 2 Type II
  • US-East + US-West data residency
Series A target:  Q3 2027 at $1.5M ARR, 130% NRR
Formula 3.2 — A milestone-anchored ask. The ask is justified by what the round buys, not by a percentage of dilution.

Slide 12 · Vision

Quality checklistSlide 12 · Vision
Include
  • One paragraph describing the world when you have won.
  • A specific second and third product the wedge unlocks.
  • An honest statement of the long-term moat.
  • A line that lets the partner repeat your bet in one sentence.
Cut
  • Bullet lists. Vision is prose.
  • Buzzword stacks ("the AI-native operating system for…").
  • Stage-2 fantasies that contradict the wedge slide.
  • Generic mission statements ("empowering humans to…").
Common failure modes
  • !Vision sounds bigger than the wedge can credibly grow into.
  • !Vision is too small — partner can't see fund-returner outcome.
  • !Reads as marketing, not as a technical or commercial bet.
  • !Final paragraph contradicts the realism of the rest of the deck.
Per-slide checklist · Slide 12 · Vision

One paragraph. What does the world look like when you have won? This is where you are allowed to sound ambitious. The wedge slide earned you the right to put it here.

Section 04

Design, density, and length

Investors read decks on a laptop in a browser tab. Design for that. One idea per slide, large type, real charts, real screenshots. The most common deck-design failure is not ugliness; it is density. Slides with more than about 50 words of body copy correlate with longer fundraise cycles in the DocSend data[1].

RuleSpecificallyWhy
Type sizeTitle 36–48pt, body 18–24ptReadable when zoomed to 1/2 in browser
Words per slide<50 in body, <12 in titleLonger = passed-over [1]
Aspect ratio16:9Default in every email/Slack preview
Color count≤3 ink colorsMore reads as agency template
Charts1 per slide maxTwo charts = none read
AnimationsNoneBreak in browser preview
File size<8MB PDFInvestors gate at ~10MB
File nameCompany_Round_Date.pdfSearchable in Drive
Table 4.1 — Concrete design rules with rationale.

Color and typography are the last 10%. They matter less than founders think. A clean Helvetica deck with real numbers will out-raise a beautifully designed deck with vague claims, every time. The best decks I have seen at the seed stage looked like they were written by adults, not designed by an agency.

Field note · Vertical SaaS, Series A · $8M round, NYCOutcome: closed in 5 weeks, 2.4x oversubscribed

The founder arrived with a 41-slide deck designed by a Lisbon studio. Beautiful. Three font weights, a custom illustration on every slide, animated transitions. DocSend showed an average session of 1m 12s — partners were closing it before the problem slide.

We replaced it with a 14-slide deck in a single typeface, two ink colors, no animations, charts pasted from the model. Same data. Same business. Average session jumped to 4m 03s. The lesson is not that ugly wins — it's that density wins. A reader who can finish a slide in eight seconds will read all twelve. A reader who can't finish slide two won't see slide three.

Section 05

The financial model behind the deck

The deck shows the headline numbers. The model behind the deck is where partners spend most of their diligence time. At the seed stage you are not expected to ship a 60-tab DCF; you are expected to ship a credible bottom-up model that ties the GTM motion to revenue, headcount to burn, and burn to runway. Bessemer's "Good, Better, Best" framework is the cleanest public starting point[8].

TabPurposeCommon founder mistake
AssumptionsAll inputs in one placeHard-coding values inside other tabs
GTM funnelLeads → MQL → SQL → WonSkipping conversion rates entirely
Revenue buildMRR/ARR by cohortShowing only top-line, no cohorts
Headcount planRole, start month, fully loaded costForgetting payroll taxes (~12%)
P&LMonthly, 24 monthsAnnual only
Cash + runwayEnding balance per monthNo 'low-water mark' callout
Cohort retentionLogo and dollar retentionMissing for pre-revenue companies
Sensitivity+/- 30% on top 3 inputsSingle-scenario plan
Table 5.1 — Minimum tabs an investor expects in a seed-stage model.

The three numbers partners actually check

  • Burn multiple = Net burn ÷ Net new ARR. Below 1.0 is great, below 2.0 is acceptable at seed, above 3.0 is a red flag [10].
  • Magic number = Net new ARR (annualized) ÷ S&M spend in prior quarter. Above 1.0 means scaling profitably [8].
  • Rule of 40 = Growth rate (%) + FCF margin (%). Used at Series B+ but increasingly tested at A [8].
Burn multiple  =  net cash burn (period)  /  net new ARR (period)
Magic number   =  4 × ΔARR (Q)             /  S&M spend (Q-1)
Rule of 40     =  YoY growth %             +  FCF margin %
Formula 5.1 — The three numbers in plain arithmetic.
Field note · Dev tools company · Seed extension, $4MOutcome: led by a tier-one fund after rebuilding model

The deck claimed $1.1M ARR and 140% NRR. The model behind it had no cohort tab. When the partner asked for retention by signup month, the founder pulled a number from memory. The partner asked for it in writing. The number didn't survive contact with the data: real NRR was 108%.

We rebuilt the model in nine days: assumptions on tab one, GTM funnel on tab two, cohort retention on tab three, P&L by month on tab four. The headline ARR didn't change. The retention story got more honest, but it got defensible. The fund led the extension at the same price the founder originally wanted, and cited the model as the reason on the call.

The principle: the deck shows three numbers; the model has to survive ten. If the model can't, the deck can't either — partners ask for the model on the second meeting, and the round dies in the gap.

Section 06

Common, expensive mistakes

  • Burying the wedge. Most decks bury the actual product behind two slides of market context. Lead with the wedge by slide four.
  • Top-down TAM. "The global market is $400B." No partner has ever bought this. Build bottom-up [8].
  • The hockey-stick projection. Five-year revenue forecasts from a pre-revenue company. Investors discount them entirely [8].
  • Logo walls of irrelevant customers. Three real design partners beats twelve "interested" logos.
  • Vague asks. "Raising a seed round" instead of "$3M on a SAFE at $20M post for 18 months of runway."
  • The 'we have no competition' slide. You do. Every customer has a current solution, even if it is a spreadsheet.
  • Confidential watermarks. Decks get forwarded. Acting otherwise reads as inexperience.
  • Founder photos without bios. The team slide must argue why this team wins, not just who they are.
  • Animations and transitions. They break in browser preview and look like a 2009 keynote.
  • Sending the deck cold without a sentence. The cover email is part of the deck. Treat it as slide zero.
  • Gross margin handwaving. If your category is 75% gross margin and yours is 40%, address it on the model slide, not in Q&A.
  • Renaming categories. Inventing "Generative Workflow Intelligence" when you mean "AI sales tool" loses the partner. Use the boring name.
  • NDAs at the cold-deck stage. Signal you do not understand the market [9].
  • Showing MRR without retention. Growth without retention reads as a leaky bucket. Always pair them.
  • Ten advisors on the team slide. One unfair-advantage advisor is leverage; ten is decoration.
Field note · Climate hardware startup · Pre-seed, $1.5M targetOutcome: closed in 11 weeks after rewriting four slides

Three of the mistakes above were stacked in the same deck: top-down TAM ("$2.1T global energy market"), a we-have-no-competition slide, and a vague ask ("raising ~$1.5M"). The deck got opened. It didn't get answered.

We replaced the TAM with a bottom-up: 4,200 industrial sites × $180k ACV = $756M SAM. We added a competitive ledger that named two incumbents and listed where we lost (cert timeline, supply chain). We tightened the ask to "$1.6M on a SAFE @ $12M post, 18 months runway, two pilot conversions to paid".

Same company. Same physics. Three different conversations, all with funds that had previously passed without a meeting.

Section 07

Process: how to actually write it

The deck is written backwards. Start with the ask. If you cannot state the ask in one sentence, the rest of the deck cannot do its job, because the deck exists to justify that ask. Once the ask is locked, write the team slide. Then the traction slide. Then everything else.

Write the body in plain text first, in a single document, with no slides. One sentence per slide. If you cannot state the slide's claim in one sentence, the slide is not yet a slide. Only after the plain-text version reads cleanly do you move to slides.


   Week 1   Week 2          Week 3            Week 4
   ──────── ────────────── ────────────────── ──────────────
   Plain    Slide v1       Operator review    Investor v1
   text     (structure)    (kill 30%)         (send cold)
   ──────── ────────────── ────────────────── ──────────────
   Lock     Add charts     Rewrite traction   Track DocSend
   ask      and screenshots and ask           opens, iterate
Figure 7.1 — A four-week deck-writing schedule that produces three real drafts.

Iterate against real readers. Show the deck to three operators you trust before you show it to a single investor. Operators will tell you when a slide does not earn its place. Investors will tell you when you have already lost them, but by then it is too late.

Plan to write the deck three times. The first version gets the structure right. The second gets the words right. The third is the one you actually send. Founders who think they are done after version one are the same founders who wonder why the round is taking six months.

Field note · Marketplace, two-sided · Seed, $3MOutcome: three drafts, one closed round

Draft one was structurally correct and unreadable: every slide had four bullets and a chart. Draft two cut every slide to one sentence and one image. We showed it to four operators (a CFO, a head of sales, a designer, a former associate). They killed the market slide and rewrote the wedge.

Draft three — the one that actually went out — was 13 slides and 280 words. The founder timed himself reading it aloud: 3m 47s, end to end. That number is the real KPI. If you can't read your own deck out loud in under four minutes, no partner will either.

Section 08

After the deck goes out

Track who opens the deck and how long they spend on each slide. DocSend, Attach, and Pitch all do this natively[1]. The data is not a vanity metric; it tells you which slides are working and which are losing the room. If investors consistently bail on slide six, slide six is broken. Rewrite slide six, not the cover email.

PatternWhat it usually meansAction
Total time < 60sCold deck failed at top of funnelRewrite title + problem
Drop-off at slide 3Why-now did not landReplace with specific shift
Long time on traction, no replyNumbers too small for fund stageRe-target investor list
Long time on team, no replyBelievability gapAdd a credibility line, get a warm intro
Re-opens 3+ timesChampion is socializing internallySend a short follow-up + memo
Opens, no scrollsForwarded but not read by partnerAsk for the partner-level intro
Table 8.1 — How to read DocSend session data. Heuristics, not absolutes.

The weekly investor update during the raise

The follow-up is part of the deck. A clean weekly update during the raise turns warm leads into committed money and committed money into a closed round. The format is boring on purpose: highlights, lowlights, metrics, asks, what's next. Five sections. Plain text. Send it on Mondays.

Subject:  [Company]  ·  Week of MM/DD  ·  Raise update

Highlights
  • Closed Acme as design partner ($24k ACV, 12-mo pilot)
  • 2 partner meetings scheduled for next week

Lowlights
  • Lost a verbal from Fund X on geography (US-only thesis)

Metrics (since last update)
  • ARR:  $312k → $338k  (+$26k)
  • Pipeline: $1.2M qualified, weighted

Asks
  • Intros to: Fund A, Fund B (specific partner, with reason)

What's next
  • Term sheet conversations open with two funds
  • Targeting first close by [date]
Template 8.1 — A weekly raise-update email. Keep it under 250 words.
Field note · Vertical AI, US/EU · Seed, $5MOutcome: closed at $5.8M, 4 weeks faster than plan

The DocSend dashboard told the whole story. Out of 38 funds, 9 re-opened the deck three or more times in the first 10 days. We sent those 9 a tailored 250-word memo on Monday morning with one new data point each (the latest ACV, a customer quote, a hire).

Six of the nine took a meeting. Four went to partner. Two made offers. The other 29 funds got the standard weekly update and roughly the conversion rate you'd expect: one meeting, no offer.

The principle: the round closes in the second loop, not the first. The first send finds your champions. The second send — the one calibrated to who's actually reading — closes them.

Section 09

Appendix: what belongs behind the divider

The appendix is where you put everything you do not need on a cold read but every diligence call asks for. Treat it as the second deck inside the deck. Separate it with a divider slide that says "Appendix" and nothing else.

  • Cohort retention curves by signup month, dollar and logo.
  • Funnel conversion rates from top-of-funnel to closed-won.
  • Sales motion economics: ACV by segment, sales-cycle length, win rate.
  • Pricing details: tiers, discounts, expansion paths.
  • Hiring plan: roles, start months, fully loaded costs.
  • Cap table summary: pre-money, option pool, prior rounds.
  • Risks page: top three risks, what would change your mind, mitigations.
  • Customer logos and quotes: real, attributed where allowed.
  • Detailed competitive map: more than fits on slide nine.
  • Founder bios: long form, with citations of prior outcomes.
Section 10

Q&A: the questions you will be asked

Every partner meeting has the same shape. The first ten minutes are your deck. The next thirty are questions. The questions are mostly the same questions, in different orders, drawn from the same partner-room playbook.

The standard fifteen

  • "Why is now the right time, specifically?"
  • "Who is the customer and what did they do yesterday?"
  • "What is the one feature that wins the deal?"
  • "What is your CAC and how do you know?"
  • "What does net retention look like, dollar and logo?"
  • "What does the first $10M of ARR look like, channel by channel?"
  • "Who is the second hire after this round closes?"
  • "What kills this company in 18 months?"
  • "Why this team, beyond the resumes?"
  • "What does the Series A look like — milestones, multiple?"
  • "How does the incumbent respond when you reach $5M ARR?"
  • "What is the bull case and what is the base case?"
  • "What is the moat in two years that does not exist today?"
  • "What is your gross margin path?"
  • "What did the last customer who churned tell you?"

The right preparation is to write a one-paragraph answer to each of these, out loud, and rehearse them until you can deliver any one of them in under 90 seconds. Founders who do this raise materially faster than founders who do not. The deck got the meeting. The Q&A closes the round.

Field note · Infra startup · Series A, $14MOutcome: term sheet at second partner meeting

We ran the standard fifteen as a drill. Two founders, a stopwatch, two evenings. The first pass was 4–6 minutes per answer, with caveats and qualifiers. By the third pass, every answer was under 90 seconds and ended on a number.

The question that broke the founder in the partner meeting was #14: "What did the last customer who churned tell you?"Because we had drilled it, the answer was a one-liner ("they went back to in-house because their CTO joined from a competitor") and the meeting moved on. Without the drill, that question consumes 15 minutes and the energy of the room.

Section 11

Final checklist before you send

  • Title slide includes round size, instrument, name, email, date.
  • One painful, quantified problem on slide 2, in the customer's language.
  • "Why now" is a specific, dated, citable shift — not background noise.
  • The wedge is on slide 4, and it is genuinely narrow.
  • Product slide has a real screenshot or a mock labelled as a mock.
  • Traction chart shows time on x, metric on y, with retention next to it.
  • TAM is bottom-up, with the arithmetic visible.
  • Unit economics: gross margin, NRR, CAC payback, all stated.
  • Competition slide includes "spreadsheets" or "do nothing".
  • Team slide answers "why this team specifically".
  • Ask slide states amount, instrument, runway, and milestones.
  • Vision is one paragraph. Not a slide of bullets.
  • Appendix has retention cohorts, hiring plan, and a risks page.
  • File is under 8MB, named Company_Round_Date.pdf.
  • Cover email is two sentences and a link, not three paragraphs.
  • You have read it out loud, top to bottom, in under four minutes.
References

Sources cited.

Hover any inline citation in the body for a quick reference card. Sort the table below by author, year, publisher, or type. Filter to the kind of source you want. Anchor links from the body land on the matching row.

10 of 10 sources
Link
[1]DocSend
Pitch Deck Interest Metrics Report
Aggregate analysis of investor reading sessions across tens of thousands of founder decks. Source for time-on-deck, per-slide attention, and deck-length statistics referenced throughout this guide.
DocSend (Dropbox)2023ReportOpen
[2]Sequoia Capital
Writing a Business Plan
The original Sequoia ten-slide pitch deck template. Foundational for the 'why now' framing referenced throughout.
Sequoia Capital2017TemplateOpen
[3]Kevin Hale
How to Design a Better Pitch Deck
YC's recommended ten-to-twelve-slide structure with one-idea-per-slide rule.
Y Combinator2019EssayOpen
[4]Andreessen Horowitz
16 Slides to Include in Your Pitch Deck
a16z's published seed-stage deck guide. Slightly longer body, structured appendix, and the lead-with-team rule for repeat founders.
a16z2021TemplateOpen
[5]First Round Capital
The Pitch Deck We Used to Raise $500K — and Lessons From Hundreds of Founder Decks
First Round commentary on patterns across founder decks, including the cycle-time impact of leading with the problem rather than the product.
First Round Review2020ReportOpen
[6]Bill Gurley
All Markets Are Not Created Equal
Canonical essay on why durable businesses look small at first. Cited for the wedge framing.
Above the Crowd2011EssayOpen
[7]OpenView Partners
SaaS Benchmarks (annual)
Source for growth-rate vs. absolute-revenue weighting at seed and Series A. Slope > magnitude.
OpenView2024BenchmarkOpen
[8]Bessemer Venture Partners
State of the Cloud / Good, Better, Best
Bottom-up TAM construction, magic number, Rule of 40, and SaaS metrics tiers used in the unit-economics tables.
Bessemer / BVP Atlas2024BenchmarkOpen
[9]Paul Graham
How to Raise Money / A Fundraising Survival Guide
Cited for founder antipatterns: NDAs at first contact, the empty-quadrant 2x2, and behavior in the partner room.
paulgraham.com2013EssayOpen
[10]David Sacks
The Burn Multiple
Definition and thresholds for burn multiple as the primary efficiency metric at seed and Series A.
Craft Ventures2022EssayOpen

Where I quote percentages or aggregate figures from DocSend, Sequoia, YC, a16z, First Round, Bessemer, OpenView, or Craft, the underlying reports are linked above. Where I state opinion, it is mine. Disagreement welcome — send a counter-example and I will update the next revision.

If reading isn't enough

Send the draft. I'll mark it up.