Last updated: September 2026
A sales battle card template is only worth using if your reps can find it, trust it, and pull it up mid-call. Too often they can't. Highspot's GTM Performance Gap Report found that 39% of go-to-market leaders admit their sales and marketing collateral "isn't activated or used effectively" by sellers — and battle cards are usually the worst offenders: outdated, buried in a shared drive, and written like product documentation instead of a weapon for live deals.
Rivals also change pricing every quarter and ship new features monthly — and whoever maintained your cards last probably left in March.
This guide fixes the whole pipeline, not just the format: field-by-field structure, AI prompts that draft each field from public competitor pages in minutes, a fifteen-minute verification pass, a filled-in example, a measurement plan, and an update cadence that keeps cards from rotting. Every template on this page is free to copy — nothing sits behind a download form.
The short answer
A sales battle card is a one-page cheat sheet that tells a rep how to win against one named competitor: where you win, where they win, three differentiators with proof, two landmine questions, and a pricing talk track. AI drafts the card from public sources in about twenty minutes; a human verifies every claim before it ships.
What goes on a battle card, field by field
A battle card is not a competitor encyclopedia. It's decision support for the ninety seconds between "we're talking to TicketTitan as well" and whatever your rep says next. Gong's guidance on card format is blunt: skip feature-by-feature charts and elevator pitches, and give sellers a talk track, two or three landmine questions per deal, and social proof that fits the deal size.
Eight fields, one page:
- Competitor snapshot — positioning, target customer, pricing model. Three lines, maximum.
- Where you win / where they win — an honest 2×2. Cards that pretend you win everywhere destroy rep trust fast.
- Three differentiators with proof points — each backed by a number, a named customer, or a benchmark.
- Two or three landmine questions — questions that get the buyer to discover the competitor's gap without you naming it.
- Pricing-objection talk track — exactly three sentences, written to be spoken aloud.
- One customer-switch story — industry, trigger, and one hard number.
- Kill criteria — where you should walk away instead of competing on price.
- Owner and last-verified date — the two fields that keep the card alive.
Close's best-practice guidance adds one rule worth pinning above your desk: soundbites, not manuals. If a field doesn't help a rep during a live call, it belongs in your win/loss archive.
Battle card, playbook, one-pager, or deck?
Teams waste hours forcing one asset to do another asset's job. Check this table before you build anything new:
| Asset | What it does | Length | Owner | Refresh cadence |
|---|---|---|---|---|
| Battle card | Win a deal against one named competitor | 1 page | Product marketing | Quarterly + triggers |
| Sales playbook | Teach the full sales motion to new reps | 10–30 pages | Sales enablement | Yearly |
| Sales one-pager | A leave-behind that sells in 90 seconds | 1 page, ~300 words | Product marketing | Quarterly |
| Pitch deck | Carry a live conversation, slide by slide | 10–15 slides | Founder or sales lead | Per narrative change |
| RFP answer library | Reuse approved answers at scale | Living library | Enablement + legal | Monthly |
| Sales sheet | Spec and pricing reference for procurement | 1–2 pages | Product marketing | Every release |
Two overlaps matter. Battle-card fields feed directly into RFP answers — same differentiators, same proof points, longer format. And the leave-behind that pairs best with a talk track is a tight sales one-pager; slides are a pitch deck conversation, not a card conversation.
How to build a sales battle card with AI in seven steps
This is the full workflow, from "we keep losing to X" to a verified card sitting in your reps' hands. Budget half a day for your first card, then about fifteen minutes per refresh.
- Rank competitors by losses, not by noise. Export lost deals from your CRM and tag the winning rival on each. The competitor your loudest rep complains about is often not the one taking your deals. Build cards for the top three.
- Collect public raw material. Paste the competitor's homepage, pricing page, changelog, two recent job posts, and their latest one-star and five-star G2 reviews into one document. Every claim must trace to a public source — scraped confidential intel is a legal risk no card is worth.
- Run the field-by-field prompts. Open a drafting tool — ArWriter's article writer is built for structured business documents — and run the five prompts in the next section, one per field.
- Do the fifteen-minute verification pass. Check every pricing claim against the live page, confirm every quote is real and attributed, delete anything marked UNVERIFIED you can't source, and stamp today's date. A 2025 Harvard Business Review study of more than 3,500 professionals found generative AI significantly improved drafting quality and efficiency — when humans stayed in the loop. Keep them there.
- Add the human-only fields. Kill criteria, the switch story, and landmine questions come from people who fought these deals. Pull two lost-call recordings and one win, and write the landmines with the rep who heard them.
- Deploy where reps already live. A card nobody opens is the 39% problem in a new hat. Put it in the CRM opportunity sidebar, the competitive Slack channel, and your enablement platform — one canonical copy, linked everywhere. Salesforce found 51% of sales leaders say tech silos hinder their AI efforts; don't let cards become another one.
- Measure, then schedule the refresh. Note the baseline competitive win rate before launch, review the metrics below monthly, and set a quarterly review with trigger-based updates in between. Salesforce's State of Sales reports 94% of sales leaders call AI agents essential to growth — let AI carry the drafting, humans the judgment.

Five prompts that draft each field
Copy these as-is and replace the curly-brace fields — they're tuned so the AI flags anything it can't verify from your pasted sources. The pricing talk track pairs well with a fuller set of objection handling scripts.
Prompt 1 — the snapshot:
Role: competitive intelligence analyst.
Task: write the "competitor snapshot" block of a sales battle
card for {competitor}. Use only the homepage, pricing page, and
about page pasted below. Output: 3 lines max covering
positioning, target customer, and pricing model. Flag any claim
you cannot verify from the source text with UNVERIFIED.
Sources: {paste pages}
Prompt 2 — the honest 2×2:
Task: build a "where you win / where they win" 2x2 for
{competitor} vs {your product}. Input: win/loss notes below.
Be honest about where they win — reps stop trusting cards that
pretend otherwise. Format: 2 bullets per quadrant, max 12 words
each. Win/loss notes: {paste}
Prompt 3 — differentiators with proof:
Task: write 3 differentiators vs {competitor}. Rules: each must
be (a) provable, (b) meaningful to {ICP and job title}, and
(c) phrased as an outcome, not a feature. Attach a proof point
to each — a stat, a customer name, or a benchmark. Mark
invented-sounding claims UNVERIFIED.
Prompt 4 — landmine questions:
Task: draft 3 landmine questions for a battle card vs
{competitor}. A landmine question makes the buyer discover the
competitor's gap by themselves — never name the competitor in
the question. Base them on the gaps below. Write one open
question, one scenario question, one migration question.
Gaps: {list}
Prompt 5 — the pricing talk track:
Task: write a pricing-objection talk track for a buyer who
says "{competitor} is cheaper." Exactly 3 sentences: (1)
reframe to the cost of the gap, (2) one proof number,
(3) a question that moves the conversation back to value.
Conversational, no jargon, no disparagement of {competitor}.
The outputs fit this skeleton — one page, every field filled:
BATTLE CARD — {Competitor}
Last verified: {date} · Owner: {name}
--------------------------------------
SNAPSHOT: {3 lines}
WHERE WE WIN: {2 bullets}
WHERE THEY WIN: {2 bullets}
DIFFERENTIATORS: 1) {claim + proof} 2) {…} 3) {…}
LANDMINES: 1) {open question} 2) {scenario question}
PRICE PUSHBACK: {3 sentences}
SWITCH STORY: {customer, industry, number}
KILL CRITERIA: walk away if {conditions}
If you'd rather not stitch five prompts together by hand, ArWriter's article writer runs the whole card as one structured draft — you paste sources, verify the output, and ship.
A filled-in example you can steal
Here's what a real card looks like when every field is populated — companies illustrative, structure exact:
BATTLE CARD — TicketTitan (legacy incumbent)
Last verified: 2026-09-12 · Owner: Dana K., PMM
--------------------------------------
SNAPSHOT: Enterprise helpdesk, sold on "suite breadth."
Targets CIOs at 1,000+ seat companies. Per-agent annual
pricing with multi-year lock-ins.
WHERE WE WIN: fast setup (days, not quarters); usage-based
pricing; AI triage out of the box.
WHERE THEY WIN: deep customization; global field service;
procurement already knows them.
DIFFERENTIATORS: 1) median go-live 6 days (customer data,
n=140); 2) AI triage cuts first-response 41% (benchmark);
3) no per-seat minimums (public pricing page).
LANDMINES: 1) "How long did your last enterprise rollout
take, end to end?" 2) "What happens to your per-agent cost
when the team doubles in peak season?"
PRICE PUSHBACK: Their number looks lower until you add the
implementation line. Our customers average payback in 4
months. What would a 6-week rollout be worth to your team?
SWITCH STORY: a 300-seat fintech moved off TicketTitan after
a 9-month rollout stalled; live in 3 weeks with us.
KILL CRITERIA: walk away if they need on-prem or 24/7 field
service in year one — we don't ship that yet.
Notice what's absent: no feature table, no trash talk, no paragraph longer than three sentences. Every claim carries a source or a number, and the landmines are questions the buyer asks themselves.
One competitor, two cards: mid-market vs enterprise
That TicketTitan card is written for an enterprise fight. Run the same competitor at a 90-seat mid-market deal and half of it misfires: the CIO references mean nothing to a VP of Support running the entire evaluation alone, the multi-year lock-in landmine lands flat because nobody at that size pushes lock-ins, and the 300-seat fintech story reads as "not us." Gong's format guidance says social proof must fit the deal size — the cleanest way to act on that is two variants of one card, sharing the snapshot and splitting everything else.
Split only when your CRM loss data shows the competitor genuinely taking deals in both segments; for most teams that's one rival, not all three. When it does:
| Field | Mid-market variant (20–200 seats) | Enterprise variant (1,000+ seats) |
|---|---|---|
| Buyer | VP of Support or Ops, single economic buyer | Committee: CIO, security, procurement |
| Lead differentiator | Time to value — live in days, no services invoice | Admin controls, compliance, uptime SLA |
| Pricing talk track | 12-month total cost, one number | 3-year cost including implementation |
| Landmine style | One question aimed at this quarter's pain | Migration and governance scenarios |
| Switch story | A company their size, same industry | The biggest logo you can name |
| Kill criteria | Walk away if they need on-prem | Walk away below 500 seats or $40k a year |
And the mid-market variant in full — same competitor, same owner, second page:
BATTLE CARD — TicketTitan (mid-market variant)
Last verified: 2026-09-12 · Owner: Dana K., PMM
--------------------------------------
WHERE WE WIN: live in 6 days median (n=140); no services
fee; monthly billing, cancel anytime.
LANDMINES: "What did rollout actually cost the last time
you added a channel?"
PRICE PUSHBACK: They bill per agent per year with a services
invoice on top; we bill monthly. Over 12 months that's 22%
cheaper with zero implementation cost. Want the side-by-side
I built for your finance team?
SWITCH STORY: a 60-seat retailer went live in 5 days after
a TicketTitan partner quoted 10 weeks.
KILL CRITERIA: walk away if they need SSO and audit logs on
the entry plan — that's the tier above.
The second variant costs about ten minutes once the first exists: duplicate the card, rerun Prompts 3 and 5 with the mid-market buyer in the ICP field, swap the switch story, and re-stamp the date. Pair each variant with its own leave-behind — a segment-specific sales one-pager — and label the two card links separately in your CRM, because the day the enterprise win rate moves and the mid-market one doesn't, you'll want to know exactly which talk track to fix.
How a Leeds SaaS team lifted competitive win rate 18% with AI-refreshed battle cards
Priya Raman, VP of Sales at a forty-person HR-tech SaaS in Leeds, inherited battle cards that were fourteen months old and lived as PDFs in a Drive folder. Reps had stopped opening them; deals against two rivals were closing at 31%.
Her rebuild took three weeks. AI drafts gave her six cards in two afternoons; a Friday verification rota — one product marketer, fifteen minutes per card — kept them honest. The real unlock came from call recordings: each card's two landmines were rewritten from actual lost-call moments, and the talk track trimmed to three spoken sentences.
One quarter later, competitive win rate against the top three rivals hit 37% — an 18% relative lift. Weekly card usage reached 71% of reps, and new-rep ramp dropped from 4.2 months to 3.1. The cadence, not the format, did the heavy lifting: every card now carries an owner and a last-verified date.
How to tell whether your cards are working
Four metrics, checked monthly:
- Card views per rep per month — adoption first. Near zero means a deployment problem, not a content problem.
- Battle-card mentions on recorded calls — reps quoting differentiators or landmines on won calls is the strongest leading signal.
- Competitive win rate vs. your pre-launch baseline — give it a full quarter before judging.
- New-rep ramp time — measure how fast new sellers run a competitive deal alone.
One cultural metric earns a slot too: LinkedIn State of Sales data via Close's roundup — 91% of buyers would give a referral, but only 11% of sellers ask. Hard proof points are what make buyers confident enough to refer you upstream.
Who owns the card, and when it gets refreshed
The split that works: product marketing owns content, sales enablement owns distribution, and a named rep per competitor owns feedback. Salesforce found 9 in 10 sales teams already use AI agents or expect to within two years — drafting is no longer the bottleneck. Ownership and cadence are.
Set two clocks:
- Quarterly refresh — the fifteen-minute verification pass, a new last-verified date, and one field improved from rep feedback.
- Trigger-based updates — competitor pricing change, funding round, product launch, or a new exec with a different strategy. Any of these starts a same-week refresh.
The fifteen-minute quarterly figure holds only once the pass is routine. Timed out, one card costs: four minutes on the live pricing page, four skimming the competitor's changelog since the last stamp, five swapping the weakest proof point using rep feedback, and the remaining two re-dating the card and pushing the canonical copy to CRM and Slack. Six cards is ninety minutes a quarter — less than one lost-deal postmortem — so make it structural: each product marketer owns two cards, and the rota is a recurring Friday calendar block, not goodwill. Once a year, archive any card for a competitor you haven't lost to in two straight quarters; a card nobody fights still eats its fifteen minutes.

Seven mistakes that kill battle cards
- Feature matrices instead of talk tracks. Gong's competitive-enablement guidance says it plainly: reps can't speak a spreadsheet. Give them sentences designed to be said out loud.
- Ten-paragraph cards. Close calls this the manual trap. If the card can't be scanned between two buyer sentences, it won't be used in the moment that matters.
- No owner and no date. An undated card is a rotting card. The last-verified stamp is what turns "is this current?" into a five-second check.
- Buried deployment. A PDF in a folder with 400 others is the 39% problem again. One canonical copy, surfaced in the CRM and Slack.
- Publishing unverified AI claims. AI drafts fast and sounds confident. Every number that reaches a buyer needs a source a human actually checked.
- Trashing the competitor. Your buyer picked them, or their colleague did. Disparagement reads as insecurity; verifiable claims read as competence.
- Zero measurement. If you can't name your competitive win rate before and after card launch, you don't have a battle card program — you have a writing hobby.
FAQ
What is a sales battle card?
A one-page internal reference that equips a rep for a deal against one named competitor. It covers where you win, where they win, three differentiators with proof, landmine questions, a pricing talk track, and kill criteria. It's built for live calls, not for reading at a desk.
What should a sales battle card include?
Eight fields: competitor snapshot, an honest win/loss 2×2, three proof-backed differentiators, two or three landmine questions, a three-sentence pricing talk track, one customer-switch story, kill criteria, and an owner plus last-verified date. One page maximum — if it reads like documentation, reps won't open it mid-call.
How do you write a battle card for a competitor?
Start from public sources: homepage, pricing page, changelog, and reviews. Draft each field with a structured AI prompt, then verify every claim against the live page. Add landmine questions and kill criteria from reps who fought the real deals, stamp the date, and deploy it inside the CRM.
How often should sales battle cards be updated?
Quarterly at minimum, plus trigger-based updates when a competitor changes pricing, raises funding, launches a product, or hires a new leader. Put the last-verified date on the card itself so reps can see staleness at a glance and know when to flag it.
Can AI create sales battle cards?
Yes, for the drafting layer. AI turns pasted competitor pages into a structured draft in minutes and flags claims it can't verify. What it can't do is own the truth of the card: pricing checks, story selection, and landmine questions still need a human who knows the deals.
What's the difference between a battle card and a sales playbook?
Scope. A battle card covers one competitor in one page and changes quarterly. A playbook teaches your entire sales motion — segments, stages, messaging, process — across ten to thirty pages and changes yearly. Cards are tactical field tools; playbooks are training infrastructure.
How do you measure battle card effectiveness?
Track four things: card views per rep per month, battle-card mentions on recorded calls, competitive win rate against the pre-launch baseline, and new-rep ramp time. If usage is high but win rate doesn't move within a quarter, the content — not the distribution — is the problem.
What are landmine questions in a battle card?
Questions that lead the buyer to discover a competitor's gap without you naming or criticizing the rival. Example: "How does your current tool handle peak-season volume?" They work because buyers trust their own conclusions faster than your claims. Gong recommends two or three per deal.
Sources
- Highspot — Sales Battlecards: Examples to Inspire B2B Sellers — https://www.highspot.com/blog/sales-battlecards/
- Gong — Boost Your Competitive Win Rate With These Battlecard Examples — https://www.gong.io/blog/sales-battle-card-example
- HubSpot — How to Use Battle Cards in Your Sales Process — https://blog.hubspot.com/sales/battle-cards
- Klue — Battlecards resource hub — https://www.klue.com/blog/battlecards/
- Salesforce — State of Sales, 6th edition (2026) — https://www.salesforce.com/resources/research-reports/state-of-sales/
Your pre-call checklist
Run this in the five minutes before any competitive call:
- Which competitor is in the room? Open that card, not the folder.
- Check the last-verified date. Older than a quarter? Verify pricing before quoting anything.
- Say the three-sentence pricing talk track out loud once.
- Pick two landmine questions — no more.
- Pick the one differentiator with the strongest proof for this buyer's role.
- Have the switch story ready in one sentence.
- Know your kill criteria, so you can qualify out instead of discounting.
- Confirm where the card link lives in the CRM.
- After the call: log which landmine landed — that's next quarter's card improvement.
- If a competitor fact changed on the call, flag the card owner the same day.
By the way, if you want battle cards drafted fast, ArWriter writes them with a full bilingual editor — starts at $4.99/month.