B-04 · in design

Investor Update Generator

The investor update, drafted from the numbers you already track and gated before it sends.

01  the number that stalled

odds of raising follow-on funding, relative 2x1x

Startups that send consistent investor updates are twice as likely to raise follow-on funding (Visible platform data). The update is the first thing that slips when the month gets hard, and the silence reads as a signal even when the business is fine. Going quiet costs real odds.

02  the system, specced

The generator turns operating data into the investor update, on a cadence that holds. Point it at the numbers you already track and each month a ready letter arrives: the metrics with their movement explained, the wins, the asks, the honest flags. The draft generates live via the Anthropic API and lands in the founder's voice. You read it, fix the one thing it flags, and send. Nothing sends without you.

The checking stays under the hood: every figure traces to a source before the draft reaches you, and a claim that fails its check surfaces as one plain fix, with a button that applies it. The record view keeps the streak, one line per month, and carries every ask forward until it closes. I have written the monthly update from the operator's seat, and the system is built around the part that actually stalls: the blank page on a busy day.

03  product screens

concept screen · the draft: the letter as a folio page, the checks as margin notes from your editor
concept screen · the draft: the letter as a folio page, the checks as margin notes from your editor
concept screen · the record: a table of contents of issues sent, the streak and asks in the sidebar
concept screen · the record: a table of contents of issues sent, the streak and asks in the sidebar

04  specced / scope

specced

  • Drafts generate live via the Anthropic API from connected operating data.
  • Every number in the draft traces to its source.
  • The draft anticipates the reader: likely investor questions surface up front, each answered in the letter.
  • A failed check surfaces as one plain fix, with a button that applies it.
  • Human pass required; the system drafts, the founder sends.
  • A record view: the streak, one line per month, and every ask carried to close.

scope

  • No analytics cockpit, by design: the letter and the record carry everything.
  • Investor updates only in v1. Board packs are a different artifact and a later decision.
  • Metric connectors start with a spreadsheet and a paste. Live integrations come after the voice holds.

status  in design · concept and screens first, code after