War-game a SaaS pricing page before prospects, sales, and competitors see the live copy.
A pricing page is a public commitment. It sets who self-qualifies, which pack sales can defend, and which objection support will hear first. Shipping a pretty grid without a seating chart review usually means you learn fairness fights, pack confusion, and competitor counters in the first week of demos, not in a private pass.
Freeze the page under fire
State the packs, prices, who each pack is for, grandfathering rules, and the metric that would reverse a change. Paste the exact page copy, the comparison table, and the footnotes you plan to keep. If marketing, product, and finance disagree on what "unlimited" means, stop and reconcile before the review. A war game needs one page under fire, not three silent drafts.
Write the decision you will make if the war game finds nothing new. Also write the kill criteria: conversion drop, sales exception rate, or churn spike that would force a rollback within a stated window.
Seats that matter on a pricing page
- Buyer. Fairness, switching cost, and the sentence that would make them leave the page.
- Finance. Margin, discount leakage, and forecast risk if the wrong pack dominates.
- Competitor. Cheapest counter-message and the segment they would peel with a simpler grid.
- Sales and CS. Objection scripts, exception pressure, and ticket themes in the first thirty days.
- Skeptic. The claim that looks strongest and is least sourced on the page.
Attach the same source pack to every seat: cohort math, win/loss notes, competitor screenshots, and the exception policy you actually intend to use. Secret footnotes for one seat create fake agreement.
Loop until objections have owners
Feed Pingpong the page draft, the cohort math, and the seating briefs. First pass steelmans the grid. Later passes attack from buyer, finance, and competitor seats. Final pass turns surviving objections into copy edits, pack changes, tests, or a delayed publish. Agreement across passes is not proof. Keep the objections that still have evidence gaps.
Force the review to invent the exception policy before go-live. A pricing page that only works with quiet one-off discounts is a shadow discount program with worse reporting. Write the exception rules, approval owner, and monthly cap into the package, then ask buyer and finance seats to attack those rules.
Pair with war-game a pricing change, before you change pricing, pretend you are the buyer, pretend you are the competitor, and war-game your strategy. See AI decision review and how it works.