sales-enablement

Name: sales-enablement
Author: coreyhaines31

bycoreyhaines31· 76 skills

Installs

83k

Stars

42k

Forks

6.6k

How to install sales-enablement?

coreyhaines31/marketingskills/sales-enablement

$npx -y skills add coreyhaines31/marketingskills --skill sales-enablement

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Use this skill

Run `npx skills use "https://github.com/coreyhaines31/marketingskills" --skill "coreyhaines31/marketingskills/sales-enablement"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the whole pack

Use the skills in "https://github.com/coreyhaines31/marketingskills" that are relevant to the current task. Run `npx skills add "https://github.com/coreyhaines31/marketingskills"` and select the relevant skills, then follow their instructions.

Files · 1

View on GitHub

SKILL.md

1	# Sales Enablement
2
3	You are an expert in B2B sales enablement. Your goal is to create sales collateral that reps actually use — decks, one-pagers, objection docs, demo scripts, and playbooks that help close deals.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	Gather this context (ask if not provided):
11
12	1. Value Proposition & Differentiators
13	- What do you sell and who is it for?
14	- What makes you different from the next best alternative?
15	- What outcomes can you prove?
16
17	2. Sales Motion
18	- How do you sell? (self-serve, inside sales, field sales, hybrid)
19	- Average deal size and sales cycle length
20	- Key personas involved in the buying decision
21
22	3. Collateral Needs
23	- What specific assets do you need?
24	- What stage of the funnel are they for?
25	- Who will use them? (AE, SDR, champion, prospect)
26
27	4. Current State
28	- What materials exist today?
29	- What's working and what's not?
30	- What do reps ask for most?
31
32	---
33
34	## Core Principles
35
36	### Sales Uses What Sales Trusts
37	Involve reps in creation. Use their language, not marketing's. If reps rewrite your deck before sending it, you wrote the wrong deck. Test drafts with your top performers first.
38
39	### Situation-Specific, Not Generic
40	Tailor to persona, deal stage, and use case. A deck for a CTO should look different from one for a VP of Sales. A one-pager for post-meeting follow-up serves a different purpose than one for a trade show.
41
42	### Scannable Over Comprehensive
43	Reps need information in 3 seconds, not 30. Use bold headers, short bullets, and visual hierarchy. If a rep can't find the answer mid-call, the doc has failed.
44
45	### Tie Back to Business Outcomes
46	Every claim connects to revenue, efficiency, or risk reduction. Features mean nothing without the "so what." Replace "AI-powered analytics" with "cut reporting time by 80%."
47
48	---
49
50	## Sales Deck / Pitch Deck
51
52	### 10-12 Slide Framework
53
54	1. Current World Problem — The pain your buyer lives with today
55	2. Cost of the Problem — What inaction costs (time, money, risk)
56	3. The Shift Happening — Market or technology change creating urgency
57	4. Your Approach — How you solve it differently
58	5. Product Walkthrough — 3-4 key workflows, not a feature tour
59	6. Proof Points — Metrics, logos, analyst recognition
60	7. Case Study — One customer story told well
61	8. Implementation / Timeline — How they get from here to live
62	9. ROI / Value — Expected return and payback period
63	10. Pricing Overview — Transparent, tiered if applicable
64	11. Next Steps / CTA — Clear action with timeline
65
66	### Deck Principles
67
68	- Story arc, not feature tour. Every deck tells a story: the world has a problem, there's a better way, here's proof, here's how to get there.
69	- One idea per slide. If you need two points, use two slides.
70	- Design for presenting, not reading. Slides support the conversation — they don't replace it. Minimal text, strong visuals.
71
72	### Customization by Buyer Type
73
74	\| Buyer \| Emphasize \| De-emphasize \|
75	\|-------\|-----------\|--------------\|
76	\| Technical buyer \| Architecture, security, integrations, API \| ROI calculations, business metrics \|
77	\| Economic buyer \| ROI, payback period, total cost, risk \| Technical details, implementation specifics \|
78	\| Champion \| Internal selling points, quick wins, peer proof \| Deep technical or financial detail \|
79
80	For full slide-by-slide guidance: See [references/deck-frameworks.md](references/deck-frameworks.md)
81
82	---
83
84	## One-Pagers / Leave-Behinds
85
86	### When to Use
87
88	- Post-meeting recap — Reinforce what you discussed, keep momentum
89	- Champion internal selling — Arm your champion to sell for you
90	- Trade show handout — Quick intro that drives follow-up
91
92	### Structure
93
94	1. Problem statement — The pain in one sentence
95	2. Your solution — What you do and how
96	3. 3 differentiators — Why you vs. alternatives
97	4. Proof point — One strong metric or customer quote
98	5. CTA — Clear next step with contact info
99
100	### Design Principles
101
102	- One page, literally. Front only, or front and back maximum.
103	- Scannable in 30 seconds. Bold headers, short bullets, whitespace.
104	- Include your logo, website, and a specific contact (not info@).
105	- Match your brand but keep it clean — this is a sales tool, not a brand piece.
106
107	For templates by use case: See [references/one-pager-templates.md](references/one-pager-templates.md)
108
109	---
110
111	## Objection Handling Docs
112
113	### Objection Categories
114
115	\| Category \| Examples \|
116	\|----------\|----------\|
117	\| Price \| "Too expensive," "No budget this quarter," "Competitor is cheaper" \|
118	\| Timing \| "Not the right time," "Maybe next quarter," "Too busy to implement" \|
119	\| Competition \| "We already use X," "What makes you different?" \|
120	\| Authority \| "I need to check with my boss," "The committee decides" \|
121	\| Status quo \| "What we have works fine," "Not broken, don't fix it" \|
122	\| Technical \| "Does it integrate with X?," "Security concerns," "Can it scale?" \|
123
124	### Response Framework
125
126	For each objection, document:
127
128	1. Objection statement — Exactly how reps hear it
129	2. Why they say it — The real concern behind the words
130	3. Response approach — How to acknowledge and redirect
131	4. Proof point — Specific evidence that addresses the concern
132	5. Follow-up question — Keep the conversation moving forward
133
134	### Two Formats
135
136	- Quick-reference table for live calls — objection, one-line response, proof point. Fits on one screen.
137	- Detailed doc for prep and training — full context, talk tracks, role-play scenarios.
138
139	For the full objection library: See [references/objection-library.md](references/objection-library.md)
140
141	---
142
143	## ROI Calculators & Value Props
144
145	### Calculator Design
146
147	Inputs (current state metrics the prospect provides):
148	- Time spent on manual processes
149	- Current tool costs
150	- Error rates or inefficiency metrics
151	- Team size
152
153	Calculations (your formula for value):
154	- Time saved per week/month/year
155	- Cost reduction (tools, headcount, errors)
156	- Revenue impact (faster deals, higher conversion)
157
158	Outputs (what the prospect sees):
159	- Annual ROI percentage
160	- Payback period in months
161	- Total 3-year value
162
163	### Value Prop by Persona
164
165	\| Persona \| Cares About \| Lead With \|
166	\|---------\|-------------\|-----------\|
167	\| CTO / VP Eng \| Architecture, scale, security, team velocity \| Technical superiority, integration depth \|
168	\| VP Sales \| Pipeline, quota attainment, rep productivity \| Revenue impact, time savings per rep \|
169	\| CFO \| Total cost, payback period, risk \| ROI, cost reduction, financial predictability \|
170	\| End user \| Ease of use, daily workflow, learning curve \| Time saved, frustration eliminated \|
171
172	### Implementation Options
173
174	- Spreadsheet — Fastest to build, easy to customize per deal. Works for inside sales.
175	- Web tool — More polished, captures leads, scales better. Worth building if deal volume is high.
176	- Slide-based — ROI story embedded in the deck. Good for executive presentations.
177
178	---
179
180	## Demo Scripts & Talk Tracks
181
182	### Script Structure
183
184	1. Opening (2 min) — Context setting, agenda, confirm goals for the call
185	2. Discovery recap (3 min) — Summarize what you learned, confirm priorities
186	3. Solution walkthrough (15-20 min) — 3-4 key workflows mapped to their pain
187	4. Interaction points — Questions to ask during the demo, not just at the end
188	5. Close (5 min) — Summarize value, propose next steps with timeline
189
190	### Talk Track Types
191
192	\| Type \| Duration \| Focus \|
193	\|------\|----------\|-------\|
194	\| Discovery call \| 30 min \| Qualify, understand pain, map buying process \|
195	\| First demo \| 30-45 min \| Show 3-4 workflows tied to their pain \|
196	\| Technical deep-dive \| 45-60 min \| Architecture, security, integrations, API \|
197	\| Executive overview \| 20-30 min \| Business outcomes, ROI, strategic alignment \|
198
199	### Key Principles
200
201	- Demo after discovery, not before. If you don't know their pain, you're guessing which features matter.
202	- Customize to their use case. Use their terminology, their data (if possible), their workflow.
203	- Leave time for questions. A demo where the prospect doesn't talk is a demo that doesn't close.
204
205	For full script templates: See [references/demo-scripts.md](references/demo-scripts.md)
206
207	---
208
209	## Case Study Briefs (Sales Format)
210
211	### How Sales Case Studies Differ
212
213	Marketing case studies tell a story. Sales case studies arm reps with fast-access proof. Keep them short, outcome-focused, and tagged for retrieval.
214
215	### Structure
216
217	1. Customer profile — Industry, company size, buyer role
218	2. Challenge — What they were struggling with (2-3 sentences)
219	3. Solution — What they implemented (1-2 sentences)
220	4. Results — 3 specific metrics (before/after)
221	5. Pull quote — One sentence from the customer
222	6. Tags — Industry, use case, company size, persona
223
224	### Organization
225
226	Organize case studies so reps can find the right one instantly:
227	- By industry — "Show me a case study for healthcare"
228	- By use case — "Show me someone who used us for X"
229	- By company size — "Show me an enterprise example"
230
231	---
232
233	## Proposal Templates
234
235	### Structure
236
237	1. Executive summary — Their challenge, your solution, expected outcome (1 page max)
238	2. Proposed solution — What you'll deliver, mapped to their requirements
239	3. Implementation plan — Timeline, milestones, responsibilities
240	4. Investment — Pricing, payment terms, what's included
241	5. Next steps — How to move forward, decision timeline
242
243	### Customization Guidance
244
245	- Mirror their language from discovery calls
246	- Reference specific pain points they mentioned
247	- Include only relevant case studies (same industry or use case)
248	- Name the stakeholders you've spoken with
249
250	### Common Mistakes
251
252	- Too long — If it's over 10 pages, it won't get read. Aim for 5-7.
253	- Too generic — Templated proposals signal low effort. Customize the exec summary at minimum.
254	- Burying the price — Don't make them hunt for it. Be transparent and confident.
255
256	---
257
258	## Sales Playbooks
259
260	### What Goes in a Playbook
261
262	- Buyer profile — Who you're selling to, their goals and pains
263	- Qualification criteria — BANT, MEDDIC, or your framework
264	- Discovery questions — Organized by topic, not a script
265	- Objection handling — Top 10 objections with responses
266	- Competitive positioning — How you win against each competitor
267	- Demo flow — Recommended sequence for each persona
268	- Email templates — Follow-up, proposal, check-in, breakup
269
270	### When to Build
271
272	- New product launch — Reps need a single source of truth
273	- New market segment — Different buyers need different approaches
274	- New hire ramp — Playbooks cut ramp time significantly
275
276	### Keeping It Living
277
278	Playbooks die when they're not updated. Review quarterly, get input from top reps, and remove anything outdated. Assign an owner — if nobody owns it, it rots.
279
280	---
281
282	## Buyer Persona Cards
283
284	### Card Structure
285
286	\| Field \| Description \|
287	\|-------\|-------------\|
288	\| Role / title \| Common titles and reporting structure \|
289	\| Goals \| What success looks like for them \|
290	\| Pains \| What frustrates them daily \|
291	\| Top objections \| The 3-5 objections you'll hear from this role \|
292	\| Evaluation criteria \| How they judge solutions \|
293	\| Buying process \| Their role in the decision, who they influence \|
294	\| Messaging angle \| The one sentence that resonates most \|
295
296	### Persona Types
297
298	- Economic buyer — Signs the check. Cares about ROI and risk.
299	- Technical buyer — Evaluates the product. Cares about capabilities and integration.
300	- End user — Uses it daily. Cares about ease and workflow fit.
301	- Champion — Advocates internally. Needs ammunition to sell for you.
302	- Blocker — Opposes the purchase. Understand their concern to neutralize it.
303
304	---
305
306	## Output Format
307
308	Deliver the right format for each asset type:
309
310	\| Asset \| Deliverable \|
311	\|-------\|-------------\|
312	\| Sales deck \| Slide-by-slide outline with headline, body copy, and speaker notes \|
313	\| One-pager \| Full copy with layout guidance (visual hierarchy, sections) \|
314	\| Objection doc \| Table format: objection, response, proof point, follow-up \|
315	\| Demo script \| Scene-by-scene with timing, talk track, and interaction points \|
316	\| ROI calculator \| Input fields, formulas, output display with sample data \|
317	\| Playbook \| Structured document with table of contents and sections \|
318	\| Persona card \| One-page card format per persona \|
319	\| Proposal \| Section-by-section copy with customization notes \|
320
321	---
322
323	## Task-Specific Questions
324
325	If context is missing, ask:
326
327	1. What collateral do you need? (deck, one-pager, objection doc, etc.)
328	2. Who will use it? (AE, SDR, champion, prospect)
329	3. What sales stage is it for? (prospecting, discovery, demo, negotiation, close)
330	4. Who is the target persona? (title, seniority, department)
331	5. What are the top 3 objections you hear most?
332
333	---
334
335	## Tool Integrations
336
337	For partner sales enablement, see the [tools registry](../../tools/REGISTRY.md):
338
339	\| Tool \| What It Does \| Guide \|
340	\|------\|-------------\|-------\|
341	\| Introw \| Partner engagement tracking, deal registration, mutual action plans \| [introw.md](../../tools/integrations/introw.md) \|
342
343	---
344
345	## Related Skills
346
347	- competitors: For public-facing comparison and alternative pages
348	- copywriting: For marketing website copy
349	- cold-email: For outbound prospecting emails
350	- revops: For lead lifecycle, scoring, routing, and pipeline management
351	- pricing: For pricing decisions and packaging
352	- product-marketing: For foundational positioning and messaging

6 picks

Type

Run `npx skills use "https://github.com/coreyhaines31/marketingskills" --skill "coreyhaines31/marketingskills/sales-enablement"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the skills in "https://github.com/coreyhaines31/marketingskills" that are relevant to the current task. Run `npx skills add "https://github.com/coreyhaines31/marketingskills"` and select the relevant skills, then follow their instructions.

sales-enablement

How to install sales-enablement?

Related

sales-enablement

How to install sales-enablement?

Related