The Web3 Founder's Monthly Investor Report Checklist

Investors don't read your monthly update to feel good about the project. They read it to answer a small, fixed set of questions before they have to think about you again next month. The checklist below covers those questions in the order they get asked.

Most founders treat the monthly update as a writing exercise. That's why they slip on it — writing is open-ended and feels easy to deprioritise. Treat it as a checklist instead. Each item below has a definite source (on-chain, GitHub, calendar, or a single sentence from you), so the report can be assembled in twenty minutes once the data is in front of you.

Treasury, in three numbers

1. Total treasury value at period end, with month-over-month change. 2. Stablecoin balance — separate, because it's the only asset that doesn't move with the market. 3. Native-token share of the treasury as a percentage. If that number is above 70%, the runway conversation needs a haircut applied.

Flows, in two numbers

4. Total inflows for the period (grants, token sales, revenue). 5. Total outflows broken down into operating categories (payroll, infra, marketing, grants, legal) plus a separate "treasury operations" line for token-sale rebalances. The reason for separating treasury ops is simple — investors who see a $2M outflow without context will assume burn, not rebalance.

Runway, with a caveat

6. Trailing-three-month operating burn (not just this month — single months are noisy). 7. Months of runway at that burn, using the operationally-liquid portion of the treasury (stablecoins + a conservative haircut on native ETH, near-zero credit on the project's own token if it's thinly traded). A range is more honest than a point estimate.

Engineering, in three signals

8. Commits and merged PRs across the engineering org for the period. 9. Active contributor count — proxy for headcount engagement. 10. One sentence on the major shipped item this month, with a public link if available (Etherscan tx, repo release, blog post). The first two come straight from GitHub; the third is the only piece you write fresh.

Token, when relevant

11. If you have a public token: price change MoM, market cap, holder count delta, and the next vesting / unlock event with a date and percentage. Skip this section entirely if you don't have a public token — padding it with vague "market context" looks worse than not including it.

The one thing investors will actually email about

12. A two-line "asks" section. New hire intros, BD intros to specific firms, a request to be added to a fund's portfolio dashboard. Investors who feel useful re-up next round. Investors who get pure-status updates feel like passengers and start to disengage.

How to actually do this every month

Pick a fixed day (most teams find the 3rd works — late enough that the previous month is fully closed, early enough that the report lands while investors are still planning the new month). Generate the source data in one pass; write only the executive summary, the one-line major-ship, and the asks fresh. The other ten items are mechanical. Vault Brief automates the mechanical ones — leaving you with three sentences to write.

Want this checklist as a Vault Brief report template? Sign up — the 14-day trial generates a real report for your treasury inside ten minutes.

Get these metrics in every report automatically

Vault Brief generates investor-ready reports from your on-chain data. No spreadsheets.