sales-enablement
Use this skill when creating battle cards, competitive intelligence, case studies, or ROI calculators for sales teams. Triggers on battle cards, competitive analysis, case studies, sales collateral, ROI calculators, sales training, product positioning, and any task requiring sales enablement content or strategy.
sales sales-enablementbattle-cardscompetitive-intelcase-studiesroiWhat is sales-enablement?
Use this skill when creating battle cards, competitive intelligence, case studies, or ROI calculators for sales teams. Triggers on battle cards, competitive analysis, case studies, sales collateral, ROI calculators, sales training, product positioning, and any task requiring sales enablement content or strategy.
sales-enablement
sales-enablement is a production-ready AI agent skill for claude-code, gemini-cli, openai-codex. Creating battle cards, competitive intelligence, case studies, or ROI calculators for sales teams.
Quick Facts
| Field | Value |
|---|---|
| Category | sales |
| Version | 0.1.0 |
| Platforms | claude-code, gemini-cli, openai-codex |
| License | MIT |
How to Install
- Make sure you have Node.js installed on your machine.
- Run the following command in your terminal:
npx skills add AbsolutelySkilled/AbsolutelySkilled --skill sales-enablement- The sales-enablement skill is now available in your AI coding agent (Claude Code, Gemini CLI, OpenAI Codex, etc.).
Overview
Sales enablement is the discipline of giving sales teams the content, tools, and knowledge they need to effectively engage buyers at every stage of the purchasing journey. The core idea is that reps should spend time selling, not hunting for materials or improvising answers to objections they have seen a hundred times before. This skill covers how to build, structure, and maintain the assets that make a sales team consistently effective: battle cards, case studies, ROI calculators, competitive intelligence briefs, product one-pagers, and training programs.
Tags
sales-enablement battle-cards competitive-intel case-studies roi
Platforms
- claude-code
- gemini-cli
- openai-codex
Related Skills
Pair sales-enablement with these complementary skills:
Frequently Asked Questions
What is sales-enablement?
Use this skill when creating battle cards, competitive intelligence, case studies, or ROI calculators for sales teams. Triggers on battle cards, competitive analysis, case studies, sales collateral, ROI calculators, sales training, product positioning, and any task requiring sales enablement content or strategy.
How do I install sales-enablement?
Run npx skills add AbsolutelySkilled/AbsolutelySkilled --skill sales-enablement in your terminal. The skill will be immediately available in your AI coding agent.
What AI agents support sales-enablement?
This skill works with claude-code, gemini-cli, openai-codex. Install it once and use it across any supported AI coding agent.
Maintainers
Generated from AbsolutelySkilled
SKILL.md
Sales Enablement
Sales enablement is the discipline of giving sales teams the content, tools, and knowledge they need to effectively engage buyers at every stage of the purchasing journey. The core idea is that reps should spend time selling, not hunting for materials or improvising answers to objections they have seen a hundred times before. This skill covers how to build, structure, and maintain the assets that make a sales team consistently effective: battle cards, case studies, ROI calculators, competitive intelligence briefs, product one-pagers, and training programs.
When to use this skill
Trigger this skill when the user:
- Asks to create or update a battle card for a product or competitor
- Needs a competitive intelligence brief or analysis
- Wants to write a customer case study or success story
- Asks to build an ROI or business value calculator
- Needs a product one-pager or sales leave-behind
- Wants to design or structure a sales training program
- Asks for help with product positioning for a sales audience
- Needs to measure or improve sales enablement effectiveness
Do NOT trigger this skill for:
- Marketing campaign copy or demand generation (audience is buyers, not reps)
- Product roadmap or engineering documentation (use product-management skills instead)
Key principles
Sales-ready, not marketing-pretty - Sales collateral must be scannable in 30 seconds and answerable in a live call. Dense prose, brand storytelling, and visual polish matter less than clarity, speed, and objection coverage. If a rep can't use it under pressure, it will never leave the folder.
Update quarterly or it's stale - Competitive landscapes, pricing, and product capabilities shift constantly. A battle card with outdated win rates or features that no longer exist actively hurts deals. Schedule a quarterly review cycle and treat outdated content as a blocker, not a to-do.
One page per asset - Every piece of enablement content should fit on one printed page or one screen without scrolling. If it doesn't fit, split it into two assets. Length signals effort to the creator; brevity signals respect for the reader's time under pressure.
Arm for objections, not just features - The job of enablement content is to prepare reps for the moments they feel vulnerable: "Your competitor does this for half the price," "We already have a solution for that," "We'll revisit next quarter." Every asset should include the three most common objections reps hear and a proven response to each.
Measure usage and impact - Enablement content that is never opened cannot drive revenue. Track view rates, download counts, content usage by deal stage, and win rates for deals where content was used versus not. Cull assets that go unused and double down on those that correlate with wins.
Core concepts
Enablement content types
| Asset | Primary use | Length | Update cadence |
|---|---|---|---|
| Battle card | Live competitive calls | 1 page | Quarterly |
| Case study | Late-stage proof | 1-2 pages | As new wins occur |
| ROI calculator | Business case / CFO | 1 spreadsheet | Semi-annually |
| Product one-pager | Discovery and demos | 1 page | With major releases |
| Competitive brief | Deep research | 3-5 pages | Quarterly |
| Sales playbook | New hire ramp / coaching | 10-20 pages | Annually |
| Objection handler | Ongoing coaching | 1-2 pages | Quarterly |
Buyer journey mapping
Align content to where the buyer is in their decision process:
- Awareness - Buyer has a problem but no solution in mind. Use thought leadership, industry data, and problem-framing one-pagers.
- Consideration - Buyer is evaluating solutions. Use competitive battle cards, feature comparison sheets, and analyst summaries.
- Decision - Buyer is choosing a vendor. Use case studies, ROI calculators, security/compliance docs, and reference call frameworks.
- Post-sale - Buyer becomes a customer. Use onboarding guides, expansion plays, and renewal decks.
Competitive positioning
Effective competitive positioning is not about tearing down competitors. It is about making the choice obvious for the right buyer. Build positioning on four pillars:
- Where we win - Deal types, company sizes, industries, or use cases where the product is the clear best fit.
- Where they win - Honest assessment of situations where a competitor is a better fit. Reps who acknowledge this build trust; reps who deny it lose deals.
- Key differentiators - Three to five concrete, provable differences - not "we are more innovative" but "we process transactions in under 50ms vs their documented 200ms average."
- Trap questions - Discovery questions that expose competitor weaknesses and pull the conversation toward your strengths.
Win/loss analysis
Win/loss analysis is the feedback loop that makes all other enablement content accurate. Conduct structured interviews within two weeks of closing or losing a deal:
- Why did the buyer choose us / not choose us?
- Which competitors were in the deal? What did they say about them?
- Which objections came up? How were they handled?
- What content did the rep use? Was it helpful?
Feed findings back into battle cards, objection handlers, and training within 30 days.
Common tasks
Create a battle card
Use the template in references/battle-card-template.md. Key sections:
- One-line pitch - Why choose us over this competitor in one sentence.
- Where we win - Three to five deal types or buyer profiles where we are the stronger choice.
- Where they win - One to two honest scenarios. Omitting this makes the card look like propaganda and trains reps to be blindsided.
- Top objections and responses - The three objections reps hear most in competitive deals, each with a validated response from a rep who has won that exchange.
- Trap questions - Two or three discovery questions that surface needs your product addresses better.
- Key differentiators - Concrete, provable, and ideally third-party validated.
- Do not say - Phrases or claims that are inaccurate, legally risky, or that consistently backfire in deals.
Write a case study
Use the Problem-Solution-Result framework:
CUSTOMER: [Name], [industry], [size]
CHALLENGE: One paragraph. What specific problem were they trying to solve?
Include the business impact of NOT solving it (cost, risk, lost time).
SOLUTION: One paragraph. What did they implement and how? Focus on capabilities
used, not product marketing language.
RESULTS: Three to five bullet points with quantified outcomes.
- Reduced onboarding time from 6 weeks to 10 days
- Saved $340k annually in manual processing costs
- Increased NPS from 32 to 67 within 90 days
QUOTE: One direct quote from the economic buyer or champion, attributed to name
and title, that captures the business value in their words.Validation rules: Every number must be approved by the customer. Every quote must be attributed. Every case study must go through legal review before external use.
Build an ROI calculator
ROI calculators must answer three questions for a CFO:
- What does the problem cost today? - Quantify the status quo in dollars. Hours wasted * loaded salary rate, error rates * average cost per error, churn caused by the problem * average contract value.
- What does the solution cost? - License cost + implementation + training + ongoing admin. Be honest. Buyers will find the hidden costs anyway.
- What is the net return and payback period? - (Annual benefit - annual cost) / annual cost = ROI%. Break-even month = total investment / monthly benefit.
Build the model in a spreadsheet with clearly labeled input cells (highlighted yellow) and output cells. Every assumption should be visible and editable. Provide conservative, base, and optimistic scenario columns.
Develop competitive intelligence briefs
Structure a competitive intelligence brief in five sections:
- Company overview - Size, funding, recent news, strategic direction.
- Product comparison - Feature-by-feature table with honest ratings (strong / comparable / weak) for both products.
- Pricing and packaging - What is known publicly; estimated ranges from deal data; typical discounting patterns.
- Sales tactics - How they sell: FUD they spread, discounting triggers, pressure tactics reps have encountered.
- How to beat them - Specific deal strategy, trap questions, and references to relevant battle card.
Sources: competitor website, G2/Gartner reviews, job postings (reveal roadmap priorities), LinkedIn, customer interviews, and your own deal notes.
Create product one-pagers
A product one-pager is not a datasheet. It is a conversation starter for discovery calls and a leave-behind after demos. Structure:
- Headline - Outcome the buyer gets, not product name or feature list.
- The problem - Two sentences on the pain. Buyers should nod.
- The solution - Three bullet points on what the product does.
- Why us - Three differentiators with evidence.
- Customer proof - One logo strip or one quote.
- Call to action - Next step that is specific and low-friction.
Avoid: feature lists without context, internal jargon, and anything that requires a product manager to explain.
Design sales training program
Structure a training program around four competency areas:
- Product knowledge - What it does, how it works, common configurations. Tested via demo certification (rep must demo without a script).
- Competitive knowledge - Who the competitors are, where we win and lose. Tested via mock competitive call with objections thrown.
- Discovery skills - How to uncover business pain, quantify impact, map to stakeholders. Practiced via recorded discovery calls with feedback.
- Deal execution - How to build a mutual success plan, navigate procurement, create urgency ethically. Practiced via deal reviews.
Ramp milestone: rep should be fully certified and carrying quota by week eight. Each certification requires a practical demonstration, not just a quiz.
Measure enablement effectiveness
Track these metrics in a monthly review:
| Metric | What it measures | Target |
|---|---|---|
| Content usage rate | % of reps using assets in active deals | > 60% |
| Asset open rate | % of sent assets opened by buyers | > 40% |
| Win rate with content | Win rate when asset used vs not | > 10 pp lift |
| Time to rep productivity | Weeks from start date to first close | Trend down |
| Competitive win rate | Win rate in tracked competitive deals | Track by competitor |
| Enablement NPS | Rep satisfaction with materials | > 30 |
Review with sales leadership monthly. Drop assets below 20% usage. Investigate and replicate assets with strong win rate correlation.
Anti-patterns / common mistakes
| Mistake | Why it's wrong | What to do instead |
|---|---|---|
| Building for marketing, not reps | Long-form PDFs and polished decks reps cannot use under pressure | Co-create with reps; test every asset in a live role play before publishing |
| Ignoring where you lose | Omitting competitor strengths makes cards feel like propaganda; reps get blindsided | Include honest "where they win" sections; this builds rep credibility with buyers |
| One ROI model for all buyers | A CFO and a VP of Engineering evaluate value differently | Build buyer-persona-specific calculators or clearly label which persona each model targets |
| Launching without training | Uploading content to a portal and expecting adoption | Run a 30-minute launch session; show reps when and how to use each asset |
| Treating enablement as a one-time project | Content is stale within months; stale content is worse than no content | Put quarterly review dates on every asset at creation time |
| Measuring output not outcomes | Reporting number of assets created instead of deals influenced | Tie every enablement initiative to a revenue or productivity metric from day one |
Gotchas
Battle card built without input from reps who've been in those deals - An enablement asset created by product marketing without validating objections against real deal data produces cards that look complete but fail in live calls. Validate every objection and response with at least two reps who have faced that competitor.
ROI calculator with hidden or locked assumptions - If buyers can't see and edit the input assumptions, they distrust the output. A locked model that produces "you save $500k" with no visible math undermines credibility. Every assumption cell must be visible, labeled, and editable.
Case study numbers not customer-approved - Publishing customer outcome numbers without explicit written approval is both a trust and legal risk. Every metric in an external case study needs sign-off from the customer's legal or PR team, not just the champion contact.
Enablement content launched without a training session - Uploading assets to a portal and sending a Slack message does not drive adoption. Reps don't use content they weren't shown how and when to use. Run a 30-minute launch session with real deal scenarios before expecting content usage.
Competitive intel briefs that don't include "where they win" - A battle card that only lists your strengths and the competitor's weaknesses reads as propaganda and trains reps to be blindsided. Honest "where they win" sections build rep credibility with buyers and prevent overconfidence in unsuitable deals.
References
For detailed content on specific topics, read the relevant file from references/:
references/battle-card-template.md- Full battle card structure with annotated examples and fill-in sections for each competitor
Only load a references file if the current task requires deep detail on that topic.
References
battle-card-template.md
Battle Card Template
A battle card is a one-page reference sheet a sales rep can scan in 30 seconds before a competitive call and reference during a live conversation. Every section must be concise enough to fit the one-page constraint. If a section is getting long, cut the weakest points - more is not better on a battle card.
Template
Copy and fill in the sections below. Annotated guidance follows each section.
[Your Product] vs. [Competitor Name]
Last updated: [YYYY-MM-DD] | Next review: [YYYY-MM-DD] | Owner: [Name/Team]
One-line pitch
[One sentence. Why should a buyer choose you over this competitor? Lead with the outcome, not a feature. Example: "Choose [Product] when you need a deployment that is live in a week, not a six-month implementation project."]
Where we win
Situations, buyer profiles, or deal types where we are the stronger choice:
- [Use case or buyer profile 1] - [One sentence on why we win here and what evidence supports it. E.g., "Mid-market SaaS companies (100-500 seats) - 78% win rate in Q3, driven by faster time-to-value and native integrations."]
- [Use case or buyer profile 2] - [One sentence with evidence.]
- [Use case or buyer profile 3] - [One sentence with evidence.]
- [Use case or buyer profile 4] - [Optional fourth scenario.]
- [Use case or buyer profile 5] - [Optional fifth scenario.]
Guidance: pull win rates from your CRM for each scenario. If you do not have data, run a win/loss analysis before publishing the card. Unsupported claims train reps to over-promise.
Where they win
Situations where the competitor is a stronger fit (be honest):
- [Scenario 1] - [One sentence. E.g., "Large enterprise deals requiring on-premise deployment - they have a mature on-prem product; ours is cloud-only."]
- [Scenario 2] - [One sentence. Optional second scenario.]
Guidance: include this section even if it is uncomfortable. Reps who acknowledge competitor strengths build more credibility than those who deny them. If you find yourself in a deal where they are the better fit, a qualified handoff is better than a lost deal that poisons your reference base.
Top objections and responses
The three objections reps hear most often in competitive deals against this competitor:
Objection 1: "[Exact words buyers use. E.g., 'Your competitor has more integrations.']"
Response: [Two to three sentences. Acknowledge the concern, reframe it, and pivot to your strength. E.g., "We have 150 native integrations covering 95% of the stack our customers actually use. More importantly, our integration setup takes minutes, not weeks - customers tell us that matters more than a longer list they never use. Can I show you the integrations relevant to your stack?"]
Objection 2: "[Second most common objection.]"
Response: [Two to three sentences following the same structure.]
Objection 3: "[Third most common objection.]"
Response: [Two to three sentences following the same structure.]
Guidance: these responses must come from reps who have won that specific exchange, not from marketing. Test each response in a role play before publishing. If it does not feel natural to say out loud, rewrite it.
Trap questions
Discovery questions that surface needs where you are stronger. Ask these before the buyer has committed to evaluating the competitor:
- "[Question 1. E.g., 'How long did your last similar implementation take, and what were the hidden costs your team absorbed?']"
- "[Question 2. E.g., 'What happens to your data if you decide to switch vendors two years from now?']"
- "[Question 3. E.g., 'When your team hits a blocker at 9pm on a Tuesday, what does your support path look like?']"
Guidance: trap questions expose competitor weaknesses without naming them. A buyer who surfaces the pain themselves is more convinced than one who is told about it. Do not use these as gotcha questions - they should be genuinely relevant to the buyer's situation.
Key differentiators
Concrete, provable differences. Avoid vague claims like "best-in-class" or "innovative." Every differentiator should survive the question: "How do you know?"
| Differentiator | Evidence |
|---|---|
| [Specific capability or outcome 1] | [G2 review data, benchmark study, customer quote, third-party report] |
| [Specific capability or outcome 2] | [Evidence] |
| [Specific capability or outcome 3] | [Evidence] |
Guidance: three strong differentiators beat ten weak ones. If you cannot cite evidence for a differentiator, do not put it on the card - it will get challenged in a deal and the rep will be left with nothing.
Do not say
Claims that are inaccurate, legally risky, or that consistently backfire:
- "[Phrase or claim 1. E.g., 'They are going out of business' - unverified and legally risky; buyers may share your card with the competitor.]"
- "[Phrase or claim 2. E.g., 'We do everything they do, plus more' - vague and easy to disprove; leads to feature bake-offs you may lose.]"
- "[Phrase or claim 3. E.g., 'Their support is terrible' - anecdotal; use G2 data or ask a trap question instead.]"
Customer references
Customers who have switched from this competitor or displaced them in an evaluation and are willing to speak:
| Customer | Contact | Deal details |
|---|---|---|
| [Company name] | [Account Executive who owns the reference] | [Size, industry, key use case] |
| [Company name] | [Account Executive] | [Size, industry, key use case] |
Guidance: always route reference requests through the owning Account Executive. Never give a reference contact directly to a prospect without checking availability.
Worked example: Acme CRM vs. Rival CRM
The following is a filled example to illustrate tone and length expectations.
Acme CRM vs. Rival CRM
Last updated: 2025-01-15 | Next review: 2025-04-15 | Owner: Sales Enablement Team
One-line pitch
Choose Acme CRM when your team needs to be live and selling within two weeks, not waiting six months for an implementation partner to finish configuration.
Where we win
- SMB and mid-market (10-500 seats) - 71% win rate in Q4 2024; buyers cite self-serve setup and transparent pricing as primary reasons.
- Companies replacing spreadsheets - Acme imports and structures CSV data automatically; Rival requires a paid data migration service.
- Teams without a dedicated Salesforce admin - Acme's no-code workflow builder needs no technical resources; 80% of customers self-configure in under a day.
- Fast-moving sales cycles (under 30 days) - Our trial-to-close motion works because buyers can validate value themselves without a lengthy demo cycle.
Where they win
- Enterprise deals (2,000+ seats) requiring complex approval workflows - Rival's enterprise tier has deeper approval chain logic that our product does not yet match.
- Companies already standardized on the Rival ecosystem - Switching costs are real; do not fight inertia without a compelling event.
Top objections and responses
Objection 1: "Rival has been around longer and has more features."
Response: "Feature count and time-in-market are not the same as fit. Rival built for large enterprise first; the complexity that comes with that often slows down teams your size. Our customers consistently tell us they use 90% of what Acme offers every week, versus 20% of what they had in Rival. Would it be useful to map the workflows you actually run to what each product does?"
Objection 2: "We got a big discount offer from Rival."
Response: "That is common - they discount heavily when they feel competitive pressure. Before comparing the numbers, it is worth understanding the full cost: their implementation typically runs $15-40k and takes 3-6 months. Our implementation is included and takes two weeks. Have you factored that in? I can put together a total-cost comparison if that would help."
Objection 3: "Our IT team prefers Rival because they already know it."
Response: "That is a fair concern, and I want to respect your IT team's time. Two things worth knowing: our API is REST-based and fully documented, so any admin who has worked with modern SaaS can manage it. And our customer success team provides direct implementation support at no extra cost, so the burden on your IT team is lower than you might expect. Could we schedule 30 minutes with them to walk through the technical requirements?"
Trap questions
- "How long did your last CRM implementation take, and what did that cost in internal hours in addition to the license fee?"
- "When you evaluated tools last time, how much of the feature set did your team end up actually using within the first six months?"
- "If you needed to pull all your data out of the CRM tomorrow and move it somewhere else, how easy would that be?"
Key differentiators
| Differentiator | Evidence |
|---|---|
| Median time-to-live of 11 days vs. Rival's 94-day median | G2 implementation timeline data, 847 reviews, as of Q4 2024 |
| Implementation included at no extra cost | Rival published partner fee schedule; Acme pricing page |
| 4.7/5.0 support rating vs. Rival's 3.9/5.0 | G2 category report, January 2025 |
Do not say
- "Rival is dying" - unverified; makes us look unprofessional if shared.
- "We do everything Rival does" - false; enterprise approval chains are a real gap.
- "Their support is terrible" - anecdotal; use G2 data or trap questions instead.
Customer references
| Customer | Contact | Deal details |
|---|---|---|
| FinanceForward Inc. | Jamie Reyes (jamier@acmecrm.com) | 85 seats, fintech, switched from Rival after failed implementation |
| BuildRight Agency | Sam Okonkwo (samo@acmecrm.com) | 40 seats, marketing agency, first CRM purchase, beat Rival on time-to-value |
Frequently Asked Questions
What is sales-enablement?
Use this skill when creating battle cards, competitive intelligence, case studies, or ROI calculators for sales teams. Triggers on battle cards, competitive analysis, case studies, sales collateral, ROI calculators, sales training, product positioning, and any task requiring sales enablement content or strategy.
How do I install sales-enablement?
Run npx skills add AbsolutelySkilled/AbsolutelySkilled --skill sales-enablement in your terminal. The skill will be immediately available in your AI coding agent.
What AI agents support sales-enablement?
sales-enablement works with claude-code, gemini-cli, openai-codex. Install it once and use it across any supported AI coding agent.