Pretend you are the treasury lead so liquidity gaps, covenant risk, and forecast theater fail before a cash package absorbs them.
Optimistic cash packages optimize for "runway will hold." The treasury lead seat does the opposite. It asks which forecast invents collections the ledger cannot show, which covenant still lacks a named breach path, which FX or bank line dual-counts the same buffer, and which "approved" wire policy is already optional in practice. A neat cash slide is not evidence that the next quarter will clear without silent liquidity debt.
Mandate the seat
Name a real job: underwrite a cash plan without inventing collection speed, clear a covenant path that finance can enforce under load, or defend a banking change without dual-counted buffers. Give constraints: the evidence standard for forecast math, the entities you will refuse to leave unowned, and the liquidity claims you will not teach when the bank line is not ready. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a board prep room, a lender call, or a fight over who owns weekend wire coverage.
Prompt example: "Treasury lead: list the top reasons to delay this cash package, the entity with the weakest owner, the liquidity 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 cash package.
- The runway or covenant claim that looks strongest and is least evidenced.
- The entity, currency, or bank line that would break first under a collections miss.
- What would make you accept residual liquidity risk in writing.
- The ten hardest follow-up questions after the meeting.
Run that brief in Pingpong against the real cash forecast, bank covenants, wire policy, 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 board date, run this seat after CFO and legal attacks so it can use earlier objections as ammunition.
When the plan leans on a single bank relationship, a single collections hero, or a single "we will refinance later" promise, force the seat to price concentration risk in writing. Ask what happens if the hero is out, if a covenant still hosts retired thresholds, or if a vendor payout lands mid-freeze. Pair with pretend you are the CFO, pretend you are the finance controller, war-game a budget reforecast, stress-test a payout schedule, and the war-game decisions hub. See how to run a Pingpong.
If the package coincides with a pricing or billing change, ask the treasury lead seat to map every claim that still assumes last quarter's cash timing. Dunning, payout calendars, and partner rebates count. A forecast that looks clean in a slide while collections still lag will fail on the first board ask.