Skip to content
Writing Style Library

Pitch Deck

A sequence of presentation slides that tells a persuasive story to win a decision, one idea per slide.

Pitch Deck

Section titled “Pitch Deck”

A pitch deck is a sequence of presentation slides that tells a persuasive story to win a decision - investment, a deal, a go-ahead - one idea per slide, built to be presented aloud or skimmed quickly. The format is defined by its presentation context: the speaker carries the thread, each slide carries one idea, and the sequence builds conviction before asking for anything. A slide that stands alone without a speaker has likely been written as a document, not a deck.

The canonical pitch deck moves through a deliberate narrative arc: establish the problem and who it hurts, reveal the solution and why this approach works, show the market and the moment, demonstrate traction or evidence, introduce the team’s capacity to execute, and close with a clear ask. Not every deck uses this exact sequence, but every effective deck follows the same logic - earn the ask before making it. Slides that skip the problem or bury the ask undermine the format’s persuasive structure.

Canonical template

Section titled “Canonical template”
## Slide 1: Problem
[Who is the customer? What is the pain? How widespread and severe is it?]


## Slide 2: Solution
[What do you do? Why is this the right answer to the problem on Slide 1?]


## Slide 3: Why Now / Market
[What has changed? How large is the opportunity? Why is this the moment?]


## Slide 4: Product
[How does it work? One or two key screens or mechanics, not a full feature tour.]


## Slide 5: Traction / Evidence
[What have you proven? Revenue, users, retention, partnerships, or pilot results.]


## Slide 6: Business Model
[How does value capture work? Who pays, how much, and with what unit economics?]


## Slide 7: Team
[Who is building this and why are you the right people to win?]


## Slide 8: Ask
[What are you requesting? Amount or approval, use of resources, and milestone by when.]

When to use

Section titled “When to use”

Pitching to investors, partners, or executives to win funding, a deal, or a strategic go-ahead; presenting at a demo day, accelerator, or board meeting where narrative speed and visual clarity matter; aligning a stakeholder group on a direction when the story arc matters as much as the details; sending a deck ahead of a live meeting so the audience can skim the narrative before the conversation.

When not to use

Section titled “When not to use”

When the decision-maker needs to reason through the full argument independently without a presenter; when the content is technically dense enough that slide-level text cannot carry the necessary precision; when the audience expects a written deliverable they can annotate, share, or return to as a reference.

Pairs well with

Section titled “Pairs well with”

product-thinker, executive, confident, candid, problem-solution

Often confused with

Section titled “Often confused with”

one-pager: A one-pager is a single-page prose document that makes one argument or presents one situation, compressed to fit on a single page and designed to be read independently by a decision-maker without a presenter. A pitch deck unfolds across many slides in a deliberate narrative sequence, relies on minimal text per slide and visual momentum, and is built for a live presentation moment where the speaker carries the story thread. The one-pager can circulate and be absorbed on its own; the pitch deck typically needs a presenter to deliver its persuasive force.

Tells

Section titled “Tells”
  • A sequence of discrete slides, each carrying exactly one idea or claim
  • Slide titles that advance a narrative arc - problem, solution, market, traction, team, ask
  • Minimal text per slide: a headline, a few bullets, or a single stat - not paragraphs
  • Visuals and data that carry the persuasive argument rather than decorate
  • A deliberate sequence that earns the ask before placing it at the end
  • An explicit Ask slide naming what is requested, the amount or approval, and the milestone
  • Designed for live presentation or rapid skim, not solo deep reading

Anti-patterns

Section titled “Anti-patterns”
  • Loading each slide with paragraph-length prose so the deck can be read without a presenter - A pitch deck is built for a presentation moment where the speaker carries the thread; text-heavy slides break the spoken rhythm and produce a poor substitute for a proper written document.
  • Treating it as a one-pager spread across many slides - writing prose sections designed for an asynchronous solo read and distributing them across slide boundaries - A one-pager is a single-page prose document designed to make one argument a reader can absorb independently; a pitch deck builds persuasion through narrative sequence and visual momentum with a live presenter. Conflating the two produces a deck that neither presents well nor reads well on its own.
  • Leading with the solution or product features before establishing the problem and who has it - The persuasive arc of a pitch deck depends on making the audience feel the problem before the solution is introduced; a solution without a felt problem has no story and no urgency.
  • Placing the ask before traction and team credibility have been established - The ask earns its authority from everything that precedes it in the narrative; an early or unsupported ask reads as a negotiation move rather than a conclusion the evidence supports.

Failure modes

Section titled “Failure modes”
  • Over-persuades into brochure mode - the deck becomes pure selling, omitting risks and weaknesses, until no sophisticated audience trusts it - Surface at least one genuine risk or constraint; acknowledging hard truths reads as credibility, not vulnerability, because it signals the presenter knows the landscape.
  • Narrative becomes theater - so much visual staging and story drama that the deck feels produced but empty; the audience senses it is being sold at rather than shown evidence - Anchor each slide in a concrete claim or number; story beats without substance dissolve the moment the audience asks follow-up questions.

Instruction

Section titled “Instruction”
Write as a pitch deck. Organize the content as a sequence of discrete slides, each carrying
one idea. Follow a persuasive narrative arc: open by establishing the problem and who
experiences it, then introduce the solution and why it works, show the market and the moment,
demonstrate traction or evidence, introduce the team, and close with a clear and specific ask.
Keep each slide to a headline plus a few bullets or a single supporting visual - not
paragraphs. Write slide titles that advance the story, not just label the category. The ask
must be earned: do not place it before the problem, evidence, and team have been established.
If a slide can stand alone without a presenter, it likely has too much text.

Template

Section titled “Template”

See the Pitch Deck template.

Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Product Thinker, Executive, Confident, Candid, Problem-Solution

Avoid with

Section titled “Avoid with”

Confessional, Reverent, Pastoral

Often confused with

Section titled “Often confused with”

One-Pager

Examples

Section titled “Examples”

Slide 1: The standup is failing half the team

Section titled “Slide 1: The standup is failing half the team”
  • Team: 11 engineers across 4 timezones - US Pacific, US Eastern, UK, India
  • 9am Pacific is 9:30pm IST
  • India engineers averaged 3.2 of 5 standups in Q1; US engineers averaged 4.6
  • This is not a discipline problem. It is a scheduling problem.

Slide 2: Swap the meeting for a three-field Slack post

Section titled “Slide 2: Swap the meeting for a three-field Slack post”
  • Engineers post to #team-standup by 10am local time
  • Three fields: Shipped, In progress, Blocked or at risk
  • Blockers @mention the person who can resolve them - no waiting for 9am Pacific
  • Status persists in Slack; searchable; no information lost between sessions

Slide 3: The team crossed the timezone threshold

Section titled “Slide 3: The team crossed the timezone threshold”
  • At 6 engineers: a 9am Pacific slot fits the whole team
  • At 11 engineers across 4 timezones: it does not
  • India headcount grew across the last two hiring rounds
  • We are already operating async in practice - only the standup pretends otherwise

Slide 4: One post per engineer, by 10am local time

Section titled “Slide 4: One post per engineer, by 10am local time”
  • Post: Shipped / In progress / Blocked or at risk in #team-standup
  • On-call engineer: reads the channel by 9am Pacific, responds to @mentions within 30 min
  • Thursday: 60-minute working session at 8am Pacific replaces the weekly sync slots - reserved for discussion that requires real-time exchange
  • No new tools. Slack templates only.

Slide 5: 14-minute meeting, 4 minutes of signal

Section titled “Slide 5: 14-minute meeting, 4 minutes of signal”
  • The standup averaged 14 minutes per session
  • Past month analysis: 4.2 minutes per session changed someone’s behavior
  • The remaining 10 minutes was status that required no response from anyone
  • Last quarter: 3 incidents where an engineer spent 1+ hour on a problem already solved in a prior standup - no persistent record existed

Slide 6: Recover 70 minutes per engineer per week, add nothing new

Section titled “Slide 6: Recover 70 minutes per engineer per week, add nothing new”
  • Recovered: 70 person-minutes per engineer per week (the 14-minute daily slot disappears)
  • Thursday session: 60 minutes replaces the five daily sync slots for the week
  • New overhead: On-call engineer adds a daily channel-read to existing scope
  • Tooling cost: Zero - Slack templates, no new subscriptions

Slide 7: The infrastructure is already in place

Section titled “Slide 7: The infrastructure is already in place”
  • Engineering manager: owns the template, the process doc, and the 30-day retro
  • On-call rotation (already running): adds daily channel triage to existing scope
  • No new roles. No new tools. No new budget.

Slide 8: Thirty days, then a decision

Section titled “Slide 8: Thirty days, then a decision”

Ask: Approval to run a 30-day trial starting next Monday

At Day 30, the director of engineering reviews:

  • Participation rate by timezone
  • Blocker resolution time vs sync baseline
  • Qualitative signal from 1:1 check-ins with all 11 engineers

Decision: Adopt, modify, or revert - with evidence.