7 Battlecard Templates

Fill in the brackets with your real competitor data. Replace placeholders with specifics — vague battlecards don't win deals.

📋 Copy into Notion or Google Docs 🖨️ Print-friendly ✏️ Replace all [ brackets ]

Quick Jump

1 Classic One-Pager 2 Objection Handler 3 Feature Matrix 4 Segment-Specific 5 Quick Reference Card 6 Pricing Battlecard 7 New Competitor Alert
1

⚔️ The Classic One-Pager

All the essentials on a single page — overview, strengths, weaknesses, landmines, and pricing.

Best for: General competitive deals
Overview
2–3 sentence competitor description
Who are they? Who do they serve? What's their key positioning or reputation?
Example: Enterprise-focused platform with strong Salesforce integration. Struggles with mid-market due to long implementation timelines and rigid annual pricing.
Strengths ✓
[ Strength 1 ]
[ Strength 2 ]
[ Strength 3 ]
Weaknesses ✗
[ Weakness 1 ]
[ Weakness 2 ]
[ Weakness 3 ]
💣 Landmine Questions
Question 1 + what it exposes
"[ Discovery question ]" → [ What weakness it surfaces ]
Example: "What's your timeline for going live?" → Exposes their 6-month implementation vs. our 2 weeks
Question 2 + what it exposes
"[ Discovery question ]" → [ What weakness it surfaces ]
Question 3 + what it exposes
"[ Discovery question ]" → [ What weakness it surfaces ]
Quick Talking Points
[ Differentiator 1 — be specific ]
[ Differentiator 2 — be specific ]
[ Differentiator 3 — be specific ]
Pricing Comparison
Line Item[ Competitor ][ Your Company ]
Base price$[ X ]/year$[ X ]/month
Implementation fee$[ X ]Included
Training$[ X ]Included
Contract flexibilityAnnual onlyMonth-to-month
True Year 1 Cost$[ X ]$[ X ]
✅ What makes this work
  • Fits on one page — reps can scan it in 60 seconds
  • Landmines include the "why" so reps understand the strategy, not just the script
  • Specific numbers, not vague claims. "2 weeks vs. 6 months" beats "faster implementation"
2

🛡️ The Objection Handler

Front-loads the most common objections with word-for-word responses and proof points.

Best for: Dominant brand competitors with high objection frequency

Write responses in a natural, conversational tone — not corporate talking points. Reps should be able to read these during a live call and sound confident, not scripted.

Objections & Responses
Objection #1: "[ Write the exact words prospects use ]"
Your response
[ Write a natural, confident reply that acknowledges the concern before countering it ]
📊 Proof point: [ Back this up with data, a G2 quote, or a customer result ]
Objection #2: "[ Write the exact words prospects use ]"
Your response
[ Write a natural, confident reply ]
📊 Proof point: [ Add supporting evidence ]
Objection #3: "[ Write the exact words prospects use ]"
Your response
[ Write a natural, confident reply ]
📊 Proof point: [ Add supporting evidence ]
Objection #4: "[ Write the exact words prospects use ]"
Your response
[ Write a natural, confident reply ]
📊 Proof point: [ Add supporting evidence ]
Objection #5: "[ Write the exact words prospects use ]"
Your response
[ Write a natural, confident reply ]
📊 Proof point: [ Add supporting evidence ]
✅ What makes this work
  • Uses the exact words prospects say — not paraphrases
  • Acknowledge before countering: "That's a fair point — here's how I'd think about it..."
  • One proof point per conversation. Rattling off five feels defensive.
  • Update quarterly — objections evolve as competitors evolve
3

📊 The Feature Matrix

Side-by-side capability comparison across multiple competitors. Visually scannable in seconds.

Best for: Technical evaluations, RFPs, security reviews

Legend: ✓ Fully supported   ✗ Not supported   ⚠️ Partial / extra cost

Security
Capability[ Your Company ][ Rival A ][ Rival B ]
SSO / SAML✓[ ][ ]
SOC 2 Type II✓[ ][ ]
Role-based access control✓[ ][ ]
[ Security feature ][ ][ ][ ]
Integrations
Capability[ Your Company ][ Rival A ][ Rival B ]
REST API✓ Read/Write⚠️ Read only[ ]
Salesforce✓[ ][ ]
Slack✓[ ][ ]
[ Integration ][ ][ ][ ]
Implementation & Admin
Capability[ Your Company ][ Rival A ][ Rival B ]
Avg. time to go live[ X weeks ][ X months ][ X weeks ]
Self-service setup✓[ ][ ]
No professional services required✓✗[ ]
[ Admin feature ][ ][ ][ ]
Support
Capability[ Your Company ][ Rival A ][ Rival B ]
24/7 support✓⚠️ Enterprise only[ ]
Dedicated CSM✓⚠️ Extra cost[ ]
SLA guaranteed✓[ ][ ]
Key Differentiators to Highlight
[ Differentiator 1 and why it matters to the buyer ]
[ Differentiator 2 and why it matters to the buyer ]
[ Differentiator 3 and why it matters to the buyer ]
✅ What makes this work
  • Be honest. If a competitor truly has a feature, mark it ✓. Buyers fact-check — dishonesty destroys credibility.
  • Highlight ⚠️ rows. "Extra cost" or "read-only" is often a meaningful disadvantage buyers miss.
  • Use proactively before technical reviews, not just in response to RFPs.
4

🎯 The Segment-Specific Battlecard

Different sections for different customer sizes or verticals — because you compete differently in each.

Best for: When segment changes the competitive dynamic
Segments

🏢 Enterprise (1,000+ employees)

Why we win here
[ Advantage 1 ]
[ Advantage 2 ]
[ Advantage 3 ]
Why they win here
[ Their advantage 1 ]
[ Their advantage 2 ]
Win rate
[ X% ]
Avg. deal size
$[ X ]K
Top landmine question
"[ Question ]"

🏪 Mid-Market (100–999 employees)

Why we win here
[ Advantage 1 ]
[ Advantage 2 ]
[ Advantage 3 ]
Why they win here
[ Their advantage 1 ]
[ Their advantage 2 ]
Win rate
[ X% ]
Avg. deal size
$[ X ]K
Top landmine question
"[ Question ]"

🛒 SMB (1–99 employees)

Why we win here
[ Advantage 1 ]
[ Advantage 2 ]
[ Advantage 3 ]
Win rate
[ X% ]
Avg. deal size
$[ X ]K
Top landmine question
"[ Question ]"
✅ What makes this work
  • Win rate per segment = confidence calibration. 89% in SMB means push hard; 40% in Enterprise means qualify carefully.
  • Honest about where you lose — helps reps disqualify bad fits before wasting cycles
  • Different landmine questions for different contexts — an SMB founder cares about different things than a CIO
5

⚡ The Quick Reference Card

30-second read. One question, one response, three proof points. Designed for mobile.

Best for: Glancing at right before jumping on a call
The Card
⚡ Quick Ref: [ Competitor ] — Win Rate: [ X% ]
They're known for
[ 1–2 words: e.g., Enterprise, Salesforce, brand ]
They struggle with
[ 1–2 words: e.g., Speed, pricing, mid-market ]
💣 Ask this
"[ Your best landmine question ]"
💬 Say this
"[ Your single best differentiator — with numbers ]"
💰 If they raise price
"[ One-liner pricing response ]"
Supporting Detail
Proof point 1
[ Specific customer result or stat ]
Proof point 2
[ G2 data or review insight ]
Proof point 3
[ Win rate or competitive stat ]
🚩 Walk away if you see...
[ Red flag 1 ]
[ Red flag 2 ]
[ Red flag 3 ]
✅ What makes this work
  • If it takes more than 30 seconds to read, trim it — this card exists for speed
  • One ask, one response. Reps need a default move, not a menu.
  • Win rate provides instant confidence calibration before the call starts
6

💰 The Pricing Battlecard

Breaks down true cost vs. quoted price. Reframes "cheaper competitor" objections with data.

Best for: Price-sensitive deals, competitors with hidden costs
Their Pricing (What They Quote)
Line ItemCost
Base license$[ X ]/year
Implementation$[ X ]
Training$[ X ]
Premium support$[ X ]/year
Required add-ons$[ X ]
True Year 1 Cost$[ X ]
Our Pricing
Line ItemCost
Base plan$[ X ]/month
ImplementationIncluded
TrainingIncluded
SupportIncluded
Required add-onsNone
True Year 1 Cost$[ X ]
When They Say "[ Competitor ] is Cheaper"
Script — write in natural, conversational language
[ Your response ]
Example: "What's the quote you're seeing? Often their base price doesn't include implementation, training, or support — which adds $25–30K. Let me show you a true apples-to-apples comparison."
ROI Talking Points
[ Faster X ] = [ Business outcome in real terms ]
[ Feature ] = [ Time/cost savings for the buyer ]
[ Included thing ] = [ What they'd pay extra for elsewhere ]
3-Year Total Cost of Ownership (optional)
Year 1Year 2Year 33-Year Total
[ Competitor ]$[ X ]$[ X ]$[ X ]$[ X ]
[ Your Company ]$[ X ]$[ X ]$[ X ]$[ X ]
Savings$[ X ]$[ X ]$[ X ]$[ X ]
✅ What makes this work
  • Never lead with price — establish value first, then use this card when it comes up
  • Always ask to see their quote. You can't compare without specifics.
  • The 3-year view matters: Year 1 savings feel small; a 3-year comparison feels significant
  • Source your data. "Based on their public pricing page" is more credible than just asserting a number
7

🆕 The New Competitor Alert

For emerging threats you're still gathering intel on. Honest about gaps while giving reps enough to respond.

Best for: Emerging competitors with limited data
⚠️ Status: EARLY WATCH
What We Know
Founded
[ Year ]
Funding
$[ X ]M [ Series X ]
Team size
~[ X ] employees
Who they target
[ Segment / persona ]
Apparent strength
[ e.g., Strong UX, aggressive pricing ]
Apparent weakness
[ e.g., No enterprise security features yet ]
Pricing (estimated)
[ What we know, or "Unknown — report back" ]
Notable customers
[ Customer names if any ]
What We Don't Know Yet
☐ Full pricing structure
☐ Implementation timeline
☐ Customer support quality
☐ Security certifications
☐ [ Add more gaps ]
Initial Positioning for Reps
How to respond when they come up in a deal
[ Write guidance — natural tone, acknowledge them without badmouthing ]
Example: "They're new and likely nimble on price. Focus on your proven track record, integrations, and enterprise-readiness. Acknowledge they're innovative but unproven at scale."
Key angles to emphasize
[ Your track record vs. their early stage ]
[ Your customer references vs. their limited base ]
[ Your certifications vs. their gaps ]
📩 If You Encounter Them — Report Back!
We need intel from the field. Report anything you learn:

• What did they quote?
• What features did they highlight?
• What were the prospect's concerns?
• Did you win or lose? Why?

📬 [ Slack channel or email link ]
✅ What makes this work
  • Acknowledging gaps builds rep trust — don't fake confidence you don't have
  • Gives reps enough to respond without overpromising or badmouthing
  • The feedback loop is the most important part — field intel turns a "watch" into a full battlecard