Writing A Battlecard Sales Will Actually Use

Most battlecards are written once, with care, by someone who knows the competitor well. Then they are put in a shared folder, and sales stops opening them within a quarter. Not because the writing was poor, but because a rep a few minutes before a call can’t tell which parts are still true, and one wrong claim in front of a buyer is enough to stop trusting the rest.

A battlecard that gets used is short, specific, sourced and current. This guide covers each of those, with a structure you can copy.

Who it is for and when they read it

Write for one reader in one moment: a salesperson, a few minutes before a call, who has just learned that the buyer is also talking to this competitor. They are not going to read an essay. They want to know how this competitor will be described to the buyer, where we win, where we don’t, and what to say when the buyer raises a point.

Everything on the card should serve that moment. Market sizing, company history and the competitor’s founding story belong somewhere else. If a section wouldn’t change what a rep says on a call, cut it.

That also sets the length: one page, readable in about two minutes. If it doesn’t fit, the card is trying to do two jobs.

A structure that works

The order matters. The first thing a rep sees should be the thing they most need if they read nothing else.

Summary

Two sentences: who the competitor is, and how they compete with you right now. Not “a leading provider of workflow solutions”, which is their tagline, but something like “Vantage sells a simpler, cheaper version of our reporting to small finance teams, and since spring has been pushing into mid-market with a new Business plan.”

At a glance

Three short facts: positioning, audience and pricing. Take positioning from their homepage, in their own words, and pricing from their pricing page as it is today. If pricing isn’t public, say “not public” rather than guessing.

How we win

Up to four talk tracks a rep can say out loud. Each one should be tied to a real difference a buyer could check. “Focus on our superior value” is not a talk track; “Their reports refresh nightly, ours refresh as the data changes, which matters if your team closes the month in three days” is one.

Their strengths

Up to five, stated honestly. This section feels counterintuitive, but it is what makes the rest of the card credible. A rep who has been told where the competitor is genuinely strong won’t be caught out when the buyer says so, and can steer the conversation to where it matters less.

Their weaknesses

Up to five, each something a buyer could verify. “Poor support” is an opinion; “Support is email-only on every plan below Enterprise, per their pricing page” is a fact with a source. Avoid anything you would be embarrassed to see quoted back to the competitor.

Objections

Up to four, in the buyer’s words, each with a short, honest answer. More on these below.

Watch

Up to three recent moves worth knowing about, newest first, each with its date. This is the part that keeps the card alive: a new plan, a new integration, a hiring push into your segment. Remove a move once it no longer changes how you sell.

Sources

A numbered list of where each claim comes from, with a date and a link. Every strength, weakness and recent move above should point to one.

There is a free battlecard template with exactly this structure, ready to copy as Markdown.

Evidence: every claim has a source and a date

The fastest way to lose a sales team’s trust is a claim that turns out to be wrong in front of a buyer. The fix is not more careful writing. It is making every claim traceable.

For each factual claim, record:

What: the claim in one line.
Where: a link to the page, posting or announcement it comes from.
When: the date it was seen, or the window if you only know it changed between two checks.

When the reader can see that the claim about pricing was checked last Tuesday on the competitor’s own pricing page, they can use it with confidence. When a claim has no date, they have to guess, and most will guess that it is stale.

Be explicit about uncertainty. “Appears to have dropped the free plan (the pricing page no longer lists it; the sign-up page still mentions it)” is far more useful than a confident claim that may be half true. Keep facts and interpretation apart: what the competitor did is a fact, what it means is your view, and the reader should be able to tell which is which.

Freshness: a card is only as good as its last update

A battlecard is a snapshot of a competitor that is still moving. Its value falls a little every week that nobody updates it, and then falls sharply the first time a rep finds something on it that is no longer true.

A few habits keep a card current:

Put the update date at the top, with the owner’s name. A rep who sees “Updated 3 days ago” reads differently from one who sees “Updated in March”.
Update on events, not on a calendar. A quarterly review misses the price change that happened in week two. When a competitor changes its pricing, launches a product or opens a new market, the card should change that week.
Let the Watch section do the work. Most updates are a new line in Watch and a new source. Rewriting the whole card is rarely needed.
Delete as well as add. A weakness the competitor has fixed is now a liability on the card. Remove it the day you learn it is gone.
One owner per card. Shared ownership means nobody updates it. Name a person.

Objections: from real calls, not from a brainstorm

Objections are the part of the card reps use most and the part most often made up. A list of objections written in a meeting tends to contain the ones the team worries about, not the ones buyers actually raise.

Collect them from where buyers speak: call notes, recorded calls, lost-deal reviews, and the questions the sales team posts in its channel. Write each one in the buyer’s words, because that is how the rep will hear it:

What the buyer says	How we answer
“Halcyon is half the price.”	“For up to five users, yes. Above that their per-seat price passes ours, and SSO is only on their top plan. How many people will use it in a year?”
“They already integrate with our CRM.”	“So do we, since June; here is the listing. The difference is that ours syncs both ways.”

A good answer is short, honest and ends by moving the conversation, often with a question. It never claims something the rep can’t back up, and it concedes what is true. Buyers can tell the difference between an answer and a deflection.

Make it easy to find and easy to use

The best card fails if a rep can’t find it in the minute before a call. Put it where sales already works: linked from the competitor field in the CRM, pinned in the sales channel, or one click from the deal. Keep a single version; copies in three folders guarantee that two of them are wrong.

Format for scanning. Short lines, bold labels, no paragraphs longer than three sentences. A rep should be able to find the pricing line or the top objection without reading anything else.

Finally, ask sales what they used. After a few weeks, ask which sections they read and which they skip. Cut what nobody reads, and make the useful parts more prominent. A card that changes in response to its readers is one they will keep opening.

Where Orlea fits

Orlea writes and maintains a battlecard for each competitor from what it has actually seen change: the latest changes on that competitor’s tracked pages, its current price list, and your own company profile. It rewrites the card shortly after new alerts and skips the rewrite when there is no new evidence. Each claim points back to its source, and the card can be copied as Markdown or printed.