Disc Proposal Walkthrough Deck

---
name: disc-proposal-walkthrough-deck
description: Turns your proposal into a walk-through deck outline of six to ten slides with the client's problem first, options side by side, the decision you need, speaker notes, and a read version if they will forward it. Use for "run disc-proposal-walkthrough-deck", "walk them through the proposal", "turn my proposal into slides", "build the proposal presentation", "slides for the proposal meeting", "speaker notes for my proposal", "a deck they can forward", part of the Claude for Winning Proposals Pack by Polar Bear.
---

# Proposal Walk-Through Deck

## When To Use
A proposal emailed cold goes silent, so you want to walk them through it. You have booked, or want to book, thirty minutes to present it live. This answers: what goes on each slide, in what order, and what do you say and ask so the meeting ends with a decision or a date for one.

## When Not To Use
If the proposal itself is not settled, run Proposal Red Team Review first; slides only make an unclear argument faster. If the signer will read one page and never sit in a meeting, use Proposal Executive Summary instead.

## Inputs
- The final proposal, the options and their prices as you set them, and your problem statement or call notes with the client's own figures.
- Who will be in the room, and whether the deck will be forwarded to people who were not.
- Your slide template, if you will build it in Claude for PowerPoint (generally available on paid plans), which works inside your own template and slide masters. Claude Slides (beta, Pro and Max first) builds from scratch and exports to PowerPoint or PDF.
If you have none of this, I start from the proposal alone and mark the output as a first draft.

## Approach
Show the outcome first, as good demos do: the client sees their problem and the result they get before any credentials. A forwarded deck is a different object, a document built in slides with fuller text, because nobody is there to speak to it. AI is good at turning a finished proposal into a tight slide order and notes in minutes; the conversation, the listening and the pauses stay with you. The failure it prevents: twelve slides about your firm, method and team, and the options shown on slide fourteen with four minutes left.

## Workflow
1. Ask at most three questions, all here: presented live, read cold, or both; how many slides you want between six and ten; how long the meeting is.
2. Slide order. Their problem and what it costs in their figures; the outcome they get; how you get there in one slide; options side by side; what they need to decide and by when; credentials last and short. Anything that does not serve the decision moves to an appendix or out.
3. Headlines. One message per slide, written as a full sentence that states the takeaway ("Your team loses [figure] a month to rework" not "Context"). Figures only from the client's numbers or your proposal; missing ones stay [bracketed].
4. Options slide. The options in columns with the same rows (what is included, what is left out, timing, price as you set it), so they compare like for like.
5. Speaker notes per slide: what to say in two or three sentences, the question to ask, and where to stop and listen. On the options slide the note is to ask which one fits before defending any.
6. Read version, if it will be forwarded: the same order with fuller text on each slide so it stands alone, and no line that depends on "as I mentioned".
7. Build: I give the outline for you to build in Claude Slides or Claude for PowerPoint on your template; you check every figure before it is shown.

## Output Format
```markdown
# Walk-Through Deck Outline
Client: [name] · Meeting: [date, length] · Mode: [live / read / both] · Slides: [count]
## Slides
| # | Headline (full sentence) | On the slide | Source of figures |
|---|---|---|---|
| 1 | [their problem and what it costs] | [two or three points] | [call notes, date] |
| [n] | [what you need them to decide, by when] | [the decision, the date] | [proposal] |
## Speaker notes
| # | What to say | Question to ask | Stop and listen |
|---|---|---|---|
| 1 | [two or three sentences] | [question] | [yes / after the question] |
## Read version changes
- Slide [n]: [added text so it stands alone]
## Decision
[You] decide the final slide count and which option to lead with by [date]; [client decision maker] is asked to choose an option or set a decision date in the meeting on [date].
```

## Done When
- The client's problem is on slide one or two and credentials come last.
- Every slide has a full-sentence headline, notes, a question and a figure source.
- The last slide states the decision and a date, and a read version exists if the deck will be forwarded.

## Quality Bar
- Six to ten slides unless you set otherwise; one message per slide.
- Options compared on the same rows; no decoy option added to steer the choice.
- Speaker notes include pauses: a walk-through that never stops to listen is an email read aloud.
- No rival named or compared on any slide.
- Their problem first, their figures only; you present and you send.

## Next
Run disc-executive-summary (Proposal Executive Summary) for the signer who was not in the room.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).