Sales battle cards: what they are and how they fit

What to take away

A sales battle card is a short, internal page that tells a rep how to position against one competitor or handle one recurring situation.
A card can bring together verified competitor information and suggested responses to recurring sales situations.
They only work when they sit inside a wider enablement library, with a playbook setting out when each card is used.
Cards holding named prospect data or comparison claims fall under UK data protection and advertising rules.

What a sales battle card actually is

A battle card is one page, sometimes two, that a rep opens five minutes before a call. It answers a narrow question: what do we say when this competitor is already in the deal?

Typical entries cover the rival's strongest sectors, the gaps a rep can press, and the wording to use when a buyer says the incumbent is cheaper.

Cards age quickly. Competitor pricing moves and products get retired, so teams that build a sales playbook template usually add a review date to every card.

Battle cards compared with other sales content

Battle cards are one item in a wider enablement library, and reps get confused when the categories overlap. The table below sets out what each asset is for.

Sales content asset comparison

Battle card

Job: Positions vs competitor
Length: One page
Owner: Product marketing

One-pager

Job: Introduces offer
Length: One to two pages
Owner: Product marketing

Case study

Job: Proves outcome
Length: One to two pages
Owner: Marketing

Playbook

Job: Sets process
Length: Ten pages or more
Owner: Sales enablement

Battle cards compared

Job it does

Battle card: Positions against one competitor or scenario
One-pager: Introduces your offer to a buyer
Case study: Proves an outcome with a named customer
Playbook: Sets out the process and the cards to use at each stage
Objection guide: Groups the most common pushbacks by theme

Typical length

Battle card: One page
One-pager: One to two pages
Case study: One to two pages
Playbook: Ten pages or more
Objection guide: Two to three pages

Owner

Battle card: Product marketing
One-pager: Product marketing
Case study: Marketing
Playbook: Sales enablement
Objection guide: Sales enablement

A card that repeats a case study, or a one-pager that lists competitor pricing, shows the library has drifted. Separate the jobs and each asset stays short.

Applying the format in UK payments and accounting software

Payments and accounting software are two UK categories where a card can be tailored to the competitor and sales situation. The prompts below are illustrative: teams should verify current product, pricing and buyer information before using them.

For a hypothetical merchant-services deal involving Barclaycard, the card could prompt a rep to verify applicable scheme and interchange rules, identify evidence-backed service differences, and record which buyer needs Barclaycard may suit. It should not imply a rate advantage without current evidence.

For a hypothetical accounting-software deal involving Sage, a card could prompt the team to research its target buyer profiles, reasons a UK firm might review its software, and migration questions likely to need answers. The card should contain verified, current details for the specific competitor rather than treating these prompts as findings.

Comparative claims are the risky part. A card that misstates a rival's pricing can turn into a misleading comparison once a rep repeats it, and the Competition and Markets Authority enforces the consumer rules that cover misleading commercial practices.

Building a battle card

Before writing anything new, run a sales content audit so you know which existing assets already cover the competitor. Use the audit to identify material to reuse or update.

Build a battle card in five steps

Pick competitor from lost deals
Gather evidence and call notes
Write one pagewins, losses, responses
Test on two reps who lost
Set review date and owner

Keeping cards compliant on data and claims

Comparison claims need evidence before a rep repeats them. UK advertising rules require claims to be substantiated, and the Committee of Advertising Practice publishes the codes that set the standard.

Prospect data is the other exposure. If a card names contacts, quotes call notes or stores objections from a specific deal, that information is personal data and the ICO's UK GDPR guidance applies.

Field reps also need a removal date. Data kept in a shared drive long after a deal closes is the sort of thing a subject access request exposes.

Common questions

What is the difference between a battle card and a playbook?

A playbook describes the whole sales process and points to the assets used at each stage. A battle card is one of those assets, focused on a single competitor or scenario.

How long should a battle card be?

One page is the working standard, two at most. If it runs longer, split it by competitor or by deal stage so a rep can find the answer in seconds.

How often should UK teams update battle cards?

Review each card once a quarter and after any major pricing change. Cards for fast-moving markets, such as payments, need checking more often than cards for stable software categories.

Can reps share battle cards with buyers?

No. Cards are internal documents, and sending one to a prospect hands over your competitive notes. Share a sanitised one-pager instead.