By Siddharth Gangal What a sales battle card actually is
The buyer says "we\'re also looking at Outreach." The rep has eight seconds to place the competitor, three seconds to acknowledge without blinking, and thirty seconds to reframe before the conversation moves on. The rep either has those words ready or they do not. That is what a sales battle card is actually for.
A sales battle card is a one-screen, tactical reference document scoped to one battle — one competitor, one objection type, or one persona. Reps use it under time pressure on live calls, not in planning meetings. The test of a good card is whether the rep can glance at it for 2 seconds during a Zoom and speak the next sentence. Everything that does not pass that test comes off the card.
Definition
Sales battle card: a single-screen, sourced, team-governed reference for one specific sales battle — competitor, persona, or objection — that a rep uses in a live call to respond in seconds, not minutes.
The card is not a deck, not a binder, not a 4-page PDF. Those are research documents. They read well in onboarding and die on Tuesday afternoon when a buyer says "we\'re looking at Outreach" and the rep has to remember which Notion page held the counter-positioning.
The 6-part sales battle card template
Every serious sales battle card template hits the same six blocks, in this order. Skip one and the card fails the first time the rep needs it. The shape is stable across every battle you build — the contents change per competitor, per persona, per use case.
- 01
KnowCompetitor snapshot
Company overview, target market, recent funding, pricing model, personas they sell to. Six lines, max. The rep uses this to place the competitor in the first 5 seconds of the conversation — not to memorize a research dossier.
- 02
SayObjection + reframe pairs
Three to five of the most common objections against you, each paired with a reframe the rep can say in under 20 seconds. These are the exact words. Not a talking point. Not a theme. The words.
- 03
ShowProof points
Three numbered customer stats, one case study link, one third-party review — each with a source and a date. Claims without sources do not go on the card. Reps lose credibility when the number turns out to be last year's.
- 04
LandminesTheir weak points (as questions)
Three questions the rep asks the buyer that quietly expose gaps in the competitor's fit. Never disparaging. Always diagnostic. "How does their solution handle X?" beats "They can't do X."
- 05
PricingOur price, their price, trade-offs
Our tiers plus the last-known competitor pricing and packaging, each with a one-line trade-off. Source and date on every number. If pricing changes monthly, the card needs a monthly review cadence.
- 06
GovernanceOwner, last updated, sources
PMM owner, last-reviewed date, links to every source. No card stays accurate without a human on the hook. No card survives a review cadence that isn't in the card itself.
The Know, Say, Show frame sits at the core of every modern battlecard the enablement vendors sell — Klue, Crayon, Kompyte, Gong all converge on the same pattern (Klue, 2024). Landmines, Pricing, and Governance are the blocks most DIY templates skip — and the ones that separate a battle card from a glorified FAQ.
1
Card = one battle
One competitor, one persona, one use case. More than that is a binder.
20sec
Per reframe read
If it takes longer to read than to say, the rep won't use it.
30days
Review cadence
Static cards rot in a quarter. Schedule the review into the card itself.
3
Reps stress-test v1
If reps won't edit the draft, they're not going to use the card.
How to build a sales battle card in 90 minutes
Ninety minutes, six steps. Any slower and the card sits in draft for months; any faster and the proof points do not have sources. Run this the first time and every subsequent card takes 30–45 minutes because the pattern is already in muscle memory.
- 0–10m
Pick one battle, not ten
The card is for one scenario — one competitor, one persona, one use case. "vs Outreach for enterprise AEs" is a card. "competitors and personas" is a binder nobody reads. Start with your highest-loss battle and build that card first.
- 10–25m
Pull the loss-reason data
Open closed-lost opportunities from the last 90 days. Read the notes. Count the top three reasons the deal went to the competitor. Those three become the "Say" block. Reps already know these; the card just writes them down.
- 25–45m
Write the reframe in rep voice
For each objection, write the reframe exactly as the rep would say it on a call. Read it aloud. If it sounds like marketing copy, cut it. A reframe that sounds like a human mouth made it — not a deck — is the one reps will actually use.
- 45–65m
Source every proof point
Three numbers, each with a link and a date. If you can't find a live source, rewrite the claim as an observation, not a statistic. "We see reps save 8 hours/week on post-call admin (internal data, 2026)" is fine. "We save reps time" is not on the card.
- 65–80m
Stress-test with 3 reps
Send the draft to three quota-carrying reps and ask one question: "Would you actually use this on a call?" Their edits are the card. Reps who say "this is fine" without edits did not read it — chase them.
- 80–90m
Ship with a review cadence
Put the card in the live-call surface (Gangly, Klue, Crayon) and schedule a 30-day review. Static cards rot in a quarter. Without a review cadence, the card is already on its way to the next Notion graveyard.
The highest-leverage step is five. Three reps with a red pen will cut half the card and save the other half — and those cuts are what turns a marketing asset into a rep asset. If the reps will not edit it, they will not carry it.
How top reps actually use a battle card mid-call
The build matters less than the surface. Most battle cards die not because the content is bad but because the rep cannot find the card when the objection hits. A live call gives the rep roughly two seconds of cognitive budget before the room notices they are searching. Two seconds is not enough to open Notion.
A rep using a live-surfaced battle card runs this motion, in order: (1) competitor name drops on the Zoom; (2) the keyword fires; (3) the card appears on screen in under a second; (4) rep glances at the Say block, reads the reframe aloud, eyes back on the camera; (5) the Show block is two scrolls down for the proof point if the buyer asks for it. Total cognitive cost: 3–4 seconds. The same motion from a Notion doc takes 45 seconds, and the buyer has already moved on.
This is why modern battlecard platforms — Klue, Crayon, Kompyte — moved away from PDF exports and toward in-call surfacing. A PDF is a document. A live battle card is a workflow. See how live call coaching actually works for the plumbing underneath.
Where battle cards go to die: the 5 failure modes
Battle card programs usually fail in the same five ways. None of them are content problems. All of them are workflow and format problems — which is why buying a better template never fixes the program.
- 1
Lives in a Notion doc
A card the rep has to open during a live call is a card the rep does not open during a live call. The card has to surface itself when the competitor name or objection keyword hits — otherwise adoption collapses within a month.
- 2
Runs to three pages
Reps skim on live calls. If the card spills to page two, the rep uses page one and ignores the rest. One screen or nothing. If the content will not fit, it is two cards, not one longer one.
- 3
Written in marketing voice
"Best-in-class platform delivering seamless value" is not a line a rep says aloud. Every reframe needs a read-aloud test. If the rep is embarrassed to say it on a Zoom, the card just added dead weight.
- 4
No proof, just claims
"Better than Outreach at call workflow" without a number is a claim the rep cannot back up. "46% talk ratio held on live Zoom (Gong Labs, 2023)" is a claim the rep can defend under pressure. Every claim needs a source or it comes off the card.
- 5
Never updated after v1
The competitor changed their pricing 3 weeks ago. The card still cites last year's number. Reps quote it in a pricing objection. The deal dies on a source the rep could not verify. A card without a 30-day review is a landmine pointed at your own foot.
The meta-failure under all five: the card was built by enablement for enablement, not by enablement for the rep. A card the rep did not help write, in a format the rep cannot use in a live call, with content the rep cannot say aloud, will never become a habit.
How Gangly keeps battle cards live in the workflow
Gangly was built around the assumption that the rep is on a live call when the card matters most — so the card surfaces itself, updates itself from call intel, and never requires the rep to open a second tab.
- Live Call Coach — detects competitor names and objection keywords on the live Zoom or Google Meet transcript, then surfaces the matching card on the rep\'s screen in under a second.
- Post-Call Notes — extracts new objections from every call and feeds them back as suggested updates to the card\'s Say block. The card learns from the pipeline instead of ageing out.
- Call Prep Engine — pulls the relevant cards into the pre-call brief automatically, so the rep sees them 30 minutes before the meeting, not while scrambling during it.
- Workflow Sequencer — ties the card to the deal record, so a battle card surfaced on a call shows up in the CRM note, not a separate dashboard.
Start with the 14-day free trial. Upload one card. Connect Zoom or Google Meet. The next time a competitor name lands on a live call, the card is on the screen before the rep finishes taking a breath.
Related reading: the 4-step sales objection handling framework covers the motion the Say block plugs into, handling the price objection zooms in on the Pricing block, and the 5-minute call prep workflow shows where cards land in the pre-call brief.