Battlecards: how to build them and keep them current

The short answer

Battlecards are one-page references that help a sales rep win a deal against one specific competitor. To build them and keep them current:

1. Pick the competitors that appear most often in your deals, one card each.
2. Interview reps and read win-loss notes before you research anything public.
3. Fill a fixed set of fields: quick dismiss, when we win and lose, landmines, objections, proof points, pricing context, sources, last updated.
4. Test the draft with reps in a short role play, then publish it where they already work.
5. Give every field an owner and a trigger that forces an update.
6. Measure whether reps open and use the card, and retire what they ignore.

What is a battlecard?

A battlecard is a short, sales-facing document that tells a rep how to compete against one named rival: what to say, what to ask, what to expect and what to prove. It is built for deal time, so a rep can scan it in the minute before a call.

A competitive battlecard differs from a competitor profile in audience and purpose. The profile is a research record for product, marketing and leadership. The battlecard keeps only the lines that change the outcome of a conversation with a buyer, and drops everything else.

Three properties separate a working sales battlecard from a document that gets ignored:

• One competitor per card. A card that compares you with five rivals answers none of the questions a rep has in a specific deal.
• Written in talk tracks. Reps need sentences they can say and questions they can ask, not adjectives about the competitor.
• Visibly dated. A rep who repeats a price the competitor dropped two months ago loses credibility with the buyer. The date tells the rep whether to trust the line.

What goes on a battlecard?

A battlecard should hold eight fields, always in the same order, so reps learn where to look. The structure below is a template you can copy into a wiki page, a document or a sales enablement tool. Each field has a note on what to write and how long it should be.

Header

• Competitor: name and the product line you meet in deals
• Owner: the person accountable for this card
• Last updated: date of the last change to any field
• Deal frequency: how often this competitor appears in your pipeline (for example "in roughly a third of mid-market deals, per CRM")

Field 1: Quick dismiss

• What to write: one or two sentences a rep can say when the buyer repeats the competitor's main claim
• Rule: acknowledge what is true in the claim, then reframe it around the buyer's priority
• Length: under 40 words

Field 2: When we win and when we lose

• We win when: three conditions that show up in your won deals (buyer profile, use case, requirement)
• We lose when: three conditions that show up in your lost deals, stated honestly
• What to do when the deal looks like a loss: qualify out early, change the evaluation criteria or bring in a specialist

Field 3: Landmines

• What to write: three to five questions a rep can ask the buyer that bring the competitor's gaps into the evaluation
• Rule: every landmine must point to a real, sourced gap; a question built on a rumor backfires when the competitor answers it well
• Format: the question, then one line on what a good answer from the buyer reveals

Field 4: Objection handling

• What to write: the three to five objections reps hear most when this competitor is in the deal
• Format per objection: the objection in the buyer's words, the response in two or three sentences, and the proof to offer
• Source: call recordings and rep interviews, not guesses from the marketing team

Field 5: Proof points

• Named customers: accounts that chose you over this competitor, if you are allowed to name them
• Switch stories: customers who moved from the competitor, with the reason in one line
• Evidence: case studies, review excerpts, third-party evaluations, each linked

Field 6: Pricing context

• Their model: how the competitor charges (per seat, usage, tiers, custom quotes) and what their public pricing page shows
• Where they discount: what reps hear in deals, labeled as field reports
• How to frame our price: the comparison to make (total cost, implementation, time to value) and the one to avoid

Field 7: Sources

• For every claim above: the page, document, call or interview it comes from
• For field reports: the rep and the deal, so the claim can be checked

Field 8: Change log

• What changed, when and why: one line per update, newest first
• Why it matters: a rep who saw the card last month can see in five seconds what is different

What does a filled-in battlecard look like?

A filled-in battlecard reads as short talk tracks with a source behind each line. The example below describes a hypothetical competitor, Corvane, an invented project management tool for construction firms, seen by a competing vendor. Every name, number and claim is made up to show the format.

• Competitor: Corvane (hypothetical), core platform
• Owner: competitive intelligence lead
• Last updated: date of last change
• Quick dismiss: "Corvane is strong on scheduling, and if scheduling is your only need it is a fair choice. Most firms your size tell us their bigger cost is change orders, which is where we were built to help."
• We win when: the buyer runs more than ten active sites; finance is in the evaluation; change orders are a stated pain
• We lose when: the buyer is a single-site firm; the evaluation is led by schedulers only; the buyer already uses Corvane's estimating add-on
• Landmine: "How do you handle a change order that affects three subcontractors' budgets at once?" (Corvane's help center describes change orders as single-contract records; help center article, date)
• Objection: "Corvane is cheaper." Response: "On list price per seat, yes. Ask what is included in their entry tier; offline mobile access sits in their top plan, and your field teams will need it." (pricing page, date)
• Proof point: a regional builder that moved from Corvane after a failed rollout across twelve sites (case study, date)
• Pricing context: three public tiers per seat, enterprise by quote; reps report discounts at quarter end (field reports from two deals, date)
• Change log: pricing context updated after Corvane moved offline access to its top tier; new objection added after four reps reported it in one week

Notice what the example avoids: no claim that Corvane is "bad at" anything without a source, and a "we lose when" field that admits real weaknesses. Reps trust a card more when it tells them where not to fight.

How do you build battlecards with sales input?

You build battlecards with sales input by starting from the deals, not from the competitor's website. Reps know which claims buyers repeat and which objections stall deals; public research then confirms or corrects what they report.

Step 1: Choose the competitors from pipeline data

Pull the competitor field from your CRM for the last two or three quarters, plus lost-deal reasons. Rank rivals by how often they appear and how often you lose to them. Build full cards for the top three to five; a rival that shows up twice a year can wait.

Step 2: Interview reps and listen to calls

Talk to four or five reps per competitor, mixing top performers and newer hires. Ask the same questions each time:

• What does the buyer say about this competitor before you bring it up?
• Which objection costs you the most time?
• What did you say the last time you won against them?
• When do you know early that a deal is lost?

If your team records calls, search the recordings for the competitor's name and listen to how buyers phrase their concerns. Those exact phrases become the objection lines in Field 4.

Step 3: Fill the fields from primary sources

Confirm every factual claim against the competitor's own material: pricing page, product documentation, help center, changelog, case studies. Where the rep report and the public source disagree, keep the public fact on the card and log the field report as a question to investigate.

Step 4: Test the draft in a role play

Run a 20-minute session where one person plays a buyer who prefers the competitor and a rep answers using only the card. Any line the rep cannot say naturally gets rewritten. Any question the "buyer" asks that the card does not cover becomes a new objection.

Step 5: Publish where reps already work

A card stored in a folder nobody opens has no effect. Put it in the CRM next to the opportunity, in the sales enablement library or pinned in the sales channel, and announce each new card with the two lines a rep is most likely to use this week.

How do you keep battlecards current?

You keep battlecards current by giving each field its own owner, its own signals and its own trigger, instead of reviewing the whole card on one schedule. Some fields change when the competitor moves; others change when your own deals change.

Which signals update which field?

• Quick dismiss: the competitor's homepage headline and category label. When the main claim changes, the dismiss changes. Owner: product marketing.
• When we win and lose: closed deals and win-loss interviews. Review after each quarterly win-loss readout. Owner: whoever runs win-loss.
• Landmines: competitor changelog, release notes and documentation. A shipped feature can turn a landmine into a liability overnight. Owner: product manager for the area.
• Objection handling: call recordings, rep feedback, the sales channel. Trigger: the same new objection reported by three reps. Owner: sales enablement.
• Proof points: new case studies and customer approvals on your side. Review quarterly. Owner: customer marketing.
• Pricing context: the competitor's pricing page and plan comparison tables. Trigger: any change to a tier, limit or listed price. Owner: CI or product marketing.

For pricing and homepage claims, an archived copy settles disputes about what changed and when; the Internet Archive explains how to browse past versions of a page in the Wayback Machine.

What cadence works?

A workable rhythm for most B2B teams:

• On trigger, within two working days: pricing changes, major releases, new positioning, acquisitions
• Monthly: a 30-minute review per primary competitor with the owner and one or two reps
• Quarterly: win and loss fields, proof points, and a decision on which cards to retire or add

The hard part is detection, not editing. Changelogs, pricing pages, executive posts and help center articles change without announcement, and nobody checks them all every week. Systems that read those sources for you can cover this layer: Kindal, for example, follows a competitor's website and posts, compares each change with the previous version and writes a brief only when something changes, with links to the source. The card owner still decides whether the change touches a landmine, an objection or the pricing frame.

How do you measure whether battlecards are used?

You measure battlecards by whether reps open them before competitive calls and whether outcomes against that competitor improve over time. Counting how many cards exist tells you nothing about either.

Useful signals, from easiest to hardest to collect:

• Views and timing. Most enablement and CI platforms report card views; the useful number is views in the days before a call with that competitor in the deal.
• Mentions in deal notes. Ask reps to note which talk track or landmine they used, and check a sample each month.
• Rep feedback. A two-question survey per quarter: which card helped in a recent deal, and which line was wrong or missing.
• Win rate against the competitor. Track it per rival over several quarters. Treat it as a direction, not proof; pricing, territory and product changes move win rates as much as any card.

When a card gets few views, ask why before rewriting it. The usual reasons are a competitor that rarely appears, a card stored in the wrong place, or content reps do not trust because the date is old.

Which tools help build and distribute battlecards?

Teams build battlecards with three kinds of tools, and the right one depends on the size of the sales team and how many competitors matter.

• Docs and wikis. A shared document or wiki page per competitor works for small teams with a handful of rivals. It costs nothing, but tracking views and enforcing a last-updated date is manual.
• Competitive intelligence platforms. Crayon and Klue monitor competitors, help build battlecards and push them into the CRM and chat tools reps use, with engagement reporting. They fit teams with a dedicated CI or product marketing owner.
• Sales enablement platforms. Highspot and Seismic store battlecards alongside decks and case studies, and report how sellers use that content. They suit companies that already run enablement there.

For a broader view of options by job, including monitoring and sales enablement, see this comparison of market intelligence options for small teams.

What are the most common battlecard mistakes?

The most common mistake is writing the card for the meeting room instead of the call. A card full of feature grids and strategic analysis impresses in a review and goes unused in a deal.

Other mistakes that weaken battlecards:

• Trash talk. Unsourced claims about a competitor's weaknesses get corrected by the buyer, or by the competitor's rep in the next meeting. The FTC's policy statement on comparative advertising encourages naming competitors when the comparison is truthful and non-deceptive; that is a sound standard for anything a rep says or sends.
• No "we lose when" field. Reps who are told they win everywhere stop believing the card. Honest loss patterns also help them qualify out early.
• Too much text. If a field needs scrolling, it will not be read before a call. Cut to talk tracks and move detail to the competitor profile.
• One review date for the whole card. Pricing and objections age in weeks; proof points age in quarters. A single annual refresh guarantees stale fields.
• No feedback loop. Without a simple way for reps to flag a wrong line, errors stay on the card until a deal is lost because of one.

A battlecard earns its place when a rep trusts it enough to say its lines to a buyer. That trust comes from three habits: sourcing every claim, dating every change, and letting the people in the deals tell you what is missing.