1# Sales Deck Frameworks
2 
3Detailed slide-by-slide guidance for building sales decks that tell a story and close deals.
4 
5## The Storytelling Arc
6 
7Every great deck follows a narrative structure: **Situation → Complication → Resolution.**
8 
9- **Situation** (Slides 1-3): The world your buyer lives in. Establish shared understanding.
10- **Complication** (Slides 2-3): Why the status quo is no longer sustainable. Create urgency.
11- **Resolution** (Slides 4-11): Your approach, proof, and path forward.
12 
13The goal is not to present features. The goal is to make the buyer feel understood, then show them a better way.
14 
15---
16 
17## Slide-by-Slide Template
18 
19### Slide 1: Current World Problem
20 
21**What to include:**
22- The challenge your buyer faces daily
23- A stat or data point that quantifies the problem
24- Visual: simple graphic or striking number
25 
26**What to avoid:**
27- Starting with your company or product
28- Generic industry trends that don't connect to pain
29- More than one core problem
30 
31**Copy prompt:** "What is the one problem that, if you could describe it perfectly, would make your buyer say 'that's exactly my situation'?"
32 
33---
34 
35### Slide 2: Cost of the Problem
36 
37**What to include:**
38- Financial impact (revenue lost, costs incurred)
39- Time impact (hours wasted, delays)
40- Risk impact (what happens if they do nothing)
41- Specific numbers wherever possible
42 
43**What to avoid:**
44- Vague claims without data
45- Fear-mongering without substance
46- Too many metrics (pick 2-3 that hit hardest)
47 
48**Copy prompt:** "If your buyer does nothing for the next 12 months, what does it cost them?"
49 
50---
51 
52### Slide 3: The Shift Happening
53 
54**What to include:**
55- Market trend or technology change creating a new opportunity
56- Why "the old way" no longer works
57- Why now is the right time to act
58 
59**What to avoid:**
60- Hype-driven trends without substance
61- Making it about your product yet
62- Overly technical explanations
63 
64**Copy prompt:** "What has changed in the market that makes the old approach unsustainable?"
65 
66---
67 
68### Slide 4: Your Approach
69 
70**What to include:**
71- Your philosophy or unique point of view
72- How your approach differs from conventional solutions
73- The "aha" insight that led to your product
74 
75**What to avoid:**
76- Feature lists (too early)
77- Jargon or acronyms
78- Claiming to be "the only" or "the first" unless provably true
79 
80**Copy prompt:** "What do you believe about solving this problem that most people get wrong?"
81 
82---
83 
84### Slide 5: Product Walkthrough
85 
86**What to include:**
87- 3-4 key workflows that map to the pain from Slide 1
88- Screenshots or product visuals
89- Brief description of what each workflow accomplishes
90 
91**What to avoid:**
92- Showing every feature
93- Dense UI screenshots without callouts
94- Talking about technology instead of outcomes
95 
96**Copy prompt:** "Walk through 3 things the buyer would do in your product in their first week."
97 
98---
99 
100### Slide 6: Proof Points
101 
102**What to include:**
103- Customer logos (aim for recognizable names in their industry)
104- Key metrics: "X% improvement," "Y hours saved," "Z% increase"
105- Analyst recognition, awards, or certifications if relevant
106 
107**What to avoid:**
108- Unsubstantiated claims
109- Too many logos without context
110- Vanity metrics that don't relate to the buyer's pain
111 
112**Copy prompt:** "What are 3 numbers that prove your product works?"
113 
114---
115 
116### Slide 7: Case Study
117 
118**What to include:**
119- One customer story told well: challenge, solution, results
120- Specific metrics (before and after)
121- Customer quote if available
122- Choose a customer similar to the prospect
123 
124**What to avoid:**
125- Multiple case studies crammed into one slide
126- Generic outcomes without specifics
127- Customers from irrelevant industries
128 
129**Copy prompt:** "Tell the story of one customer who went from struggling to succeeding with your product."
130 
131---
132 
133### Slide 8: Implementation / Timeline
134 
135**What to include:**
136- Clear phases with timeline (e.g., Week 1: Setup, Week 2-3: Integration, Week 4: Live)
137- What's required from their side vs. yours
138- Support resources available
139 
140**What to avoid:**
141- Overcomplicating the process
142- Hiding time requirements
143- Skipping the "what do I need to do?" question
144 
145**Copy prompt:** "How does a customer get from signing to live? What does each week look like?"
146 
147---
148 
149### Slide 9: ROI / Value
150 
151**What to include:**
152- Expected return based on their inputs or industry benchmarks
153- Payback period
154- Total value over 1-3 years
155- Comparison to cost of inaction
156 
157**What to avoid:**
158- Unrealistic projections
159- ROI without showing your math
160- Generic numbers not tied to their situation
161 
162**Copy prompt:** "If they buy today, what does the next 12 months look like in dollars and hours?"
163 
164---
165 
166### Slide 10: Pricing Overview
167 
168**What to include:**
169- Pricing tiers or structure
170- What's included at each level
171- Recommended plan for their situation
172 
173**What to avoid:**
174- Burying the price or being cagey
175- Too many options (3 tiers max)
176- Surprising them with hidden costs
177 
178**Copy prompt:** "What does it cost, what do they get, and which plan is right for them?"
179 
180---
181 
182### Slide 11: Next Steps / CTA
183 
184**What to include:**
185- Specific next action with timeline ("Start a pilot next week")
186- What happens after they say yes
187- Your contact information
188 
189**What to avoid:**
190- Vague CTAs ("Let's stay in touch")
191- Multiple competing next steps
192- Ending without energy
193 
194**Copy prompt:** "What is the one thing you want them to do after this meeting?"
195 
196---
197 
198## Persona Customization Guide
199 
200### Technical Buyer Deck
201 
202**Add:**
203- Architecture diagram slide after Product Walkthrough
204- Security and compliance details
205- Integration ecosystem and API capabilities
206- Technical implementation requirements
207 
208**Remove or minimize:**
209- ROI calculations (they care about capability, not cost)
210- High-level market trends (they want specifics)
211 
212**Adjust tone:** Precise, no fluff, respect their expertise. Avoid marketing superlatives.
213 
214### Economic Buyer Deck
215 
216**Add:**
217- Detailed ROI slide with calculations shown
218- Total cost of ownership comparison
219- Risk mitigation and compliance
220- Executive summary slide up front
221 
222**Remove or minimize:**
223- Technical details and architecture
224- Feature-level walkthroughs
225- Implementation specifics (they'll delegate)
226 
227**Adjust tone:** Business-focused, outcome-driven. Speak in dollars and percentages.
228 
229### Champion Deck
230 
231**Add:**
232- "Internal selling" slide — key points for them to present to their team
233- Quick-win slide — what success looks like in 30 days
234- Peer proof — companies like theirs who succeeded
235- Objection pre-handling — common pushback they'll face internally
236 
237**Remove or minimize:**
238- Deep technical or financial detail
239- Anything that requires context they can't relay
240 
241**Adjust tone:** Empowering, equipping. Make them look smart to their boss.
242 
243---
244 
245## Anti-Patterns
246 
247### The Feature Dump
248Every slide is a feature with a screenshot. No story, no "so what," no connection to the buyer's world. Reps click through it; prospects tune out.
249 
250### The Wall of Text
251Slides with 200+ words. Nobody reads them during a presentation. If the slide requires reading, it belongs in a leave-behind.
252 
253### The Missing Story Arc
254Slides exist in isolation — no narrative flow from problem to solution to proof. The deck feels like a brochure, not a conversation.
255 
256### The Generic Screenshot
257Product screenshots without callouts, annotations, or context. The prospect can't tell what they're looking at or why it matters.
258 
259### The Premature Demo
260Jumping to product features before establishing the problem. The buyer has no frame of reference for why your features matter.
261 
262### The Kitchen Sink
263Trying to address every persona, every use case, every feature in one deck. The result is a 40-slide monster that nobody wants to sit through.
264