Sharing bad news with investors

The rule for bad news in an investor update is the same rule as for good news — lead with the number — applied on the month you least want to. Investors forgive bad months routinely. What they don’t forgive is finding out you knew and wrote around it.

Hiding it costs more than saying it

Founders bury bad news to protect the relationship; the burying is what damages it. Your investors talk to each other, sit on other boards, and read forty updates a month — pattern recognition is their job. A “light” month in your update followed by a down-round conversation two quarters later doesn’t read as misfortune; it reads as a founder whose reports lag reality. From that point, every update you send gets the skeptical read — and the skeptical read is expensive precisely when you next need fast yeses.

The inverse is also true, and it’s the useful part: a plainly reported bad month raises your credibility. It proves your updates are the real feed, not the highlight reel — which makes every good month you ever report worth more.

Lead with the number anyway

The headline slot doesn’t change jobs in a hard month. If churn spiked, the headline is the churn number; if the round fell through, the headline is the runway consequence. Anything else — the team news first, the product win up top, the bad number in paragraph four — teaches readers that your ordering hides things, and they will re-read every future update looking for what’s below the fold.

A hard-month headline in the house style:

MRR $39,900, down 5.4% — two churns, runway still 13.1 months. Plan inside.

Number, direction, consequence, and a signpost to the plan. Notice what it doesn’t do: apologize, pre-frame, or spend its one sentence on context. (The format itself is covered in how to write an investor update.)

The format under stress

The seven-section format was designed for exactly these months — each section has a stress-mode job:

• What changedstates the delta plainly and points at the cause: “Two enterprise churns took MRR down 5.4%; both cited the missing SSO story.”
• The metrics block stays complete. Dropping runway from the block on the month it shortened is the single most noticeable omission you can make.
• What won still appears — smaller, honest, not inflated to counterweight the bad news. A thin real win beats a padded one.
• What’s hard becomes the load-bearing section: the number, the honest cause, the plan, in that order.
• What we need converts the problem into a specific ask. Bad months are when investors most want to help and are least often given a way to.

A worked hard month

Take the sample company from these guides in a rougher April: CAC ran $410 against a $340 target while paid spend scaled. The weak version hides it inside “we leaned into our growth engine and learned a ton.” The strong version:

What’s hard. CAC crept to $410 against a $340 target. Paid channels are doing less of the work than the pipeline suggests, so May’s plan trims spend until the outbound math is proven.

Then the ask makes the problem workable: “If you know a growth lead who’s fixed CAC drift at seed stage, one intro would save us a month of guessing.” The complete update this excerpt comes from is annotated in investor update examples.

Spin words to ban

Spin is detectable as vocabulary. Each of these phrases has a plain version; use the plain version:

• “Growth moderated” → “MRR fell 5.4%.”
• “We’re seeing some headwinds” → name the metric and the number.
• “Strategic pivot” → what stopped working, and what you’re doing instead.
• “Extending our runway conversations” → “the raise is taking longer than planned; here’s the bridge math.”
• “Right-sizing the team” → “we let four people go, cutting burn to $31k.”

When it’s runway-level serious

There’s a tier of bad news where the update format stops being the whole answer: anything that moves your survival math. If the miss changes the runway picture, recompute it before you write — how to calculate startup runway covers the honest version, and the free runway calculatorgives you the zero-cash date in thirty seconds. Then answer Paul Graham’s question — are you default alive?— and tell investors which side of it you’re on and what the plan assumes. A stated plan with dated checkpoints turns the scariest update you’ll ever send into the one that proves you can run a company through weather.

Questions