Product Marketing and GTM skill 11 of 13
Sales Enablement SKILL.md
The Sales Enablement skill makes Claude, Codex or another AI agent give sellers what they need to win. It builds a sales narrative from positioning, discovery guides, use-case demos, objection handling from win-loss, battlecards, proof and value calculators, organises content by deal stage inside the CRM, retires unused assets, runs role-plays and call reviews and plans 30-60-90 day onboarding.
sales-enablement/SKILL.md, version 1.0.0, 1,504 words.
By Afeez Adebayo, Marketing, SEO & Growth Expert with 10+ years of experience.
Created 10 October 2026. Updated 10 October 2026. Free to use under CC BY 4.0.
Sales enablement gives sellers what they need to win: a clear story, the right content at the right stage, answers to objections, competitive guidance, product knowledge and practice. Many enablement programmes produce piles of content that sellers never use, stored across shared drives, wikis and chat threads, while reps build their own decks the night before calls. Enablement works when it starts from how deals are actually won and lost, fits into the tools sellers already use and is measured by impact on win rates and cycle times.
This skill builds and improves enablement programmes: the core pitch and deck, stage-based content, objection handling, discovery and demo guides, battlecards, onboarding for new reps, training and measurement.
Operating principles
- Start from deals. Win-loss findings and call recordings show what sellers need.
- Fewer, better assets. A strong deck, demo flow and objection guide beat a hundred documents.
- Meet sellers where they work. Content inside the CRM, enablement tool or chat, not hidden in folders.
- Practise, don't just inform. Role-plays and call reviews change behaviour; slides rarely do.
- Measure use and impact. Track which assets are used in won deals and how win rates move.
Core enablement kit
| Asset | Purpose |
|---|---|
| Sales narrative and deck | The story from problem to value, built on positioning |
| Discovery guide | Questions that qualify and uncover pain, triggers and criteria |
| Demo flow | A demo built around the buyer's use case, not a feature tour |
| Objection handling guide | Top objections with evidence-based responses |
| Battlecards | Competitor-specific guidance |
| Case studies and references | Proof by segment and use case |
| ROI or value calculator | Quantifies value for the economic buyer |
| Pricing and packaging guide | How to position plans and discounts |
| Email and follow-up templates | Consistent, helpful outreach |
When to use, and when not to
Use it when win rates fall, when ramp time for new reps is long, after repositioning or launches, when sellers ignore existing content and when entering new segments.
Don't use it to define positioning (positioning) or for sales operations topics such as territory design and compensation.
Inputs to ask for, in one message
- Current deck, demo script, content library and where it lives.
- Win-loss findings and call recordings (or summaries).
- Sales process stages and qualification framework.
- Rep feedback on what helps and what's missing.
- Ramp time for new reps and win rates by rep, segment and stage.
- Tools: CRM, enablement platform, call recording.
Raw SKILL.md file
This is the exact file agents read, including the credit header and licence notice. Save it as sales-enablement/SKILL.md.
--- name: sales-enablement description: "Build sales enablement that wins deals: a sales narrative built on positioning, discovery guides, use-case demos, objection handling from win-loss, battlecards, proof, value calculators, pricing guides, stage-based content inside the CRM, retirement of unused assets, role-plays and call reviews, 30-60-90 onboarding and measurement by use, win rate and ramp time. Use whenever someone asks about sales enablement, a sales deck, sales narrative, objection handling, demo scripts, discovery questions, rep onboarding, sales content or why sellers don't use marketing materials." license: CC-BY-4.0 metadata: author: Afeez Adebayo author_url: https://afeezadebayo.com author_linkedin: https://www.linkedin.com/in/afeez-adebayo/ author_x: https://x.com/za_icon source: https://afeezadebayo.com/skills-md/marketing/product-marketing/sales-enablement/ category: marketing subcategory: product-marketing version: "1.0.0" created: "2026-10-10" updated: "2026-10-10" --- # Sales Enablement Sales enablement gives sellers what they need to win: a clear story, the right content at the right stage, answers to objections, competitive guidance, product knowledge and practice. Many enablement programmes produce piles of content that sellers never use, stored across shared drives, wikis and chat threads, while reps build their own decks the night before calls. Enablement works when it starts from how deals are actually won and lost, fits into the tools sellers already use and is measured by impact on win rates and cycle times. This skill builds and improves enablement programmes: the core pitch and deck, stage-based content, objection handling, discovery and demo guides, battlecards, onboarding for new reps, training and measurement. ## Operating principles 1. **Start from deals.** Win-loss findings and call recordings show what sellers need. 2. **Fewer, better assets.** A strong deck, demo flow and objection guide beat a hundred documents. 3. **Meet sellers where they work.** Content inside the CRM, enablement tool or chat, not hidden in folders. 4. **Practise, don't just inform.** Role-plays and call reviews change behaviour; slides rarely do. 5. **Measure use and impact.** Track which assets are used in won deals and how win rates move. ## Core enablement kit | Asset | Purpose | |---|---| | Sales narrative and deck | The story from problem to value, built on positioning | | Discovery guide | Questions that qualify and uncover pain, triggers and criteria | | Demo flow | A demo built around the buyer's use case, not a feature tour | | Objection handling guide | Top objections with evidence-based responses | | Battlecards | Competitor-specific guidance | | Case studies and references | Proof by segment and use case | | ROI or value calculator | Quantifies value for the economic buyer | | Pricing and packaging guide | How to position plans and discounts | | Email and follow-up templates | Consistent, helpful outreach | ## When to use, and when not to Use it when win rates fall, when ramp time for new reps is long, after repositioning or launches, when sellers ignore existing content and when entering new segments. Don't use it to define positioning (`positioning`) or for sales operations topics such as territory design and compensation. ## Inputs to ask for, in one message 1. Current deck, demo script, content library and where it lives. 2. Win-loss findings and call recordings (or summaries). 3. Sales process stages and qualification framework. 4. Rep feedback on what helps and what's missing. 5. Ramp time for new reps and win rates by rep, segment and stage. 6. Tools: CRM, enablement platform, call recording. ## Workflow ### Step 1. Diagnose Where do deals stall or die? Which reps win most, and what do they do differently? Which assets get used? ### Step 2. Build the narrative A sales story built on positioning: the shift in the world, the problem, the cost of the status quo, the better way, proof, and how to start. ### Step 3. Build stage-based content Map assets to stages: prospecting, discovery, demo, evaluation, proposal, negotiation, close. ### Step 4. Write objection handling The top objections from win-loss and calls, with responses and proof. ### Step 5. Design demos Use-case demos for each priority segment, with a short and a long version. ### Step 6. Organise content One source of truth, linked from the CRM by stage and deal type; retire outdated assets. ### Step 7. Train and practise Launch sessions, role-plays, call reviews and certification for new narratives. ### Step 8. Onboard new reps A 30-60-90 day plan with product, customer, competitor and process learning, plus shadowing. ### Step 9. Measure Asset use in won and lost deals, win rate, cycle length, ramp time and rep feedback. ## Sales narrative structure ``` 1. A shift in the world (why now) 2. Winners and losers of that shift 3. The promised land (what good looks like) 4. Obstacles to getting there 5. How we help (capabilities mapped to obstacles) 6. Proof (customers, results) 7. Next step ``` ## Discovery questions (examples) - What prompted you to look at this now? - How do you handle this today, and what does it cost you? - Who else is affected, and who decides? - What would success look like in six months? - What have you tried before? - What would stop you from moving forward? ## Rep onboarding (30-60-90) | Period | Focus | Proof of readiness | |---|---|---| | Days 1-30 | Product, ICP, positioning, narrative, tools | Delivers the narrative in a role-play | | Days 31-60 | Discovery, demos, objections, competitors | Runs supervised calls; passes demo certification | | Days 61-90 | Full deals with coaching | Owns pipeline with call reviews | ## Measuring enablement | Metric | Source | |---|---| | Asset usage in won vs lost deals | Enablement tool and CRM | | Win rate by stage and segment | CRM | | Sales cycle length | CRM | | Ramp time to first deal and quota | Sales operations | | Rep confidence and usefulness ratings | Quarterly survey | ## Content governance - One owner for each core asset, with a review date. - Retire assets unused for two quarters. - Version names that show the date, not "final-v3". - A request channel so sellers can ask for missing content. ## Call review routine Each week, managers and product marketing review two or three recorded calls: one win, one loss and one stalled deal. Note where the narrative landed, which objections came up and which assets helped, then update enablement and coaching from what you hear. Share call clips of great moments in team meetings so good practice spreads quickly. ## Edge cases and judgement calls | Situation | What to do | |---|---| | Product-led company with a small sales team | Focus on usage-signal plays, short demos and expansion talk tracks | | Enterprise deals | Add mutual action plans, security and procurement kits, executive briefings | | Reps resist the new narrative | Pilot with top performers and share their results | | Content sprawl | Audit, retire unused assets, keep one library | | New segment | Build segment-specific discovery, demo and proof first | ## Handoffs to related skills - Positioning and messaging: `positioning`, `messaging-framework` - Loss reasons: `win-loss-analysis` - Battlecards: `competitive-intelligence` - Proof: `case-studies-customer-proof` - Pricing guidance: `pricing-packaging` - Launch readiness: `product-launch` ## Worked example A B2B security company had a 60-slide deck, a shared drive with 300 files and a nine-month ramp for new reps. Call reviews showed top performers skipped most of the deck, ran discovery on audit deadlines and demoed only the compliance workflow. Enablement rebuilt a 12-slide narrative around passing audits faster, a discovery guide, two use-case demos, an objection guide from win-loss and a 30-60-90 onboarding plan with role-plays. Content moved into the CRM by stage and 240 files were retired. Ramp time fell to around five months, and demo-to-opportunity conversion rose. ## Output format ``` # Sales enablement plan: <company>, <date> ## Diagnosis (where deals stall, top performer patterns, asset usage) ## Sales narrative ## Stage-based content map ## Objection handling and demo flows ## Content organisation and retirement list ## Training and onboarding plan ## Metrics ``` ## Common mistakes - Producing content sellers don't use. - Feature-tour demos. - Objection responses without evidence. - Content scattered across tools. - Training once, without practice or follow-up. ## Questions to ask before you build - Where do deals stall, and why? - What do top performers do differently? - Which assets do reps use today, and which do they ignore? ## Self-check before you answer - Is enablement based on win-loss and call evidence? - Is there one narrative built on positioning? - Are assets mapped to stages and stored where reps work? - Are practice and impact measures included? ## Further reading - Andy Raskin on strategic narratives: https://andyraskin.com/ - April Dunford, Sales Pitch (2023) --- Created by Afeez Adebayo, Marketing, SEO & Growth Expert Website: https://afeezadebayo.com LinkedIn: https://www.linkedin.com/in/afeez-adebayo/ X: https://x.com/za_icon Source: https://afeezadebayo.com/skills-md/marketing/product-marketing/sales-enablement/ Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.
Workflow
Step 1. Diagnose
Where do deals stall or die? Which reps win most, and what do they do differently? Which assets get used?
Step 2. Build the narrative
A sales story built on positioning: the shift in the world, the problem, the cost of the status quo, the better way, proof, and how to start.
Step 3. Build stage-based content
Map assets to stages: prospecting, discovery, demo, evaluation, proposal, negotiation, close.
Step 4. Write objection handling
The top objections from win-loss and calls, with responses and proof.
Step 5. Design demos
Use-case demos for each priority segment, with a short and a long version.
Step 6. Organise content
One source of truth, linked from the CRM by stage and deal type; retire outdated assets.
Step 7. Train and practise
Launch sessions, role-plays, call reviews and certification for new narratives.
Step 8. Onboard new reps
A 30-60-90 day plan with product, customer, competitor and process learning, plus shadowing.
Step 9. Measure
Asset use in won and lost deals, win rate, cycle length, ramp time and rep feedback.
Sales narrative structure
1. A shift in the world (why now)
2. Winners and losers of that shift
3. The promised land (what good looks like)
4. Obstacles to getting there
5. How we help (capabilities mapped to obstacles)
6. Proof (customers, results)
7. Next stepDiscovery questions (examples)
- What prompted you to look at this now?
- How do you handle this today, and what does it cost you?
- Who else is affected, and who decides?
- What would success look like in six months?
- What have you tried before?
- What would stop you from moving forward?
Rep onboarding (30-60-90)
| Period | Focus | Proof of readiness |
|---|---|---|
| Days 1-30 | Product, ICP, positioning, narrative, tools | Delivers the narrative in a role-play |
| Days 31-60 | Discovery, demos, objections, competitors | Runs supervised calls; passes demo certification |
| Days 61-90 | Full deals with coaching | Owns pipeline with call reviews |
Measuring enablement
| Metric | Source |
|---|---|
| Asset usage in won vs lost deals | Enablement tool and CRM |
| Win rate by stage and segment | CRM |
| Sales cycle length | CRM |
| Ramp time to first deal and quota | Sales operations |
| Rep confidence and usefulness ratings | Quarterly survey |
Content governance
- One owner for each core asset, with a review date.
- Retire assets unused for two quarters.
- Version names that show the date, not "final-v3".
- A request channel so sellers can ask for missing content.
Call review routine
Each week, managers and product marketing review two or three recorded calls: one win, one loss and one stalled deal. Note where the narrative landed, which objections came up and which assets helped, then update enablement and coaching from what you hear.
Share call clips of great moments in team meetings so good practice spreads quickly.
Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Product-led company with a small sales team | Focus on usage-signal plays, short demos and expansion talk tracks |
| Enterprise deals | Add mutual action plans, security and procurement kits, executive briefings |
| Reps resist the new narrative | Pilot with top performers and share their results |
| Content sprawl | Audit, retire unused assets, keep one library |
| New segment | Build segment-specific discovery, demo and proof first |
Handoffs to related skills
- Positioning and messaging:
positioning,messaging-framework - Loss reasons:
win-loss-analysis - Battlecards:
competitive-intelligence - Proof:
case-studies-customer-proof - Pricing guidance:
pricing-packaging - Launch readiness:
product-launch
Worked example
A B2B security company had a 60-slide deck, a shared drive with 300 files and a nine-month ramp for new reps. Call reviews showed top performers skipped most of the deck, ran discovery on audit deadlines and demoed only the compliance workflow. Enablement rebuilt a 12-slide narrative around passing audits faster, a discovery guide, two use-case demos, an objection guide from win-loss and a 30-60-90 onboarding plan with role-plays. Content moved into the CRM by stage and 240 files were retired. Ramp time fell to around five months, and demo-to-opportunity conversion rose.
Output format
# Sales enablement plan: <company>, <date>
## Diagnosis (where deals stall, top performer patterns, asset usage)
## Sales narrative
## Stage-based content map
## Objection handling and demo flows
## Content organisation and retirement list
## Training and onboarding plan
## MetricsCommon mistakes
- Producing content sellers don't use.
- Feature-tour demos.
- Objection responses without evidence.
- Content scattered across tools.
- Training once, without practice or follow-up.
Questions to ask before you build
- Where do deals stall, and why?
- What do top performers do differently?
- Which assets do reps use today, and which do they ignore?
Self-check before you answer
- Is enablement based on win-loss and call evidence?
- Is there one narrative built on positioning?
- Are assets mapped to stages and stored where reps work?
- Are practice and impact measures included?
Further reading
- Andy Raskin on strategic narratives: https://andyraskin.com/
- April Dunford, Sales Pitch (2023)
On this page
- When to use this skill, and when not to
- Example prompts
- Example output
- What the agent needs from you
- How this skill hands off to related skills
- How to run Sales Enablement step by step
- Situations this skill handles
- What makes this skill different
- Practical tips from real projects
- Frequently asked questions
- Changelog
When to use this skill, and when not to
Use it when win rates fall, when new reps take too long to ramp, after repositioning or launches, when sellers ignore existing content and when entering new segments.
Many enablement programmes produce piles of content stored across drives and wikis while reps build their own decks the night before calls. Enablement works when it starts from how deals are won and lost, lives where sellers work and is measured by impact.
Don’t use it to define positioning (use Positioning) or for sales operations topics such as territories and compensation.
Example prompts
- “Rebuild our 60-slide deck into a sales narrative.”
- “Write a discovery guide for our mid-market reps.”
- “Build objection handling from our win-loss findings.”
- “Design a 30-60-90 onboarding plan for new AEs.”
- “Which enablement assets actually help win deals?”
Example output
The skill returns a fixed structure. A shortened example for an imaginary site:
# Sales enablement plan: example security company, 11 October 2026 Diagnosis: 60-slide deck, 300 files, nine-month ramp Top performers: discovery on audit deadlines; demo only the compliance workflow Kit: 12-slide narrative, discovery guide, two use-case demos, objection guide, battlecards Content: moved into CRM by stage; 240 files retired Onboarding: 30-60-90 plan with role-plays and certification
Enablement is built from what top performers and buyers show works, and judged by asset use in won deals, win rates and ramp time.
What the agent needs from you
The skill asks for the current deck, demo script and content library, win-loss findings and call recordings, sales stages and qualification framework, rep feedback, ramp time and win rates and the tools sellers use.
How this skill hands off to related skills
Enablement brings the set into deals: Positioning and Messaging, objections from Win-Loss, battlecards from Competitive Intelligence, proof from Customer Proof, pricing guidance from Pricing and launch readiness from Launches.
How to run Sales Enablement step by step
- Install the skill as
sales-enablement/SKILL.md. - Diagnose where deals stall and what top performers do.
- Build the narrative from positioning.
- Create stage-based content and objection handling.
- Organise content in the CRM and retire the rest.
- Train, practise and measure impact.
Situations this skill handles
Enablement needs vary by sales model. The skill handles these situations:
| Situation | What the skill does |
|---|---|
| Small sales team in a product-led company | Usage-signal plays and short demos |
| Enterprise deals | Mutual action plans and security kits |
| Reps resist the new story | Pilot with top performers |
| Content sprawl | Audit and retire unused assets |
| New segment | Segment-specific discovery and demos |
| Long ramp time | 30-60-90 plan with certification |
What makes this skill different
Most enablement teams measure output: decks made, documents published. This skill measures use and impact, building a small kit from win-loss evidence and top performer behaviour, placing it where sellers work and reinforcing it with practice.
Retiring unused content is part of the job, because a smaller library is easier to trust and use.
Practical tips from real projects
- Start from deals.
- Fewer, better assets.
- Meet sellers where they work.
- Practise, do not just inform.
A worked example: a B2B security company had a 60-slide deck, a shared drive with 300 files and a nine-month ramp for new reps. Call reviews showed top performers skipped most of the deck, ran discovery on audit deadlines and demoed only the compliance workflow. Enablement rebuilt a 12-slide narrative around passing audits faster, a discovery guide, two use-case demos, an objection guide from win-loss and a 30-60-90 onboarding plan with role-plays. Content moved into the CRM by stage and 240 files were retired. Ramp time fell to around five months, and demo-to-opportunity conversion rose.
The sales narrative follows seven beats: a shift in the world that explains why now, the winners and losers of that shift, what good looks like, the obstacles to getting there, how the product helps with each obstacle, proof from customers and a clear next step. Built on positioning, it gives every rep the same story while leaving room for their own style.
Discovery questions uncover pain and timing: what prompted the search now, how the buyer handles the problem today and what it costs, who else is affected and who decides, what success looks like in six months, what they tried before and what could stop them moving forward.
Demos are built around use cases for each priority segment, with a short and a long version, showing the buyer their own workflow rather than a tour of every feature.
Onboarding runs in three stages. In the first 30 days new reps learn the product, ICP, positioning, narrative and tools, and prove readiness by delivering the narrative in a role-play. In days 31 to 60 they learn discovery, demos, objections and competitors, run supervised calls and pass a demo certification. In days 61 to 90 they run full deals with coaching and regular call reviews.
Each week, managers and product marketing review two or three recorded calls (one win, one loss and one stalled deal), noting where the narrative landed, which objections came up and which assets helped, then update enablement from what they hear.
Governance keeps the library useful: one owner per core asset with a review date, retirement of assets unused for two quarters, dated version names and a request channel so sellers can ask for missing content.
Measurement covers asset usage in won versus lost deals, win rate by stage and segment, sales cycle length, ramp time to first deal and quota and quarterly rep ratings of usefulness.
Sharing short clips of strong call moments in team meetings spreads good practice faster than any document.
Frequently asked questions
What is sales enablement?
Giving sellers the story, content, guidance, knowledge and practice they need to win deals, measured by impact on win rates and cycles.
What belongs in a core enablement kit?
A sales narrative and deck, discovery guide, demo flow, objection handling, battlecards, proof, a value calculator, pricing guidance and follow-up templates.
Why do reps ignore marketing content?
It is often hard to find, out of date or not built around how deals are won. Fewer, better assets inside sellers’ tools fix that.
How long should a sales deck be?
Long enough to tell the story; many strong narratives fit in 10 to 15 slides.
How do I speed up rep ramp time?
A structured 30-60-90 plan with role-plays, demo certification, shadowing and call reviews.
How is enablement measured?
Asset usage in won and lost deals, win rate by stage, cycle length, ramp time and rep feedback.
Changelog
- 1.0.0, 10 October 2026: first release.
Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.
All Product Marketing and GTM skills
- Product Marketing Audit
- Positioning
- Messaging Framework
- Ideal Customer Profile and Personas
- Customer Research and Jobs-to-Be-Done Interviews
- Competitive Intelligence and Battlecards
- Win-Loss Analysis
- Go-to-Market Plan
- Product Launches
- Pricing and Packaging
- Case Studies and Customer Proof
- Partner Marketing and Co-Marketing
