Sales battlecard template, built from win/loss evidence

This template is for product marketers and enablement leads who build battlecards, and for account executives who need one before a competitive deal and can't wait for marketing. It works for any B2B product with two or three named competitors you meet often, and it slots into the competition section of your sales playbook. Building the first card properly takes about a day, most of it spent on win/loss evidence. After that, keeping it current takes an hour a month.

What a battlecard is for

A battlecard helps a rep do three things in a live deal:

1. Know when you're likely to win, and when to walk away early.
2. Ask questions that bring out your strengths without attacking anyone.
3. Answer the competitor's claims accurately and calmly.

It isn't a feature comparison, a competitive analysis or a list of the competitor's faults. Those documents have their place, but a rep can't use them mid-call.

Keep one card per competitor. If a rep can't find an answer in ten seconds, the card is too long.

The battlecard template

COMPETITOR: [name]   Owner: [name]
Last checked: [date]   Expires: [date + 90 days]

WHO THEY ARE (two lines, facts only, each with a source)
What they sell, who they target, how they price:

WHEN WE MEET THEM
Segments, deal sizes or regions where they show up:

WHERE WE WIN (each line backed by 3+ deals)
1.
2.
3.

WHERE WE LOSE (be honest)
1.
2.

WALK AWAY WHEN
[the deal pattern where we rarely win]

LANDMINE QUESTIONS (that a fair buyer would want answered)
1.
2.
3.

THEIR CLAIMS AND OUR ANSWERS
Claim: | Answer: | Source and date:
Claim: | Answer: | Source and date:

PROOF WE MAY USE
Customer, result, permission date:

DON'T SAY
[claims that are unproven, out of date or unfair]

Every line about the competitor on the card should trace back to an entry in an evidence log. The log is what lets you defend a claim, update it, or delete it when it expires.

Claim | Source (URL, document or deal) | Date seen | Checked by | Expires | Status

e.g. "Prices per vehicle, 36-month minimum" | their pricing page | 14 Oct 2026 | [name] | 12 Jan 2027 | current
e.g. "No engine-hour reporting for equipment" | lost-deal debrief, buyer quote | 2 Sep 2026 | [name] | 1 Dec 2026 | re-check with release notes

How to build one from win/loss evidence

1. List the deals. Pull every closed deal from the last 12 months where this competitor was involved, won and lost. Fewer than ten deals means you don't have enough evidence for "where we win" yet: say so on the card.
2. Code the reasons. For each deal, record the segment, the deal size and the real reason it went the way it did. Use a short list of reason codes so you can count them.
3. Interview buyers. Within a few weeks of the decision, ask three to five buyers (won and lost) why they chose as they did. Use the guide below. Buyers tell an outsider or a non-sales colleague things they won't tell the rep who lost.
4. Find the pattern. Calculate your win rate by segment. Where it's high, you have "where we win" lines. Where it's very low, you have a "walk away when" line.
5. Write only what three or more deals support. One enthusiastic customer is a story, not a pattern. Keep single anecdotes in the evidence log until they repeat.
6. Check the competitor's side. Confirm their current pricing, packaging and features from their own pages before you write anything about them.
7. Test it with two reps who have recently met this competitor. If they disagree with a line, find out why before you publish.

1. What started your search? What was happening at the time?
2. Which options did you consider, and how did you narrow them down?
3. What mattered most in the final decision? What came second?
4. Where did [winner] do better than the others? Where did they do worse?
5. Was there a moment when the decision became clear?
6. What did you hear about us that turned out to be wrong, or right?
7. What would have changed your decision?
8. Is there anything you wish every vendor had done differently?

Record their words, not your summary. Ask permission before quoting anyone.

Worked example: a battlecard for fleet telematics

Illustrative example. Groundline Telematics, HaulSight and every deal, figure and source below are fictional, to show the method and the level of detail.

The seller: Groundline Telematics (groundline.example) sells GPS tracking and equipment monitoring to construction firms. The competitor: HaulSight (haulsight.example), a fleet telematics vendor built for on-road trucking.

Groundline's product marketer pulled 34 closed deals from the last 12 months where HaulSight was involved:

The coded reasons told the same story. Of the 14 wins, 8 buyers named engine-hour and idle reporting on excavators and loaders, and 4 named jobsite time reports. Of the 20 losses, 8 buyers wanted one vendor for trucks and driver logs, 6 cited HaulSight's lower per-vehicle price, 4 needed a specific accounting integration, and 2 gave other reasons.

That gives the card its most valuable line. The 12 on-road deals took as much sales time as the others and produced two wins. Moving that effort to small mixed fleets, where 9 of 14 deals were won, is worth more than any rebuttal.

Owner: Product marketing   Last checked: 14 Oct 2026   Expires: 12 Jan 2027

WHO THEY ARE
Fleet telematics for on-road trucking: GPS, driver logs, fuel cards.
Priced per vehicle on 36-month contracts, hardware included
(haulsight.example/pricing, checked 14 Oct 2026).

WHEN WE MEET THEM
Contractors whose trucks are tracked already and who now want equipment covered.

WHERE WE WIN
1. Heavy equipment: engine hours, idle time and service reminders for yellow iron
   (named by 8 of 14 won buyers, FY2026).
2. Jobsite time reports for billing and payroll (4 of 14 won buyers).
3. Month-to-month option for fleets under 150 assets (our price list, Oct 2026).

WHERE WE LOSE
1. Buyers who want one vendor for trucks and driver logs (8 of 20 losses).
2. Price per vehicle on large on-road fleets (6 of 20 losses).

WALK AWAY WHEN
The fleet is mostly on-road trucks and driver logs are the main need (2 wins in 12).

LANDMINE QUESTIONS
1. "How will you see engine hours on the excavators that don't have a road VIN?"
2. "If a crew leaves a site early, how would you know before payroll runs?"
3. "What does it cost to add or remove a machine mid-contract?"

THEIR CLAIMS AND OUR ANSWERS
Claim: "One platform for your whole fleet."
Answer: "For trucks, they're strong. Ask to see equipment reporting on one of your
machines during the trial." | Source: their product page, 14 Oct 2026
Claim: "Cheaper per vehicle."
Answer: "Often true on trucks. Compare the cost per machine over 36 months, including
the contract minimum." | Source: their pricing page, 14 Oct 2026

PROOF WE MAY USE
Ridgeway Civil (fictional), 90 machines: approved 3 Sep 2026.

DON'T SAY
"Their hardware is unreliable." (no evidence)
"They don't track equipment." (they added an equipment tag in 2026: release notes, 2 Jul 2026)

What makes this good:

• Every "where we win" line has a count behind it, and the counts come from buyers, not reps.
• The "walk away" line is backed by the worst segment in the data, which saves more time than any talk track.
• The answers to their claims start by agreeing with what's true.
• The "don't say" list catches a claim that used to be true and no longer is.

Landmine questions

A landmine question is one you ask so the buyer discovers a difference themselves, usually by asking the competitor. Done well, it's simply good discovery. Done badly, it's planting doubt about something that isn't real.

The test: would a fair-minded buyer want to know the answer even if you weren't in the deal? If yes, ask it. If the question only works because it implies something false, don't.

Bad landmines hint at problems you can't prove: "Have you asked them about their security issues?" when you know of none. Buyers notice, and the trust you lose doesn't come back.

Using the battlecard in a live deal

"[Competitor] is a good company, and they're strong at [their real strength].

Where we're different is [the one difference that matters to this buyer], which matters because you told me [their own words about the problem].

The best way to see it is to test both on [their hardest real case]. Would that be useful?"

Deal: [account]   Outcome: [won / lost / no decision]   Date:
Competitor(s):
What they claimed about us, in the buyer's words:
What the buyer said decided it:
Which battlecard line helped, or was wrong:

For the objections that come up in competitive deals, such as "your competitor is cheaper" or "we already use someone", see the objection handling guide.

What not to say, and the legal side

This is general information, not legal advice. Have counsel review comparative claims before they appear in written material.

• US: truthful comparisons are allowed, and the bar is the same as for any claim. The FTC's policy statement on comparative advertising encourages naming competitors, as long as the comparison is clear and not deceptive. The FTC judges comparative claims the same way as any other advertising: could it be false or deceptive? Truthful statements that make a competitor look worse are permitted.
• Claims need support before you make them. The FTC expects a reasonable basis for objective claims before they're made. "Faster setup" needs a test or data you could show.
• Competitors can sue. Under the Lanham Act, a business that misrepresents the nature, characteristics or qualities of its own or another's goods or services in commercial advertising or promotion can be sued by anyone who believes they are, or are likely to be, damaged by it. Treat anything a rep says or sends as something that could be quoted back to you.
• UK: comparisons must be objective and verifiable. The Business Protection from Misleading Marketing Regulations 2008 allow comparative advertising only if it isn't misleading, compares products meeting the same need, objectively compares material, relevant, verifiable and representative features (which may include price), and doesn't discredit or denigrate a competitor.

In practice, keep these off the card:

• Superlatives you can't prove ("fastest", "most accurate").
• Facts past their expiry date, especially pricing.
• Rumors about a competitor's finances, layoffs, lawsuits or security.
• Anything from a competitor's confidential documents, such as a proposal a buyer forwards you. Ask counsel before you use it at all.
• Claims about which customers are leaving them, unless the customers said so publicly.

Keeping it current

To find which of your target accounts already use a competitor, look for job postings that name the tool, case studies, and technographic data such as Bebop Insights. Then you know which card a rep needs before the first call.

Before you publish or update a card, check:

• Does every competitor fact have a source and a date inside the last 90 days?
• Is every "where we win" line backed by three or more deals?
• Is there a "walk away when" line?
• Would you be comfortable if the competitor read the card?
• Could a new rep use it in ten seconds mid-call?

Common mistakes

• Writing it from opinion. Reps' beliefs about why they lose are often wrong. Buyers' words are better evidence.
• No dates. An undated claim gets repeated for years after it stopped being true.
• Leading with the competitor. Bringing up a rival the buyer hasn't mentioned spends your time on them.
• Feature grids. A 40-row grid invites a feature fight. Focus on the two or three differences that decide deals.
• Hiding where you lose. Reps find out anyway, in front of the buyer.

Next step: prepare the answers your reps will need when buyers raise price, timing or "we already use someone" with the objection handling guide.