A monthly investor update, drafted from your notes

Send the same short update every month: a one-line headline, the numbers, the wins, the lows, and one clear ask. Keep the facts in your folder as the month happens, let an AI agent draft the update from them, and spend your half hour on the parts only you can write.

Why updates slip

The writing isn’t the hard part. The gathering is: last month’s numbers, where the pilot stands, the three decisions you made, spread across tools and chats. So the update waits for a quiet week that doesn’t come, and a missing update says more than a flat month would have.

What to put in it

Keep the shape the same every month, so investors can compare one update with the last:

1. Headline. The month in one sentence.
2. Numbers. The same few every time: cash, burn, runway, and the metric your stage runs on, such as pilots, active users or revenue.
3. Wins. Two or three, each with a number or a name.
4. Lows. What didn’t work, and what you’re changing because of it.
5. Asks. One or two specific ones: an intro to a named company, a candidate for a role, an hour with someone who has solved your problem.
6. Thanks. Name the people who helped.

The notes that make it draftable

An agent can only draft from what’s written down. Four habits cover it:

• A monthly snapshot with the numbers in fields (tracking MRR, costs and launches in markdown).
• Decision files, dated, each with the reason.
• Your weekly reviews (a weekly review for a company of one).
• Last month’s update, so the draft carries the thread: what you said you’d do, and whether you did.

Let an agent draft it

Save a template at templates/investor-update.md:

---
type: InvestorUpdate
description: September 2026 update. Draft.
tags: [Investors, Business]
month: 2026-09
---
# Headline
# Numbers
Cash:
Burn:
Runway:
Main metric:
# Wins
# Lows, and what changes
# Asks
# Thanks

Then open Claude Code, Codex or Cursor in the folder and ask:

Draft the investor update for September 2026 in updates/2026-09.md
from templates/investor-update.md. Read last month's update, this
month's snapshot, the decisions dated this month and the weekly
reviews. Use only numbers from those files, and link each one to its
source file. Mark anything you're unsure of with [check]. Don't
send anything.

Asking for the source of every number is the step that makes the draft checkable. You read the update with the files one click away.

What stays yours

The draft puts the facts in order. The update is still yours:

• The headline, and how honestly the lows read.
• Which ask matters most this month.
• Anything about people, fundraising or plans that isn’t in the files yet.
• Sending it. The agent drafts. You read it, correct it and send it.

Keep the agent out of what the update doesn’t need, such as your journal. Telling it to skip those files is a request. Scoping it is a boundary (scoping an AI agent with tags).

Where Oknola fits

In Oknola, an agent allowed the BusinessOS tag drafts the investor update, and it never opens your journal. Oknola types, tags and files what lands in the folder as the month happens, so the snapshot, the decisions and the weekly reviews are there when the draft needs them. See it on the solo founders page, and what is available today is on the roadmap.

Questions people ask

How long should an investor update be?

Short enough to read on a phone in two minutes. Keeping the same sections every month makes it quick to skim and easy to compare.

Should I send an update in a bad month?

Yes. A short, honest update in a bad month builds more trust than silence, and the lows are where investors can help.

What numbers should a pre-revenue founder report?

Cash, burn and runway, plus the metric your stage runs on: pilots, active users, waitlist growth or conversion from trial. Report the same ones every month.

Can the agent send the update for me?

Keep sending with you. Read the draft, check each number against the file it links to, and send it yourself.