The definitive guide to battlecards

One card per named competitor, never one card for the competition

The honest answer to “why not just use them?” is different for every specific competitor a deal is actually being weighed against. A card that tries to cover every rival at once ends up making the generic argument, which is exactly the improvisation the card existed to prevent.

So the unit is one card per named rival, and the list of rivals is not a guess. Anchor it in real deal pressure: which specific competitor came up in your last three lost or contested deals, not the one you assume is your biggest threat. Those are frequently different companies, and the card you need is for the one that actually showed up.

Radically scannable, which means labeled blocks and no prose

Structure every card identically, so a rep under pressure finds the right block by its position before they have read a word of it. The working set of blocks, under imperative labels:

• Who this is for. The competitor, the objection, or the persona this card covers.
• Lead with. The three things to say first, in the order to say them.
• If they say. The specific pushback, and the specific answer.
• Never say. The three things not to say, even when true.
• Trap questions. What this competitor's own sales team coaches their reps to ask, and the answer, ready before it lands.
• Proof. The points that back the claims, each with its source and its date.

Write every block as a label plus a short, scannable line. Not a paragraph. Color-code the block types consistently across every card, one tone for what to say and a distinct one for what to avoid, so a rep finds the right block by glancing at the color. High contrast, and larger type than a customer-facing sheet would use, because this is read fast and often one-handed on a phone.

The never-say block is as important as the lead-with block

Most battlecards are built entirely out of ammunition and carry nothing about restraint, which is a mistake, because the fastest way to lose a contested deal is not to run out of things to say. It is to say the one thing that makes you look petty rather than credible.

So ask the question directly when you build the card: what is the one thing a rep should never say about this competitor, even if it is true? The answer is usually specific and usually memorable, and writing it down converts a judgment call made live, under pressure, by whoever happened to take the call, into a decision the business has already made once.

Source and date every competitor claim, without exception

A battlecard asserting a competitor's weakness with no source and no date attached is not merely unpersuasive if challenged. It is a legal exposure the moment it is wrong, and competitor features move fast enough that an undated claim ages into a lie within months without anybody noticing.

An unsourced claim does not get softened into “probably true.” It does not go on the card until it has a source and a date beside it. And the reverse applies: when you build a card, go looking specifically for the claim your reps already repeat that nobody can source. There is almost always one, it is usually two years old, and it is the single item most likely to be said out loud to a prospect who knows better.

Research each competitor the same way every time, from their own site, their recent public communications, and their pricing where it is public, so every card is built on comparably current material rather than whatever somebody remembered from the last deal this rival showed up in.

Concede something, or convince nobody

The structural pattern worth borrowing from a good published comparison is the order it argues in, and the fact that it starts by giving the other side its due. Six moves: the one-line answer to why a buyer who already owns the competitor should care; what they genuinely already get from it; what it leaves sitting on their desk; what you add, specific to that gap; how the two coexist, including when the competitor alone is honestly enough; and the sources.

A comparison that concedes nothing convinces nobody, and a rep who opens with “they are terrible at everything” has told the prospect that this document is marketing rather than information. The fifth move, naming when the competitor alone is genuinely enough, is the one that makes a rep trustworthy for the rest of the conversation. It also saves real time: a deal that was never yours is better qualified out in the first call than in the fourth.

Design it for the day it leaks

A battlecard is internal, and it will eventually be read by the competitor it names. That is not a risk to be managed with a confidentiality footer; it is a design constraint to build against from the start. Treat “what happens if their sales team gets a copy of this” as a real question you answer on the page.

Practically, that means three things. Keep every claim sourced and dated, so a leaked card reads as an assessment rather than an accusation. Keep the tone factual rather than mocking, because a line that is funny internally reads as contempt when quoted back at you. And never phrase a weakness in language you would not want repeated in front of a prospect, since that is exactly where it will end up.

A card that leaks and reads as a fair, internal competitive assessment survives that moment far better than one that reads like an attack ad. The second kind does not just embarrass the business; it hands the competitor a document they can show to your prospects.

Keep it internal in look as well as in label

Do not give a battlecard a cover page, a polished hero image, or the tone of a customer-facing document. Function over ornament here, with the caveat that function includes design: the color coding, the contrast and the type size are what make it usable in thirty seconds, and they are not decoration.

Two layouts carry this well. A grid of parts, with strongly labeled cells, for a card covering several situations. A versus split for a genuine head-to-head. A sidebar rail holding the quick-reference items beside the main content works with either.

Currency is this row's real maintenance problem

A sell sheet decays slowly. A battlecard decays the moment the competitor it names does something, and the trigger is not a date on a calendar. Re-verify a card when the competitor repositions, ships a feature that changes the comparison, or changes public pricing. A card arguing against last year's version of a rival is worse than no card at all, because a rep trusts it.

And retire a card the moment the competitor it names stops being a live alternative that prospects are actually weighing. An unused card is not harmless: it sits there looking current, and somebody eventually opens it.

How you know this has decayed

• Two reps give different answers to the same competitor objection, and both believe they are saying the company line.
• A claim on a card cannot be traced to a source, and nobody can remember where it came from.
• The competitor repositioned and no card was touched.
• There is a card for the rival you assume is your biggest threat and no card for the one that actually showed up in the last three contested deals.
• Reading a card cold takes longer than thirty seconds to find the answer to one named objection.