Battle Cards: What Goes in One, and Why They Rot (+Template)

Mid-call, a rep reads a line off the battle card: the competitor doesn’t support single sign-on. The buyer saw it in their demo last week. The deal survives. The card doesn’t: that rep stops opening it, and tells the rest of the team why. This guide covers what goes on a card, why cards go wrong, and what to tell reps when a new competitor appears.

What is a battle card?

A sales battle card is a one-page reference a rep uses to sell against one specific competitor: why you win, where the rival is strong, the objections it triggers and the replies, and the proof. Some vendors spell it “battlecard.” Same thing. The test is whether a rep can take it in during the thirty seconds between a discovery call and a demo.

Reps need one because the competitor comes up live, with the buyer waiting, and nobody can search a wiki mid-sentence.

The card is not the research. Your competitor analysis is where a PMM thinks about a rival over time: funding, go-to-market motion, the full SWOT, the sources. The card is what you hand the field, the four or five things from that profile a seller can say under pressure. The dependency runs one way, so a card inherits every error upstream of it. Tag the wrong competitor in the analysis and the card becomes a confident, well-designed lie.

That makes it a product marketing deliverable, and PMMs are the people most tempted to overload it. The discipline is leaving almost everything off.

Build the head-to-head type first, one card per competitor you actually lose deals to. Persona, objection and win/loss cards reorganize the same intelligence around a buyer type, a recurring objection, or what buyers said after the decision. Role versions only change the depth: BDRs want the discovery questions, AEs the objection handling, execs the snapshot.

What goes in a battle card?

A battle card holds nine elements at most, each written as something a rep can say rather than as marketing copy.

Element	What it is	What good looks like
Competitor snapshot	Who the rival is and who it sells to	One sentence a rep can drop in passing
Why you win	Two or three differentiators that hold against this rival	A buyer outcome, not a feature
Where they’re strong	Where the rival genuinely beats you	Stated plainly. Reps check the card against this row
Objection responses	The objection this rival triggers, and the approved reply	A line the rep can say out loud
Landmines	Questions that expose the rival’s known weakness	“Ask them how long setup actually takes.”
Discovery questions	Whether that weakness applies to this buyer	Two or three, tied to a landmine
Positioning one-liner	Why you over them, in one sentence	Drawn from your positioning, easy to repeat
Pricing contrast	How packaging compares, and where theirs is gated	The gap named, not a teardown
Proof	A customer who chose you over this rival	A named switch story, ideally a short quote

Fact, Impact, Act, a battlecard framework Klue popularized, keeps every row honest: each line carries a fact, why it matters to this buyer, and what the rep does with it. A row that stops at the fact is trivia. Filled in, a landmine reads like this. Fact: their setup runs through a paid services project. Impact: this buyer has no admin to spare this quarter. Act: ask how long the last rollout they heard about took.

To build the first one, pick the competitor you lose to most and ask two or three reps what buyers say when that name comes up. Pull the facts from your analysis, write each row the way a rep would say it, and cut every line nobody would. Keep it to one screen; a row that needs a paragraph belongs back in the analysis. Then put it in front of those reps before you call it finished.

“

If your sales reps can’t communicate it to a prospective customer, it means nothing.

Why do battlecards go out of date?

When reps say the competitive material is outdated, they’re often right. Battle cards rot because the card is static and the competitor isn’t. Rivals ship features, relaunch and reposition on their own schedule. And the failure isn’t gradual. Trust is binary, which is how the card in the opening died.

57.5% of teams report more competitive deals than a year ago, per Crayon’s 2026 State of Competitive Intelligence, and 58% of CI pros told Crayon in 2024 that keeping battlecards updated is a struggle.

Staleness is the most expensive of the four common ways a card fails, because it fails silently:

Mistake	Why it fails
Too long to skim	A rep can’t read a page mid-call
Out of date	The rival ships and the card doesn’t
No landmines	Describes the competitor, gives the rep no move
Dishonest “why we lose”	The rep finds the gap in front of the buyer

Nobody files a ticket against a wrong card. The rep stops opening it, and the first sign is a loss review that names a feature the card listed as missing.

So when the complaint arrives, don’t rebuild the whole library. Open the cards for the rivals in this quarter’s open deals, check every “where they’re strong” and pricing line against the competitor’s own site and docs, and tell reps which lines changed and why. A short changelog wins back more reps than a redesign.

If your cards live in a CI suite you pay for mostly to keep them current, weigh what Klue and Crayon cost against what the suite covers beyond the cards, and if you leave, plan how to move your battle card history before the contract ends.

What do you tell sales when new competitors launch?

Send a holding line within 24 hours and a one-page brief by Friday, and don’t try to finish a battle card in launch week. A card needs confirmed facts, and on Monday you have a press release. What reps need first fits on one page: what you’ve confirmed, what you’ve only heard, and what to say when a buyer asks.

The holding line is three sentences in the channel reps already read: you’ve seen the launch, the brief lands Friday, and until then nobody comments on the rival’s features or pricing.

Every claim about the newcomer then gets a status before it reaches a rep, because the expensive mistake that week is a weakness nobody checked:

Status	What reps may say	What it means
Confirmed	State it, with the source	Their own dated page, doc or changelog says it
Reported	Nothing they’d have to defend	One third-party source says it
Unverified	Ask the buyer where they saw it	A buyer’s account, a rep’s sighting, a launch-post claim

Keep that log wherever your team already keeps competitive notes, linked from the affected deals, with one owner (the PMM, or whoever covers competitive work) and a date and a source on every line, so Friday’s brief is a copy rather than a rewrite. The brief, in the order a rep reads it:

1. What happened, in one sentence, with the source and the date.
2. Which open deals and segments it touches, by name.
3. What’s confirmed and what isn’t, straight from the fact log.
4. What to say (“Yes, we’ve seen it. Tell me what you’re comparing and we’ll go through your criteria.”) and what not to say.
5. Where reps post what buyers tell them, and who updates the page next Friday.

Hold any pricing or product-plan change until the newcomer is generally available and shows up in more than one open deal. The brief becomes a card once enough lines are Confirmed to fill the battle card template. Until then, protect the thread where reps post sightings. In Crayon’s 2026 State of Competitive Intelligence, soliciting sales feedback weekly was the single biggest driver of strong CI adoption: 69% against 22%.

How do you keep battlecards current?

Refresh a card when its competitor moves, not when the calendar says so. A move is anything a buyer could raise in a call: a new feature, a new tier, a new claim on the homepage, a new name in your pipeline. In practice that means three tiers: a weekly look at the two or three rivals in most of your deals, a monthly pass on the next handful, and a check on everyone else only when something on their website or in their docs changes. A quarterly refresh policy is a decision about which quarter the card will be wrong in.

Watch use as closely as accuracy. If reps stop pulling a card, or keep asking the same question in Slack, it’s missing the line they need. Two questions on the deal-close form, which line helped and which one failed, tell you where to look. Buyer calls are the best place to find the missing lines, and what sales calls add to a battle card is worth a read before you mine them.

“Update harder” was never the fix, because the watching doesn’t fit a person’s week. Catching every change to a rival’s pricing page, docs and changelog, then folding it into the right line, is low-glory work that gets dropped first. It’s also where AI takes the grind while the judgment stays human.

Calven is an AI product marketing platform covering positioning and messaging, audience and research, and its Competitive Intelligence Agent does this watching. It identifies your direct and indirect competitors, writes a dossier on each, generates sourced battle cards from it, and monitors competitor websites and docs, folding each change back into the right section of the dossier the cards draw on. Every change carries its source, a person reviews it before it reaches reps by default, and your team still decides what’s true and what a rep can say.

“

The mistake I see most often is treating the battle card as a deliverable you finish. It isn’t something you complete, it’s a distillation you maintain. The template takes an afternoon. Keeping it true takes forever, and the day it lies to your own reps is the day it’s dead.