Project Leader
Draft the monthly investor update before you remember it's due
Assembles revenue, burn, pipeline, and shipped work from your APIs and repo into a draft update; you edit one paragraph instead of writing five.
The investor update is due the same week every month, and every month it eats an evening: pull the revenue number, recompute burn, remember what shipped, find last month's email to keep the format consistent. Your agent runs that assembly line. Give it API keys for your billing provider and your analytics tool, and clone the repo into its workspace; it pulls the numbers, reads the month's commit history for what actually shipped, and drafts the update in your established format.
How it works
- 01
The draft covers the standard sections: revenue and growth against last month, burn and runway, pipeline movement, product highlights, and the asks. Numbers come straight from the APIs, so they match what the dashboard says when an investor checks. The agent remembers what you reported previously, so "up from last month" is computed, not estimated, and the narrative stays consistent across editions.
- 02
A calendar trigger produces the draft three days before your send date, as a desk document with a note on which sections it is confident about and which need your judgment, usually the commentary on a soft month. You rewrite one paragraph, add the thing only a founder knows, and send. The archive of past updates lives on your desk, which turns out to be exactly what you need at the next raise.