Pretend you are the largest customer so soft roadmap cuts and pricing moves fail before the account that can hurt revenue hears them cold.
Optimistic packages optimize for the average user. The largest-customer seat does the opposite. It asks which commitment is now soft, which integration breaks, which SLA still looks real on paper, and which renewal conversation becomes adversarial if you ship as written. A fluent product brief is not evidence that a careful enterprise buyer will stay calm.
This is one of the core moves in a serious pricing, sunset, or roadmap war game: after you describe the upside, seat a careful concentration account and make it try to escalate. The output you want is not theater. It is a short list of material objections, the exhibits each needs, and the edits that would survive a real QBR.
How to cast the seat
Name a real mandate: protect contracted outcomes, keep a critical workflow alive, or underwrite a renewal without heroics. Give constraints: the contract terms you will honor, the notice window you expect, and the residual risk you will not invent away. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear from a careful buyer.
Write the seat into the prompt as a named role with a mandate. Example: "Largest customer: list the top reasons to escalate or churn after this change, the claim with the weakest evidence in our pack, the workflow risk that worries you most, and the ten diligence questions you would send after the QBR. Stay inside a realistic mandate and avoid illegal tactics."
What to demand from the pass
- Top reasons to escalate, renegotiate, or churn after this change.
- The claim that looks strongest and is least evidenced for your account.
- The workflow, SLA, or integration path that would worry you most.
- What would make you accept a narrower change instead.
- The ten hardest diligence questions you would send in writing.
Run that brief in Pingpong against the real memo, contract excerpts, and usage exhibits. Follow with a home-team response pass so you leave with edits and notice plans, not only fear. When the decision is a sunset or pricing move, run this seat after product and finance attacks so it can use earlier objections as ammunition.
When the plan leans on a single logo for a large share of revenue, force the seat to price concentration risk in writing. Ask what happens if that account renews down, pauses expansion, or demands a custom holdout. Concentration that only appears in an appendix still counts.
Pair with pretend you are the angry customer, pretend you are the enterprise buyer, war-game a churn response, war-game a roadmap cut, and the war-game decisions hub. See how to run a Pingpong.