War-game a competitive battlecard before claims, proof points, and talk tracks harden into how every competitive deal gets briefed.
Battlecards fail when claims invent product truth the roadmap will not keep, when screenshots go stale within a quarter, when legal never cleared comparative language, and when sellers use the card as a smear sheet instead of a diligence aid. A neat PDF is not evidence.
Freeze the package
State which competitor and deal stages the card covers, who owns updates and legal review, what success looks like after two quarters of win-loss notes, and the kill criteria if claim disputes or legal flags exceed a named threshold. Attach the proof library, dated screenshots, win-loss excerpts, and the measured refresh cadence. If product marketing, sales, and counsel disagree on which comparative claims are allowed, reconcile before seating.
Name the decision you will make if the war game finds nothing new, and the hold criteria if any major claim still lacks a dated source or a named refresh owner.
Seats
- Account executive. Fear that a stale claim becomes embarrassment mid-call.
- Product marketing. Cards that look complete while proof packs never update.
- Counsel. Comparative language that invites a dispute the company will not defend.
- Win-loss or RevOps. Usage metrics that dual-count views without showing deal impact.
- Skeptic. The claim that looks strongest and is least sourced.
Optional competitive intelligence seat if a teardown already exists and must stay aligned. Same pack for every seat.
Run the loop
Feed Pingpong the draft card and exhibits. First pass steelmans the structure. Later passes attack from the seats above. Final pass turns surviving objections into dated proof, narrower claims, or a hold. Delete invented "we always win on X" lines and dual-counted enablement hours.
Force a day-after narrative: what happens if a competitor publishes a rebuttal, if a screenshot from last year is still in the deck, or if a buyer forwards the card to counsel. If those stories are stronger than your refresh plan, fix the package before you publish. Separate a battlecard from a competitive teardown or a win-loss program so each decision stays testable.
Ask every seat to mark which steps are optional in practice. Optional monthly refreshes become skipped within a month if nobody names the owner and the time box. Related: war-game a competitive teardown, war-game a win-loss program, pretend you are the competitor, pretend you are the product marketing lead, and the war-game decisions hub. Process: how to run a Pingpong.