What is a Competitive Intelligence battlecard — and what should it actually contain?

Every sales team has battlecards. Most of them sit in a shared drive, unread, built from public sources that the competitor already knows about. A battlecard that does not change how a rep competes in the room is not a battlecard. It is a document. Here is the cognitive science behind the difference — and the anatomy of one that works.

The competitive intelligence battlecard has become standard equipment in B2B sales organisations. Virtually every team competing in a crowded market has them. A 2022 survey by Crayon found that 71% of sales teams reported using battlecards in their competitive process.¹ The same survey found that fewer than half of those teams rated their battlecards as effective.

The gap between prevalence and effectiveness is not accidental. It is structural. Most battlecards are built from the wrong data, designed without reference to how sales cognition works under competitive pressure, and treated as information repositories rather than decision-support instruments. Understanding what a battlecard is actually for — at the level of cognitive science rather than sales process convention — is the prerequisite for building one that changes outcomes.

What a battlecard is — and what it is not

A competitive intelligence battlecard is a structured, concise document designed for use at a specific point in a competitive deal cycle: the moment a named competitor enters the conversation. Its function is not to inform a sales rep about a competitor in the abstract. It is to change what that sales rep says and does in the next 20 minutes of a live deal.

That functional definition has direct implications for design. A tool used under the time pressure, social pressure, and cognitive load of a live sales interaction has entirely different design requirements from a research report read at a desk on a Tuesday afternoon. The research on this distinction is unambiguous — and almost entirely ignored in how most battlecards are built.

RESEARCH CONTEXT

Cognitive load theory, developed by John Sweller (1988) and extensively applied in educational and decision-support research, establishes that working memory has a fixed capacity — estimated by Miller (1956) at seven items plus or minus two — that degrades further under stress and time pressure.2 A battlecard that requires a sales rep to process more than seven discrete action points before responding to a competitive objection has exceeded the cognitive capacity available in that moment. The excess information is not filtered and applied selectively. It is simply not processed.

The practical implication is direct. A battlecard is not a better research report. It is a fundamentally different artefact — one designed around the cognitive constraints of the person using it in the moment they need it most.

What most battlecards get wrong

The failure modes in battlecard design are consistent across industries and organisations. They stem from the same root cause: battlecards are typically built by people who understand the competitor rather than people who understand how the sales rep will use the document under pressure.

The column on the left describes what competitive monitoring software produces. It is not useless — it establishes baseline knowledge. But it does not answer the question a sales rep is asking at the point of competitive pressure: what do I say next?

The cognitive science of retrieval under pressure

Sales conversations are not information-processing environments. They are social performance environments with competing cognitive demands: active listening, relationship management, real-time objection analysis, and response formulation — all occurring simultaneously under the social pressure of a professional evaluation.

Research by Brainerd and Reyna on gist memory — the psychological mechanism by which the brain retrieves information under conditions of stress and divided attention — is directly relevant to battlecard design.³ Gist memory prioritises the essential meaning of information over its precise detail. Under cognitive load, the brain retrieves categorical patterns and simplified representations rather than exact content.

The practical implication: a sales rep under competitive pressure in a closing call will not recall that a competitor’s G2 score dropped from 4.3 to 4.1 in Q3 and that three reviews cited implementation timelines. They will recall a pattern — “this competitor struggles with implementation at enterprise scale” — if that pattern was encoded clearly and repeatedly in their preparation.

Battlecard design that works with gist memory encodes patterns, not data points. It uses the same language a rep will use in conversation — not the language of a research report. It structures objection responses as complete sentences ready for use, not as bullet points requiring real-time synthesis.

“A battlecard that requires more than two minutes to read before a call has already failed its primary design criterion.”

• 71% of B2B sales teams use battlecards in competitive deals (Crayon, 2022)

• <50% rate their battlecards as effective — the majority are not changing outcomes (Crayon, 2022)

• 7±2 items is the working memory limit available under social and time pressure (Miller, 1956)

The anatomy of a HUMINT-led battlecard

A battlecard built from primary human intelligence has a fundamentally different content structure from one built from public monitoring. The sections below represent the QUAS battlecard framework — designed around the cognitive constraints of field use and populated exclusively from primary source intelligence.

QUAS BATTLECARD — ANATOMY (HUMINT-led)

1. Competitor positioning summary

How this competitor describes themselves in sales conversations — their core claim, their primary differentiator narrative, and the buyer profile they target. Not from their website. From how their reps actually open a conversation.

2. Pricing intelligence

Known pricing floor — the point below which they will not go regardless of deal size or competitive pressure. Discount trigger conditions: what the buyer needs to say or do to unlock a concession. Late-stage concession patterns observed across multiple deals.

3. Live demo script

The sequence they run in a product demonstration — what they lead with, the features they emphasise under competitive scrutiny, and the ones they consistently avoid demonstrating. The specific language they use when handling objections about your product in the room.

4. Three objection handles

The three most consistent competitive objections this competitor deploys — phrased exactly as they use them — with specific, tested response language ready for use in conversation. Not generic rebuttals. Exact responses to exact language, grounded in elicitation from sources who have experienced the interaction directly.

5. Known competitive weaknesses

The pressure points this competitor consistently exposes under scrutiny — observed across multiple competitive evaluations, not inferred from review sites. The questions that create discomfort in their sales process. The customer profiles where they reliably underperform.

6. Recommended counter-strategy

A single, deal-stage-specific strategic recommendation: what to do differently in this evaluation given what is known about how this competitor operates. Not a general observation about market positioning — a specific action for the rep to take in the next interaction.

7. Surface intelligence summary

Recent publicly available signals — website changes, product announcements, leadership moves — for context. This section is the only one built from monitoring tools. It provides background, not action. It is deliberately the last section, not the first.

The structure is deliberate. Sections 1 through 6 are exclusively HUMINT-sourced because they contain the intelligence that determines competitive outcomes. Section 7 — the only section drawn from public monitoring — is positioned last because it provides context, not action. Most battlecards invert this structure entirely: they lead with published positioning and end, if they get there at all, with a generic objection handling section of limited operational value.

Why the intelligence source determines battlecard quality

The sections above cannot be populated from competitive monitoring software. Not because the software is poorly built — because the information required does not exist in any public source.

A competitor’s pricing floor is a commercial policy decision held in the institutional memory of their sales leadership. It is not on their website, their G2 profile, or their job postings. The only way to access it is through sources who have direct knowledge: former employees who operated under that policy, channel partners who have negotiated against it, or customers who have tested it in live commercial negotiations.

Their demo script is an operational document that exists in their sales enablement system and in the muscle memory of their account executives. It is visible only to someone who has observed it — directly, in a live demonstration context.

Their consistent pressure points under competitive scrutiny are a pattern observable only across multiple competitive interactions. No single data source contains this pattern. It emerges from structured analysis of multiple primary-source accounts of how this competitor behaves in the room.

The deployment problem — the last mile of intelligence

Battlecard design is only one part of the problem. The second — and equally important — part is deployment: how intelligence moves from a document into a sales rep’s behaviour in the room.

Research on knowledge transfer in sales organisations by Szulanski (1996) identified four stages at which knowledge fails to transfer effectively: the initiation stage, the implementation stage, the ramp-up stage, and the integration stage.⁴ Battlecards that are shared via email and added to a shared drive typically fail at the initiation stage — they are never adequately socialised into the sales team’s practice, so the transfer never begins.

Effective battlecard deployment requires three things that document sharing does not provide. First, a structured briefing — not a self-serve read, but a facilitated session in which the intelligence is walked through and objection responses are rehearsed under conditions that approximate the pressure of real use. Second, a retrieval mechanism — the battlecard must be accessible at the point of competitive trigger, not filed in a folder that requires three clicks to open during a call. Third, a feedback loop — win and loss data against specific competitors must flow back into the intelligence function so that battlecards are updated on a cycle driven by field observation, not by a renewal date.

Intelligence without deployment is research. The measure of a battlecard is not how comprehensive it is. It is whether the rep competed differently in the last call — and whether that difference is traceable to something they read on a single page before dialling.

How often should battlecards be updated?

The validity window of a battlecard depends on the intelligence source. Battlecards built from public monitoring signals can be updated continuously as signals change — and most monitoring platforms offer automated alerts for this purpose. The problem is not update frequency for this category of intelligence. It is that the category of intelligence has limited relevance to deal outcomes.

Battlecards built from HUMINT primary sources have a different validity profile. Research on organisational knowledge decay — including Walsh and Ungson’s (1991) work on organisational memory — suggests that operationally relevant competitive knowledge remains accurate for between six and twelve months before material drift occurs in most B2B markets.⁵ Competitive pricing strategies shift with market conditions. Sales methodologies evolve in response to competitive losses. Key personnel who held and enacted specific strategies leave and are replaced.

For organisations competing in markets with active competitive pressure and high deal velocity, a six-month HUMINT refresh cycle is the appropriate standard. For markets with slower cycles and more stable competitive dynamics, twelve months is defensible. Annual refresh as a default — which is the most common pattern in organisations that conduct HUMINT intelligence at all — is insufficient for markets where competitors are actively learning and adapting.

The battlecard is not a finished artefact. It is a living document whose accuracy decays at a rate determined by how fast the competitive environment moves. Treating it as a deliverable to be filed, rather than an instrument to be maintained, is the most common single cause of battlecard obsolescence — and the most avoidable.

REFERENCES

1. Crayon. (2022). State of Competitive Intelligence Report. Crayon Inc. Annual industry survey, n=1,000+ revenue and marketing professionals.

2. Sweller, J. (1988). Cognitive load during problem solving: effects on learning. Cognitive Science, 12(2), 257–285. See also: Miller, G.A. (1956). The magical number seven, plus or minus two. Psychological Review, 63(2), 81–97.

3. Brainerd, C.J., & Reyna, V.F. (2002). Fuzzy-trace theory and false memory. Current Directions in Psychological Science, 11(5), 164–169.

4. Szulanski, G. (1996). Exploring internal stickiness: impediments to the transfer of best practice within the firm. Strategic Management Journal, 17(S2), 27–43.

5. Walsh, J.P., & Ungson, G.R. (1991). Organizational memory. Academy of Management Review, 16(1), 57–91.