Battlecards

A battlecard is not a document. It is something someone reads in the middle of a live conversation, under time pressure, looking for one specific thing. Everything about how it should be built follows from that — and most battlecards are written as if they will be studied in advance, which they never are.

One screen. Scannable. The answer before the reasoning.

The operational shape

Trigger. New competitor intel, or a competitor showing up repeatedly in lost deals. The second is the better trigger and the slower one to notice.

Reads. Verified competitor files and the wedge, from the market map and positioning. Objection and answer pairs, from learnings.

Cadence. Per competitor, maintained.

Gate. Approve before publish. Nominally internal — but treat every line as public, because battlecards get forwarded, pasted, and screenshotted.

What good looks like

It concedes something real, up front. The competitor's genuine strength, stated plainly. A rep who concedes it keeps the room's trust for the disagreement that follows. A rep who concedes nothing is heard as a salesperson and discounted accordingly.

It answers the question that actually gets asked, in the words it gets asked in. Not "how do we compare on architecture" but "so you're basically a cheaper them?" — and one sentence that ends it.

It says what to do when the answer is no. The deal-losing limit, named, with the honest response. A rep who discovers a limit live improvises, and the improvisation becomes a commitment.

Every claim carries its verification date. The same discipline as a public comparison page, for the same reason: these are claims about someone else's product, and they age without notice.

It is one screen. If it needs a second, it is two battlecards.

When it goes stale

Battlecards rot worse than public comparison pages, and the reason is structural: a public page is read constantly and someone eventually notices it is wrong. A battlecard is read only at the moment it is needed, by someone who has no time to doubt it.

Four triggers. The competitor shipped, and the limitation the card rests on is gone. They repriced, which is the claim most likely to be quoted verbatim in a call. They repositioned, so the framing no longer matches how the prospect heard them describe themselves. And a rep found a better answer and did not write it back — the most common decay, and the only one the system can capture automatically.

What it feeds

• Comparison pages — the same verified facts, arranged for a reader instead of a talker
• Objection handling — the pairs that keep recurring belong in the FAQ too
• Learnings — what actually came up, which is how the next card gets better

The write-back is the part most teams skip and the part that matters most. A battlecard that only ever receives updates from marketing is a guess about conversations somebody else is having.