Founders & Small BusinessFree
Investor Update Backfill After Silence
The whole gap reconstructed from records you already have, with the interior shown only for the metrics whose path differs from the straight line.
River rebuilds the silent period from the records that already hold it, then tests each metric against the straight line between the last figure your investors have and today's. What comes back is a sheet with one row per missed period on today's definitions, and the catch-up message itself, which opens up only the metrics whose path differed from that line and gives the rest two points. The reason for the gap goes into the message itself, rather than into a preamble nobody reads.
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.
Three of five metrics needed the middle
Osney Instruments last reported March, then went quiet for eleven months. Cash read $1,412,000 in March and $1,108,000 in February. Both true, and together a gentle decline. The straight line between them puts October at $1,218,545. October actually closed at $318,000, which against a trailing three-month net burn of $171,000 was 1.9 months of runway. The interpolated October reads 7.1 months. Two dated events explain the shape: twelve roles cut on 30 October, and a $1,050,000 bridge closed on 19 November.
That is the test the whole catch-up turns on. For each metric, measure the widest gap between the path it took and the line between its two reported ends, as a share of the last figure they hold. Cash came out at 63.8%, net burn 106.7%, headcount 48.8%. Revenue managed 4.2% and customers 2.5%, so those two are one line each. Public filers work under a rule requiring whatever further information keeps a true statement from being misleading.
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
When the last one went out, what it said, and who received it.
Add the records
Bank statements, billing exports and payroll for every month since, in whatever form they exist.
Add what happened
The departures, the cuts, the bridge, the customer you lost, each with its date.
Read the shortlist
Which metrics need the months in between, then approve the cadence you can actually hold.
What you get
- One row per missed period, rebuilt from bank, billing and payroll records you already hold
- Every metric tested against the straight line between the last reported figure and today's
- The interior shown only where the path differed, so the message stays readable
- Events inside the gap listed with their dates, including the ones you would rather not
- The reason for the silence written as a reason, with a date attached
- A going-forward cadence sized to 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.
Investor Update Backfill After Silence
Fill in the form and your workspace opens with the work already underway.