How to Build a Sales Battlecard (Step by Step, with a Free Template)

A battlecard has one user, one moment, and one budget: a sales rep, the thirty seconds after a prospect says a competitor’s name, and however much attention fits in that window. Everything about how to build one follows from that constraint — which is why most battlecards fail. They’re written as research documents, and research documents don’t fit in thirty seconds. This is the step-by-step for building one that does, block by block, plus the maintenance loop that decides whether it survives contact with a real quarter. The free templatemirrors this structure exactly, ungated, if you’d rather start filling in than reading.

Before you write: pick the competitor and gather three inputs

Build cards for competitors that appear in real deals — not the biggest names in the category. Your CRM’s loss reasons, your reps’ last month of calls, and win-loss interviews (if you run them) tell you which two or three names earn a card. For each, gather three inputs before writing: what their public positioning actually says today (their homepage, pricing page, and comparison pages — read them, don’t remember them), what your reps actually hear (“they’re cheaper,” “they have X”), and what deal outcomes actually show. The gap between those three is where battlecards earn their keep.

Block 1: the two-line profile

Who they are and who they’re for, in two lines a rep can repeat verbatim. Not history, not funding, not the org chart — “Enterprise CI suite for dedicated enablement teams; sold sales-led on annual contracts” is a complete profile. The test: could a rep who read only this block avoid saying something wrong about the competitor on a call?

Block 2: the positioning summary

Two halves: how they’ll frame you, and how you frame them. The first half is the one teams skip and shouldn’t — if the competitor has a comparison page about you, it’s a gift: their claims against you are the objections your reps will hear next quarter, written down in advance. How to find and read those pages is covered in tracking competitor SEO and content strategy.

Blocks 3 and 4: win rows and lose rows

Two or three of each, grounded in deal outcomes rather than feature pride. A win row is a specific, checkable claim plus the situation where it decides deals (“faster time-to-value for teams without an analyst — decisive in deals under 50 seats”). A lose row is the honest mirror — where they genuinely win — because a card that concedes nothing gets distrusted everywhere. Reps calibrate off the lose rows; that’s what makes the win rows credible.

Block 5: objection scripts and landmines

For each of the two or three objections reps actually hear: acknowledge, reframe, evidence. “They’re cheaper” becomes: yes, their entry price is lower — reframe on total cost at the prospect’s actual seat count — with the competitor’s own published pricing as the evidence, linked and dated. Landmines are the offensive half: questions a rep plants that are easy for you and hard for them (“ask how long their last customer’s migration took”). Write only landmines that stay fair — a landmine that misrepresents them detonates on you when the prospect checks.

Block 6: the freshness footer

The block that separates cards reps trust from cards reps abandon: when each claim was last verified, and where it came from. A battlecard describing last year’s pricing actively loses deals, and — worse — one caught being wrong once stops being opened at all. Every factual claim on the card should trace to a source a rep could open mid-call. If that standard sounds heavy, it’s the same one we hold research to generally; the case for it is in why competitive intelligence goes stale.

The maintenance loop is the product

A battlecard is a cache of your competitive knowledge, and caches need invalidation. Two mechanisms, together: a trigger — when a monitored change fires (pricing, packaging, repositioning), the affected rows get updated that week, which requires actually monitoring those surfaces (pricing pages especially) — and a cadence, monthly for fast movers and quarterly for stable ones, where you re-verify every claim and re-date the footer. Rep feedback closes the loop: what they hear on calls is the freshest competitive signal you have, and a card nobody can correct quietly drifts into fiction.

Distribute where reps already are

A perfect card in an unopened folder is a failed card. Pin it where the deal work happens — the CRM, the deal channel, the enablement tool — and keep it one screen so it survives being read on a phone between meetings. Product marketing owns the card; sales owns telling product marketing when it’s wrong; the monitoring loop owns telling both when the competitor moved. The full division of labor is in the product marketers use-case guide.

Start with the template — or with the research half done

The sales battlecard templatecarries this exact structure with a worked example, free and ungated. And if the research half — the reading, sourcing, and re-verifying — is the part that won’t survive your calendar, that’s the loop Dozier automates: cited findings on each rival, sources archived as captured, and Radar flagging the changes that should trigger a card update. Either way, build the card small, source every claim, and date everything — the rest is maintenance.