The monthly investor update is one of those tasks that's never urgent until Friday afternoon, and then it's the only thing you're doing for four hours. The reason it takes four hours isn't the writing — most updates are six paragraphs and a metrics table. It's the assembly. You're hunting through Slack for the customer-win that happened two Wednesdays ago, scrolling the dashboard for last month's churn delta, opening the last update to remember what you said about the hiring pipeline, and trying to remember whether you already mentioned the new partnership or are about to mention it for the second time.
The fix isn't a fancier template. It's holding the source material in one place that an agent can read across — wins, hires, customer notes, board questions, prior updates — so the assembly stops being a four-hour scavenger hunt. The same shape underwrites annual planning and goal setting and the cycle around a board-of-directors meeting, which usually feed into the same investor narrative.
A vault shaped around the update cadence
The shape that holds up across rounds and stages is roughly: one top-level page for investor relations, with sub-pages for the running narrative, the metrics commentary, the board-question log, the prior updates archive, and the per-investor context. Capy supports unlimited page nesting, so you can fan out into per-investor sub-pages for the partners who ask follow-up questions or want different framing.
The whole vault is plain markdown. That matters because when you sit down to write the next update, you ask the agent to read across every relevant page in one query and draft a starting version. The friction of "where did I write that down" goes away. The thing you're left with is the actual writing — which is the part that should be hard.
Wins and lowlights captured the moment they land
The hardest part of the monthly update isn't the metrics — it's remembering the qualitative wins and the honest lowlights from four weeks ago. By the end of the month, the customer who churned in week one feels like ancient history, and the partnership announcement that landed on day three is a blur.
A working setup: a "monthly log" page where you drop a one-line entry whenever something happens worth telling investors about. Customer signed, customer churned, hire started, hire left, partnership shipped, partnership stalled, regulatory thing surfaced. You're not writing the update; you're capturing a breadcrumb. Two minutes per week, max. (The same capture pattern shows up in first-time founders moving faster — the underlying habit is identical.)
When update day arrives, ask the agent: read this month's log, group entries by category, and surface anything that contradicts something I said in last month's update. You get a sorted list of source material with the inconsistencies flagged. The contradictions are usually the most interesting part of the update.
Metrics commentary that doesn't restart from blank
The numbers come from your dashboard. The commentary is what investors actually read. Most founders write the commentary from scratch every month, which means they re-derive the same baseline framing about why ARR moved or why CAC drifted, and the framing slowly drifts away from how they actually think about the business.
A working flow: keep a "metrics commentary" page where each KPI has a short paragraph explaining how you currently think about it, what would constitute a real signal versus noise, and what you're watching for. When you sit down to write the month's commentary, ask the agent to read the current numbers (you paste them in or attach the export) plus the framing page, and draft commentary in your existing voice.
You edit. The draft is rarely right out of the gate, but it gives you something to push against — which is faster than starting blank. And the framing page itself becomes a quiet document of how your thinking on the business has evolved.
Board questions that stop dying in the meeting
A specific failure pattern: a board member asks a hard question in the November meeting. You give a partial answer in the room. You promise to follow up. In the December update, you forget. By February, the board member has either forgotten too or — worse — quietly noted that you don't follow up on hard questions.
The fix is mechanical. Have an inline database called "board questions" inside your investor-relations page, with rows for date asked, who asked, question, answer, status, follow-up date. The database lives directly in the page via the :::database::: directive — you don't switch to a separate tab.
After every board meeting, ask the agent to read the meeting recap and propose new entries. You confirm or edit. Before you draft the next update, ask the agent to surface any open questions older than thirty days and remind you what's still owed. The follow-up becomes part of the update instead of a thing you keep meaning to do.
Per-investor context, with PDFs from the last raise alongside
Investors aren't a monolith. The lead at the last round wants depth on unit economics. The angel from the seed wants founder-mode storytelling. The strategic on the cap table wants integration angles. Sending one update is correct, but knowing which investor will follow up with which question — and being ready — is what makes the conversations afterward shorter and warmer.
A working setup: a sub-page per investor relationship with their typical follow-up patterns, the questions they've asked over the years, and the topics they care most about. After every investor conversation, drop a short recap on their page. Drop the original deck and any memos from the round on the same page; they auto-convert to markdown via docstrange so the agent can read them as searchable text. Before sending the monthly update, ask the agent to read the per-investor pages and predict who's likely to reply with what — and to surface places where this month's actuals are diverging from the projections you made in the last round's deck. The same workflow underwrites our writeup of due diligence in acquisitions — different artifact, same mechanic of treating PDFs as searchable text.
Drafting the update from the vault
Once the source material is captured, the actual writing gets short. A working flow: fresh page, paste in the metrics, tell the agent to read the month's log, the metrics commentary framing, the open board questions, the relevant context from the last raise, and draft a v1 update in the voice of last month's update.
You edit. The draft is usually 70% of the way there because the agent has actually read your prior updates and your framing page — it's not generating from generic web data. The 30% you change is the editorial judgment about emphasis and tone, which is the part that's actually yours. (The drafting-from-vault pattern is the same one agency owners use to take on more work without hiring — different deliverable, same speed-up.)
The update goes out on Friday afternoon instead of Friday evening. The compounding effect is real over a year of updates, and the quality goes up rather than down.
What this isn't
Capy doesn't replace your dashboard, your CRM, or your data room. The structured-data side of investor relations still lives in the tools that handle structured data. Capy is for the unstructured side — the wins log, the commentary, the board-question history, the per-investor context — which is the part that's currently sprawled across Slack and Drive and your head.
It's also single-user by design. One operator, one vault. If your investor-relations function is a multi-person team passing documents around with role-based permissions, that isn't this product. The shape that fits is a founder or solo IR lead who wants the assembly cost of the monthly update to drop without dropping the quality. Pricing tiers are on the pricing page if you want to see what scales with you.
A small first test
Take the last three monthly updates you sent. Drop them in a Capy page along with this month's wins-and-lowlights log. Ask the agent to draft a v1 of this month's update in the voice of the prior three. If the draft surfaces something from the log you'd otherwise have forgotten — or catches a contradiction with last month's narrative — you've got the sense of what the agent does for you across the rest of the year.
Try Docapybara free. Run one month's update from a vault and see how Friday afternoon feels.