Key takeaways
- Most investor updates are written from memory, late, by a founder who is already behind.
- The aim is a starting point drawn from the company's own email, meetings and records: what moved, what slipped and what was promised last time.
- Promises made in earlier updates are checked against what happened, so the founder can address them before investors ask.
- The founder writes and approves the update, and nothing is sent without approval. In pilot today with design partners.
The problem
A good investor update is short, honest and regular. It says what moved, what slipped, what the company learned and where investors can help. Founders know this, and most still find the update one of the hardest things to write each month, because the facts are scattered across months of email, calls, chat and spreadsheets.
Picture the last working day of the month at a 25-person startup. The founder blocks two hours in the evening for the update. She opens last month's update to copy its structure, then spends the first hour hunting: which customer signed, which hire accepted, what the pilot partner said on the call last week, whether the product launch is still on the date she gave last month. By the time she has the facts, she is tired, and the update says less than it should.
The bigger risk is the promise she forgot. Last month's update said a pilot with a large customer would start in November. The customer has since asked to move it to December, in a thread with the sales lead that she skimmed. If this month's update stays silent, an investor who reads carefully will notice, and the next conversation starts with a question about trust instead of a question about help.
Updates written from memory drift toward good news and skip quiet slips. The cost is credibility at the moment the founder needs it most: the next fundraise.
What GeniOS is designed to surface
In pilot, GeniOS is designed to give the founder a prepared starting point before the update is due, drawn from email, calendar, chat, meeting notes and the business tools the company already uses.
- What moved. Customers signed, hires made, milestones reached, each tied to the email or record that shows it.
- What slipped. Dates that moved since the last update, with the thread where the change happened.
- Promises from earlier updates. Commitments made to investors last month or last quarter, with whether they were kept.
- Open investor asks. Introductions, numbers or documents investors asked for that have not been sent.
GeniOS thinks and delegates; it does not write the update itself. The founder can delegate the first draft to a drafting agent working from these facts, then edit and approve it. Each item ends with Delegate, Done, Later or Not relevant. For the promises themselves between updates, see Strategic Commitment Tracking; for investors waiting on a reply, see Relationship & Opportunity Intelligence.
A worked example
Example at a generic company. Names, dates and numbers are made up to explain the idea.
A 25-person software startup sends a monthly update to six investors. The founder writes it on the last working day of the month. In October, three things happened that she has not connected: two new customers signed, one of three planned engineering hires accepted an offer, and the pilot promised in the September update for November moved to December at the customer's request.
Here is how it would look in pilot: two days before month end, the founder receives one note. It lists the two signed customers with their contract emails, the one accepted offer, and the moved pilot, with the thread where the customer asked for December. It flags that the September update promised the pilot for November and suggests she explain the move in this update. It also notes that one investor asked three weeks ago for an introduction list that was never sent.
She delegates a first draft to a drafting agent and the introduction list to her operations lead. On the last day she spends twenty minutes editing the draft, adds a line on what she learned from the pilot delay, and approves it. The item closes when GeniOS sees the sent update, and the investor's introduction list closes separately when that email goes out.
How teams use it day to day
Investor Update Preparation is designed around a monthly rhythm, with a few minutes of attention through the month.
- Keep promises visible
When an update makes a promise, it stays visible through the month alongside the work that should deliver it.
- Read the prepared facts
A few days before the update is due, read what moved, what slipped and which earlier promises are affected.
- Decide what to say about slips
Choose how to explain each slip, so investors hear it from the founder first.
- Delegate the draft
Hand the first draft to a drafting agent, then edit and approve it. Nothing goes out unapproved.
- Close open asks
Send the introductions, numbers or documents investors asked for, and let the sent emails close them.
Where it applies
These are application areas where this use case can apply, not a list of current deployments. Our design partner work so far is in manufacturing, with Vaultex.
The use case applies to any company that reports to investors regularly. That includes software and technology startups, e-commerce and retail brands, financial services firms, life sciences companies and energy businesses raising capital. Investor relations, the executive office and finance would share the same record of what was promised and what happened.
- Domains: Investor Relations, Executive Office, Finance
- Industries: SaaS & Technology, E-commerce & Retail, Financial Services, Pharmaceuticals & Life Sciences, Energy & Utilities
- Roles: Founders
Status
Pilot We are shaping this use case with design partners now, and it is not yet a finished part of the product. If this is a problem you have, talk to us about shaping it with us. Design partners help us decide which facts a founder needs first when an update is due.