# Sales Enablement — Marketing Skill for AI Agents

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.

> Maintained by Corey Haines · v2.0.1 · Updated 2026-06-16

Install: `npx skills add coreyhaines31/marketingskills`
Source: https://github.com/coreyhaines31/marketingskills/tree/main/skills/sales-enablement

## What's inside

**The playbook covers:** Before Starting, Core Principles, Sales Deck / Pitch Deck, One-Pagers / Leave-Behinds, Objection Handling Docs, ROI Calculators & Value Props, Demo Scripts & Talk Tracks, Case Study Briefs (Sales Format), Proposal Templates, Sales Playbooks, Buyer Persona Cards, Output Format, Task-Specific Questions, Tool Integrations

### Reference library

- [Sales Deck Frameworks](https://github.com/coreyhaines31/marketingskills/blob/main/skills/sales-enablement/references/deck-frameworks.md) — Detailed slide-by-slide guidance for building sales decks that tell a story and close deals.
- [Demo Script Templates](https://github.com/coreyhaines31/marketingskills/blob/main/skills/sales-enablement/references/demo-scripts.md) — Scene-by-scene templates for different call types, with timing, talk tracks, and interaction guidance.
- [Objection Library](https://github.com/coreyhaines31/marketingskills/blob/main/skills/sales-enablement/references/objection-library.md) — Common B2B SaaS objections with response frameworks. Organized by category for quick reference.
- [One-Pager Templates](https://github.com/coreyhaines31/marketingskills/blob/main/skills/sales-enablement/references/one-pager-templates.md) — Templates for different one-pager use cases, with layout guidance and copy prompts.

## Key data

- Interaction point (at the 5-min mark):**

## Example

**Prompt:** 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.

**Objection quick-reference row**

"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?"

**One-pager skeleton**

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

- **competitors** — For public-facing comparison and alternative pages
- **copywriting** — For marketing website copy
- **cold-email** — For outbound prospecting emails
- **revops** — For lead lifecycle, scoring, routing, and pipeline management
- **pricing** — For pricing decisions and packaging
- **product-marketing** — For foundational positioning and messaging

---
Canonical: https://marketing-skills.com/skills/sales-enablement