Pitch Deck Builder

Pitch Deck Builder

Overview

A pitch deck is a persuasion tool, not a feature list. The best decks make one argument: "the way the world works is changing, and we are the answer." They support that argument with proof and end with one clear action.

Prospects remember 3 things from any presentation. Design the deck so those 3 things are what you want them to remember.

When to Use

• "Build a pitch deck for our product"
• "Create a sales presentation"
• "Make an investor deck"
• "Design slides for our demo"
• "Build a board presentation"
• "I need a deck structure"

Do NOT use for:

• One-page documents → use one-pager-builder
• Competitive comparisons → use battlecard-builder
• Email sequences → use cold-email-copywriting

Authoritative Foundations

• Force Management Command of the Message — Value Messaging Framework. Every slide should connect to a Required Capability the buyer has articulated. Before Scenario → PBOs → Required Capabilities → Defensible Differentiators.
• Andy Raskin — Strategic narrative arc: name the enemy, show the promised land, explain why now, tease the secret sauce.
• Corporate Visions — message architecture. "Why change → Why you → Why now" progression beats feature-forward presentations.

Step-by-Step Process

Phase 1: Intake

Ask the user all at once:

1. Who is the audience? (prospect, investor, board, conference)
2. What persona(s)? (CTO, VP Sales, CEO, Champion, mixed)
3. What's the desired outcome? (meeting, investment, approval, purchase)
4. What are the top 3 things you want them to remember?
5. What proof points do you have? (metrics, logos, case studies, testimonials)

Phase 2: Deck Architecture

Standard 11-slide structure (adjust for context):

Slide 1 — Title

• Company name, tagline, presenter name
• One sentence: what you do, for whom, the outcome

Slide 2 — The Problem (Current World)

• Describe the status quo. Make it visceral.
• "Teams spend 15 hours/week on manual enrichment."
• Use the buyer's language, not your marketing copy.

Slide 3 — Cost of the Problem

• What inaction costs: time, money, risk, missed opportunity.
• Quantify. "$X per rep per month lost to [task]."
• Make the status quo unacceptable.

Slide 4 — The Shift (Why Now)

• Market change creating urgency. AI commoditizing old approaches.
• New regulation. New buyer behavior. New competitive threat.
• Answer: "why solve this now, not next year?"

Slide 5 — Our Approach (The Big Idea)

• How you solve it differently. Not features — principles.
• "Instead of X, we do Y."
• One big idea, clearly stated.

Slide 6 — Product Walkthrough

• 3-4 key workflows, not a feature tour.
• Each workflow: problem it solves → how it works → outcome.
• Screenshots over bullet points. Show, don't tell.

Slide 7 — Proof Points

• Metrics: "Customers see 40% reduction in time-to-X."
• Logos: recognizable brands that trust you.
• Analyst recognition, awards, press.
• One strong metric beats ten logos.

Slide 8 — Case Study

• One customer story, told well.
• Before (the pain) → After (the result) → How (your role).
• Include specific numbers. "Acme Corp reduced churn from 5% to 1.5%."

Slide 9 — ROI / Value

• Quantify the return. Conservative, moderate, aggressive scenarios.
• Payback period. "Investment recovers in 4 months."
• Make the economic case undeniable.

Slide 10 — Pricing Overview

• Transparent, tiered if applicable.
• What's included at each level.
• "Starting at $X/month" if exact pricing is variable.

Slide 11 — Next Steps / CTA

• One clear action. Not three options.
• Timeline. "This week: review proposal. Next week: technical deep-dive."
• Contact information.

Phase 3: Persona Customization

Same deck, different emphasis per audience:

Slide	CTO Version	VP Sales Version	CEO Version
Problem	Integration complexity, technical debt	Rep productivity, ramp time	Strategic risk, competitive threat
Approach	Architecture decisions	Workflow transformation	Market position
Proof	Security/compliance, scalability	Revenue impact metrics	Analyst validation, market momentum
ROI	Engineering hours saved	Pipeline generated	Valuation impact

Phase 4: Speaker Notes

Every slide gets speaker notes:

• What to say (not read — say)
• When to pause for questions
• What question to ask the audience
• Transition to next slide

Rule: never read slides aloud. The deck supports the speaker, not replaces them.

Output Format

Complete deck outline delivered as:

# Pitch Deck: [Company/Product]

## Slide 1: Title
**Headline:** [headline]
**Body:** [body copy, 2-3 bullets max]
**Speaker Notes:** [what to say, questions to ask]
**Visual Direction:** [screenshot, diagram, hero image]

## Slide 2: The Problem
...

Quality Check

• Deck tells ONE story, not ten
• Every slide answers "so what?" for the specific audience
• Proof points are specific and verifiable
• CTA is singular and clear — one next step
• Speaker notes exist for every slide
• Persona customization applied (not one-size-fits-all)
• Deck can be presented in 20 minutes with 10 minutes for discussion

Common Pitfalls

1. Feature dump. Slides listing features without connecting to outcomes. "We have AI-powered enrichment" → "Reps spend 0 minutes on manual research."

2. One deck for everyone. CTO and VP Sales care about different things. If the same deck works for both, it works for neither.

3. No speaker notes. Slides without delivery guidance produce inconsistent presentations. The deck is a tool, not a script.

4. Too many slides. 10-11 is the sweet spot. 25 slides = nobody remembers anything. If you need more detail, put it in an appendix.

5. Reading slides aloud. The audience can read. The speaker adds context, stories, and conviction the slides cannot.

6. No clear CTA. "Let us know if you're interested" is not a next step. "Does Thursday at 2pm work for a technical deep-dive?" is.

Execution Artifacts

• references/framework-notes.md — named frameworks, citation anchors, and operating assumptions
• templates/output-template.md — copy-paste deliverable structure for the user
• scripts/check-output.py — local checklist validator for required sections This skill includes lightweight artifacts the agent can load on demand: Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.

Related Skills

• sales-enablement: Complete enablement package
• one-pager-builder: Companion one-pagers for leave-behind
• battlecard-builder: Competitive positioning for deck content
• positioning-messaging: Foundation positioning the deck draws from