Founders & Small BusinessFree
Investor Update Backfill After Silence
Share your last update and your records since, and get one honest catch-up update that covers the whole gap and shows the months that matter.
River rebuilds the months you missed from records you already have, such as bank statements, billing exports and payroll. Then it checks each number against the simple line between the last figure your investors saw and today's. You get a Sheet with one row per missed month on today's definitions, and the catch-up update itself. The update spells out the months only for numbers that dipped or spiked along the way, gives the rest one line each, and explains the silence in a sentence.
The reason the next update never goes out is not shame, it is arithmetic. Eleven missed months look like eleven updates to write, so nothing gets written. They are not. Most metrics moved the way anyone would guess from the two endpoints, and those need one line each. The two or three that did something else are the entire content of the catch-up, and they are identifiable before you write a word, from records you already have.
Written for a founder who last wrote to their holders a long time ago, knows it, and has been putting it off for exactly that reason. Reach for it when you want the next twelve months to be different rather than to produce a single apologetic email. Once the gap is closed, the cadence that keeps it closed is a monthly update on pinned definitions, and its board-facing twin is a board meeting pack, with the board deck writer drafting the next pre-read.
Which months a catch-up update has to show
Osney Instruments, a fictional hardware startup, last reported in March, then went quiet for eleven months. Cash read $1,412,000 in March and $1,108,000 the next February. Both true, and together a gentle decline. A straight line between them puts October at $1,218,545. October actually closed at $318,000, which against $171,000 of monthly net burn was 1.9 months of runway, not the 7.1 the line suggests. Two dated events explain it: twelve roles cut on 30 October, and a $1,050,000 bridge on 19 November.
That is the check the whole update turns on. For each number, find the month where the real path strayed furthest from the straight line, as a share of the last figure investors saw. Cash strayed 63.8%, net burn 106.7% and headcount 48.8%, so those three need their months shown. Revenue strayed 4.2% and customers 2.5%, so one line each is honest. Public companies must add whatever further information keeps a statement from being misleading, a sound standard here too.
The last piece is the promise, because the broken one started the silence. Osney had committed to monthly, but its books closed an average of 34.4 days after period end and inside 30 days in only 3 of 12 months. Inside 45 days it managed 11 of 12. When a public filer is late it must state why, in reasonable detail, and the date the report will arrive. A date the close calendar supports is the only kind worth writing.
How it works
Name the gap
Paste your last update, or its date and figures, and say who received it.
Add the records
Attach bank statements, billing exports and payroll since, and list what happened, each with its date.
Get the update
River rebuilds each month, picks the numbers that need their months shown, and writes the catch-up update.
Send and keep going
Edit the update in chat, send it yourself, and set up the next one on a schedule you can keep.
What you get
- One row per missed month, rebuilt from bank, billing and payroll records you already have
- Each number checked for dips or spikes that the first and last figures alone would hide
- Months spelled out only for the numbers that need them, so the update stays short
- Events during the gap listed with their dates, including the ones you would rather skip
- The reason for the silence written in one plain sentence, with the date of the next update
- A realistic schedule for future updates, based on how long your books actually take to close
Common questions
How far back do I actually have to go?
To the last figure they hold, because that is the number your new one gets compared against. Osney's gap was eleven months and the message covered all of it, but only three of five metrics needed the months in between spelled out. Length of gap decides how much you reconstruct, not how much you send.
Can I just send today's numbers and move on?
You can, and it is the most common version. It is also where the trouble sits: two accurate endpoints can describe a path that never happened. Osney's endpoints implied 7.1 months of runway at the low point against an actual 1.9. That gap surfaces later, in a diligence process, and then it looks deliberate.
Do I have to explain why I stopped writing?
Give the reason, once, in a sentence, with a date for the next one. The discipline public filers work to is the reason in reasonable detail plus the date the report arrives, and it is a good shape here. What does not work is three paragraphs of apology, which reads as the same avoidance in a different font.
What cadence should I promise going forward?
Whatever your close calendar has already demonstrated. Osney had promised monthly while closing its books inside 30 days in 3 of 12 months, and inside 45 in 11 of 12. So the promise became quarterly at 45 days, plus a monthly two-line note on the metrics that need no close at all.
Something happened in the gap that I would rather not raise.
Then it is probably the one thing that has to be in there, with its date. A bridge, a departure, a redundancy round and a lost anchor customer all reappear in the next diligence pack. Where a bridge or notes changed what people own, the arithmetic is a SAFE and note conversion model.
One of my investors has already asked me for numbers.
Then answer the request and close the gap in the same week, but not in the same document. The request has its own lanes and its own deadline, which is an investor data request response. The catch-up goes to everyone, and it is what stops the next request from arriving as a chase.
Will it write the financial statements too?
No. It reads what your systems already produced and records where each figure came from, which is what makes the eleven months comparable to each other. Building the statements underneath an update is a different job, done by investor update financials, and it wants a finance function rather than a founder.
Sources
Built by
Chandler Supple
Co-founder & CEO, River
Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.
Investor Update Backfill After Silence
Describe what you need, add any files you have, and your workspace opens with the work already underway.