Pretend you are the expansion rep so usage gaps, timing theater, and expansion blur fail before an expansion package absorbs them.
Optimistic expansion packages optimize for "usage will pull the upsell." The expansion rep seat does the opposite. It asks which expansion motion invents readiness the account never showed, which cohort dual-counts the same seat as expanded and as still on the base plan, which "required" usage gate is already optional in practice, and which account still lacks a named expansion owner. A neat expansion pipeline chart is not evidence that next quarter's net new ARR will clear.
Mandate the seat
Name a real job: underwrite an expansion playbook without inventing product readiness, clear a usage claim that billing can reconcile under load, or defend a multi-product attach motion without dual-counted expansion rates. Give constraints: the evidence standard for expansion timing, the accounts you will refuse to leave unowned, and the attach claims you will not teach when product gaps remain. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a forecast review, a QBR fight, or a dispute over who owns multi-product attach.
Prompt example: "Expansion rep: list the top reasons to delay this expansion package, the account cohort with the weakest owner, the attach claim that worries you most, and the ten diligence questions you would send after review. Stay inside a realistic mandate."
Outputs worth keeping
- Top reasons to challenge, delay, or rewrite this expansion package.
- The usage or attach claim that looks strongest and is least evidenced.
- The segment, product, or region that would break first under a forced push.
- What would make you accept residual expansion risk in writing.
- The ten hardest follow-up questions after the meeting.
Run that brief in Pingpong against the real usage map, expansion backlog, QBR notes, and open risk list. Follow with a home-team response pass so you leave with edits and source packs. When the decision is a public packaging or pricing change, run this seat after CS and product attacks so it can use earlier objections as ammunition.
When the plan leans on a single hero account, a single "usage will force the upgrade" promise, or a single product attach path, force the seat to price concentration risk in writing. Ask what happens if the usage dashboard still hosts retired metrics, if expansion still lacks a named weekend owner for large renewals, or if marketing keeps teaching attach language CS already retired. Pair with pretend you are the customer success lead, pretend you are the head of sales, war-game an account plan, war-game a packaging change, and the war-game decisions hub. See how to run a Pingpong.
If the package coincides with a usage cap or pricing change, ask the expansion rep seat to map every claim that still assumes last quarter's entitlements. Quotes, partner portals, and in-product upgrade prompts count. An expansion memo that looks clean in a slide while billing still posts retired plan codes will fail on the first large attach attempt.