LaunchWeek.ai

Back to Day 1: Position

Build a Pitch Deck — Even If You Never Plan to Raise

The pitch deck is the most under-used asset for non-fundraising founders. Most indie founders skip it because "I'm not raising," then regret it the first time they need to recruit a contractor, pitch a strategic partner, apply to an accelerator, or explain the business to a journalist in 2 minutes. A 10-slide pitch deck is the most compressed format your strategy can take. The work of building it forces you to make decisions you've been postponing — and once it exists, it's reusable across a dozen contexts that have nothing to do with raising money.

Why Build a Deck If You're Not Raising

Three real uses for non-fundraising founders:

  • High-leverage explanations. When a press inquiry, accelerator application, podcast invitation, or strategic partner email lands, you need to explain the business in under 2 minutes. The deck does this. Without it, you write a long email each time, badly.
  • Forces decisions you keep punting on. Building a deck makes you commit to specific numbers — TAM, growth rate, unit economics, 12-month roadmap. These decisions are uncomfortable, which is exactly why founders avoid them. The deck is the forcing function.
  • Recruiting tool for early hires and contractors. A great senior contractor or first hire wants to understand the trajectory before signing on. A 10-slide deck answers their first 80% of questions in 4 minutes. You skip the awkward "tell me about your company" call.

A pitch deck is also surprisingly cheap once you have the upstream work done — Customer Discovery, ICP, Value Proposition, Pricing Strategy, Competitive Positioning, Founder Story. The deck assembles the artifacts you've already produced into one tight narrative.

The 10-Slide Structure That Works

The deck format that lands across every audience — VC, accelerator, partner, recruit, journalist — has been stable for 15 years. Don't reinvent the structure; spend the energy on the content.

  1. Title — company name, 1-line tagline, your name + role + contact
  2. The problem — what's broken in the world, specifically
  3. The solution — what you've built, in 1 sentence + 1 visual
  4. Why now — what changed in the last 1-3 years that makes this the right moment
  5. How it works — a single product screenshot or short demo flow
  6. Market — who buys this, how big is the addressable opportunity
  7. Business model — pricing structure + unit economics
  8. Traction — what proof you have so far
  9. Team — who's building it and why this team can win
  10. The ask — what you want from the reader (specific)

For non-fundraising versions, slide 10 is "Get in touch" or "What's next" — not "raising $X". Same template, different ask.

This guide assumes you have already done the upstream LaunchWeek work. If you haven't, the deck will reveal the gaps; building it is also a quality check on the strategy underneath.

1. Title Slide

The title slide is the test for whether your positioning fits in 12 words.

Help me write the title slide for [your product] at [your-domain.com]. The slide must include:

1. Company / product name (large, centered)
2. A 1-line tagline (NOT a value prop — the value prop is a sentence; the tagline is a phrase that pairs with the name)
3. Date + version (so reviewers know which deck they're looking at)
4. Your name + role + contact (email + LinkedIn)

The tagline rules:
- 5-10 words max
- Names the category and the trade-off (per [Competitive Positioning](competitive-positioning.md))
- Specific, not generic ("Customer support for AI products" beats "Better customer support")
- Drops "the [adjective] [category]" formula if that's how you're positioned

Avoid:
- "AI-powered" / "next-generation" / "world-class" — generic adjective stacking
- Mission statements that don't say what the product is
- Multiple lines (it should fit on one)

Output 5 tagline candidates, pick the strongest, and explain why.

The title slide is also the slide journalists screenshot. Make it look like a product, not a deck template. Logo, tagline, name, contact, white space.

2. Problem Slide

The single most-watched slide. If the reader doesn't immediately think "yes, that's a real problem," the deck dies here.

Help me write the problem slide. The structure:

1. **Headline (1 sentence)**: the problem, in the customer's voice
2. **Three sub-bullets** (NOT 5-7): the specific dimensions of the problem
3. **One specific cost or stat** that quantifies the problem
4. **One customer quote** (verbatim from your discovery interviews) that makes it concrete

Example, for an indie analytics tool:
- Headline: "Founders need product analytics that fit between Mixpanel and a spreadsheet."
- Bullets:
   - Mixpanel and Amplitude take 2 weeks to instrument and need an event taxonomy team to maintain
   - Spreadsheet exports answer last week's question 3 days after you stopped caring
   - The dashboards you build "just to check" decay within 2 weeks of every product change
- Stat: "73% of pre-seed SaaS founders report 'analytics setup' as a top-5 time sink in their first year."
- Quote: "I spent six weeks setting up Amplitude and never opened it again."

Anti-patterns:
- Vague problems ("teams struggle with...")
- Problems only your team understands
- Problems that aren't actually problems people pay to solve (some "pains" are minor inconveniences, not businesses)
- Stats without sources

Output the slide content + the source for the stat.

Two principles:

  • Use the customer's exact language. From customer-discovery interviews. Verbatim. The reader either feels "yes, that's how I'd say it" or "this founder is making it up."
  • One stat is enough. Three stats look like a mood board; one specific stat reads as definitive. Pick the strongest.

3. Solution Slide

The simplest slide to write, the easiest to overcomplicate.

Help me write the solution slide. The structure:

1. **Headline (1 sentence)**: what the product is, in plain language
2. **One product visual**: either a hero screenshot, a key UI moment, or a 60-second demo embed
3. **Three sub-points**: what the product does, in active verbs (not features)

Critical rules:
- The headline is what you'd say if a friend asked "what does it do?" — not marketing copy
- The visual is real product, not a marketing illustration. A real screenshot beats a stylized diagram.
- The sub-points are jobs done, not feature lists. "Tracks activation, retention, revenue" not "advanced analytics dashboard, real-time tracking, custom reports"

Anti-patterns:
- Showing the entire product map (looks busy, says nothing)
- Stock illustrations (anyone-could-be-anything energy)
- Feature lists with checkmarks (boring; tells the reader nothing)

Output the headline, the visual spec (which screenshot to use + why), and the 3 sub-points.

The solution slide is where the Demo Video shines if embedded. A 30-second cut on this slide does more work than any text.

4. Why Now Slide

The slide most decks skip. Skipping it is a tell that the founder doesn't have a strong "now" story.

Help me write the "why now" slide. The structure:

3 trends or shifts in the last 1-3 years that make this the right moment. For each:
- The shift, in 1 line
- Concrete evidence (a stat, a product launch, a regulation change, a market behavior change)
- Why it specifically enables [your product]

Strong "why now" categories:
- **Technology shift**: a new capability is available (LLMs in 2023, GPT-4-class agents in 2024-2025, on-device AI in 2025-2026)
- **Behavior shift**: customer behavior changed (remote work, no-code adoption, AI-native expectations)
- **Cost shift**: something got 10x cheaper (model inference, GPU access, edge compute)
- **Regulation shift**: a new requirement created demand (EU AI Act, GDPR enforcement, accessibility laws)
- **Distribution shift**: new channels exist (TikTok B2B, Substack, AI-answer-engine SEO)

Avoid:
- "AI is the future" — too generic, every deck has it
- "The market is growing" — every market is growing on a long-enough timeline
- Trends that aren't actually new (mobile, cloud, SaaS itself)

The strongest "why now" sounds inevitable in retrospect: of course this is when this should exist.

Output the 3 shifts with specific evidence.

The "why now" is also one of the most useful self-tests. If you can't articulate a strong "now," the timing might genuinely be wrong — better to find out at the deck stage than 18 months in.

5. How It Works Slide

A walkthrough, not an architecture diagram.

Help me write the "how it works" slide. The structure:

Pick ONE approach:

**Approach A: 3-step user flow**
- Step 1: User does X → screenshot
- Step 2: System does Y → screenshot
- Step 3: User gets Z → screenshot
- Best for: products with a clear value-delivery flow

**Approach B: A single annotated product screenshot**
- The hero UI screen with 3-4 callouts pointing to key elements
- Best for: products where the dashboard is the value

**Approach C: A 60-second embedded demo video**
- Use the [Demo Video](../2-content/demo-video.md) cut
- Best for: products that demo well visually
- Don't rely on autoplay; have a static fallback for PDF readers

Pick the approach that fits my product and output the slide content. Avoid:
- Architecture diagrams (boxes-and-arrows; reader's eyes glaze)
- Code snippets (alienates non-technical readers)
- Multi-step flows with more than 4 steps (cognitive overload)

The "how it works" slide should let a non-technical reader walk away saying "I think I understand what they do."

6. Market Slide

Every deck has it; most are bad. The fix is "TAM/SAM/SOM" calculated from realistic assumptions, not bottom-up made-up numbers.

Help me write the market slide. The structure:

1. **TAM** — Total Addressable Market: every dollar in the world that could conceivably be spent on [your category]. Source: industry research firms (Gartner, IDC, BMC), public filings, government data.

2. **SAM** — Serviceable Addressable Market: the slice of TAM that fits your specific positioning (segment + geography + tier). Often 10-30% of TAM.

3. **SOM** — Serviceable Obtainable Market: realistic 5-year revenue if you execute well. Often 1-5% of SAM. This number must be defendable from a bottom-up calculation: (number of customers in your ICP segment) × (your average ARPA) × (your realistic share at year 5).

For each:
- The number (with source)
- The methodology in 1 sentence
- Why this specific slice is yours to win (positioning, distribution, founder advantage)

Anti-patterns:
- "$60B market" with no source or breakdown
- TAM that's actually the broader category's TAM (saying "the entire CRM market is yours" when you serve a 5% niche)
- SOM that's "1% of TAM = $X00M" — lazy and meaningless
- Bottom-up that doesn't add up (e.g., assuming you'll capture 40% of a market in 5 years)

Strong market slide:
- Specific numbers with sources cited
- Bottom-up SOM that makes the path believable
- Why this market is growing (CAGR with source)
- Your specific entry point

Output the slide with the math shown.

For non-fundraising decks, this slide can be simpler — just "who buys" + "how many of them" + "average price." But it's still worth doing the math; it sharpens decisions about pricing, segmentation, and where to invest.

7. Business Model Slide

Pricing structure, unit economics, the math.

Help me write the business model slide. The structure:

1. **Pricing model** (1 sentence): subscription / usage-based / hybrid / per-seat / per-feature
2. **Tier table**: 3-4 tiers with prices and key feature breakouts (pulled from [Pricing Page](../4-convert/pricing-page.md))
3. **Unit economics** (3-5 numbers):
   - ARPA (average revenue per account, monthly)
   - CAC (customer acquisition cost)
   - Payback period (months)
   - Gross margin
   - Net revenue retention (if mature enough to have one)

Strong unit economics:
- ARPA: realistic for the segment (B2B indie SaaS in 2026 ranges from $20-$500/mo)
- CAC: documentable from your data (channel + funnel + cost)
- Payback < 12 months for self-serve, < 18 for sales-led
- Gross margin 70-85% for SaaS (if much lower, explain why)
- NRR 100%+ at maturity (if you have it; skip if pre-launch)

Anti-patterns:
- Unit economics from a spreadsheet that has never been audited
- "We expect 80% gross margin" with no current data point
- CAC from ads that haven't been run yet
- Pricing tiers with no anchoring rationale

If your data is thin (pre-launch or early), be honest: show the assumptions, not made-up actuals. Investors and partners forgive thin data; they don't forgive made-up data.

Output the slide content with the numbers and one sentence of rationale per number.

8. Traction Slide

Honest. Specific. Forward-looking.

Help me write the traction slide. Show the proof you have, in roughly this order of strength:

1. **Revenue trajectory** — MRR or ARR by month for the last 6-12 months (line chart). Most powerful if it's growing.
2. **Paying customer count** — total + growth rate
3. **Logos** — named customers (with permission) — 5-10 logos arranged tastefully
4. **Engagement metrics** — DAU/MAU, activation rate, retention curve (if these are healthy)
5. **Pipeline / interest** — qualified prospects, signed LOIs, beta waitlist size (if pre-revenue)

Pick the 3-5 strongest signals and put them on the slide. Don't include weak ones — they dilute the narrative.

For pre-revenue products:
- Replace "revenue" with "waitlist size growing", "pre-orders signed", or "pilot customers"
- Replace "logos" with "design partners we're talking to" — but only if specific names exist
- Be candid: "We're pre-launch but [specific signal]" is stronger than fake-traction theater

Anti-patterns:
- Vanity metrics that don't predict revenue (Twitter followers, GitHub stars, page views)
- Charts with no axis labels or unit ("MRR" with no $ scale)
- Cherry-picked time windows that hide flat or down months
- "Customers" who are friends, family, or one-time non-paying signups

The traction slide is where investors / partners / journalists test honesty. Show what's real; explain context for what isn't yet.

Output the 3-5 picked signals with chart specs and the headlines.

The cleanest traction slide is one number, one chart, three logos. The temptation is to add more; resist it. Three strong signals beat eight weak ones.

9. Team Slide

Who's building it. Why this team can win. Not "look how impressive we are."

Help me write the team slide. The structure:

For each founder:
- Photo (square, friendly, not LinkedIn-corporate)
- Name + role
- 1-line credentials (most credible signal: "ex-X" if X is recognized; "built Y" if Y is shipped; "Z years in [domain]" if specific)
- 1 sentence on why this person specifically can win this market

If solo founder:
- Same format, single panel
- Plus: "Currently solo, hiring [specific role] in Q[N]"
- Or "Working with contractors for [specific function]" — be transparent

If team of 2-3:
- Standard 2-3 column layout
- Show complementary skills

Add: 2-3 named advisors or mentors if they're genuinely involved (with affiliation: "Y, advisor — formerly Head of Z at [company]"). Skip name-dropping advisors who don't actually help.

Anti-patterns:
- Stock-photo-quality headshots
- Vague credentials ("technologist", "10x engineer", "full-stack expert")
- Pretending a contractor is a co-founder
- Listing a 12-person "team" when 10 are friends who haven't done any work
- Advisors with no measurable involvement

The team slide answers: "should I trust these people to execute?" Be specific, be honest, and don't oversell.

Output the slide content for my team configuration.

For non-fundraising decks, the team slide can be even leaner — just enough to establish trust with the specific reader (e.g., for a recruit, focus on what working there is like).

10. The Ask Slide

The single most-skipped slide. Without it, the deck has no call to action.

Help me write the ask slide. The ask depends on the audience:

**For investors** (fundraising deck):
- "Raising $X to do Y by Z"
- The 3 specific milestones $X will fund
- The 12-18 month roadmap to reach them
- "We're targeting a Y-month / Y-month-to-default-alive runway"
- Contact + how to reach you

**For accelerators / programs**:
- The specific program tier you're applying to
- Why this program specifically (not generic)
- The 3 things you'd want from the program (mentor, network, capital, access)

**For strategic partners**:
- The specific partnership shape (integration, distribution, co-marketing)
- What you bring; what you need from them
- The first 90-day pilot proposal

**For recruits**:
- The role
- The opportunity (equity range, salary range, scope)
- Why this role matters to the company's next 12 months

**For journalists / press**:
- The specific story angle
- Available assets (founder interview availability, customer references, screenshots)
- Embargo / timing if applicable

**For non-fundraising / general audiences**:
- "What's next" + "How to follow"
- Email signup, Twitter, calendar link
- One specific thing the reader can do today (try the product, share with a friend, intro to a customer)

Pick the audience for THIS deck variant and output the ask. Then specify what changes if you re-version the deck for a different audience.

The ask makes the deck functional. Without it, the reader closes the deck and does nothing — which is the same as a deck that doesn't exist.

Producing the Deck

Once the content is written, the production matters less than founders think.

Help me pick the right tool and template for producing the deck.

Tools (2026):
- **DeckChat / STORYD / Beautiful.AI** — AI-assisted deck builders, fast for first draft
- **Pitch** — modern, collaborative, good templates
- **Figma** — most flexible, requires design taste
- **Slides / Keynote / PowerPoint** — old-school, infinite flexibility, infinite ways to look amateur
- **Tome** — visual narrative format, good for non-traditional decks

For most indie founders in 2026: Pitch or Figma. Skip Slides/Keynote unless you have design taste already proven elsewhere.

Design rules:
- One idea per slide; no slide does two jobs
- Max 30 words per slide
- Real fonts (Inter, IBM Plex, Söhne) not Times/Calibri
- One color palette (3-5 colors)
- One logo treatment, used consistently
- Slide numbers in the corner
- Charts with axis labels and data sources
- Screenshots that show real product, not mockups

Anti-patterns:
- Animated transitions
- Stock photos of people in suits
- Inspirational quotes
- Multiple fonts per slide
- Centered everything

Output:
- The recommended tool for my situation
- A 2-paragraph design direction (palette, fonts, screenshot style)
- The version-control plan (every deck change in git via PDF export, with named versions)

What Done Looks Like

By the end of week 2 of this work:

  1. 10-slide deck shipped in PDF format
  2. 2-3 versions of the deck for different audiences (investor, partner, recruit) with shared core slides
  3. A "live" deck link (Pitch / Tome / Figma) for fresh sends, plus PDF for archival
  4. A README in your /docs folder pointing to the latest version, with notes on what audience each version targets
  5. The first 3 sends: to one investor (or potential one), one partner candidate, and one recruit candidate — for feedback, not necessarily for transactional asks

Within 90 days:

  • The deck has been refined based on 5+ rounds of feedback
  • One concrete outcome attributable to the deck (a meeting, a hire, a partnership, an article)
  • The deck is referenced in your standard intro email template

Within 12 months:

  • The deck has been versioned through major product / pricing / team changes
  • Each version retired with a one-line note on why
  • Multiple specific outcomes (5+ meetings, 1+ hires, 1+ partnerships) traced to the deck

Common Pitfalls

  • Building the deck before the underlying work is done. The deck reveals every gap in your strategy. Build ICP, Value Proposition, Pricing Strategy, Competitive Positioning, and Founder Story first. The deck assembles them.
  • Skipping the "why now" slide. A deck without "why now" reads as "I had this idea." A deck with "why now" reads as "this moment is the right moment." Big difference.
  • Inflating traction. Investors / partners / recruits all check the math. One inflated number contaminates the whole deck.
  • Including a "competitive landscape" 2x2 chart with you in the upper-right. Everybody puts themselves upper-right. The chart says nothing.
  • Designing the deck in PowerPoint with default templates. Use Pitch, Tome, or Figma; the production quality difference is enormous and visible.
  • Sending the same deck to every audience. Create variants. The investor deck and the recruit deck have different asks and different traction emphasis.
  • No version control. Six months in, you have 14 PDFs and don't know which is current. Use git or a single living link.
  • Treating the deck as fundraising-only. The non-fundraising uses (recruits, partners, press) are often the ones that compound first.

Where the Pitch Deck Plugs Into the Rest of LaunchWeek

Verdict

The pitch deck is one of the most under-built artifacts in indie SaaS. Founders skip it because "I'm not raising," missing that 70% of the deck's value is non-fundraising — recruiting, partnerships, press, accelerator applications, and the strategic clarity the build forces. A 2-day investment that compounds for the next 12 months across half a dozen contexts.

Build it now while the business is small enough that the answers are still forming. The act of putting the answers on slides forces commitments you've been postponing. Six months later, when an opportunity lands in your inbox, the deck is ready and you respond in 5 minutes instead of 5 days.

Back to Day 1: Position

← PreviousWrite Your Landing Page CopyNext →Pricing Strategy for Early-Stage SaaS