How to Write a Battlecard a Rep Will Actually Open Mid-Call

Open ten competitive battlecards at random and count how many words appear before the first objection shows up. In most stacks that number is somewhere past two hundred — a paragraph on company history, a logo wall of "founded in," a mission statement nobody asked a rep to defend live on a call. By the time a rep reaches anything useful, the buyer has already said the thing the card was supposed to help with, and the moment's gone.

Cut the company overview first

The rep already knows who they work for. A battlecard exists to arm them against a specific rival, not to restate the pitch they give in their sleep. If new joiners genuinely need company background, that belongs in onboarding material, not on the one document a rep is meant to open in the ten seconds after a buyer says a competitor's name out loud. Every line of company overview on a battlecard is a line standing between a rep and the objection they actually opened the card for.

Lead with the single most common objection

Don't guess which objection matters most — pull it from your own data. Go through the last quarter of loss reasons, win/loss call notes, and CRM stage-change comments, and count how often each specific objection about this competitor actually comes up. Whichever one appears most often goes first on the card, above everything else, full stop. Not the objection your product team wishes reps got asked. The one they're actually getting asked.

A real example, the kind that shows up constantly against a platform incumbent: "Why would we pay for a point solution when you're telling me this is basically built into what we already have?" A battlecard that buries the answer to that under a differentiation slide and two paragraphs of positioning has already failed the rep who needed it ninety seconds ago.

The one-scroll test

Here's the actual test, and it's deliberately literal: open the card on a phone, in portrait, the way a rep might glance at it under the desk mid-call. If the top objection and its full rebuttal aren't both visible without scrolling, the card fails. Cut something. This isn't a metaphor for "keep it concise" — it's a physical constraint that forces real editing decisions instead of good intentions about brevity.

Structure that survives the test

1. Top objection, verbatim, as the header — phrased the way a buyer actually says it, not the way marketing would write it up.
2. A two-line rebuttal directly underneath. If it needs three lines, it needs another edit, not another line.
3. Objection two, same treatment. Same for objection three if the data supports it. Stop at three; a fourth just pushes the first one further down the next scroll.
4. One differentiation line — a sentence, not a paragraph, and only the one that's actually load-bearing against this specific rival.
5. The pricing or packaging delta, only if a buyer is likely to ask directly, and only the number, not a justification essay.
6. Landmines — the two or three things a rep should never say, because they're wrong, outdated, or hand the competitor an opening.
7. A link out to the deeper material — full case study, proposal template, competitive deck — clearly marked as post-call reading, not something to chase mid-conversation.

Formatting rules that matter more than people expect

Bullets, never paragraphs. Bold the buyer's actual objection phrasing as the header so a rep pattern-matches it instantly against what they just heard, rather than reading and translating under pressure. Cap every rebuttal at two lines a rep could say out loud, unedited, without sounding like they're reading from a script. If a rep has to paraphrase your rebuttal before saying it, you've written marketing copy, not a battlecard.

A worked example

Before: "Our platform offers superior native integration capabilities compared to point solutions, providing a unified experience that reduces total cost of ownership and administrative overhead for IT teams managing multiple vendor relationships."

After: "They said it's basically built in already — why pay for a point solution?" → "Built-in usually means basic. Ask what happens when they need X — most teams end up buying the point solution anyway, twelve months later, after the built-in version hits its ceiling. We're the version they'd have bought first if they'd known."

Same claim. One version gets read aloud on a call. The other gets skimmed once and never opened again. If "think about it" is the actual objection on the table rather than a build-versus-buy one, the same two-line discipline applies — an I Need to Think About It Rebuttal Kit is worth stealing from directly rather than writing your own from scratch under deadline.

Build order

Start from a Competitor Battlecard Template so the scaffold is already right, then rank your actual objections before writing a single rebuttal using an Objection Handling Matrix Template — frequency first, rebuttals second, never the other way round. Writing rebuttals before you know which objection is actually most common is how you end up with a beautifully argued answer to a question nobody's asking.

The next battlecard you write, draft the top objection and its rebuttal first, before you write anything else — including the title. Everything the card earns the right to include after that has to fit in the space that's left.