Sales Battlecard Template: 7 Must-Have Sections

A useful sales battlecard has seven components: a one-line competitor summary, their ideal-fit buyer (so reps know when they're likely to lose), a side-by-side capability comparison anchored to two or three deal-critical criteria, verbatim landmines to plant during discovery, the three objections you'll actually hear with tested responses, pricing posture and discount triggers, and a "walk away" section that tells reps when to disqualify. Everything else is decoration. If a rep can't glance at the card during a live call and change what they say in the next 30 seconds, the card has failed.

Start with the competitor's best pitch, not yours

Most battlecards open with a chest-beating summary of why the home team wins. Flip it. The first block should be the competitor's own positioning, in their words, pulled from their homepage and last two earnings calls or funding announcements. Two or three sentences.

Why this order matters: reps who can articulate the competitor's pitch back to a prospect immediately build credibility ("Yes, that's exactly how they describe it"). Reps who can't sound like they're reading from a script written by someone who's never lost a deal.

Underneath that, add a single line: "They win when…" Fill it in honestly. Examples that actually help a rep in the moment:

• "They win when the buyer is a 50-person SaaS team already using HubSpot and doesn't need custom object modeling."
• "They win when procurement leads the process and the buyer has under six months to deploy."

If your card can't finish that sentence honestly, the whole document is a marketing brochure.

The capability grid should compare three things, not thirty

The most common battlecard failure is the feature matrix with 40 rows of green checkmarks. Reps don't read it. Prospects don't care about 37 of the rows. Pick the two or three capabilities that decide deals in your ICP and compare those, in plain language, with a clear verdict.

A hypothetical example. Say you sell a revenue intelligence platform and your main competitor is Gong. Your grid isn't 30 features. It's:

| Deal-critical capability | You | Competitor | |---|---|---| | Call recording accuracy on non-English calls | Native support for 14 languages | English-first, others in beta | | Time to first insight after implementation | Under 2 weeks with template library | 6–8 weeks typical | | Integration with custom Salesforce objects | Native, no middleware | Requires paid connector |

Three rows. Every row is something a buyer asked about in the last quarter's lost deals. The rest goes in an appendix or, better, gets deleted.

Landmines are the highest-leverage section

A landmine is a question your rep plants during discovery that will detonate later, when the buyer is evaluating your competitor. Done well, this is the single highest-ROI element on the card. Done badly (or omitted, which is the norm), it's the reason your reps get outsold by an inferior product.

Write landmines as verbatim questions, not concepts. Bad: "Ask about their multi-language support." Good: "Ask them: 'If we run our EMEA QBRs in French and German, will your product summarize those calls in the same dashboard as our US calls, or in separate reports?'"

The specificity matters because it forces the competitor to either lie, hedge, or admit a gap. Any of those outcomes is a win. A generic prompt lets the competitor pivot; a precise, buyer-plausible question boxes them in.

Aim for five to seven landmines per competitor, each tied to a real weakness that shows up in their sales cycle. Refresh quarterly because good competitors close gaps.

Objections and pricing: give the exact words

This section fails when it reads like a philosophy essay. Reps under pressure on a live call don't want frameworks. They want a sentence they can say.

For each of the top three objections you hear about this competitor, include:

1. The objection in the buyer's likely words. ("We're already using Competitor X and switching feels risky.")
2. A first response designed to reframe, not rebut. ("Most teams that switched from X to us weren't unhappy with X's core product. They hit a wall on [specific thing]. Is that something you've run into, or is this more about consolidating tools?")
3. A proof point that isn't a customer logo wall. A specific outcome from a named customer segment ("mid-market fintech teams typically see…") is more useful than a generic case study link.

For pricing, tell reps two things: your posture (do you match, hold firm, or lead with a premium justification) and the specific discount triggers that are approved without escalation. If a rep has to guess whether a 15% multi-year discount is allowed, the card isn't doing its job.

Include a "walk away" section

This is the part battlecards almost always miss. Tell reps when to disqualify. If the competitor genuinely wins in a specific segment, say so, and route the rep to a better use of their time.

A concrete version: "If the prospect is under 25 employees, has no dedicated RevOps hire, and their primary use case is basic call recording, we lose this deal 8 times out of 10. Qualify hard on the RevOps question in the first call."

This does two things. It saves pipeline hours on unwinnable deals, and, more importantly, it earns the card credibility with reps. A document that admits its own limits gets used. A document that pretends every deal is winnable gets ignored after the first lost forecast.

Format so a rep can use it in 15 seconds

The physical format matters more than the content quality if reps can't access it mid-call. Two rules that hold up:

• One page per competitor, maximum. If it's longer, it won't get read. Put depth in linked appendices for the reps who want it.
• Live in the CRM, not a wiki. A battlecard buried in Notion or Confluence gets consulted the first week and forgotten. A card that surfaces automatically on an opportunity when the competitor field is set gets used on every deal.

The teams that get real lift from battlecards treat them as living documents with a named owner (usually product marketing or sales enablement) and a quarterly refresh tied to win-loss interviews. The teams that don't treat them as a launch-and-forget asset get exactly the outcome you'd expect.

The takeaway

• Rewrite your top-competitor card this week using the seven-component structure: competitor pitch, "they win when," three-row capability grid, verbatim landmines, top three objections with scripted responses, pricing posture, walk-away criteria.
• Pull the landmines directly from your last ten losses to that competitor. If you can't name ten, run the win-loss interviews before writing the card.
• Move the cards out of your wiki and into the CRM opportunity view, triggered by the competitor field. Adoption is a distribution problem, not a content problem.
• Assign one owner and put a quarterly refresh on the calendar. A stale battlecard is worse than none, because reps quote outdated claims to prospects.