A rep I worked with lost a deal to a competitor he had a battlecard for. The card existed. It lived in a Google Drive folder somewhere, 11 pages, color-coded, built by the product marketing team after a quarter of research. On the call where the prospect said "we're also looking at [competitor], and honestly their pricing looks better," the rep said "let me get back to you on that." He never opened the card. He did not even remember it existed.
That is the whole problem with sales battlecards in one story. Somebody spends weeks building a beautiful document, it gets a launch announcement in the enablement channel, and then it dies in a folder nobody opens after onboarding. The intel was right there. The rep froze anyway, because the card was built to be read at a desk, not used in the middle of a live call.
I have built competitive enablement for a few B2B teams and audited it for more. The pattern is depressingly consistent. The cards exist, the win rate does not move, and everyone blames the reps. The reps are not the problem. The format is.
The adoption gap nobody wants to talk about
Here is the number that should bother every product marketer. According to Crayon's State of Competitive Intelligence, 79 percent of competitive intelligence teams produce battlecards for their sales reps. Only 26 percent of those teams say reps actually use them enough. Three out of four battlecard programs are, by their own admission, shelfware.
Of the teams that build battlecards say reps actually use them enough to matter. The other three quarters spent the research time and got a document nobody opens on a live call.
This is not because the intel is bad. The teams that get adoption right see real results. Among businesses that use battlecards, 71 percent say the cards lifted their win rate, and 93 percent of those say the lift was more than 20 percent. The teams that refresh their cards monthly report win-rate lifts as high as 59 percent. Competitive enablement works. The version that sits in a folder does not.
And competitive deals are not a niche. In the same research, sellers report running into a competitor in 68 percent of their deals. Two out of three times a rep is on a call, there is a "we're also evaluating" lurking in the conversation. If your reps cannot handle that moment cleanly, you are losing winnable deals to a document problem.
Why most battlecards fail
The failures are not subtle once you know what to look for. I see the same four every time.
They are written like reports, not call tools
The average battlecard reads like a research deliverable. Company history, funding rounds, full feature matrix, market positioning, the works. All true, all useless when a VP of Product is staring at your rep waiting for an answer. A rep on a live call has about ten seconds to find the right line. If the answer is buried on page 6 of a document, it does not exist. The card has to be scannable in seconds, not readable in minutes.
They lead with features instead of objections
Most cards open with everything the competitor offers. Reps do not need the competitor's full feature list. They need to know what the prospect is going to say when the competitor comes up, and exactly how to respond. "They're cheaper" is an objection. "They have a mobile app" is an objection. The card should be organized around the sentences a buyer actually says, with a tight, sayable response under each one. Organize by objection, not by feature.
They are built in a vacuum
Enablement and product marketing build the card alone, often without having been on a real sales call in years. The result looks great in Notion and falls apart in front of a skeptical buyer. The reps who are in competitive deals every week know the actual objections, the traps, the lines that land and the ones that get them laughed off. If they are not co-authoring the card, it will be theoretically correct and practically useless.
They go stale and nobody updates them
A competitor changes their pricing on Tuesday. Your battlecard still quotes the old number in March. The rep who trusts the card walks into a deal with wrong information, which is worse than no card at all. Most teams treat updates as a quarterly project that needs research time and approvals, so the card is always weeks behind reality. By the time the new competitor card ships, the deals are already lost.
What a battlecard reps actually use looks like
Strip the card down to what a rep needs in the moment. For each competitor, the whole thing should fit on one screen with no scrolling, and every section should answer a question the rep is about to face.
A one-line "why we win" and "why we lose"
Two sentences at the top. Not a paragraph. "We win when the buyer cares about X and has more than Y users. We lose when they only need Z and price is the only criterion." This frames the entire conversation and tells the rep within seconds whether this is a deal worth fighting for.
Landmines to plant early
The questions your rep should get the buyer asking before the competitor demos. If you know the competitor is weak on data exports or has a painful implementation, the rep plants that question in discovery: "How are you planning to get your historical data out if you ever switch?" These work best early, which is exactly why discovery and competitive prep belong together. I wrote about the questions that move deals in the discovery call guide, and the best landmines come straight out of that conversation.
Objection responses in the rep's own voice
The core of the card. Each common objection a buyer raises about the competitor, with a short, sayable response underneath. Not marketing language. The actual words a rep can say out loud without sounding like they are reading a brochure. If a rep cannot say the line naturally on a call, it does not belong on the card.
Proof, not adjectives
One customer who switched from the competitor and why. One number. A specific quote. Buyers discount adjectives and remember stories. "A 60-person team switched from them last quarter because their reporting could not handle multi-currency" beats "we offer superior reporting" every time.
If a rep cannot find the right line in under ten seconds mid-call, the card does not exist.
Comprehensive is the enemy of adoption. The teams winning competitive deals are not the ones with the most thorough cards. They are the ones whose reps can find the right piece of the right card before the moment passes.
Build cards by role, not one card for everyone
A BDR and an AE need completely different things from the same competitor. The BDR needs qualification and discovery angles: how to spot the competitor early and what questions to plant. The AE needs objection handling and proof for the middle of the deal. A sales engineer needs the technical differentiation that holds up under a deep evaluation. One card trying to serve all three serves none of them well.
You do not need three separate documents. You need one card with role-tagged sections, so each person sees the part that matters to their stage. This is the same logic behind a sales playbook reps actually use: match the content to the moment, not to a generic everyone.
How to build the first set in a week
You do not need a quarter of research to ship a useful card. Start with the deals you are already losing and work backward.
The closed-lost data in step one is the part most teams skip, and it is the cheapest research you have. Your CRM already knows which competitors cost you deals and why. If your closed-lost reasons are a mess of free-text and blanks, that is its own problem worth fixing first, and it ties straight into honest win/loss analysis. Clean reasons in, useful cards out.
Where battlecards live and how to keep them current
A card in a folder is dead. A card in the deal record is alive. The single biggest adoption lever is putting the card where the rep already is. If you run HubSpot or Salesforce, the competitor field on the deal should surface the right card automatically, so the rep sees it the moment they tag the competitor. Getting that wiring right is exactly the kind of work we do on the CRM and RevOps side: making the system put the right thing in front of the rep without anyone hunting for it.
The other half is keeping cards fresh without it becoming a full-time job. Competitor pricing pages, G2 reviews, job postings, and product changelogs all signal when something has moved. You can watch those sources automatically and route an alert to whoever owns the card the moment a competitor changes pricing or ships a feature. We build these monitoring flows with tools like Clay for signal collection and n8n for the automation, which is part of our AI and automation work. The point is simple: do not wait for a quarterly refresh cycle. Update the card the day the intel changes, because a stale card actively loses deals.
Battlecards your reps never open?
Book a free 30-minute audit and we'll show you how to turn shelfware into cards that live in the CRM and move your win rate.
Book an audit →Measure usage and wins, not page count
The last mistake is measuring the wrong thing. Teams count how many cards they shipped, which tells you nothing. The two numbers that matter are usage and outcome. Are reps opening the card on competitive deals? And do deals where the card got used close at a higher rate than deals where it did not? If you tag competitive deals in the CRM and track which ones touched a battlecard, you can answer both. That relationship between usage and win rate is the only proof that the program works, and it is the argument that gets you the budget to keep doing it.
Tie this back to your broader competitive motion and it compounds. The same objections that show up in your cards should feed your messaging, your go-to-market positioning, and the discovery questions reps ask. Competitive intel is not a document you ship once. It is a loop: deals teach you what buyers say, the cards capture the best responses, and the wins tell you which responses work.
Get the format right and the rest follows. One screen, organized by objection, written in the rep's voice, living in the CRM, updated the day intel moves. That is a much smaller thing than the 11-page masterpiece, and it is the version that actually wins deals.
Frequently asked questions
What should a sales battlecard include?
Keep it to one screen per competitor: a one-line "why we win" and "why we lose," two or three landmines for the rep to plant early, the common buyer objections with short responses in the rep's own voice, and one concrete proof point like a customer who switched. Skip the company history, funding rounds, and full feature matrix. Those make the card thorough and unusable. The test is whether a rep can find the right line in under ten seconds during a live call.
Why don't sales reps use battlecards?
Usually because the card is built like a report instead of a call tool. It is too long, organized by feature instead of by objection, written in marketing language reps cannot say out loud, buried in a folder they have to leave their workflow to reach, and often out of date. Crayon's research found that 79 percent of teams produce battlecards but only 26 percent say reps use them enough. The fix is format and placement, not nagging the reps.
How often should you update battlecards?
Update them the day the intel changes, not on a quarterly schedule. A competitor that changes pricing or ships a feature makes your card wrong immediately, and a wrong card is worse than no card. Teams that refresh monthly report win-rate lifts as high as 59 percent. Set up monitoring on competitor pricing pages, review sites, and changelogs so you get alerted when something moves, then push the update right away.
Should battlecards be different for BDRs and AEs?
Yes. A BDR needs qualification and discovery angles to spot and frame the competitor early. An AE needs objection handling and proof for the middle of the deal. A sales engineer needs technical differentiation. You do not need separate documents, just one card with role-tagged sections so each person sees the part relevant to their stage. A single card built for everyone ends up useful to no one.
Where should sales battlecards live?
Where reps already work, which means inside the CRM on the deal record and in Slack or Teams, not in a separate documents folder. The strongest setup surfaces the right card automatically when a rep tags a competitor on the deal, so there is no hunting. If a rep has to leave their workflow and remember a folder location to find the card, adoption collapses. Accessibility is the single biggest driver of whether the program works.
If your battlecards are sitting in a folder nobody opens while you keep losing competitive deals, the cards are the problem, not your reps. Book a free audit and we will help you rebuild them into something that lives where the work happens and actually moves your win rate.