You closed the round a few weeks ago. Somewhere in the paperwork there was a line about regular reporting, and now one of your investors has asked when the first update is coming. You have never written one, and you are not sure whether they want a deck, a spreadsheet, or an email.
Short version: they want an email, monthly, that takes under two minutes to read. Not a deck.
A board meeting and a board update are not the same thing
These get conflated, and the confusion is why founders overbuild their first one.
A board meeting is a scheduled session with your formal board, and it comes with a deck circulated in advance. NextView Ventures makes the useful point that the deck is a pre-read rather than a presentation aid, and that more than half the meeting should go to actually discussing problems instead of narrating slides. At pre-seed and seed you may have two or three people on your board, or no formal board at all, and meetings might be quarterly.
A monthly investor update is an email to everyone who put money in. It is the instrument that matters at your stage, and it is the one to start now.
If you do nothing else after reading this, start the monthly email. Consistency does more for you than polish.
The four numbers
Every update needs these, in the same format, every month:
| Metric | What it answers |
|---|---|
| MRR (or your revenue equivalent) | Is it working? |
| Net burn | How fast is cash leaving? |
| Cash on hand | How much is left? |
| Runway | How long until you need to raise? |
Two questions sit behind every investor read: is this working, and how long can you keep going. Those four answer both. Add a fifth company-specific metric only when it genuinely explains the month.
Note net burn, not gross. Gross burn is what you spent. Net burn is what you spent minus what came in, and it is the number that sets runway. If you are pre-revenue they are the same, which is fine, but say which one you are reporting.
Then the rule most first updates fail: your runway has to be derivable from the cash and burn you just reported. If you say you have $400,000 in the bank and you are burning $50,000 a month, your runway is eight months. If you then write "runway: 12 months" because you are assuming revenue growth, you have handed a careful reader a contradiction inside the same paragraph. Report the arithmetic honestly, or show the assumption explicitly.
Our post on burn rate and runway works through how to calculate both properly, and the MRR post covers the revenue side.
Freeze your definitions
If burn means net burn in January, it means net burn in December. If customer count means paying customers in one update, it cannot quietly become signups in the next.
This sounds pedantic. It is the difference between an update investors can read as a trend and one they have to reinterpret every month. If you do have to change a definition, say so rather than hoping nobody notices. They notice. Investors read updates side by side, and a metric that quietly changes shape reads as something being hidden.
The three sections that carry the story
What changed. One or two sentences comparing this month to last. It is the section founders leave out, and without it your reader is reconstructing the trend from memory.
What is not working. This is where the update earns trust or loses it. Every company has something hard every month, and naming yours plainly, with the number attached, is what makes the good news believable. Not "sales is slower than we hoped" but "our average sales cycle went from 43 days to 67 days, we think because we moved upmarket, and here is what we are doing about it." An update that is all wins reads like marketing, and the reader discounts the wins accordingly.
What is next. One to three things that define success in the next thirty days, specific enough that your investor can check them against next month's update. "Grow faster" is not checkable. "Close the two deals in final negotiation" is.
The ask
One ask. Two at most. A list of five gets none of them acted on.
Make it specific enough to act on without a follow-up question. "Intros would be great" produces nothing. "A warm intro to a VP of Operations at a 200 to 500 person SaaS company evaluating workflow tools this quarter" produces an intro.
Your investors see a lot of companies and know a lot of people. The ask is the only part of the update that puts any of that to work, and most founders waste it.
What it looks like filled in
Here is a complete example. The company and every number in it are invented for illustration.
Subject: Northwind, August 2026 update
We closed August at $18,400 MRR, up 11% from July, added six customers, and lost our largest pilot. Focus for September is converting the four remaining pilots.
By the numbers
Metric Aug Jul Change MRR $18,400 $16,600 +11% Net burn $41,000 $38,500 +$2,500 Cash $612,000 $653,000 Runway 14.9 months at current net burn Customers 34 28 +6 What changed. Growth came almost entirely from the self-serve tier, which we did not expect. Six of eight new accounts arrived without ever talking to us.
What is not working. We lost the Brightline pilot, worth $2,100 of expected MRR. They needed SSO and we do not have it. That is the third deal SSO has cost us, so it moves up the roadmap for September.
What is next. Ship SSO. Convert at least two of the four open pilots. Hold net burn under $42,000.
Ask. We are hiring a first support engineer. If you know someone who has done support at a sub-20-person B2B company and wants more ownership, I would like the intro.
Numbers behind this are in the shared folder. Reply any time.
Under 200 words plus a table, which is shorter than the range below and perfectly fine. It took fifteen minutes to write because the format did not change from last month.
Notice that the numbers agree with each other. Cash fell from $653,000 to $612,000, a drop of exactly the $41,000 net burn reported on the line above. Runway of 14.9 months is $612,000 divided by $41,000. A reader can check every figure against the others in about ten seconds, and that is the point.
Length, cadence, and two things before you send
Aim for 250 to 600 words plus the metrics block. TechCrunch's guide puts seed and Series A updates in the 250 to 750 word range, which matches what investors say they actually read. Longer is not more thorough. An investor who wants detail will reply and ask, and that reply is worth more than the detail would have been.
Send monthly, on a fixed date, whether the month was good or bad. Draft it a week ahead so a bad week does not turn into a missed update.
Then two checks that cost nothing. Search the draft for the word "excited" and delete it. And confirm that nothing in the update contradicts what you said last month, by reading the previous update rather than trusting your memory.
Pulling these four numbers together should take minutes, not an evening of reconciling spreadsheets. That is the part Fintoit handles: burn, runway, MRR, and cash stay current, and the board-ready version generates off them.