How to Build Sales Battlecards That Your Team Will Actually Use

Most sales battlecards fail not because they contain bad information, but because they're written for the person who built them, not the rep who needs to use one thirty seconds before a discovery call. A ten-page competitor analysis is not a battlecard. A one-page, opinionated, objection-ready reference sheet is. The difference determines whether your competitive enablement actually changes deal outcomes — or just collects views on your internal wiki.

What makes a sales battlecard actually get used?

The single biggest predictor of battlecard adoption is length. If a rep can't extract what they need in under sixty seconds, they won't open it during a live deal — and that's the only moment it matters. Every battlecard you build should fit on one printed page or one screen without scrolling.

The second predictor is source. Battlecards built exclusively by product marketing — without rep input — tend to emphasise feature comparisons that reps rarely need. The objections that actually appear in deals are often not the ones that appear in competitor teardowns. The reps closing the most deals against a specific competitor know things that aren't in any product brief. Build with them, not just for them.

Third: storage location. Salesloft's research on competitive enablement consistently shows that reps default to whatever is already open — their CRM, Slack, email. A battlecard living in a separate wiki that requires a login and a search is a battlecard that doesn't exist for most of your team.

"We had twelve battlecards in Confluence. Beautiful, thorough, completely ignored. We rebuilt them as one-pagers pinned inside Salesforce opportunities and adoption went from maybe 10% to over 70% in a quarter."

— VP of Sales Enablement, 80-person B2B SaaS company

What should a competitive battlecard template include?

A strong competitive battlecard template has six sections — nothing more. Each section should be as short as possible while still being actionable. Here's the structure:

1. Competitor snapshot (2–3 sentences)

One paragraph: what they do, who they target, and how they position themselves. Not a biography — just enough context for a rep who hasn't encountered this competitor before. Include their approximate pricing tier if known.

2. When you'll see them (triggers)

List the deal types, company sizes, or use cases where this competitor comes up most often. "Usually appears in mid-market deals with existing HubSpot infrastructure" is more useful than "a major competitor." This helps reps anticipate the fight before it starts.

3. Your top three differentiators against them

Three only. Forced prioritisation is the point. If you list twelve differentiators, reps will remember zero of them. These should be the three claims that have actually moved deals in your favour — sourced from win interviews, not from your product deck.

4. Their three most common objections — with scripted responses

Write the objection exactly as a prospect says it, then write a 2–3 sentence response the rep can say verbatim or adapt. "They say X. You say Y." Do not write essay-length responses. The rep needs something they can actually say, not something they need to paraphrase in real time.

5. Landmine questions

One or two questions the rep can ask that surface a known competitor weakness without sounding like an attack. "How are you handling [specific pain point] today?" when you know the competitor's product has a documented limitation in that area. This is often the highest-leverage section — a well-placed discovery question does more than any pitch claim.

6. Deal intelligence field

A blank or templated area where the rep logs what they learn: pricing quoted, specific objections raised, what ultimately drove the decision. This section feeds your next battlecard update. Without it, institutional knowledge about each competitor stays siloed in individual reps' heads and leaves when they do.

How do you find companies that are already using your competitors?

Building the battlecard is only half the problem. The other half is knowing which prospects to actually deploy it against. You can't run a competitor-targeted sequence without a list of companies you know are using that competitor right now.

The most scalable method is technology signal data. Companies that list a competitor's product in job postings, or that show the competitor's tracking code in their tech stack, are confirmed active users — not just companies that might use them. This data is available at scale and refreshes continuously, which matters because tech stacks change.

This is what Stealery was built for: you type in a competitor name and get a list of every company currently using it, filtered by company size, location, and hiring signals. Instead of guessing which accounts to prioritise for a competitor displacement campaign, you're starting from confirmed intent. The battlecard you built for that competitor now has a ready-made list to go with it.

The combination matters. A battlecard without a targeted list is a training document. A targeted list without a battlecard produces generic outreach that loses to incumbents. Together, they form an actual displacement campaign.

How do you build battlecards from win/loss data?

Win/loss analysis is the most underused source of competitive intelligence in B2B sales. According to Gartner, companies that conduct structured win/loss interviews achieve win rates 50% higher than those that don't — yet fewer than a third of B2B sales organisations do them consistently.

The process for building a battlecard from win/loss data is straightforward:

1. Pull your CRM data. Filter closed-lost deals by competitor and look for the three or four names that appear most often. These are your highest-priority battlecard targets.
2. Interview the rep who worked the deal. Ask specifically: what objection did the prospect raise in favour of the competitor? What did you say? Did it work? What would you say differently? This produces the raw material for your objection responses — in the actual language deals happen in.
3. Interview deals you won. Ask what ultimately shifted the prospect away from the competitor. These answers reveal your real differentiators — not the ones on your website, but the ones that move money.
4. Check your closed-won data for landmines. When you won, what question or moment exposed the competitor's weakness? That becomes a landmine question on your card.
5. Validate with two or three top performers. Before publishing, show the draft to your best closers against that competitor. If they say "we never actually hear that objection" or "the real differentiator is X, not Y" — update the card. Top performers' implicit knowledge is the most valuable thing a battlecard can encode.

What are common battlecard mistakes that reduce adoption?

The pattern that kills most competitive enablement programs is building battlecards as proof of research rather than tools for use. Here are the mistakes that show up most often:

Too long, too balanced

A battlecard that lists both the competitor's strengths and weaknesses in balanced detail is a competitor analysis in disguise. Reps don't need balance — they need to know what to say. Be opinionated. The card should read like advice from your best closer, not a Wikipedia entry.

Feature comparison over objection handling

Most battlecard templates lead with a feature-by-feature matrix. This is the section reps use least. What they actually need is help when a prospect says "but [competitor] does X" — and the scripted response to that. Lead with objections, not features.

No named owner

If nobody is responsible for keeping a battlecard current, it will be outdated within two product cycles. Assign each card to a specific person — usually someone in product marketing or sales enablement — with a quarterly review on the calendar. When a competitor announces a pricing change or a new feature that directly addresses one of your differentiators, that person updates the card within the week.

Building cards for every competitor at once

The first battlecard program that tries to cover all twelve competitors in the market produces twelve mediocre cards and exhausts the team that built them. Start with the two or three competitors that appear in more than 20% of your lost deals. Build those cards properly. Get adoption. Then expand.

How do you measure whether battlecards are working?

There are three metrics worth tracking for a competitive battlecard program. Win rate against specific competitors is the primary outcome — if your win rate against Competitor A is 35% before the battlecard and 48% six months later, the program is working. This requires clean CRM data on which competitor was involved in each deal.

The second metric is usage rate. Most CRMs or sales enablement platforms can log when a document is accessed. If fewer than 40% of reps are opening the relevant battlecard before or during competitive deals, the adoption problem needs solving before you can measure impact. Usage is a leading indicator; win rate is lagging.

The third is deal review feedback. In weekly pipeline reviews, ask reps which card they pulled on each competitive deal. What did they use? What was missing? What didn't land? This qualitative feedback loop is what keeps cards accurate over time — and it signals to reps that you expect them to use the cards, which itself drives adoption.

Battlecard programs that track all three — win rate, usage, and feedback — tend to compound over time. The cards get sharper each quarter, reps trust them more, and the win rate improvement becomes self-reinforcing. Programs that track none of these tend to plateau after the initial launch energy fades, because there's no signal telling the team whether the cards are working or which ones to improve first.

For a deeper look at building the prospect list that goes with each card, see the Competitor Intelligence section of the blog, or browse all Stealery articles for more on competitive sales tactics.