Sales Enablement

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

1. 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.

2. 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.

3. 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.

4. 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.

5. 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

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:

1. Where we win - Deal types, company sizes, industries, or use cases where the product is the clear best fit.
2. 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.
3. 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."
4. 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:

1. One-line pitch - Why choose us over this competitor in one sentence.
2. Where we win - Three to five deal types or buyer profiles where we are the stronger choice.
3. Where they win - One to two honest scenarios. Omitting this makes the card look like propaganda and trains reps to be blindsided.
4. 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.
5. Trap questions - Two or three discovery questions that surface needs your product addresses better.
6. Key differentiators - Concrete, provable, and ideally third-party validated.
7. 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:

1. 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.
2. What does the solution cost? - License cost + implementation + training + ongoing admin. Be honest. Buyers will find the hidden costs anyway.
3. 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:

1. Company overview - Size, funding, recent news, strategic direction.
2. Product comparison - Feature-by-feature table with honest ratings (strong / comparable / weak) for both products.
3. Pricing and packaging - What is known publicly; estimated ranges from deal data; typical discounting patterns.
4. Sales tactics - How they sell: FUD they spread, discounting triggers, pressure tactics reps have encountered.
5. 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:

1. Product knowledge - What it does, how it works, common configurations. Tested via demo certification (rep must demo without a script).
2. Competitive knowledge - Who the competitors are, where we win and lose. Tested via mock competitive call with objections thrown.
3. Discovery skills - How to uncover business pain, quantify impact, map to stakeholders. Practiced via recorded discovery calls with feedback.
4. 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:

Review with sales leadership monthly. Drop assets below 20% usage. Investigate and replicate assets with strong win rate correlation.

Anti-patterns / common mistakes

Gotchas

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

Companion check

On first activation of this skill in a conversation: check which companion skills are installed by running ls ~/.claude/skills/ ~/.agent/skills/ ~/.agents/skills/ .claude/skills/ .agent/skills/ .agents/skills/ 2>/dev/null. Compare the results against the recommended_skills field in this file's frontmatter. For any that are missing, mention them once and offer to install:

npx skills add AbsolutelySkilled/AbsolutelySkilled --skill <name>

Skip entirely if recommended_skills is empty or all companions are already installed.