sales-enablement

name: sales-enablement description: | Create sales enablement content that helps reps close deals faster. Trigger: user mentions "sales enablement", "battle card", "pitch deck", "case study", "ROI calculator", "objection handling", "demo script", "proposal template", "competitive positioning", "one-pager", "sales playbook", "sales content", "sales collateral", "competitive intel", "sales tools" metadata: version: 1.0.0 author: Andre Ginja

Sales Enablement Content

Sales Enablement Content System

Content by Funnel Stage

Content Prioritization

Build these in order of impact:

1. Battle cards (reps ask for these most and use them in real-time)
2. Case studies (buyers trust peer experiences over vendor claims)
3. Pitch deck (used in every qualified opportunity)
4. Objection handling guide (addresses the top reasons you lose deals)
5. One-pagers (leave-behind for champions to share internally)
6. Demo script (ensures consistent product storytelling)
7. ROI calculator (quantifies value for economic buyers)
8. Proposal template (speeds up deal velocity)
9. Sales playbook (onboards new reps and standardizes approach)
10. Competitive positioning docs (deep dives for specific competitors)

Battle Cards

Battle Card Structure

Each battle card should fit on one page (front and back) and cover a single competitor:

## [Competitor Name] Battle Card

### Quick Facts
- Founded: [Year]
- HQ: [Location]
- Funding/Revenue: [If public or known]
- Target market: [Their primary segment]
- Pricing: [Model and known price points]

### Where We Win
- [Differentiator 1]: [One-sentence explanation]
- [Differentiator 2]: [One-sentence explanation]
- [Differentiator 3]: [One-sentence explanation]

### Where They Win
- [Their strength 1]: [Honest assessment]
- [Their strength 2]: [Honest assessment]
(Being honest about competitor strengths builds rep credibility)

### Landmines to Set
Questions reps should ask early that expose competitor weaknesses:
- "How important is [feature/capability] to your evaluation?"
- "Have you considered [use case] where [competitor] typically struggles?"
- "What happens when you need [scenario competitor can't handle]?"

### Objection Responses
"We're already using [Competitor]"
→ Response: [Specific talk track]

"[Competitor] is cheaper"
→ Response: [Value-based counter, TCO comparison]

"[Competitor] has [feature we lack]"
→ Response: [Alternative approach or roadmap context]

### Trap Questions to Expect
Questions the competitor will tell the prospect to ask you:
- "[Trap question]" → Response: [Honest, confident answer]

### Win Stories
- [Customer A]: Switched from [Competitor] because [reason]. Result: [metric].
- [Customer B]: Evaluated both, chose us for [reason]. Result: [metric].

### Last Updated: [Date]

Battle Card Best Practices

• Update quarterly or when competitors ship major features
• Source intelligence from: won/lost deal interviews, G2/Gartner reviews, competitor websites, sales call recordings
• Distribute via the tool reps already use (Slack, CRM, Gong, Highspot) — not a dusty Google Drive folder
• Train reps on how to use battle cards — a document they never reference is worthless
• Never bash competitors in writing — focus on your strengths and set landmines through questions

Pitch Decks

Pitch Deck Structure (12-15 slides)

Pitch Deck Principles

• The deck is a conversation guide, not a script — reps should talk through slides, not read them
• One idea per slide — crowded slides kill attention
• Customize slides 2-4 per prospect's industry, size, and stated pain points
• Build modular — create slide appendixes for specific industries, use cases, and objections that reps can insert as needed
• Design for the champion — this deck will be forwarded to stakeholders who weren't in the room. It must stand alone.
• No more than 40 words per slide — if you need more, split the slide

Deck Variations

Create these variants from the master deck:

• Industry-specific — Swap examples, data, and terminology for top 3-5 industries
• Persona-specific — Technical deck (architecture, security, integration) vs. executive deck (ROI, strategic value)
• Short version — 5-6 slides for a 15-minute meeting
• Leave-behind — More detailed version with notes, sent after the meeting

Case Studies

Case Study Template

## [Customer Name]: [Headline Result]

### Company Profile
- Industry: [Industry]
- Size: [Employees / Revenue]
- Use case: [Primary use case]

### The Challenge
[2-3 paragraphs describing the customer's situation before your product]
- What problem were they trying to solve?
- What had they tried before?
- What was the business impact of the problem? (quantify)

### The Solution
[2-3 paragraphs on why they chose you and how they use the product]
- Why did they choose your product over alternatives?
- Which specific features/capabilities address their needs?
- How was implementation/onboarding?

### The Results
[Specific, quantified outcomes]
- Primary metric: [e.g., "40% reduction in customer churn"]
- Secondary metric: [e.g., "Saved 15 hours per week on manual reporting"]
- Tertiary metric: [e.g., "ROI achieved within 3 months"]

### Key Quote
"[Direct quote from customer champion that captures the transformation]"
— [Name], [Title], [Company]

### Why It Matters
[1 paragraph connecting this story to the broader value proposition]

Case Study Best Practices

• Lead with the result in the headline — "How [Company] Increased Revenue 35% with [Product]"
• Always include hard numbers — vague outcomes ("improved efficiency") are worthless
• Build a case study matrix: cover your top 3 industries x top 3 use cases = 9 case studies as a target
• Create multiple formats from one interview: full PDF, one-page summary, slide for pitch deck, quote card for social
• Get customer approval in writing before publishing
• Include a clear CTA at the end — "See how [Product] can deliver similar results for your team"

Case Study Interview Questions

Ask these during the customer interview:

1. What was happening in your business that made you look for a solution?
2. What had you tried before? Why didn't it work?
3. How did you find us? Who else did you evaluate?
4. What made you choose us over alternatives?
5. Walk me through your implementation experience.
6. What specific results have you seen? (push for numbers)
7. What surprised you about using the product?
8. How has your day-to-day changed since adopting [Product]?
9. What would you tell someone considering [Product]?
10. Would you be willing to be quoted by name and title?

ROI Calculators

ROI Calculator Framework

Build a calculator that takes customer inputs and outputs financial justification:

Input Variables:

• Number of [users/customers/transactions] per month
• Average [revenue/cost/time] per [unit]
• Current [conversion rate/efficiency/cost]
• Hours spent on [manual process your product replaces]
• Average hourly cost of employee time

Calculation Engine:

Current Annual Cost = (Hours per week on task) x (Hourly rate) x 52
                    + (Error rate) x (Cost per error) x (Annual volume)
                    + (Opportunity cost of delayed action)

With [Product] = (Reduced hours) x (Hourly rate) x 52
               + (Reduced error rate) x (Cost per error) x (Annual volume)

Annual Savings = Current Annual Cost - With [Product]
Product Annual Cost = [License cost]
Net ROI = ((Annual Savings - Product Cost) / Product Cost) x 100%
Payback Period = Product Cost / (Annual Savings / 12)

Output Display:

• Annual savings (dollar amount)
• ROI percentage
• Payback period in months
• 3-year total value

ROI Calculator Best Practices

• Use conservative assumptions — understated ROI is more credible than overstated
• Allow customers to adjust all assumptions — transparency builds trust
• Pre-fill industry benchmarks as defaults but let them override
• Build in a "your data" vs. "industry average" toggle
• Output a PDF or one-pager that the champion can forward to the CFO
• Include a sensitivity analysis: "Even if results are 50% of average, you still achieve X"

Objection Handling Guide

Top 10 Universal Objections

1. "It's too expensive"

• Reframe from cost to value: "Based on what you've shared, [problem] costs you [X] per year. Our solution pays for itself in [timeframe]."
• Ask: "Too expensive compared to what? The current cost of not solving this?"
• Offer phased implementation or starter package

2. "We're happy with our current solution"

• "That's great — what's working well? And if you could change one thing, what would it be?"
• Share a case study from a customer who switched from the same solution
• Plant seeds for future: "Happy to check back in [timeframe]. What would need to change for this to become a priority?"

3. "We need to think about it"

• "Absolutely. To help you think it through, what are the key factors you're weighing?"
• Identify the real objection (usually budget, internal politics, or competing priorities)
• Offer to provide additional information for their internal discussion

4. "We don't have budget right now"

• "When does your next budget cycle start? Let's plan for that timeline."
• "Is this a priority problem? If so, let's build the business case together for budget approval."
• Offer a pilot or free trial to demonstrate value before budget commitment

5. "I need to get buy-in from [stakeholder]"

• "I'd love to help you make that case. What does [stakeholder] care about most?"
• Provide a champion toolkit: executive summary, ROI one-pager, case study
• Offer to join a meeting with the stakeholder

6. "Your competitor has [feature]"

• "You're right, they do. Can I ask how critical that specific feature is to your use case?"
• Explain your alternative approach if applicable
• Redirect to areas where you're stronger

7. "We can build this in-house"

• "You absolutely could. The question is whether that's the best use of your engineering team's time."
• Calculate TCO of build vs. buy: development time, maintenance, opportunity cost
• Ask about timeline: "How long would internal development take vs. being live next month?"

8. "The timing isn't right"

• "I understand. What's driving the timing concern?"
• "What's the cost of waiting [3/6/12 months] to address this problem?"
• Agree on a specific follow-up date, not a vague "later"

9. "We've been burned by similar tools before"

• "I'm sorry to hear that. What went wrong?"
• Address their specific past pain point directly
• Offer risk-reduction: pilot program, phased rollout, strong SLA

10. "Send me more information"

• This is usually a polite no. Test with: "Happy to. To make sure I send the right materials, what specific questions are you trying to answer?"
• If they can't articulate specific questions, they're not engaged — move to nurture
• If they have specific questions, answer them on the call and send a follow-up summary

Demo Scripts

Demo Structure

Demo Script Template

## Pre-Demo Recap
"Before I show you the product, let me confirm what I heard in our last conversation.
You mentioned that [pain point 1] and [pain point 2] are your biggest challenges.
Is that still accurate? Anything changed since we last spoke?"

## Transition to Demo
"Great. I've tailored this demo around those priorities. I'll show you how
[Product] handles [pain point 1], then [pain point 2], and I'll highlight
a few things I think you'll find interesting based on what you've shared.
Feel free to interrupt me at any point with questions."

## Use Case Flow (repeat for each use case)
"So here's the scenario: [describe their actual workflow or problem].
Watch what happens when I [action in the product]...
[Demonstrate]
Notice how [key benefit]. For your team, this means [specific value to them]."

## Closing
"Based on what you've seen, does this address [pain point 1] and [pain point 2]?
What questions do you have?
[Handle questions]
What would the next step look like on your end? Here's what I'd suggest: [specific next step with timeline]."

Demo Best Practices

• Never demo without discovery — you need to know their pain points first
• Show, don't tour — demonstrate workflows, not features
• Use their language — if they call it "projects," don't call it "campaigns"
• Personalize the demo environment — use their company name, industry-relevant data, realistic scenarios
• Pause after key moments — "Does this resonate with what you're dealing with?"
• Have a backup plan — if the product breaks during demo, have screenshots or a recorded fallback
• Limit to 30 minutes — attention drops sharply after 30 minutes. If you need more time, schedule a second session.

Proposal Templates

Proposal Structure

1. Executive Summary (1 page)
   - Restate their challenge in their own words
   - Your proposed solution in 2-3 sentences
   - Expected outcomes with metrics

2. Understanding Your Needs (1-2 pages)
   - Summarize discovery findings
   - Current state and desired future state
   - Success criteria they've defined

3. Proposed Solution (2-3 pages)
   - How your product addresses each stated need
   - Implementation approach and timeline
   - Team and resources involved

4. Expected Outcomes (1 page)
   - Quantified results based on ROI calculator or case study data
   - Timeline to value
   - Success metrics and measurement approach

5. Investment (1 page)
   - Pricing breakdown
   - Payment terms
   - What's included vs. optional add-ons

6. Why [Your Company] (1 page)
   - Key differentiators (max 3)
   - Relevant case study summary
   - Team and support commitment

7. Next Steps (half page)
   - Clear action items with dates
   - Decision timeline
   - Contact information

Appendix:
   - Detailed case studies
   - Security and compliance documentation
   - Technical specifications

One-Pagers

One-Pager Template

A one-pager is what your champion uses to sell internally. It must stand alone without explanation.

[HEADER]
Company logo + Product name
One-line value proposition

[THE PROBLEM] (2-3 bullet points)
- Current pain point with quantified impact
- Industry trend making this urgent
- Cost of inaction

[THE SOLUTION] (2-3 bullet points)
- How you solve it (not features — outcomes)
- Key capability that differentiates you
- Speed to value

[PROOF] (2-3 data points)
- "40% reduction in [metric]" — Customer A
- "ROI in 90 days" — Customer B
- [Award or analyst recognition]

[LOGOS] (6-10 recognizable customer logos)

[CTA]
"Schedule a demo: [URL]"
Contact: [Name, email, phone]

One-Pager Variants

Create separate one-pagers for:

• Each major product line or use case
• Each target persona (technical vs. business)
• Each key industry vertical
• Partner/channel (co-branded)

Sales Playbooks

Playbook Structure

## [Segment/Motion] Sales Playbook

### Ideal Customer Profile
- Industry: [target industries]
- Company size: [employee count and/or revenue]
- Buyer personas: [titles and roles involved]
- Common pain points: [what triggers purchase consideration]
- Disqualification criteria: [when to walk away]

### Sales Process
Step-by-step with specific actions, talk tracks, and content for each stage.

### Discovery Questions
20-30 questions organized by category:
- Business context
- Current pain
- Impact of the problem
- Decision process
- Budget and timeline

### Qualification Framework
[BANT, MEDDIC, or SPICED — with specific criteria for your product]

### Competitive Landscape
Summary of top 3-5 competitors with key differentiators.

### Pricing and Packaging
How to present pricing, common configurations, discount authority.

### Common Objections
Top 10 objections with approved response frameworks.

### Email Templates
- Cold outreach (3-email sequence)
- Post-discovery follow-up
- Post-demo follow-up
- Proposal follow-up
- Break-up email

### Tools and Resources
Links to all relevant enablement content: battle cards, case studies,
ROI calculator, demo environments, proposal templates.

Playbook Maintenance

• Review and update quarterly
• Incorporate win/loss analysis findings
• Add new competitor intelligence as it emerges
• Solicit feedback from top performers — codify what they do differently
• Track content usage — if nobody uses the playbook, simplify it