War-game an account plan before stakeholder maps, expansion bets, and QBR decks harden into how every strategic account gets worked.
Account plans fail when stakeholders invent access the team never earned, when expansion math dual-counts the same seats, when risks stay in a private note, and when customers hear a roadmap promise nobody owned. A neat account slide is not evidence.
Freeze the package
State the account outcome for the next two quarters, which stakeholders and use cases the plan covers, who owns each risk and expansion bet, what success looks like after the next renewal, and the kill criteria if engagement or expansion slips past a named threshold. Attach the stakeholder map, usage and health signals, open risks, and the measured lag from commitment to delivery. If CS, sales, and product disagree on whether the account is expand-first or renew-first, reconcile before seating.
Name the decision you will make if the war game finds nothing new, and the hold criteria if any critical stakeholder still lacks a named owner or a dated next meeting.
Seats
- Account executive. Fear that an optimistic expansion number becomes forecast blame.
- Customer success. Plans that look complete while adoption work has no capacity.
- Product. Roadmap promises that punish missing features the account already filed.
- Finance or RevOps. Expansion math that dual-counts seats, trials, or multiyear pulls.
- Skeptic. The claim that looks strongest and is least sourced.
Optional counsel seat if the plan includes contractual remedies or public case-study asks. Same pack for every seat.
Run the loop
Feed Pingpong the plan memo and exhibits. First pass steelmans the outcome. Later passes attack from the seats above. Final pass turns surviving objections into clearer owners, fairer expansion math, or a hold. Delete invented "they already love us" claims and dual-counted outreach hours.
Force a day-after narrative: what happens if the champion leaves, if a red health signal appears mid-quarter, or if the account screenshots a roadmap promise you cannot keep. If those stories are stronger than your mitigation plan, fix the package before you operationalize it. Separate an account plan from a renewal playbook or a customer health score so each decision stays testable.
Ask every seat to mark which steps are optional in practice. Optional monthly QBRs become skipped within a month if nobody names the owner and the time box. Related: war-game a renewal playbook, war-game a customer health score, war-game a pipeline review, pretend you are the customer success lead, and the war-game decisions hub. Process: how to run a Pingpong.