LaunchWeek.ai

Back to Day 4: Convert

Sales Enablement Content & Battle Cards: The 1-Pager That Wins Deals (and the One That Loses Them)

Most founders ship a pitch deck and call sales enablement done. The first AE struggles in week 3 because they can't answer "how do we compare to [competitor]?" They make up an answer; lose the deal; founder gets pulled in. The fix is sales enablement content — the artifacts AEs use BEYOND the pitch deck: battle cards (per competitor), objection-handling docs, demo scripts, ROI calculators, one-pagers per persona, recorded demos, customer-quote libraries. Done well, AEs ship faster; founder isn't the bottleneck; deals close on competitive merit. Done badly, AEs improvise; quality varies; deals lost.

A working sales enablement system answers: which artifacts to ship (5-10 essentials), how to maintain (these go stale fast), how to organize (Notion / Confluence / Highspot), how to update (quarterly review + per-deal feedback), how to use battle cards in real calls, and how to measure (which content actually wins deals).

This guide is the playbook for sales enablement artifacts. Companion to Sales Playbook, Sales Onboarding Ramp, Sales Discovery Call Playbook, Sales Demo Calls, Win Loss Analysis, and Competitive Positioning.

What Done Looks Like

By end of this exercise:

  • 5-10 core sales enablement artifacts shipped
  • Battle cards for top 3-5 competitors
  • Per-persona one-pagers (decision-maker / champion / end-user)
  • Objection-handling library
  • Demo recording library
  • ROI calculator (when applicable)
  • Customer-quote / case study library
  • Storage system: Notion / Highspot / sales-team-accessible
  • Quarterly review + update cadence
  • Usage metrics (which content drives deals)

This pairs with Sales Playbook, Sales Onboarding Ramp, Sales Discovery Call Playbook, Sales Demo Calls, Win Loss Analysis, Competitive Positioning, Pitch Deck, Customer Case Studies, Customer References, Annual Contract Negotiation, Pricing Strategy, Pricing Packaging Tier Design, First Sales Hire, Sales Compensation Plans, and Sales-to-CS Handoff.

The Essential 7 Sales Enablement Artifacts

Help me identify must-ship artifacts.

The 7 essentials for B2B SaaS in 2026:

**1. Pitch deck** (already covered in [Pitch Deck](../1-position/pitch-deck.md))
- 12-15 slides
- Used at first / second meeting
- Tells the story; positions the company

**2. Battle cards** (per top competitor)
- 1-page; per competitor
- "When you face [Competitor], here's what to say"
- Strengths / weaknesses / objection responses
- Updated quarterly

**3. Objection-handling library**
- Common objections (price / feature / timing / competitor / etc.)
- Approved response per
- "When they say X, you say Y"

**4. Persona one-pagers**
- Per buyer persona (CTO / VP Sales / CFO / etc.)
- Their priorities; how product fits; their language
- 1 page each

**5. Demo recording library**
- Pre-recorded demos for self-serve
- Different lengths (30-sec / 5-min / 15-min)
- Per use case

**6. ROI calculator** (if you can quantify)
- Spreadsheet / web tool
- Customer inputs their metrics; gets ROI estimate
- Sales sends as follow-up

**7. Customer quote / case study library**
- Indexed by industry / use case / size
- Quotes attributed (when permission granted)
- Case studies (1-pagers)

**Optional 8th-12th** (as you scale):

8. Discovery call playbook (already covered)
9. Demo script per persona
10. Pricing playbook (when to discount; how much)
11. Trial / POC playbook
12. Email sequence library

For my company:
- Top revenue-impact artifacts to ship
- Effort estimates

Output:
1. Priority 1-3
2. Effort budget
3. Owner per

The mistake to avoid: shipping all 12 at once. Scope creep; nothing finished; AEs ignore. Ship 3 priority ones in week 1; iterate; expand.

Battle Cards: The 1-Page Format

Help me write battle cards.

The standard format (1 page; viewable on phone):

[Competitor X] Battle Card

When prospects mention them:

  • Common context: who's already using X; what they're moving from / to
  • Where they win: specific scenarios

Strengths (their):

  • What they're objectively good at (don't mock; acknowledge)
  • 3-5 specifics

Weaknesses (their):

  • Where we win
  • 3-5 specific gaps in their offering
  • Quotes from customers who switched

Our differentiation:

  • 1-2 sentences: how WE'RE different (not better at everything; better at specific things)

Objection scripts (if they say... we say...):

  • "We already use [X]" → "Many of our customers came from [X] because of [specific reason]. The biggest difference is [Y]. Want to see a side-by-side?"
  • "[X] is cheaper" → "Yes. We're priced at [Y] because [value mechanism]. Customers find that for [use case Z], the difference pays back in [time frame]."

Sales talking points:

  • The 3-5 things to emphasize when prospect mentions them
  • The 3-5 things NOT to say (don't trash; respect)

Demo flows:

  • Show [feature A]: where we crush them
  • Show [feature B]: where we differ meaningfully
  • Skip [feature C]: where they're better; don't draw attention

Customer evidence:

  • 1-2 named customers who switched FROM them
  • Quotes: "Why we left [X]"

Recent changes:

  • Their pricing changes
  • Their product changes
  • Their funding / business changes
  • (Updated quarterly)

**The discipline**:

- Honest. Don't trash competitors.
- Specific. "Better UX" is meaningless; "Saves 10 hours/week on [task]" is concrete.
- Updated. Markets shift; cards stale fast.

For my competitors: [top 3-5]

Output:
1. Per-competitor card
2. Update cadence
3. Distribution

The discipline: never trash competitors publicly OR in writing. Battle card stays internal. AE reads; uses key points; never shows to prospect. Trash-talk leaks; damages your reputation.

Objection-Handling Library

Help me build the objection library.

The format:

Objection: "[Common phrase prospect says]"

What's REALLY behind it:

  • The unstated concern / fear
  • Often: risk-aversion; budget; champion-credibility

Approved response:

  • Acknowledge first
  • Reframe / counter
  • Provide evidence

Wrong responses:

  • Things AEs default to that hurt the deal
  • Pressure tactics
  • Unsupported claims

Examples:

  • "It's too expensive"
  • "We need more time to evaluate"
  • "We already have [competitor]"
  • "We don't have budget"
  • "Send me a proposal"
  • "Need to talk to my boss"

**Sample objection scripts**:

Objection: "It's too expensive."

Behind it: usually "I can't justify this internally" / "I'm worried about being on the hook for ROI"

Response (don't lower price first):
"What's behind that? Compared to what?"

Listen. Then:
- If "compared to [competitor]": "Yes. We're priced at [X] because [value mechanism]. For [your use case], customers find the difference pays back in [time]."
- If "compared to budget": "Help me understand your budget cycle. What would make this fit?"
- If "compared to expectations": "What did you expect? Let me explain how we got to this number."

Objection: "Send me a proposal" (without earning it).

Behind it: "I want this off my desk; I'll forward to whoever owns it."

Response:
"Happy to. Before I do — to make sure the proposal lands, can I confirm a few things?
- [Stakeholder list]: who needs to weigh in?
- [Timeline]: when are you trying to make a decision?
- [Budget]: do you have approval? Or do we need to budget-plan first?"

If they answer fully → real proposal.
If vague answers → they're not really evaluating. Disqualify.

For my objections:
- Top 10 heard in last 90 days
- Approved response per

Output:
1. Library structure
2. Top 10 objections
3. Sample responses

The discipline: track objections from real calls. Listen to recordings; note unique objections; add to library. Library grows organically; quality compounds.

Persona One-Pagers

Help me write persona docs.

Per persona, 1 page:

**[Persona Name]: [Title; e.g. "VP of Engineering at Series B SaaS"]**

**Their world**:
- Day-to-day pain points
- Metrics they're measured on
- Reports they look at
- Decisions they own / influence

**What they care about** (top 3):
- 1. [Specific outcome]
- 2. [Specific outcome]
- 3. [Specific outcome]

**Their language**:
- Terms they use
- Acronyms they're fluent in
- Things they avoid (jargon they distrust; feature-spam)

**Where they hang out**:
- Communities (Slack channels; Reddit; LinkedIn groups)
- Content sources (blogs; podcasts; conferences)
- Peer groups

**Common objections**:
- 3-5 specific to this persona

**Pitch frame**:
- How to position the product TO them
- What to emphasize
- What to skip

**Customer quote** (from this persona type):
- Real quote (or composite) showing the value resonates

**Demo flow**:
- Per persona, show different things
- Engineering: technical depth
- Procurement: trust + compliance
- End user: workflow ease

For my personas:
- Top 3 personas in deals
- Per-persona doc

Output:
1. Persona list
2. One-pager per
3. Sales-team usage

The win: per-persona pitch within the same call. Discovery → "ah this is the engineering persona" → AE pivots to engineering-relevant value. Better than generic pitch.

Demo Recording Library

Help me build a demo library.

The categories:

**1. Self-serve demos** (60-180 seconds each):
- "Quick overview" — what is this product
- "Problem we solve" — why exists
- "Top use case" — most common
- For website / email; non-sales-led

**2. Sales-supporting demos** (5-15 min):
- Persona-targeted
- Recorded by founder / SE
- Live / on-demand viewable

**3. Full deep-dive demos** (30-60 min):
- Technical detail
- For evaluation phase
- Often interactive (live shared)

**4. Customer-success demos**:
- For onboarding new customers
- Workflow-focused
- Beyond sales

**Tools**:

- **Loom** — recorder; sharing; standard
- **Vidyard** — sales-flavored
- **Tavus** — AI-driven personalization
- **Storylane / Demostack / Reprise / Saleo** — interactive product tours

**The "share a demo" pattern**:

After discovery call:
- AE sends specific demo (matched to use case)
- "Here's a demo of [X feature] for [Y use case] — relevant to what you mentioned"
- Personalized; not "here's our generic demo"

**Tracking**:

- Loom / Vidyard tracks views
- Sales sees: "they watched 80% of demo X" → engaged
- Or: "they didn't watch" → re-engage

For my library: [stage]

Output:
1. Demo categories
2. Tooling
3. Library structure

The 2026 trend: interactive product demos (Storylane / Demostack / Reprise / Saleo). Prospects click around; explore; engage longer. Replace static screenshots; significantly higher engagement.

ROI Calculator: When and How

Help me decide on ROI calculator.

When ROI calculators work:
- Product has measurable economic outcome
- Buyers want quantitative justification
- ACV justifies the calculator complexity ($10K+ deals)

When they don't:
- Outcome is qualitative (happier users; better UX)
- ACV too small (calculator overhead > deal value)
- Industry doesn't price-justify (consumer / SMB)

**Format**:

Spreadsheet OR web tool with:
- Input: their metrics (team size; current cost; volume)
- Output: estimated savings / value
- Annualized
- 3-year projection

**The honest calibration**:

Don't inflate. ROI calculators that promise 10x value have 0% credibility.

Conservative ROI calculator that delivers in real life > optimistic that doesn't.

**Implementation**:

Simple: Google Sheet template (sales sends; customer fills)
Modern: web tool (Calconic / custom React)
AI: input company info; output personalized ROI

**The sales conversation**:

"Let me show you the math. If you put in your numbers, here's what we're talking about..."

Customer's number → makes it real.

For my product:
- Quantifiable outcome?
- Calculator format

Output:
1. Calculator decision
2. Format
3. Implementation

The honest framing: don't ship ROI calculators if your product's value is qualitative. Forced quantification feels desperate. Some products (developer tools / design tools) win on craft, not ROI math.

Customer Quote and Case Study Library

Help me build the library.

The structure:

**Per customer**:

Customer: [Name] Industry: [SaaS / Healthcare / etc.] Size: [Employees / ARR] Use case: [Specific workflow] Why chose us: [The reason] Quote: "..." Date: 2026-04 Permission status: [public / private / quote-only / case-study] Stakeholders: [contacts]


**Indexable filters**:
- By industry (find a healthcare reference fast)
- By size (mid-market reference for mid-market deal)
- By use case (specific workflow)
- By outcome (saved $X / lifted Y%)

**Tools**:
- Notion / Airtable for indexing
- HubSpot / Salesforce custom fields
- ReferenceEdge / RO Innovation (specialist)

**The reference program**:

Pay-it-forward:
- Customer agrees to be reference
- Gets invited to advisory board
- Speaks at conference / podcast
- Gets early-access features
- Compensated optionally (gift card / event tickets)

**Anti-pattern**:

Asking customer for reference cold the first time you need it. Bad UX.
Better: build relationship; offer first; ask later.

For my customer base: [stage]

Output:
1. Indexing structure
2. Reference program
3. Use in sales process

The discipline: ask permission to use quotes BEFORE customer churns. Quotes from happy-then-churned customers feel hollow. Get permission; use; track expiration.

Storage and Distribution

Help me organize artifacts.

The 2026 stack:

**Notion / Confluence / Slite** (most indie / mid-market):
- Single workspace for sales content
- Searchable
- Free / cheap
- Version history

**Highspot / Seismic / Showpad** (mid-market+):
- Sales-content management
- Engagement analytics (which content viewed / shared)
- Buyer enablement (share with prospect; track)
- $$$$ but ROI for $1M+ ARR

**Specific docs** (e.g. battle cards):
- Notion pages
- Linked from sales-team Slack channel
- Cmd+K accessible

**Org for AEs**:

Sales Wiki/ ├── Onboarding (sales-onboarding-ramp content) ├── Process (sales-playbook) ├── Battle Cards/ │ ├── Competitor A │ ├── Competitor B │ └── ... ├── Personas/ ├── Objections/ ├── Demos/ ├── Case Studies/ └── Templates (emails / proposals)


**Update cadence**:

- Weekly: new wins / quotes added
- Monthly: top 5 objections refreshed
- Quarterly: battle cards reviewed
- Annually: persona docs rewritten

For my team: [stage]

Output:
1. Storage tool
2. Org structure
3. Update cadence

The discipline: central, searchable, AE-accessible. Battle cards in PDF lost in Drive = nobody uses. Battle cards in Notion linked from #sales channel = used in every deal.

Common Sales Enablement Mistakes

Help me avoid mistakes.

The 10 mistakes:

**1. Building 20 artifacts; nobody uses**
Volume over quality.

**2. Stale battle cards**
Competitor changed pricing; card reflects 2024 reality.

**3. Trash-talking competitors**
Battle card leaks; brand damaged.

**4. ROI calculator with wishful inputs**
Inflated; nobody trusts.

**5. Storage scattered**
Drive / Notion / Slack DMs; AEs can't find.

**6. No update cadence**
Content rots; AEs improvise.

**7. Founder writes everything alone**
Can't scale; goes stale.

**8. Generic persona docs**
"VP of Sales" — every company has VP of Sales differently.

**9. No usage tracking**
Don't know what works.

**10. Treating enablement as one-time setup**
It's continuous; not project-with-end.

For my approach: [risks]

Output:
1. Top 3 risks
2. Mitigations
3. Process changes

The discipline: own the enablement function. Hire BDR / RevOps / SE who maintains content; ships updates; trains AEs. Without owner, content rots.

What Done Looks Like

A working sales enablement system:

  • 5-10 core artifacts shipped + maintained
  • Battle cards for top 3-5 competitors (quarterly updated)
  • Objection library with 10-20 common scenarios + scripts
  • Persona one-pagers per ICP
  • Demo recording library (self-serve + sales-supporting)
  • Customer-quote library indexed by industry + use case
  • Storage tool: Notion / Highspot / similar; searchable
  • Owner: BDR / RevOps / SE / founder (clear DRI)
  • Quarterly review with team feedback
  • Usage tracked (which content viewed / shared)

The proof you got it right: a new AE in week 4 can handle a competitive deal without founder involvement; battle card has the right answer; closes the deal.

See Also

← PreviousSales Discovery Call Playbook: The Questions That Decide Whether You Have a Deal Or a Tire-KickerNext →Sales Forecasting & Pipeline Management