Competitive battlecard template
Most battlecards are feature comparison grids written by product marketing, and reps stop using them the first time a buyer points out that a row is wrong. A battlecard that gets used is short, honest about where the competitor is better, and built from what happened in real deals. This template fits on one page and is organized around what a rep needs mid-deal: when we win, when we lose, what to ask, what not to say, and which customer to point to.
- Category:
- Enablement & Process
- Formats:
- PDF + web view
- Sections:
- 6
- Updated:
What you get
- A one-page layout: summary, where we win, where we lose, landmines, traps, and proof
- Worked example rows for a fictional Competitor A
- Landmine questions that raise the buyer's own concerns without attacking the competitor
- A source and freshness checklist so every claim can be traced and dated
Who it's for
- Product marketers building battlecards reps will open
- Enablement teams maintaining competitive content
- AEs who want a one-page answer mid-deal
What's inside
- 1
Summary
6 fields to complete
- 2
Where we win and where we lose
4 columns, 4 worked example rows
- 3
Landmines
3 columns, 3 worked example rows
- 4
Traps to avoid
6-point checklist
- 5
Proof
4 columns, 3 worked example rows
- 6
Why battlecards go unused
Guidance notes
Preview of section 1
Summary
The top of the card. A rep should be able to read this in 30 seconds.
- Competitor
- e.g. Competitor A
- Who they sell to
- e.g. Mid-market teams that want a quick setup and a low entry price
- How they position
- e.g. All-in-one, easy to set up, no admin needed
The preview shows part of section 1. The full template has all 6 sections (5 not previewed here), with blank rows ready to fill in. Download the full template
How to use it
- 1
Start from win-loss data, not product docs
Pull every deal from the last two quarters where this competitor was involved. Read the loss notes and, if you can, interview two lost buyers. Where we lose is the most valuable section and the one most often left vague.
- 2
Be honest about where they are better
Reps who hear 'we are better at everything' stop trusting the card. Name the situations where the competitor usually wins, and tell reps whether to compete or to qualify out.
- 3
Write landmines as questions, not claims
A landmine is a question the rep asks that leads the buyer to discover a weakness themselves, such as 'how will you handle multi-currency quoting?'. Claims about a competitor invite a rebuttal; questions do not.
- 4
Date every claim and name the source
Competitors change pricing and ship features. Every statement on the card carries a source and a date, and anything older than six months is rechecked before it stays.
- 5
Keep it to one page
If it does not fit, cut. Detailed feature comparisons can live in an appendix for SEs.
Frequently asked questions
What should a competitive battlecard include?
A short summary of the competitor, the situations where you usually win and lose, landmine questions to ask the buyer, traps to avoid, and proof such as references and case studies. Each claim should have a source and a date.
How often should battlecards be updated?
Review each card quarterly and whenever the competitor changes pricing, ships a major feature, or your win rate against them moves noticeably. Recheck any claim older than six months.
Who should own battlecards?
Product marketing usually owns them, with input from win-loss interviews, SEs, and top reps. Name one owner per card so updates do not fall between teams.
Related templates
All sales ops templatesWin/Loss analysis template
Pipeline & Forecasting
A win loss analysis template with a buyer interview guide, a coded reason taxonomy, and a sampling rule so patterns hold up. Free PDF and CSV.
Objection handling template
Enablement & Process
An objection handling template: each objection, what sits behind it, a clarifying question, a response that has worked, and proof. Free PDF and CSV.
Sales playbook template
Enablement & Process
A sales playbook template built from plays with a trigger, a target persona, steps, and an exit criterion, so reps can run it. Free PDF and CSV.