What is a sales battlecard template?
A sales battlecard is a short, internal reference card that helps a seller handle one competitor in a live deal. The template is the fixed structure every card follows, so a rep who has used one card can find the same answer in the same place on every other card. Product marketing usually owns the content, sales enablement owns distribution and training, and the best-performing reps validate the talk tracks.
A battlecard is not a competitive analysis. A competitive analysis is long, strategic and written for leadership. A battlecard is written for a seller who has thirty seconds before a call, or who just heard a competitor named in discovery. If it cannot be scanned in that time, it will not be used.
The gap a battlecard closes is applying messaging in the moment. In Highspot's 2026 GTM Performance Gap survey of 450 go-to-market leaders, 36% said sellers struggle to apply messaging live (Highspot, page updated 2026-08-19). That figure is Highspot's survey result, not Revspire data, but it describes the problem a well-built card is meant to solve.
When should you use a battlecard?
- A named competitor appears in an open opportunity, or the buyer mentions they are "also looking at" someone.
- You are preparing a discovery or demo call where you know the incumbent tool.
- A new rep, partner or channel team is ramping and needs approved competitive answers fast.
- A competitor launches a product, changes pricing or packaging, or is acquired.
- Win/loss reviews show you keep losing to the same rival for the same reason.
Which type of battlecard do you need?
Most teams start with one competitor battlecard per top rival, then add lighter cards for specific moments. The template on this page is the full competitor card; the other types reuse a subset of its sections.
| Card type | Use it when | Sections to keep from the template |
|---|---|---|
| Competitor battlecard | A rival is actively in the deal | All sections |
| Quick-dismiss card | A competitor is mentioned in passing and you want to move on | Snapshot, quick dismiss, one proof point |
| Objection card | One objection keeps recurring across competitors ("too expensive", "we will build it") | Objection handling, proof assets |
| Pricing and packaging card | Deals stall at commercial stage against a cheaper rival | Pricing and packaging, discount guardrails, objection handling |
| Persona card | Different buyers (CFO, IT, end users) need different reasons to choose you | Why we win, talk tracks, landmine questions per persona |
| Partner or channel card | Resellers sell against the same rivals without your team on the call | Snapshot, why we win, quick dismiss, escalation contact |
The sales battlecard template
Copy this structure into your own tool, or download it. Keep every section to short bullets; the whole card should fit on one screen. Fields in brackets are prompts to replace.
1. Header
| Field | What to write |
|---|---|
| Competitor | [Competitor name and the product line you meet most often] |
| Card owner | [Name or team responsible for keeping this card accurate] |
| Last reviewed / next review | [Date reviewed] / [date the next review is due] |
| Sources | [Win/loss notes, call recordings, the competitor's public pages, review sites; note the date of each] |
| Audience | Internal only. Do not forward to buyers. |
2. Snapshot
| Field | What to write |
|---|---|
| Who they are | [One sentence: what they sell and to whom] |
| How they position themselves | [Their main claim, paraphrased from their own site] |
| Where we meet them | [Segment, deal size, use case or stage where they usually appear] |
| Their typical buyer | [The role that usually champions them] |
3. Why we win (top three)
| Differentiator | Proof | Talk track (one sentence a rep can say) |
|---|---|---|
| [Differentiator 1] | [Customer-approved story, demo moment or third-party source] | [Talk track] |
| [Differentiator 2] | [Proof] | [Talk track] |
| [Differentiator 3] | [Proof] | [Talk track] |
4. Where they are strong (be honest)
| Their strength | How we respond |
|---|---|
| [A real strength buyers mention] | [Acknowledge, then reframe to what matters for this buyer] |
| [Strength 2] | [Response] |
5. Landmine questions
| Question to ask the buyer | What it surfaces |
|---|---|
| [Open question that exposes a gap in their approach] | [Why the answer helps you] |
| [Question 2] | [What it surfaces] |
| [Question 3] | [What it surfaces] |
6. Objection handling
| Objection they plant | Our response | Proof asset to share |
|---|---|---|
| "[They are cheaper]" | [Response] | [Link] |
| "[We already use them]" | [Response] | [Link] |
| "[They have feature X]" | [Response] | [Link] |
7. Pricing and packaging
| Field | What to write |
|---|---|
| Their pricing model | [Only what they publish, with the source link and date; "not published" if it is not] |
| Our packaging response | [How to frame your packaging against theirs] |
| Discount guardrails | [What a rep can offer, and who approves anything beyond it] |
8. Quick dismiss, proof and walk-away
| Field | What to write |
|---|---|
| Quick dismiss | [One or two sentences to use when they are mentioned in passing] |
| Proof assets | [Case studies, comparison pages, reviews, demo clips; links only] |
| When they are the better fit | [The deal profile where you should qualify out honestly] |
| Escalation contact | [Who to ask in a live deal: PMM, SE lead or competitive Slack channel] |
Prefer a file? Both downloads are free and ungated.
Sales battlecard example
Example: fictional company
Below is the same template filled in for an invented software company competing against an invented rival, so you can see the level of detail that works.
Ferncastle Analytics sells revenue-forecasting software to mid-market sales teams. Its most frequent competitor is Harborview Metrics.
Header and snapshot
| Field | Example entry |
|---|---|
| Competitor | Harborview Metrics (forecasting add-on for its BI suite) |
| Card owner | Ferncastle product marketing; reviewed with the SE lead |
| Who they are | A business-intelligence vendor that added a forecasting module for sales teams. |
| How they position themselves | One analytics suite for the whole company, forecasting included. |
| Where we meet them | Accounts that already run Harborview dashboards in finance. |
| Their typical buyer | The CFO or a finance systems lead, not the sales leader. |
Why we win
| Differentiator | Proof | Talk track |
|---|---|---|
| Built for sales managers, not analysts | Live demo of the weekly forecast call view | "Your managers run the forecast call in Ferncastle without asking an analyst for a new report." |
| Deal-level risk signals | Customer-approved story from a logistics customer | "You see which deals are slipping before the call, not after the quarter." |
| Faster rollout for the sales team | Implementation plan template shared in the proposal | "Sales can start without waiting for a BI project to be scheduled." |
Where they are strong, and landmines
| Item | Example entry |
|---|---|
| Their strength | Finance already trusts Harborview data. Respond: "Keep Harborview for company reporting; Ferncastle feeds it a cleaner sales forecast." |
| Landmine question | "Who builds a new forecast view when your sales leader asks for one, and how long does that take today?" |
| Landmine question | "How do your frontline managers see deal risk between forecast calls?" |
Objections and pricing
| Objection | Response |
|---|---|
| "Harborview is already paid for." | Ask what the sales team uses today, then compare the cost of analyst time for custom forecast reports with a tool sales can run alone. |
| "One vendor is simpler." | Agree it is simpler for IT; show the integration that sends Ferncastle's forecast into Harborview dashboards. |
| Pricing model | Harborview sells forecasting as an add-on to its BI suite. Do not quote their prices from memory; link their pricing page with the date checked, and position Ferncastle on time to value for the sales team. |
| When they are the better fit | Small teams whose forecast is owned entirely by finance, with no frontline manager use. |
Example: fictional company. Ferncastle Analytics, Harborview Metrics, Marlow & Finch Logistics and every person named in this example are invented for illustration. Any resemblance to real companies or people is coincidental.
How to build a battlecard with this template
Pick the competitors that matter
Start with the two or three rivals that appear most often in your CRM competitor field and in win/loss notes. A card for a competitor you meet once a year will go stale before it is used.
Collect evidence before you write
Pull win/loss interview notes, call recordings where the rival was named, their public website and pricing page, and review-site comments. Record the source and date beside every claim so the card can be checked later.
Draft one card per competitor
Fill in each section with bullets, not paragraphs. Write talk tracks as sentences a rep would actually say aloud, and keep claims to what you can prove.
Validate with the people who sell
Review the draft with two or three top reps and a sales engineer. Ask which answers they would never use and why. Then rehearse the objection responses in a role-play before you publish.
Publish where reps already work
Put the card in the CRM, the enablement tool or the channel where competitive questions get asked. Retire the old version so only one card exists per competitor.
Review on a schedule
Set the next review date on the card. Update it after competitor launches, pricing changes and every few win/loss interviews, and check whether reps actually open it.
Common battlecard mistakes
Writing an analysis, not a card
Ten pages of feature comparisons will not be read during a call. Link to the deep analysis; keep the card to one screen.
Trash-talking the competitor
Buyers have often seen the rival's demo. Claims you cannot prove cost credibility and can create legal risk. Stick to verifiable facts and your own strengths.
No owner and no review date
Competitors change pricing, packaging and messaging. A card without an owner quietly becomes wrong, and reps stop trusting all of them.
Features without the "so what"
A feature list does not tell the rep why this buyer should care. Every differentiator needs a proof point and a talk track.
Pretending they have no strengths
If the card ignores what the competitor does well, reps are caught off guard. Name the strength and give the response.
Never practising the talk tracks
A response that has never been said aloud rarely survives a live objection. Rehearse the card before it ships.
How Revspire automates battlecards
The template works in any document tool. The hard part is keeping dozens of cards current and getting them in front of reps at the right moment. Revspire's AI Playbook Engine drafts battlecards and objection plays with AI grounded in your approved revenue knowledge, routes them for approval, and publishes the governed version into seller workflows, with usage analytics on which plays get used.
Because Revspire also includes AI Sales Training & Coaching, reps can rehearse a battlecard's objection responses in AI role-play before a competitive call.
Sales battlecard template FAQs
What should a sales battlecard include?
A competitor snapshot, your top three reasons to win with proof, the competitor's real strengths and how to respond, landmine questions, objection responses, pricing and discount guardrails, a quick-dismiss line, proof assets and an owner with a review date. The template above has a section for each.
How long should a battlecard be?
One page or one screen. A seller should be able to find the answer they need in under a minute. Put deep analysis, full feature matrices and long customer stories in linked documents rather than on the card.
How often should battlecards be updated?
Give every card an owner and a next-review date. We suggest reviewing each card at least once a quarter, and immediately after a competitor launches a product, changes pricing or appears in several lost deals in a row.
Should battlecards be customer-facing?
No. Battlecards are internal and often include candid notes about weaknesses and discount guardrails. If buyers need a comparison, publish a separate, factual comparison page that legal and product marketing have approved.
Can AI or ChatGPT create a battlecard?
AI can draft a card quickly from sources you supply, such as win/loss notes and the competitor's public pages. Treat the draft as a starting point: check every claim against a dated source, have product marketing approve it, and publish only the reviewed version.
Related templates and reading
- Free templateMutual action plan templateA shared, dated plan from discovery to go-live, with a buyer owner and a seller owner on every milestone.
- Free templateStakeholder map templateEvery person in the buying group on one page, with buying role, influence, stance, priorities and a next action.
- Blog: building a battlecard programmeThe complete guide to competitive battle cards
- Blog: feeding win/loss insight into cardsAutomated win/loss analysis
- Blog: rehearsing objection responsesObjection handling with AI practice
Sources
- Highspot, GTM Performance Gap Report 2026 (2026-08-19)