Battlecards Are Dead. Build Briefs On Demand.
A static battlecard is stale before sales opens it. Build on-demand, per-deal competitor briefs for proposals and board decks instead. Here's the framework.
Want this inside your company?
Tell us the outcome you need, and we'll show you what we can build.
Problem: Your team maintains a folder of competitor battlecards. They were accurate the quarter they were written. Now a rep is on a live deal, or you're building a board deck, and the one thing you need, how you beat this competitor, right now, isn't in the PDF, because the competitor changed their pricing page last month and nobody updated the card.
Quick Win: Stop maintaining static battlecards as your primary competitive asset. A battlecard is a standardized one-pager built on a calendar; a competitor brief is generated on demand for the specific deal or deck in front of you, with every fact reframed around your wedge. The distinction matters because competitive intelligence is perishable, 65% of sales opportunities are competitive for the average software company, yet 58% of CI professionals say keeping battlecards updated is a struggle. The card is stale before the rep opens it.
Want this inside your company?
Tell us the outcome you need, and we'll show you what we can build.
Competitive intelligence is perishable. Quarterly PDFs are already stale.
Here's the uncomfortable math on the battlecard model. Gartner surveyed 227 chief sales officers and found their organizations completed an average of four transformations in the past 12 months, pricing changes, repackaging, repositioning, new segments. That's the ground shifting roughly every 90 days, and that's just your side. Your competitors are moving on the same clock.
Now overlay how battlecards actually get maintained. Someone owns them as a side-of-desk task. They refresh a batch when they can, ship the PDF, and move on. By the time a rep pulls it into a live call, the "current pricing" line is two competitor updates old and the "they don't have SSO" objection was closed out in a release three weeks ago.
A battlecard reflects reality from whenever someone last had time to update a file. A live deal needs reality from this week. Those two dates are almost never the same, and the gap is exactly where deals get lost, the buyer who did their homework notices you're a step behind, and quietly loses confidence.
The problem isn't that battlecards are a bad idea. It's that a static asset can't win a moving fight.
Battlecard vs. competitor brief: the distinction most teams miss
Most teams treat "battlecard" and "competitor brief" as the same thing. They're not. One is a format built for the average case; the other is built for the case in front of you.
| Static battlecard | On-demand competitor brief | |
|---|---|---|
| When it's built | On a calendar (quarterly, if you're lucky) | The moment a deal, proposal, or deck needs it |
| What it covers | A competitor, in general | This competitor, for this deal or this board question |
| Freshness | As old as the last refresh | Pulled from current public signals |
| Framing | Feature-by-feature facts | Every fact reframed around your wedge |
| Primary reader | Whoever opens the folder | A named rep on a named deal, or your board |
| Failure mode | Silently goes stale | Only as good as its trigger and its "so what" |
The incumbent playbook (Klue and Crayon both define the battlecard as a concise, standardized enablement document) is genuinely useful for onboarding a new rep or covering a competitor you see occasionally. Crayon's own guidance has moved toward battlecards that are "real-time, role-specific, dynamic" rather than a static one-pager, which is the tell: even the category leaders are describing something that no longer looks like a PDF.
The brief is what the battlecard becomes when you stop pretending a calendar can keep up with a market. Same DNA, different refresh model. Instead of "here's our card on Competitor X," it's "here's the brief for the Acme deal, generated today, built around the two things Acme actually cares about."
The 7 sections every per-deal competitor brief needs
A brief is not a data dump. A fact about a competitor is worthless on its own; a fact reframed around your wedge wins the deal. That reframe is the whole job, and it's what a static card almost never does. Here's the structure that forces it.
-
The deal context. Who's the buyer, what do they care about, and which competitor is actually in the room. A brief with no trigger is just a battlecard wearing a costume. This one line decides everything below it.
-
Current competitor snapshot, dated. Their positioning, pricing posture, and recent moves, each stamped with the date pulled. If it isn't dated, a reader can't tell fresh intel from a guess. Freshness is a feature you make visible.
-
Where they genuinely win. Name it honestly. Reps who pretend the competitor has no strengths get caught by informed buyers and lose trust for the rest of the call. Naming the strength is how you earn the right to reframe it.
-
Your wedge, the "so what." For every competitor fact, the sentence that turns it into your advantage. "They're cheaper" becomes "they're cheaper because onboarding is self-serve, which is why their mid-market churn shows up in their own review pages." This section is the difference between intelligence and trivia.
-
Objection handling for this competitor. The two or three things this competitor's reps say about you, and the clean response: proof points, not adjectives.
-
Landmines to set. The questions that expose the competitor's real weakness without you ever badmouthing them. "Ask them how their SSO provisioning handles offboarding" beats "they're insecure."
-
The one-line takeaway. If the reader remembers nothing else, this is the sentence they carry into the room. Every good brief resolves to a single defensible claim.
Notice what sections 4 and 5 have in common: they're useless unless someone did the translation work. That translation is perishable, it depends on the competitor's current pricing, current release notes, current review-site language. Which is precisely why it can't live in a quarterly file.
Build briefs only for the competitors in your lost-deal data
The instinct when you kill battlecards is to build briefs for every competitor you can name. Don't. That just recreates the maintenance treadmill in a new format.
Run the win-loss analysis first. Look at the deals you actually lost, and to whom. In most B2B pipelines, three or four competitors account for the overwhelming majority of competitive losses, and a long tail of names shows up once and never again. Build deep, on-demand briefs for the handful that keep beating you. For the long tail, a thin generic card is fine, you're not losing a board seat over them.
This is the same discipline as a bottleneck diagnosis: rank by cost to the business, then fix in order. Competitive intelligence that isn't tied to a deal you're actually losing is a hobby. Anchoring your briefs to lost-deal data is what keeps the effort proportional to the money at stake, and it's why the same buying-signal discipline that surfaces qualified leads works here: you build for the signal, not for completeness.
The board-deck version: a benchmark scorecard, not a talk track
A per-deal brief and a board brief are cousins, not twins. Your board doesn't need objection handling. It needs a benchmark scorecard: where you're ahead, where you're exposed, and what you're doing about each gap, scored across the functions the board actually cares about: pricing, product surface, go-to-market motion, hiring velocity.
The build is the same discipline pointed at a different reader. Pull the competitor's current public footprint: pricing pages, job posts and hiring signals, funding, product changelog, the language on their review pages. Score each function, and date the whole thing. A board deck with a scorecard dated this month reads as command of the market. One built on last quarter's battlecards reads as homework you didn't finish.
This is exactly the kind of recurring, high-standard output that's better produced on demand than rebuilt by hand every quarter, the format is stable, only the facts change.
Where this breaks: thin public data and the depositioning trap
On-demand briefs are not magic. Two failure modes are worth naming honestly, because pretending they don't exist is how you ship a bad brief.
Thin public data. For a well-covered public competitor, the signals are everywhere. For a quiet private competitor with no pricing page, no changelog, and a threadbare careers section, an on-demand brief can only be as good as what exists to pull. When the public footprint is thin, the honest brief says so, "low-confidence, based on limited public signal", rather than inventing detail to fill the template. A confident-sounding brief built on nothing is worse than no brief, because someone will repeat it in a room.
The depositioning trap. The wedge reframe is powerful, which makes it easy to overreach into badmouthing. Buyers punish this. The line is simple: a landmine exposes a real weakness through a question the buyer asks themselves; depositioning is you making a claim the buyer has to take on faith. The first builds trust, the second burns it. If your brief's "so what" only works when the competitor isn't in the room to respond, it's not intelligence, it's spin, and informed buyers smell it.
The third quiet failure: a brief that's never triggered. If the workflow to request one is slower than winging it, reps will wing it. On-demand only beats static if "on demand" is genuinely fast.
The showable artifact
Here's the shape of a single competitor brief, anonymized and illustrative (the format, not real intel):
| Section | What it holds (example shape) |
|---|---|
| Deal context | Mid-market buyer, security-led evaluation, Competitor X in final two |
| Snapshot (dated) | Current pricing tier, latest release, recent repositioning, each stamped |
| Where they win | Faster self-serve onboarding, lower entry price |
| Your wedge ("so what") | Their price is low because support is self-serve, surfaces as churn in their own reviews |
| Objection handling | Their "we're cheaper" → your total-cost and retention proof points |
| Landmines | "Ask how their offboarding handles data retention" |
| One-line takeaway | "We lose on sticker price, we win on the second year" |
The values are made up to show the structure. A real brief runs on the competitor's actual, current facts and your actual proof points, and it's generated the day the deal needs it, not the quarter it was scheduled.
Frequently asked questions
Isn't this just a battlecard with a new name?
No. A battlecard is built on a calendar to cover a competitor in general; an on-demand brief is generated for a specific deal or board question, with every fact reframed around your wedge. The format overlaps, both name strengths, objections, and proof points. The refresh model is the entire difference, and it's the thing that decides whether the asset is right when a rep actually needs it.
How do I build competitive intelligence for a board deck specifically?
Build a benchmark scorecard, not a sales talk track. Pull each competitor's current public footprint, score them across the functions your board cares about (pricing, product, go-to-market, hiring), reframe each fact as a "so what" for your strategy, and date the whole thing. Boards reward command of the current market; a scorecard dated this month delivers it, last quarter's battlecards don't.
Which competitors should I build deep briefs for?
The three or four that show up in your win-loss analysis as the ones actually beating you. Build deep, on-demand briefs for those and thin generic cards for the long tail. Competitive intelligence that isn't anchored to a deal you're losing is effort spent where the money isn't.
If your team is maintaining battlecards that go stale faster than anyone can update them, the fix isn't a better PDF, it's changing what triggers the intel and who it's built for. We install on-demand competitive intelligence inside companies: per-competitor and per-deal briefs, plus benchmark scorecards that go straight into proposals and board decks, built from current public signal and reframed around your wedge. You keep the output, and it keeps producing after we hand it over. If your last board deck leaned on last quarter's cards, let's talk.
Want this inside your company?
Tell us the outcome you need, and we'll show you what we can build.
Buying Signals vs. Intent Data
Intent data is the most overrated tool in the sales stack. Public signals (a hire, a raise, an expansion) are verifiable. The decay windows that make them convert.
Win-Loss Analysis: The Cheapest Competitive Intel You Are Not Running
Win-loss analysis is the free competitive intel your CRM is lying about. The interview method, the 6 questions, and why 85% of loss reasons are wrong.