The battle cards reps don't use share a physical property: they are long. Three pages, five pages, sometimes seven pages of text that reps skim once during enablement and never open during a live deal. The cards reps do use share the opposite property: they fit on one page, they have obvious structure, and the structure maps to the questions the rep will face in the next 15 minutes of conversation. The four-box framework below is our attempt to distill that shape into a reusable template.
The four boxes
All four boxes are required. A card with only three is a card reps can't close the loop on.
Each box is roughly 80 to 120 words. Four boxes at that length fill one page. More than that and the card loses the one-screen advantage; less and the boxes don't carry enough context for the rep to execute on.
Box 1 · Claim
The Claim box contains the competitor's actual claim, quoted, with a source. Not your paraphrase of what they say. Their specific words, usually from their homepage hero, a recent CEO statement, or an analyst-report quote.
Why this matters: reps meeting a competitor in a deal will hear the claim in roughly the competitor's language, often from the buyer who has been on the competitor's website. The rep who recognizes the exact phrasing reads the situation faster than the rep who has been taught a generalized version.
What the box contains: the verbatim claim (20–30 words), the source (homepage, press release, earnings call, analyst report), the date last verified (claims change; a battle card's claim box should be checked quarterly). If the claim has a number attached ("2× faster," "40% cheaper"), the number is preserved as the competitor states it.
Box 2 · Counter
The Counter box is the reframe — the strategic move the rep is executing in response. This is the load-bearing box. It is what makes the card different from a feature-comparison grid.
The counter is not "why they're wrong." It's "where the conversation should go instead." Two shapes work. The first: acknowledge the claim is partially true and add the missing context that changes the math. ("They are faster on a greenfield deployment; the math changes for customers with existing data, and 80% of our shared prospects have existing data.") The second: pivot to a different axis entirely. ("Speed is their strongest frame. We don't win that one. The frame that matters for your use case is total cost over 18 months, and that's where the numbers flip.")
The counter is what the rep has to internalize before the call. It's the strategic move; everything else in the card supports executing it.
Box 3 · Proof
The Proof box is one specific piece of evidence. Not three. Not five. One. A named customer, a benchmark number, or a published data source. The specificity is what makes the proof credible; a list of three generic proof points is weaker than one named, verifiable piece of evidence.
What qualifies as proof in the four-box framework
What does not qualify: "customers tell us," "in our experience," "industry-leading," or any phrase without a specific number, named source, or documented evidence. The Proof box is a rigor check on the counter — if you can't name the proof, the counter is probably softer than it needs to be.
Box 4 · Response
The Response box is what the rep actually says on the call. Three sentences maximum. Speakable, not written. The box should read as if a rep dictated it into their phone after a successful call, not as if marketing drafted it.
The response box is often the hardest part to write. Marketing teams default to written-sounding sentences — "While their solution offers certain capabilities, our platform delivers measurable outcomes across..." — which no rep will ever say out loud. The test: read the response out loud. If it sounds like a rep, keep it. If it sounds like a brochure, rewrite it.
An example of a response that works: "Yeah, they're faster to stand up — no argument on that. Where we see the picture change is at month six. Our customers stop paying per-transaction overage by month three; theirs scale with usage forever. I've got a specific case I can send you." That is speakable. It concedes a real competitor strength, pivots to the rep's axis, and offers a next step.
What goes above the four boxes
A single line. The trigger. When to use this card. "When the buyer mentions [competitor] in the context of [specific concern], pull this card." The trigger line makes the card findable in the moment; without it, reps have to scan the full card library to know whether this is the right one.
One line. Not a paragraph. The one-line trigger and the four boxes together produce the one-page card that reps will actually keep open during a Zoom call.
What is deliberately not in the framework
Three things that appear on most battle cards are deliberately excluded.
Company background. The rep doesn't need to know the competitor's history during an active deal. If the deal advances, the rep can research separately. The card is for the moment in the call; company history is enablement, not tactical support.
Feature-comparison grid. The four-box framework refuses the feature grid by design. The reason is strategic: a feature grid concedes that the decision hinges on features, which is the ground the incumbent or larger competitor usually wins. The card's value is in the counter — pulling the comparison off the feature axis, not arguing it.
Objection library with ten objections. Each objection deserves its own four-box card. Merging ten objections into one monster card produces the unused-because-too-long problem. Ten separate cards, each trigger-tagged, each one page, is the right scale.
Rollout and maintenance
A new card goes through a specific rollout: the PMM writes the first draft, a senior AE reviews the Response box (this is where the "sounds like a rep" test gets applied), and sales enablement runs a 15-minute team walkthrough in the weekly standup. The walkthrough is essential — reps who learn a card by reading it on their own retain roughly 30% of the counter; reps who learn it by hearing it from the author retain roughly 70%.
Maintenance: quarterly review of every active card. Is the claim still what the competitor says? Is the proof still current? Has the sales team's experience suggested a better response? Thirty minutes per card per quarter is roughly the right budget. Cards that haven't been used in two quarters get archived; cards that have been used heavily get reinforced with a second proof point.
The four-box framework is not the only way to write a battle card. It is the way we've seen reps actually reach for, across multiple programs, across multiple industries. The boxes are not magic; the one-screen constraint is. Everything else is supporting structure to make the constraint liveable.
Battle Cards
Auto-updating per-competitor rebuttal kits. Each card updates when Competitor Signals detects a material move.
See how it worksOne sharp positioning read, most Thursdays.
Field-tested frameworks, teardowns, and pattern notes from our working library. No "Top 10" lists. No launch roundups. Unsubscribe whenever.
Keep reading
How to Build Battle Cards That Sales Actually Uses
Tactical guide to battle cards that field reps open during live deals — not the ones that rot in Drive two weeks after they ship.
5 Battle Cards from Enterprise SaaS, Deconstructed
Five real battle-card patterns from enterprise SaaS programs — what each does right, what each does wrong, and the single piece of structure that separates the cards reps use from the ones they ignore.
How to Write Battle Cards for Pricing Objections
Most pricing battle cards re-argue the price. The ones sales reps actually use reframe the comparison — here's the five-section template, the three objections it has to answer, and the test for whether the card is working.