Pretend you are the billing ops lead so dunning gaps, invoice theater, and exception blur fail before a billing package absorbs them.
Optimistic billing packages optimize for "collections will clear." The billing ops lead seat does the opposite. It asks which invoice invents payment speed the gateway will not support, which dunning step dual-counts the same account as recovered and as written off, which "required" hold is already optional in practice, and which cohort still lacks a named exception owner. A neat collections dashboard is not evidence that next month's cash will clear.
How to cast the seat
Name a real job: underwrite a dunning rewrite without inventing agent capacity, clear an invoice claim that finance can reconcile under load, or defend a plan-code cutover without dual-counted recovery rates. Give constraints: the evidence standard for payment failures, the cohorts you will refuse to leave unowned, and the recovery claims you will not teach when tooling is not ready. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a close review, a cash forecast fight, or a dispute over who owns multi-currency exceptions.
Prompt example: "Billing ops lead: list the top reasons to delay this billing package, the cohort with the weakest owner, the recovery claim that worries you most, and the ten diligence questions you would send after review. Stay inside a realistic mandate."
What to demand from the pass
- Top reasons to challenge, delay, or rewrite this billing package.
- The recovery or invoice claim that looks strongest and is least evidenced.
- The plan code, region, or payment method that would break first under a spike.
- What would make you accept residual collections risk in writing.
- The ten hardest follow-up questions after the meeting.
Run that brief in Pingpong against the real dunning map, exception log, gateway reports, 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 pricing or packaging change, run this seat after finance and support attacks so it can use earlier objections as ammunition.
When the plan leans on a single hero agent, a single "gateway will catch up" promise, or a single large unpaid cohort, force the seat to price concentration risk in writing. Ask what happens if the ERP still hosts retired plan codes, if dunning still lacks a named weekend owner, or if sales keeps teaching invoice language finance already retired. Pair with pretend you are the revenue accountant, pretend you are the finance controller, stress-test a dunning sequence, stress-test a billing change, and the war-game decisions hub. See how to run a Pingpong.
If the package coincides with a refund or credit memo change, ask the billing ops lead seat to map every claim that still assumes last quarter's exception paths. Invoices, partner portals, and support macros count. A billing memo that looks clean in a slide while dunning still posts retired reason codes will fail on the first close.