# Sales Enablement Kit

> Build a sales enablement kit so reps can sell a product, feature, or launch confidently. Use when asked to create sales enablement materials, a rep-ready one-pager, talk tracks, objection handling, or a launch enablement package. Produces a complete kit — positioning summary, discovery questions, talk track, demo flow, objection handling, competitive counters, and a call-to-action for reps.

- Skill: `mohitagw15856/sales-enablement-kit` (Agent Skill)
- Install (CLI): `npx skillmds add mohitagw15856/sales-enablement-kit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mohitagw15856/sales-enablement-kit/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: Mohit Aggarwal (https://skillmd.com/u/mohitagw15856)
- Updated: 2026-09-07
- Page: https://skillmd.com/skills/mohitagw15856/sales-enablement-kit

---


# Sales Enablement Kit Skill

Give reps everything they need to have a confident, on-message conversation about a product or launch — without reading a 40-page deck. The kit should be skimmable, specific, and usable live on a call.

## What This Skill Produces

- A one-screen positioning summary reps can internalize fast
- Discovery questions that surface the pain this product solves
- A talk track and demo flow tied to buyer value, not features
- Objection handling and competitive counters
- Clear next steps and where to find assets

## Required Inputs

Ask for these if not provided:

- **What's being sold** — product, feature, or launch, and who it's for (segment, persona, buyer vs user)
- **The core value** — the problem it solves and the measurable outcome
- **Proof** — customers, metrics, case studies, or a demo environment
- **Top competitors** and the main objections reps hear today
- **Pricing/packaging** basics and any constraints on what reps can say
- **The motion** — inbound, outbound, PLG-assist, partner

Mark anything unknown as `[to confirm]` rather than inventing claims or metrics.

## Process

1. **Anchor on the buyer** — name the persona, their pain, and the outcome they buy.
2. **Compress positioning** — one sentence a rep can say, plus 3 value pillars with proof.
3. **Write discovery** — questions that make the pain vivid and qualify fit.
4. **Build the talk track** — what to say at each stage; lead with value, land features as evidence.
5. **Map the demo** — the shortest path that shows the "aha," not every screen.
6. **Arm for resistance** — the real objections and crisp, honest counters; competitive traps and how to reframe.
7. **Close the loop** — the CTA, next step, and links to assets.

## Output Format

---

# Sales Enablement Kit — [Product / Launch]

**For:** [Segment · persona · buyer] · **Motion:** [inbound/outbound/PLG] · **Status:** [GA / beta]

## The 10-Second Pitch
[One sentence a rep can deliver verbatim.]

## Who It's For & Why They Care
- **Persona:** [role] · **Pain:** [what hurts today] · **Outcome:** [measurable result]

## Value Pillars
| Pillar | What it means to the buyer | Proof |
|---|---|---|
| [Pillar] | [buyer-language benefit] | [metric / customer / demo step] |

## Discovery Questions
1. [Question that surfaces the pain]
2. [Question that quantifies impact]
3. [Question that qualifies fit / timing / budget]

## Talk Track
- **Opening:** [value-led framing]
- **Deepen:** [tie pain to pillar]
- **Evidence:** [proof point]

## Demo Flow (shortest path to "aha")
1. [Setup — the before state]
2. [The key moment — the payoff]
3. [Expand — one adjacent value]

## Objection Handling
| Objection | Honest response | Reframe |
|---|---|---|
| [Objection] | [acknowledge + answer] | [move the conversation forward] |

## Competitive Counters
- **vs [Competitor]:** [where we win] · **Trap to avoid:** [what not to claim]

## Next Step & Assets
- **CTA:** [the specific next step to ask for]
- **Assets:** [deck, one-pager, case study, demo env — or `[to confirm]`]

---

## Quality Checks

- [ ] The 10-second pitch is one sentence and jargon-free
- [ ] Every value pillar has a proof point, or is marked `[to confirm]`
- [ ] Discovery questions surface pain, not product features
- [ ] The demo flow is the shortest path to the payoff, not a tour
- [ ] Objection responses are honest — they don't over-claim
- [ ] A new rep could run a call from this kit alone

## Anti-Patterns

- [ ] Do not list every feature; reps sell outcomes, not spec sheets
- [ ] Do not invent metrics, logos, or case studies — mark them `[to confirm]`
- [ ] Do not write objection answers that dodge the real concern
- [ ] Do not make the demo a full product tour; find the one "aha"
- [ ] Do not bury the CTA — reps need to know exactly what to ask for next

## Example Trigger Phrases

- "Build a sales enablement kit for our new [feature] launch"
- "Write a rep-ready one-pager with talk track and objection handling"
- "Create discovery questions and a demo flow for [product]"
- "Arm the sales team to sell against [Competitor]"