Capital

War-game an investor update before you hit send

War-game an investor update before soft metrics, heroic forecasts, and buried risks become the written baseline your next raise inherits.

Updates fail when narrative and appendix disagree, when "on track" hides a miss, when asks appear without options, and when the first careful reader is an investor who forwards the note. A polished paragraph is not evidence that the package survives scrutiny.

Freeze the update package

Lock the period, the headline metrics, the misses you will own, the ask if any, and the constraints already treated as fixed. Attach the source tabs for every material number, prior update promises, runway math, and the customer or product proof you will cite. If the narrative and the spreadsheet disagree, fix that before you ask models to review it.

Write the question you hope nobody asks. Put it in the brief first. Investor inboxes reward teams that arrive having already answered the hard line.

Director and investor seating chart

  • Finance-minded investor: cash, forecast integrity, and what the chart hides.
  • Operator investor: execution risk in the next ninety days.
  • Customer-minded reader: whether the story matches delivery.
  • Skeptic: the strongest-looking claim with the weakest source.
  • Prior-promise auditor: which line from last update quietly vanished.

Optional counsel seat if the update sits near a raise, a dispute, or regulated disclosure. Optional competitor seat if strategy or pricing is the headline.

Private failure loop

Run the note through Pingpong with those seats named. Sequential review lets an early pass organize the story while later passes try to kill unsupported claims. Keep a change log of claims removed, sources added, and numbers redefined. If a model invents a metric or a customer quote, delete it.

Treat Q&A as part of the same war game. Ask for the ten hardest follow-ups from each seat, answer them with sources, and either edit the note or consciously leave a known risk on the table. An investor update is a decision artifact, not a storytelling contest.

If the ask is capital, headcount, or a strategic bet, put the alternatives in the note with owners and dates. Readers compare packages. A single-path update invites improvisation in email. Ask the skeptic seat to invent the missing alternative if you left it out. Nearby: war-game a board deck, war-game a fundraising deck, war-game a data room, pretend you are the skeptical investor, before you reply to the board, and the war-game decisions hub. See how to run a Pingpong.