Battle cards that stay sharp
because they update themselves.
A per-competitor card with their pitch, the gaps in it, your differentiated answer, and the proof reps need to land it. Auto-refreshed when Competitor Signals detects a material move.
Most battle cards die in a Drive folder six weeks after the offsite. Ours die when the competitor stops shipping.
Cards are generated per competitor, with one card per. Available in Pro workspaces.
“The rep got broadsided on a question we’ve answered ten times.”
Sales loses a deal on a competitor objection. Marketing patches the deck. Six weeks later the same objection lands a different rep — because the patch went to one Drive folder and the rep got the version from another.
Static battle cards age out. The competitor ships, the market moves, and the card stays frozen at the moment it was written. By month three it’s wrong; by month six it’s actively misleading.
The fix isn’t better cards. The fix is cards that update themselves whenever the competitor moves — and one canonical place reps actually open during a deal.
Five blocks. Field-ready.
Each block is short, specific, and quotable. No hedging. No “leverage the synergy.” A rep should be able to read a card before a call and pitch from it during one.
Their pitch (steel-manned)
A one-paragraph version of the competitor’s strongest argument, in their voice. If you can’t pitch their position, you can’t answer it.
The gaps
Three to five specific places their pitch breaks down — anchored to their own pricing page, docs, or recent announcements, not your interpretation of them.
Your differentiated answer
One paragraph + three quotable lines. Not a pillar restatement; the version of your story that specifically beats theirs in the head-to-head.
Proof and citations
Customer quotes, third-party validation, head-to-head case studies, public benchmarks. Every claim links to its source so reps can forward, not paraphrase.
Objection handlers
The five most common ‘but they have X’ questions, with calibrated answers. Updated when Win/Loss Review surfaces a new pattern.
Last-updated stamp
The competitor moved on Tuesday; your card noted it on Wednesday. Reps can trust the card because they can see when it last touched reality.
Acme vs. Competitor A — abridged.
‘Best-in-class data warehouse for analytics teams who want zero infra overhead. Faster than Snowflake on small queries; cheaper than BigQuery on cold storage.’
(1) Workflow: no orchestration, requires third-party scheduler. (2) Governance: row-level security in beta only. (3) Pricing: per-query model penalizes heavy dashboard users.
‘Acme is the workflow engine they don’t have, with the governance their largest customers churned over. Same query speed, native scheduling, predictable pricing.’
Stripe deck slide 14 (TPC-DS benchmark, public). Linear case study (workflow migration). Govern-by-default whitepaper, p.4.
Short answers.
As many as you add. Typical mid-market team tracks five to twelve. Cards run independently.
Material moves detected by Competitor Signals: pricing change, new product page, launch, repositioned hero, executive change. The card flags what changed and what shifted in the answer.
Yes. Generated drafts are starting points. Every block is editable; edits persist across auto-updates unless the underlying signal contradicts them.
On opt-in: Slack or email when a card you watch changes materially. Default is silent updates.
Related capabilities.
Competitor Signals
The watch that triggers the update. Add a competitor to Signals and a Battle Card is auto-generated.
See Competitor Signals →Win/Loss Review
Lost-deal patterns surface new objections. Battle Cards picks them up and adds them to the handler block.
See Win/Loss Review →Positioning Brief
Pillars change; differentiated answers change. The Brief is the source of truth Battle Cards reads from.
See Positioning Brief →Score positioning first. Then arm the field.
Battle Cards inherit your pillars from the Positioning Audit. Run the free audit; once you’re happy with the pillars, your competitor cards generate from them automatically.