Sales enablement creates collateral reps trust and use, which means writing in their language and tying every claim to a business outcome — replace "AI-powered analytics" with "cut reporting time by 80%." A sales deck follows a 10-12 slide story arc (problem, cost of the problem, the shift, your approach, product walkthrough, proof, case study, implementation, ROI, pricing, next steps), not a feature tour, and gets tailored by buyer type — technical, economic, or champion. Objection docs give each objection a five-part response: the exact wording reps hear, the real concern behind it, how to acknowledge and redirect, a specific proof point, and a follow-up question. Everything should be scannable in 3 seconds mid-call, not comprehensive.
What's inside
The playbook covers
Reference library — 4 deep-dives
Key data
The recommendations are grounded in benchmarks, not opinion:
See it in action
Help me create a sales deck for our B2B SaaS product. We sell an employee engagement platform to HR directors at companies with 500-5000 employees. Our main differentiator is real-time pulse surveys with AI-powered insights.
"Competitor X is cheaper" → Response: "They are — here's what you give up at that price point." → Proof: feature comparison + a customer who switched → Follow-up: "Which of those tradeoffs would actually hurt your team?"
1. Problem in one sentence 2. What we do 3. Three differentiators 4. One strong proof metric 5. CTA with a named contact (not info@)
FAQ
How many slides should a sales deck have?
10-12, structured as a story arc rather than a feature dump: current-world problem, cost of the problem, the market shift creating urgency, your approach, a product walkthrough of 3-4 workflows, proof points, one case study, implementation timeline, ROI, pricing, and clear next steps. One idea per slide, and design it to support a conversation, not to be read on its own.
What's the framework for handling a sales objection?
Document five parts for each: (1) the objection exactly as reps hear it, (2) why they really say it — the concern behind the words, (3) how to acknowledge and redirect, (4) a specific proof point, and (5) a follow-up question to keep the conversation moving. Keep a quick-reference table for live calls and a detailed doc for prep and role-play.
When should I demo the product?
After discovery, never before. If you don't yet know the prospect's pain, you're guessing which features matter and the demo becomes a feature tour. Use their terminology and data, structure the call as opening, discovery recap, a walkthrough of 3-4 workflows mapped to their pain, and a close with next steps — and leave time for questions, because a demo where the prospect doesn't talk won't close.
Related skills
Build a tool for this workflow?
Marketers run this skill mid-task — the exact moment your tool matters. Partner tiers put your tool inside the skill their agent runs.
See partner tiers