Izveidot kontuCreate account
‹ All playbooks
Write the monthly investor update

management.investor-update·version 1.0.0·draft

Write the monthly investor update

Investors receive a one-page update with the month's numbers, progress and asks, and the company has a record of what was sent.

KristapsData Analystruns itProfile ›
Whenscheduled · monthly — monthly, fixed day agreed with investors (e.g. the 5th workday after month end)
Who actsthe agent acts after approval
Time60–90 min active, spread over 1–2 days
Countryany country
Sign in to run thisThis playbook opens inside Brain Club. Sign in to read and run it.

When to use

The monthly reporting date arrives and investors are owed an update. Not for the internal monthly review of the business itself — use money.month-close first (this playbook consumes its outputs) and growth.monthly-growth-review for the internal reading of the same numbers. Not for a formal board pack or board meeting — use management.board-meeting.

Before you start

  • money.month-close for the reporting month is done — revenue, costs, cash and runway are final, not draft.
  • The recipient list is confirmed with the owner, including who is excluded this month.
  • The owner has said, in one sentence, the month's headline (good or bad) and anything that must not go out.

What a run requires3

  • Approval · S5 · ownerthe run stops until a named person records the decision
  • Approval · S6 · ownerthe run stops until a named person records the decision
  • Irreversible · S7an agent never closes it alone

Any step can wait until a date and reopens by itself; every closed step leaves evidence (a note, a link, a number).

The trail8 steps

  1. Pull the numbersagent

    Take revenue, gross margin if tracked, costs, cash on hand, runway in months, and headcount from the month-close records for the reporting month. Note the source record for each figure.

    Done when every number in the draft has a named source and month.

  2. Pull progress against goalsagent

    Read the current goals and the tasks moved in the month; list what shipped, what slipped and why in one line each. Use bc goals add if a goal the update references does not exist as a record yet.

    Done when the progress section covers every goal an investor was told about last month.

  3. Collect the asks and the lowlightsagent

    Open items where the company needs investor help (hiring, intros, a follow-on decision), and the month's misses.

    Done when the asks list names, for each item, who acts and by when.

  4. Draft the updateagent

    One page: headline, the numbers table from S1, progress, lowlights, asks, cash position and runway. Plain sentences; no adjectives doing the work of numbers. Link to dashboards rather than pasting unstable screenshots.

    Done when the draft exists as a document with the source links inline.

  5. Check the draft against the sources, then the owner reviewsagentneeds approval · owner

    Approval · S5 · owner — the run stops until a named person records the decision

    Read every number back against its source record; flag any that differ. Then present the draft plus the sensitive-information check (no unreleased customer names, terms, or personnel matters) to the owner.

    Done when the owner has marked edits or said "send as is", and the recipient list is confirmed.

    ⛔ A number the owner cannot trace to a source record does not go out — re-derive it or cut it.

  6. Approve final text and recipientsownerneeds approval · owner

    Approval · S6 · owner — the run stops until a named person records the decision

    Done when the owner has approved the exact text and the exact recipient list, named.

  7. Sendagentirreversible

    Irreversible · S7 — an agent never closes it alone

    Send to the approved list only; bcc or individual sends so addresses are not shared. If any number was corrected after S5, say so in the send note.

    Done when the sent message is in the archive folder and each recipient is recorded.

  8. Record and set up next monthagent

    Archive the sent update and the source snapshot; create next month's draft task with the reporting date; copy unresolved asks into it.

    Done when next month's draft task exists with the date and the carried-over asks.

Checks — how we know it worked

  • Every number in the sent update equals the number in its named source record (read back, not remembered).
  • Recipient count on the sent message equals the approved list, no more.
  • The update contains no item the owner marked as not-for-sharing.
  • Cash and runway figures match the month close to the euro / to the month.

If it goes wrong

SymptomResponse
A wrong number discovered after sendingSend a correction within one workday, stating old value, correct value, cause; record both in the archive.
Sensitive information reached the wrong listTell the owner immediately, assess what leaked, agree the message to affected parties; tighten the recipient check in S5 in the next version.
Month close not ready on the reporting dateSend a two-line holding note with the new date; do not send draft numbers.
Recipient list disputedDo not send until the owner re-confirms in writing; keep last month's list as the baseline.
Update late by more than a weekNote the cause in the archive record; if it recurs twice, move the reporting date in this playbook's next version.

What each step leaves behind

  1. S1every number in the draft has a named source and month.
  2. S2the progress section covers every goal an investor was told about last month.
  3. S3the asks list names, for each item, who acts and by when.
  4. S4the draft exists as a document with the source links inline.
  5. S5the owner has marked edits or said "send as is", and the recipient list is confirmed.
  6. S6the owner has approved the exact text and the exact recipient list, named.
  7. S7the sent message is in the archive folder and each recipient is recorded.
  8. S8next month's draft task exists with the date and the carried-over asks.

Evidence to keep

The sent update (text or PDF) · the approved recipient list · the owner's approval in S5 and S6 (who, when) · the source snapshot behind the numbers · any correction issued, with its cause.

How this playbook improves

After every 6 runs ask: how many days from month end to sent, and which step waited? Were any corrections issued after sending, and at which check should they have been caught? Which sections did investors reply to — keep those, cut what drew no response? A new version changes the step that caused the wait or the miss, and says so in its change note.