Framework · 6 min read
Competitive Battlecard Framework
A practical battlecard grounded in buyer and competitor evidence.
Klue · View sources ↓At a glance
- Use this when
- Reps need concise, credible guidance for a specific competitive conversation.
- What you will work towards
- A practical battlecard grounded in buyer and competitor evidence.
- Bring to the reading
- A specific decision from your work and the customer evidence you have so far.
What it is
A standard one-page structure that gives a sales rep everything they need to win a competitive deal in the middle of a live conversation: the competitor's likely pitch, your counter-position, objection responses, landmines to plant early, and the proof points that back each claim. A battlecard is not a research document; it is a field tool, built to be read in ninety seconds between a discovery call and a demo, that turns the slower, deeper work of the Competitive Intelligence & Positioning Update Framework into something a rep can act on live. Where competitive intelligence answers "what is the competitor doing and how should our positioning respond?", the battlecard is the artefact that carries the answer into the deal itself, structured so that any rep, not just the ones who read every competitor blog post, can hold their own against a well-briefed prospect.
When to use it
- Sales reports losing deals to a specific named competitor and cannot explain, deal by deal, why.
- A new competitor enters the market or an existing one repositions, and the sales team's mental model of them is now out of date.
- Win/loss interviews surface a recurring objection ("Competitor X is cheaper", "Competitor X already has feature Y") that reps are answering inconsistently or not at all.
- You are onboarding new sales hires and need a fast way to bring them up to competitive speed without a several-week ramp.
- A significant competitor pricing change, feature launch, or funding round shifts how a deal is likely to be contested.
- Sales enablement audits (10-Step PMM Process, Step 7) flag that competitive collateral is missing, stale, or inconsistent across the team.
Ownership
At a scaled company, the Head of Product Marketing (or the PMM leading competitive intelligence) owns the card's content and the call on what counter-position ships; VP Sales or the Head of Sales Enablement owns distribution into the CRM and enablement platform, and holds reps accountable for actually using it. At a solo or founding-PMM stage, the PMM owns the card outright, from research through publication and rep training, because no separate enablement function exists to take distribution off their plate.
How to apply it
- Choose the competitor and confirm it is worth a card. Build a battlecard only for competitors you actually face in live deals with enough frequency to matter (a reasonable bar is 10+ competitive deals a quarter); a card for a competitor sales rarely meets is wasted effort and one more document nobody trusts.
- Gather their pitch, not your assumption of it. Watch a demo if you can get one, read their website and pricing page, pull their capture from recent lost-deal notes, and ask reps what the prospect actually repeated back after meeting them. Write their pitch in their words, not a strawman version that makes them easy to beat on paper but fails the moment a well-prepared prospect quotes them accurately.
- Build the counter-position. For each of their headline claims, write the specific, evidenced response: not "we're better", but the mechanism and the proof. If they lead on price, the counter is not "we're worth it" but the total-cost-of-ownership comparison that shows why.
- Plant landmines. Identify one or two questions a rep can ask early in a deal, before the competitor is in the room, that expose the competitor's known weakness without ever naming them: "How does your current process handle multi-region compliance?" is a landmine if you know the competitor's product does not.
- Write objection responses verbatim. For the three to five objections reps hear most often about this competitor, write the exact sentence a rep should say, not a bullet of talking points; reps under pressure in a live call read scripts far better than they improvise from a list of themes.
- Attach proof points to every claim. A counter-position without a named customer outcome, a benchmark, or a third-party validation is an assertion, and prospects increasingly ask for evidence live in the call. Pull proof from Win/Loss Analysis and named references, refreshed each quarter.
- Keep it to one page. A battlecard a rep will not read in the ninety seconds before a call is not a battlecard; ruthlessly cut anything that is not immediately actionable in a live conversation, and push deeper research into a linked appendix instead.
- Train and pressure-test with sales. Run the card through a live role-play with two or three reps playing the prospect and pushing back; revise language that does not survive contact with a sceptical objection before it goes company-wide.
- Version, distribute, and refresh. Store the card in the tool reps already use (CRM opportunity view, enablement platform, wherever they actually look mid-deal), owned by one PMM, and refresh it on a fixed cadence and whenever a competitor materially changes their product, pricing, or pitch.
Example
Fictional B2B payments platform Ledgerbeam was losing 60% of competitive deals against Instaflow, a better-funded rival two years its senior, and reps could not agree on why: some said price, some said brand, some blamed a missing feature. PMM pulled 22 lost-deal notes and interviewed six reps and four recently lost prospects directly. The pattern: Instaflow's sales team consistently led with "we integrate natively with NetSuite", a claim Ledgerbeam reps had no rehearsed answer to, so the conversation stalled there in roughly half of contested deals. PMM built a one-page battlecard: Instaflow's pitch section named the NetSuite claim explicitly rather than avoiding it; the counter-position showed Ledgerbeam's integration took 3 days to configure against Instaflow's own documented 6-week implementation average, sourced from two of Instaflow's own public case studies; a landmine question ("How long did your NetSuite rollout actually take, end to end?") was placed early in the discovery script; and three named customers who had switched from Instaflow specifically over implementation time were listed as proof, with contact details for reference calls. The card was role-played with the eight-person sales team over one session, then loaded into the CRM opportunity view for any deal tagged "Instaflow" as the competitor. Within one quarter, competitive win rate against Instaflow rose from 40% to 58%, average sales cycle in Instaflow-contested deals shortened from 61 to 44 days, and the reference-call request rate (a proxy for reps actually using the card's proof points) reached 70% of contested deals, the three metrics PMM had set at the outset to judge whether the card was actually being used rather than just filed away.
Pitfalls
- Writing the competitor's pitch as a strawman. Cards that make the competitor sound obviously worse than they are collapse the first time a well-prepared prospect repeats the competitor's real pitch accurately, and reps lose trust in the whole card. Recovery: rebuild the competitor's pitch section from a real demo recording or transcript, not from memory or internal bias, and have someone outside the deal review it for fairness before publishing.
- Building a research report instead of a field tool. A five-page card with market analysis and SWOT tables does not get read in the ninety seconds before a call, so reps default to improvising instead. Recovery: cut the card to one page of immediately usable material and move any deeper analysis into a linked appendix that exists for onboarding, not live deals.
- Publishing once and letting it go stale. A competitor's pricing, features, and messaging move faster than most PMM teams update their cards, so a battlecard six months old can actively mislead a rep into repeating a claim the competitor has already invalidated. Recovery: assign one owner, put a refresh date on every card, and treat a competitor funding round, feature launch, or pricing change as an explicit trigger to update within two weeks, not the next scheduled quarterly review.
How the ideas connect
Choose where to go next
Make it useful
Bring it back to your work.
Name one decision this guide could help you make. Write down the evidence you need, the output you would produce, and how you would know it was useful.
Check your understanding
Practise applying Competitive Battlecard Framework in five short scenarios.
5 practical scenarios. Choose an answer, explore the reasoning, and revisit the guide whenever you need.
Sources
- No single named originator is documented for battlecards as a sales-enablement practice; the best-known practitioner guide is Klue, "Sales Battlecards 101: Guide + Battlecard Templates" (accessed 2026)