Sagatavot ikmēneša investoru atjauninājumu

Kad izmantot

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.

Pirms sāc

• 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.

Ko izpilde pieprasa3

Ceļš8 soļi

1. S1

   Pull the numbersaģents

   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.

   Izdarīts, kad every number in the draft has a named source and month.

2. S2

   Pull progress against goalsaģents

   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.

   Izdarīts, kad the progress section covers every goal an investor was told about last month.

3. S3

   Collect the asks and the lowlightsaģents

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

   Izdarīts, kad the asks list names, for each item, who acts and by when.

4. S4

   Draft the updateaģents

   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.

   Izdarīts, kad the draft exists as a document with the source links inline.

5. S5

   Check the draft against the sources, then the owner reviewsaģentsvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S5 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   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.

   Izdarīts, kad 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. S6

   Approve final text and recipientsīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S6 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Izdarīts, kad the owner has approved the exact text and the exact recipient list, named.

7. S7

   Sendaģentsneatgriezenisks

   Neatgriezenisks solis · S7 — aģents to nekad nenoslēdz viens

   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.

   Izdarīts, kad the sent message is in the archive folder and each recipient is recorded.

8. S8

   Record and set up next monthaģents

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

   Izdarīts, kad next month's draft task exists with the date and the carried-over asks.

Pārbaudes — kā zinām, ka izdevās

• 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.

Ja noiet greizi

Ko atstāj katrs solis

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.

Ko saglabāt

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.

Kā šī procedūra uzlabojas

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.