Sales Enablement Content

Create battle cards, one-pagers, ROI calculators, demo scripts, objection handling guides, case study briefs, proposal templates, sales playbooks, and buyer persona cards that sales reps actually use in live deals.

Pre-Work Framework

Before creating or updating sales collateral, gather the following context to ensure the output is battle-tested and rep-ready:

1. What type of collateral are you creating? Battle card (competitive positioning), one-pager (solution overview), ROI calculator (financial justification), demo script (feature walkthrough), objection handler (pre-written responses), case study brief (customer story for social proof), proposal template (deal-specific doc structure), sales playbook (multi-motion framework), or buyer persona card (stakeholder profile). Each type has different content density, structure, and use cases. Clarifying the collateral type prevents building a battle card that reads like a marketing brochure.

2. Who is the target buyer persona? Is this for a CFO, VP of Sales, CTO, Head of RevOps, or an individual contributor? What are their title, department, seniority, and primary concerns? A CFO cares about ROI and headcount savings. A CTO cares about security, integrations, and infrastructure impact. A VP of Sales cares about rep adoption and quota coverage. A single persona per document prevents document drift and ensures reps know exactly when to deploy each piece.

3. What deal stage or sales motion is this supporting? Discovery (understanding prospect needs), early-stage demo (building credibility), deep-dive (technical proof), negotiation (overcoming price objections), or closing (removing final obstacles). Each stage requires different collateral—discovery reps need persona cards and open-ended question guides, while closing reps need case studies and ROI calculators. Misalignment here produces collateral that looks professional but sits unused because it does not match how reps actually sell.

4. What is your sales motion type? Land-and-expand (selling into existing customers), enterprise (complex, multi-stakeholder, longer sales cycle), mid-market (speed and champion-building), or SMB (self-service to transaction). Enterprise playbooks require stakeholder mapping and approval processes. SMB playbooks need brevity and quick decision frameworks. Enterprise and SMB collateral are fundamentally different despite selling the same product.

5. What existing materials, wins, and competitive context should inform this? Do you have successful one-pagers from past wins that you can reference? Have you documented common objections your team has overcome? Do you have case studies with quantified business impact? Do you have a competitive positioning framework? Are there specific competitor attack points your team mentions repeatedly? Reusing proven language and examples accelerates creation and ensures continuity.

Core Principles

Sales Uses What Sales Trusts

Reps will not deploy collateral they do not believe in. If a battle card contains marketing claims that reps do not see validated in customer interactions, they will set it aside. If a case study lacks credibility—either because it is not from a comparable customer or because the results feel unattainable—reps will not lead with it. Before publishing any collateral, validate it with your top 3 reps and ask them: "Would you give this to a prospect right now, as-is, without editing?" If the answer is "not quite," identify what is missing or misaligned. Trust-building requires reps to see themselves and their wins reflected in the material.

Situation-Specific Not Generic

Generic collateral ("Our platform helps teams sell faster") deploys in no situation because it applies equally to every situation. Situation-specific collateral addresses a particular buyer, deal stage, objection, or pain point. A battle card should say: "When you're competing against Gong and the prospect asks why they should switch, reference these three differentiators and use this case study." A one-pager should target the CFO's ROI concerns, not the CTO's security concerns—those are two different documents. Situation specificity means reps can hand the document directly to a prospect without editing it, knowing it speaks directly to their situation.

Scannable Over Comprehensive

Reps do not read 10-page documents on a Zoom call. In a live meeting, they scan for the headline, one-sentence proof point, and a specific number. One-pagers should be literally one page, structured with clear headings, short paragraphs, bullet points, and visual anchors so a rep can point to a key idea in under 10 seconds. Case study briefs should start with the headline and the result (before/after), then provide 2–3 supporting details, not a full narrative. Battle cards should use a table format with columns for "Competitor Claim," "Why It Matters," "Our Position," and "Proof" so reps can skim and find the relevant comparison in seconds. Comprehensive is for documentation. Scannable is for selling.

Tie Back to Business Outcomes

Features do not close deals. Business outcomes close deals. A buyer does not care that your solution has "real-time coaching dashboards." They care that real-time coaching reduces rep ramp time from 6 months to 3 months, which frees up $400K in quota capacity earlier. Tie every feature, capability, and competitive claim back to a business outcome using this structure: "[Feature/Capability] enables [business outcome] which means [financial or operational impact]." Do not assume reps will make this connection. Make it explicit. When your collateral includes quantified outcomes (20% faster deal closure, $X reduction in quota risk, Y hours saved per rep per week), reps use it more often because they have a narrative beyond features.

Rep Language Not Marketing Language

Marketing says: "Our AI-powered platform leverages advanced NLP and machine learning to provide strategic insights." Reps say: "You talk to the prospect, we write the email. Takes 10 seconds." Do not mix them. Collateral written in marketing language sounds inauthentic when a rep reads it aloud. It creates friction between the way reps naturally sell and the words they are asked to speak. Use active voice, simple sentence structure, and the language your top-performing reps actually use when closing deals. If your reps say "it's a 3-person month to get set up," do not round it to "streamlined 90-day implementation." Use rep language throughout—it builds credibility and ensures reps will actually deploy the collateral.

The Process

Phase 1: Collateral Discovery and Need Validation (15 minutes)

Before drafting, clarify exactly what problem the collateral will solve. Schedule a brief call or send a Slack message to 2–3 target reps with these questions: "When do you encounter [buyer objection/deal stage]? What collateral do you currently use? What is missing from what you have?" Listen for gaps and pain points. Document the specific situation where the collateral will deploy (e.g., "15 minutes into a discovery call, after the prospect has mentioned cost concerns, Sarah hands them this ROI calculator"). Understanding the deployment moment prevents creating collateral that looks right but is never used.

Exit criteria: You have identified 2–3 specific moments where reps will deploy this collateral and you have one or two quotes from reps about what they need.

Phase 2: Research and Competitive Context Gathering (20 minutes)

Gather proof points, case studies, competitive positioning, and customer outcomes that will populate the collateral. Pull from your CRM, success stories, sales cycles that closed, and wins against competitors. Document: customer names and titles, quantified results (% improvement, dollar amount, time reduction), competitive battleground situations, customer quotes about the outcome, and any objections this collateral will overcome. If you are building an ROI calculator, document 3–5 real customer ROI outcomes. If you are building a battle card, pull the most common competitive attacks your team has encountered. If you are building a case study brief, find a win that mirrors the target buyer's situation (same industry, company size, and challenge).

Exit criteria: You have a document with 5–10 proof points, 2–3 real customer outcomes, and 1–2 customer quotes ready to incorporate.

Phase 3: Draft Creation with Rep Input (30 minutes)

Use the collateral type template (see Output Format section) to structure your initial draft. Write it from the rep's perspective: "What would I say to this buyer, and what would I show them?" Start with the headline (the single most important idea), then fill in supporting details, proof points, and next steps. Do not overthink; draft fast and messy. The goal is to get the structure and core ideas out, knowing it will be refined in the next phase.

Exit criteria: You have a complete first draft in the correct format for the collateral type.

Phase 4: Rep Validation and Iteration (20 minutes)

Share the draft with 2–3 target reps. Ask them: (1) "Would you give this to a prospect today?" (2) "What is missing?" (3) "What would you change?" Listen for specific feedback. If a rep says "I would never say it like that," ask what they would say instead and incorporate their language. If a rep says "We need a number here," identify which number and add it. Do not defend the draft; treat feedback as gold. Iterate based on 2–3 specific rep comments. Most collateral improves dramatically after one round of rep input because you catch language misalignment, missing proof points, and structural issues that slow down deployment.

Exit criteria: You have incorporated feedback from 2+ reps and have a draft that at least one rep says "I would use this."

Phase 5: Final Review and CRM Integration (10 minutes)

Do a final check: (1) Is the collateral scannable in under 10 seconds? (2) Does every claim have a proof point? (3) Is the language rep-authentic? (4) Does it tie features back to business outcomes? (5) Does it have a clear next step or call-to-action? Add the collateral to your sales enablement system, CRM, or shared drive in a place where reps know to look. Create a Slack or email notification to reps that this collateral is available and when to deploy it. Consider assigning ownership to one rep per collateral type so that reps know who to contact with questions or updates.

Exit criteria: The collateral is in a shared system, reps have been notified, and ownership is assigned.

Anti-Patterns

The Marketing Brochure

Description: Creating collateral that reads like a feature list or marketing pitch rather than a sales tool. Heavy brand colors, glossy language, and value statements that sound like ad copy instead of rep-authentic guidance.

Why it's harmful: Reps will not hand a marketing brochure to a prospect in a discovery call. It signals sales, not partnership. It kills the conversational flow because the rep is pointing to a polished document instead of having a conversation. Prospects perceive marketing collateral as non-credible. Reps feel like they are not allowed to customize or simplify the language, so they avoid using it. Collateral that looks too much like marketing is collateral that does not get used.

What to do instead: Focus on formatting for salesability, not visual appeal. Use simple tables, bullet points, and clear section headings. Avoid brand color overuse. Write as if you are the rep explaining this to a peer over coffee, not a marketer pitching a prospect. Use numbers, customer names, and specific outcomes. Let a top rep read the draft aloud—if they sound uncomfortable saying it, rewrite it.

The Kitchen Sink

Description: Trying to address every possible buyer concern, objection, or use case in a single document. The collateral becomes 15 pages long, covering product features, competitive positioning, ROI, use cases, and implementation roadmap all at once.

Why it's harmful: Long collateral is not deployed because reps do not have time to search through 15 pages in a live meeting. Buyers are overwhelmed by breadth instead of focused on depth. The collateral tries to prove everything and proves nothing because there is no narrative thread. Reps report using "the ROI section on page 8" or "the competitive comparison on page 12," suggesting the document should have been split into separate, targeted pieces.

What to do instead: Create one collateral type, one buyer persona, one deal stage per document. A one-pager is one page. A battle card addresses one competitor. An ROI calculator focuses on one financial metric (cost savings, quota capacity, or revenue impact—pick one). An objection handler covers one category of objections (price, timing, need, authority, competition). Narrow focus produces tighter, more deployable collateral. If you have multiple use cases, create multiple, targeted documents.

The Stale Battlecard

Description: Creating a competitive battle card against a competitor and then not updating it when the competitor releases new features, changes positioning, or the market evolves. Reps pull out a card from 6 months ago that no longer reflects competitive reality.

Why it's harmful: Credibility dies when a rep hands a prospect a battle card claiming "Our competitor lacks X capability" and the prospect says "Actually, they released that last month." Reps lose trust in the collateral. They go back to riffing on competitive claims from memory instead of using the documented framework. Stale collateral is worse than no collateral because it actively undermines rep credibility.

What to do instead: Assign ownership of each competitive battle card to a specific person (usually the product marketer or a senior AE). Set a quarterly review cadence. Assign a Slack reminder for every battle card to ask "Is this still accurate?" every 90 days. Update based on competitive releases, pricing changes, or positioning shifts. Version control your collateral (v1.0, v2.0) so reps know what they are using. If you do not have the bandwidth to maintain collateral, do not publish it.

The Solo Author

Description: One person (usually marketing or an enablement manager) creates all collateral without involving sales input. The documents are professionally written but disconnected from how reps actually sell.

Why it's harmful: Collateral created in isolation misses critical sales context. It does not reflect the language reps use, the objections they actually encounter, or the proof points they trust. Reps feel unheard and do not adopt collateral they did not help create. The collateral sits in a folder unused. Energy spent on creation is wasted because deployment is weak. Sales feels like sales is being sold to, not partnered with.

What to do instead: Involve reps at every stage—discovery, draft review, iteration, and updates. Give reps co-ownership of collateral types. When reps write portions of the collateral (e.g., "Sales Tip: What I always lead with when a prospect says..."), the document becomes theirs and they deploy it. Make rep feedback mandatory before any collateral goes live. Celebrate reps whose collateral drives closes by sharing metrics in a team meeting.

The Aspirational Case Study

Description: Using a customer case study that is technically a win but does not mirror the target buyer's situation. The customer is a much larger enterprise, from a different industry, with a different problem, or achieved results that feel unattainable for the target prospect.

Why it's harmful: Prospects see the case study and think, "That's a Fortune 500 company—we're mid-market. Those numbers are not realistic for us." The case study loses impact because the prospect cannot see themselves in it. Reps sense this friction and do not lead with aspirational case studies. The most credible case studies are from customers who match the target prospect's profile: same industry or use case, similar company size, and outcomes that feel achievable.

What to do instead: Match case studies to buyer personas. If you are selling to mid-market SaaS companies, use case studies from mid-market SaaS companies, not enterprise. If you are selling to financial services, use fintech or banking customers, not generalist case studies. If the outcome was a 50% improvement, say so, not "dramatic results"—transparency builds trust. If you have limited case studies that match your target market, create brief customer stories from wins that do match and prioritize those over enterprise marquee names.

Output Format

After completing the collateral creation process, outputs are structured as follows by type:

Battle Card

• Format: Table with 4 columns (Competitor Claim | Why It Matters to the Buyer | Our Position | Proof Point / Resource)
• Length: 1 page maximum
• Components: Header with competitor name, 3–5 key competitive comparison rows, one customer quote differentiating you from the competitor, a final row with "Next Step: Lead with [Your Differentiator], then ask [open question]"
• Tone: Direct, confident, fact-based
• Example header: "Competing Against Gong? Here's What You Need to Know"

One-Pager

• Format: Single page, structured with headline, problem statement, solution overview, key features tied to outcomes, customer proof (name + metric), and call-to-action
• Components: Headline (5 words max), problem/opportunity statement (2 sentences), solution summary (1 sentence), 3–4 key differentiators each tied to a business outcome, one customer quote or metric, clear next step ("Suggested Ask: Explore a 30-day pilot...")
• Tone: Conversational, benefit-focused, outcome-oriented
• Visual structure: Use clear sections, bolded headers, bullet points, and white space so it scans in 10 seconds

ROI Calculator

• Format: Table or template with input fields for company size, current state metric, improvement %, and calculated financial outcome
• Components: Assumptions (clearly stated), input variables (company size, headcount, current cost or time), calculation logic, output (annual savings, quota capacity unlocked, or revenue impact), sensitivity analysis (what if the improvement is 20% instead of 30%?), real customer example
• Tone: Data-driven, transparent about assumptions, humble about variability
• Example structure: "Enter your number of reps → Enter current deal cycle length → We calculate: X hours saved per rep per year = $Y annual capacity"

Demo Script

• Format: Screen-by-screen or topic-by-topic script with persona-specific talking points, anticipated questions, and timing
• Components: Opening hook (30 seconds, why this demo matters), 3–5 demo sections (each 4–6 minutes), section headers, exact talking points for each screen, 2–3 anticipated questions per section with prepared responses, closing ask, total timing
• Tone: Conversational, confidence-building, clear
• Example structure:
  • Section 1: "The Problem (Why You Called)"
  • Talking points (3–4 bullet points of what to say)
  • What to show (which screens)
  • Likely question: [Q] → [A]
  • Time: 4 minutes

Objection Handler Guide

• Format: Objection category, real examples, reframe-proof-bridge response structure, alternative approaches
• Components: Objection category (e.g., "Price/Budget"), 2–3 real example objections reps have encountered, acknowledgment statement (validates the concern), reframe (why the concern might be shifted), proof (customer example or data), bridge (transition back to value), alternative response if the first does not land
• Tone: Empathetic, confident, conversational
• Example structure:
  • Objection: "That's more than we budgeted"
  • Acknowledgment: "I hear you—budget constraints are real"
  • Reframe: "Most teams we talk to realize the cost per rep per month is the right metric"
  • Proof: "A VP of Sales at [Customer] had the same concern initially; they calculated that each rep's 2 hours saved per week paid for the tool in the first month"
  • Bridge: "Can we explore what an investment at scale looks like for your team?"

Case Study Brief

• Format: 1–2 pages with headline, customer snapshot, challenge, solution, results, quote, and next step
• Components: Customer name and logo, customer snapshot (company size, industry, role of buyer), challenge statement (the specific problem they faced), solution (what they did with your product), quantified results (% improvement, $ saved, time reduction, quota impact), one customer quote, hiring/growth indicator post-solution, suggested use case ("Use this when competing for a Head of RevOps in a growth-stage SaaS company")
• Tone: Credible, specific, outcome-focused
• Example structure:
  • Header: "How [Customer] Reduced Sales Cycle by 3 Weeks"
  • Customer snapshot: Company, size, buyer role
  • The challenge: 2–3 sentences describing their situation
  • The solution: How they used your product
  • The results: Quantified metrics (e.g., "3-week cycle reduction, 15% quota acceleration")
  • Quote: From the customer
  • Suggested deployment: "Lead with this when a prospect says 'We need to move faster'"

Proposal Template

• Format: Structured sections with headers, callout boxes for key terms and pricing, clear next-step language, version control
• Components: Executive summary (1-paragraph overview of the deal), scope of work (what is included), pricing and terms (transparent), timeline and implementation, success metrics and measurement, approver signature block, version number and date
• Tone: Professional, clear, deal-advancing (removes obstacles, does not create new ones)
• Example structure:
  • Executive Summary
  • Scope of Work
  • Investment & Terms (clearly highlighted)
  • Implementation Timeline
  • Success Metrics
  • Next Steps: "Upon your approval, we will..."

Sales Playbook

• Format: Multi-motion framework with sections for each motion (land, expand, enterprise pipeline, negotiation), entry/exit criteria, reps roles, key collateral to deploy
• Components: Playbook title and motion, motion description (what situations trigger this motion), entry criteria (when you know this motion applies), rep roles (who leads, who supports), key activities (discovery, meetings, communication cadence), common objections and responses, exit criteria and success metrics, resources and collateral
• Tone: Instructional, clear decision trees, prescriptive
• Example structure:
  • Motion: "Expand into Financial Services Vertical"
  • Entry: When we identify a prospect in banking or fintech
  • Key Activities: Industry research, peer benchmarking, regulatory considerations discussion
  • Common Objections: Compliance, integration complexity
  • Exit: Booking a proof-of-concept or pilot

Buyer Persona Card

• Format: Single-page persona profile with title, reporting structure, priorities, pain points, and conversation starters
• Components: Persona name and title, company context (size, industry), 3–5 top priorities (what success looks like for them), 2–3 pain points they likely face, budget authority (do they control it?), timeline (when do they make decisions?), 2–3 conversation starter questions, objections this persona typically raises, recommended collateral to use
• Tone: Directive, rep-ready, specific
• Example structure:
  • Persona: "Enterprise CRO"
  • Reports to: CEO
  • Priorities: Revenue growth, sales team productivity, quota attainment
  • Pain points: Legacy processes slow down large deals; team ramp time is long
  • Conversation starter: "I noticed you're hiring 5 new AEs this quarter—how are you planning to get them productive?"
  • Recommended collateral: ROI calculator (capacity unlocked), case study (large enterprise)

Task-Specific Questions

When Creating New Sales Collateral

• What specific moment will a rep use this collateral? (e.g., "15 minutes into a demo, when the prospect asks about pricing")
• Who is the target buyer persona, and what are their top 2 priorities?
• What is the one thing this collateral needs to accomplish? (If you cannot name it in one sentence, it is too broad.)
• Do we have 3–5 real customer or competitive examples we can reference?
• Have we validated this collateral idea with 2+ reps, or are we building on assumption?
• Will this collateral be scannable in under 10 seconds during a live call?

When Updating Existing Collateral

• What specific feedback prompted this update? (Do not update without feedback.)
• Have we checked whether our competitive positioning or customer wins have changed since the last version?
• Are we updating the content, the format, or both?
• Will the updated version deploy immediately, or do reps need to be trained on new language?
• Should we sunset the old version, or maintain both?

When Reviewing Collateral for Quality

• Can a rep hand this to a prospect right now, as-is, without editing it?
• Does every claim have a proof point or example backing it?
• Does this collateral tie features back to business outcomes, or does it stop at features?
• Is the language authentic to how our reps actually talk, or does it sound like marketing?
• Will reps know when to deploy this, or is the use case unclear?
• Is there any information in here that is more than 6 months old (competitive positioning, case study results, customer names)?

Quality Checklist

Before publishing any collateral, verify the following:

1. Buyer clarity: The target buyer persona is crystal clear. The collateral could not apply equally to a CFO and a VP of Sales. If it could, it is too generic.

2. Deployment moment: The specific sales moment when a rep will deploy this collateral is documented. Reps know: "Use this when..." or "Hand this to the prospect when..."

3. Proof points: Every claim or positioning statement is backed by a customer example, case study, competitive data, or internal sales result. No unsupported assertions.

4. Scannability: The collateral can be scanned and understood in under 10 seconds. Headings are clear, paragraphs are short (2–3 sentences max), and visual hierarchy guides the eye.

5. Business outcome language: The collateral ties features to outcomes. It does not stop at "We have real-time coaching"—it says "Real-time coaching reduces rep ramp time from 6 to 3 months."

6. Rep authentication: At least one rep has reviewed the draft and said "I would use this." If no rep has said that, it is not ready.

7. Version control: The collateral has a version number and date. Reps know whether they are looking at the latest version.

8. Competitive freshness: If this collateral includes competitive positioning, the competitive intelligence is current (less than 90 days old). If older, it is flagged for review.

9. Grammar and clarity: No typos, broken links, or unclear passages. Proofread with fresh eyes before sharing.

10. Next step clarity: The collateral ends with a clear next step or call-to-action. Reps know what comes after the prospect engages with this material.

Related Skills

• Competitive Intelligence — Research and competitive positioning frameworks to inform battle cards, positioning talks, and win/loss analysis.
• Demo Scripting — Persona-tailored demo scripts with opening hooks, feature sequences, and competitive differentiation integrated naturally into the flow.
• Objection Handling — Real-time strategies for the five most common objections (price, timing, authority, need, competition) with branching response trees.
• Pricing Negotiation — ROI justification frameworks, value-based pricing language, and negotiation playbooks for closing deals at higher price points.

Example Prompts

• "Create a battle card for competing against Gong. Include our top 3 differentiators, a case study comparison, and the exact question to ask after showing the card."
• "Build a one-pager targeting CFOs who are concerned about ROI. Include the top 3 business outcomes, quantified results from 2 customer wins, and a clear next step."
• "Generate a ROI calculator template for a mid-market SaaS buyer. Show cost savings per rep, quota capacity unlocked, and total annual impact."
• "Create an objection handler for 'Your solution is too complex to implement.' Include acknowledgment, reframe, proof point, and a bridge back to value."
• "Build a case study brief from [Customer Case]. Focus on their challenge, solution, quantified results, and when a rep should deploy it."
• "Develop a buyer persona card for an Enterprise CRO. Include priorities, pain points, typical objections, and recommended collateral to use in conversations."
• "Create a sales playbook for our land-and-expand motion. Include entry criteria, key activities, common objections, and success metrics."
• "Generate a proposal template for enterprise deals. Include scope of work, investment terms, implementation timeline, and success metrics."