Pretend you are the finance controller so soft accruals, missing owners, and heroic close timelines fail before the spend plan becomes policy.
Optimistic plans optimize for the headline number that looks clean on a slide. The finance-controller seat does the opposite. It asks which cost centers still lack owners, which commitments sit outside the system of record, which variance bands have no named response, and which accrual will surprise the next close. A tidy budget table is not evidence that the company can explain spend when the board or auditor asks.
This is one of the core moves in a budget or headcount war game: after you describe the capacity upside, seat a careful controller and make them try to decline. The output you want is not cheerleading. It is a short list of material objections, the exhibits each needs, and the edits that would survive them.
How to cast the seat
Name a real mandate: protect close integrity without inventing new process mid-cycle, underwrite a spend surge without pretending variance will self-heal, or approve a plan only when every line has an owner and a control. Give constraints: systems you will not replace this quarter, headcount you will not invent for the control tower, and residual risk you will not accept. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear.
Write the seat into the prompt as a named role with a mandate. Example: "Finance controller: list the top reasons to pause or sequence this spend plan, the assumption with the weakest source, the control or accrual gap that worries you most, and the ten diligence questions you would send after the meeting. Stay inside a realistic mandate and avoid illegal tactics."
What to demand from the pass
- Top reasons to delay, sequence, or cut lines.
- The assumption that looks strongest and is least sourced.
- The control, accrual, or owner mismatch that would worry you most.
- What would make you approve instead.
- The ten hardest diligence questions you would send in writing.
Run that brief in Pingpong against the real plan, last close notes, and variance history. Follow with a home-team response pass so you leave with edits and named owners, not only fear. When the decision sits near a reforecast or cost center split, run this seat after CFO and ops attacks so it can use earlier objections as ammunition.
When the plan leans on one spreadsheet, one person who "knows the numbers," or one late manual journal, force the seat to price concentration risk in writing. Ask what happens if that person is out, if the export breaks, or if two teams book the same commitment differently. Concentration that only appears in an appendix still counts. Pair with pretend you are the CFO, war-game a budget reforecast, war-game a cost center split, war-game a headcount plan, and the war-game decisions hub. See how to run a Pingpong.