BlogSales enablement

Sales enablement

How to get your sales team to actually use battlecards

You spent two weeks building a battlecard. Reps opened it twice. Here is the honest reason your battlecards get ignored, and the four changes that fix adoption inside a quarter.

By Devin PatelMay 1, 20267 min read

If your battlecards are not getting used, the problem is almost never the content. It is the format, the delivery, and the freshness. Sales reps will read a 90-second one-pager that lives where they already work. They will not read a 12-page PDF that lives in Notion behind two clicks and a login. This guide covers the four levers that move adoption.

The honest reasons reps do not use your battlecards

Three patterns show up in every sales enablement conversation we have with PMMs.

  1. 1The battlecard is too long. Anything past one screen on a phone gets skimmed at best, abandoned at worst. Reps prep for calls with 30 to 60 seconds of attention. A document that requires more is a document that never gets opened.
  2. 2The battlecard is stale. Reps tried it once, found one thing that was wrong (an outdated price, a feature that shipped, a customer that churned), and stopped trusting the document. Trust is binary.
  3. 3The battlecard does not live where reps work. If a rep has to leave Salesforce or Slack to find it, they wing it. Every extra click is a 30 percent drop in usage.

Lever 1: One page. Mobile first. Always.

If your battlecard is more than one screen on a phone, you are guaranteed to lose adoption. Compress ruthlessly.

The format that works:

  • Top of page: a 2-line summary of the competitor (who they are, where they win)
  • Middle: 3 landmine questions a rep can ask the prospect
  • Middle: 3 objection-response pairs (the things the prospect will say, and the one line that handles each)
  • Bottom: pricing intel with actual numbers

That is it. No SWOT analysis. No org chart. No marketing deck slides. Anything that does not directly help the rep on a 30-minute call gets cut.

Lever 2: Make the link the unit of distribution

Reps do not navigate to dashboards before calls. They open Slack or Salesforce, search for the competitor name, and click the first thing. Whatever shows up is what they use.

So the goal is to make sure the first thing they find is your battlecard. Three concrete steps:

  1. 1Generate a public share URL for every battlecard. No login required. No seat-based access controls. Just a link.
  2. 2Pin those links in your sales team's Slack workspace under a #competitors channel, organized alphabetically. Use Slack canvases or pinned messages.
  3. 3Drop the same link into the relevant Salesforce account record's notes field. When a rep opens an account, the battlecard is one click away.

If you have a sales enablement platform like Highspot or Seismic, the public share link works there too. The point is link-based distribution, not platform-specific integration.

Lever 3: Update the battlecard the day a competitor changes

The fastest way to lose rep trust is for them to deliver a talk track from the battlecard, only to have the prospect say 'that is not their pricing anymore.' One stale data point is enough to make the rep stop opening the document.

Manual battlecard updates have a maximum cadence of about every 30 days, because that is what one human can sustain. Real competitive activity (pricing changes, feature launches, positioning shifts) happens weekly. The math does not work.

The fix is automation. Either a tool that auto-regenerates battlecards when competitor pages change, or a process where you manually scrape every competitor's homepage, pricing page, and changelog every Monday and update only the sections that need it.

Lever 4: Measure adoption and feed back the data

Most PMMs cannot answer the question 'how many times did sales open the Klue battlecard last month?' That is a fixable problem.

Public share URLs give you view counts. View counts let you do three things:

  • Identify which battlecards get used (and which are wasted effort, so you can stop maintaining them).
  • Identify which reps use battlecards (and which need a coaching nudge).
  • Tie views to deal outcomes. If reps who opened the Klue battlecard before a call won 60 percent of those deals and reps who did not won 30 percent, you have proof of value the VP of Sales will internalize.

Without the data, the conversation about battlecard adoption is anecdote. With it, you have a metric.

What to do this week

  1. 1Pick your top 3 competitors. Compress each battlecard to one page. Test the format on the newest AE on your team: hand them the doc, give them 60 seconds, ask them to role-play an objection. If they cannot, cut more.
  2. 2Generate or get a public share link for each. Drop the links into Slack and Salesforce.
  3. 3Set a calendar reminder for every Monday at 9am to scan competitor changes (or use a tool that does it automatically).
  4. 4Track view counts for 30 days. If usage is below 5 opens per battlecard per week, the format is still wrong. Compress more.

Frequently asked

Questions worth answering

How long should a battlecard be?
One page. Mobile first. If a rep cannot get a usable talk track in 30 to 60 seconds, the battlecard is too long. Compress until they can.
Should battlecards live in Notion, Confluence, or a sales enablement tool?
It does not matter where they live as long as the public share link is what reps use. Reps do not navigate to dashboards before calls. They open Slack and click the first link they find. Make your battlecard that link.
How do I track battlecard adoption?
Use public share URLs that have view-count tracking built in. Modern CI tools (Clinch, Klue, Kompyte) all expose view counts on shared battlecards. Without view counts, you cannot prove ROI to the VP of Sales.
What is the most underrated battlecard section?
Landmine questions. Three questions a rep can ask the prospect that surface a weakness in the competitor without attacking. Reps love them because they are conversational and high-leverage. Most battlecards skip them.
How often should I update battlecards?
The day the competitor changes anything material (pricing, packaging, major feature). For most B2B SaaS competitors, that means weekly check-ins on homepage, pricing page, and changelog. Automation is the only way this is sustainable.

Stop writing battlecards from scratch

Clinch does the CI work so you can do the rest of your job.

Snapshots in under two minutes. Auto-updating battlecards. Weekly digests your team will actually read. 79 dollars per month.

Ready when you are

Start knowing.

Setup takes under 3 minutes. No credit card required.

Start free