Sales Deck Builder

---
name: sales-deck-builder
description: Use when building a customer-facing sales deck for a post-discovery meeting. Triggers on "sales deck", "customer deck", "pitch deck for prospect", "demo deck", "AE deck".
---

# Sales Deck Builder

Most sales decks lose deals because they're feature tours. The buyer sat through 30 slides of product screenshots and learned nothing about how their specific pain gets solved. A good sales deck mirrors the discovery conversation back, then bridges to the solution.

## Required inputs

1. **Prospect** — company + the specific people in the room with titles
2. **Discovery findings** — the specific pain they named, in their words
3. **Their stage** — first follow-up, technical eval, business case review
4. **Competition** — what else they're considering
5. **Your one-line value prop** for THIS prospect (not the generic homepage one)
6. **Social proof** that's relevant to them (similar size, similar industry, similar pain)

If the user can't quote the prospect's actual pain back to you, push back: "Go back to discovery notes. The deck is built around their words, not yours."

## Slide-by-slide structure (10-15 slides)

- **Slide 1 — Title**: Prospect company name + your company. Date. Names of attendees on both sides.
- **Slide 2 — What we heard**: Their pain, in their words, specific examples from discovery. This is the most important slide. If they nod here, the rest is downhill.
- **Slide 3 — Why this matters now**: Cost of inaction. Specific. "Every week without this, your team is X."
- **Slide 4 — How we think about this problem**: Your point of view. Not "what we do" — how you see the problem differently.
- **Slide 5 — The solution (overview)**: One sentence + one screenshot. Don't tour the product yet.
- **Slide 6-8 — How it works for YOUR pain**: 2-3 slides walking through the specific scenario from their world. Use their language, their examples.
- **Slide 9 — Social proof**: 1-2 customers who looked like them and got result Y. Real numbers.
- **Slide 10 — Why us vs the alternatives**: Including "build it ourselves" and "do nothing." Be honest.
- **Slide 11 — Pricing / packaging**: If appropriate at this stage. Range, not final quote, unless they asked.
- **Slide 12 — What rollout looks like**: Timeline, who from their team is involved, what success looks like at 30/60/90.
- **Slide 13 — Open questions / next step**: Specific ask. Not "let us know." A meeting on the calendar with a date.

## Narrative principles

- **Their words on slide 2.** If you can't quote them, you didn't listen.
- **Your POV before your product.** Buyers buy worldview before features.
- **Their scenario, not your demo flow.** "Here's how we'd handle the Friday alert storm you mentioned" beats "here's our alerting feature."
- **Specific next step.** Always. "Demo with your eng team Tuesday at 2pm" beats "let's keep talking."

## Anti-patterns (strip these)

- 30+ slides — you're touring, not selling
- Generic "trusted by" logo wall — meaningless without context
- 10 features on one slide — none of them land
- "We're the leader in X" — buyers don't care
- Pricing on slide 4 — too early
- "Any questions?" as the last slide — abdication. End with a specific ask.

## Output

1. The slide-by-slide outline tailored to the prospect (with placeholders showing where their specific pain quotes go)
2. A python-pptx script generating the .pptx in 16:9 with their company name in the title and a clean template the AE can refine
3. A "what to memorize" list — the 3 slides where the AE should NOT be reading off the deck. Slide 2 is always one of them.

The AE refines the deck in PowerPoint or Google Slides before the call. python-pptx output is the structured starting point.