How we handle GDPR data-subject requests on a deadline
Legal
A monthly agent we run on Kortix — connected to Postgres, Stripe, and last month's update. It pulls the core metrics, compares them to last month and to plan, and drafts the update in our format for a founder to finalize.
The monthly investor update is a small, recurring task that eats a founder's time. The numbers live in a few different places, they have to be pulled and compared to last month and to plan, and then the whole thing has to be written up in a consistent format. None of it is hard; it's just an hour or two of gathering and formatting that comes around every month.
We run an agent on Kortix that does the gathering and the first draft. This is how we draft our own investor update, including the connections and guardrails involved.
Writing the update every month means pulling MRR and revenue from Stripe, active accounts and growth from the product database, and burn and runway from the finance numbers, then setting each against last month and against plan. The data is spread across systems, the comparisons are done by hand, and the write-up has to match the format investors are used to seeing.
The common fixes are incomplete. A BI dashboard shows the current numbers but doesn't write the narrative or compare against plan. A saved template still needs someone to fill in every figure. Doing it by hand each month is reliable but it's the founder's time going into gathering and formatting rather than into the commentary that actually matters.
On Kortix, a monthly cron triggers an agent. It spawns an isolated session (a cloud sandbox) with read-only access to the product database, Stripe, and last month's update. It pulls the core metrics — MRR, growth, burn, runway, active accounts — compares them to last month and to plan, and drafts the update in our usual format as a document. A founder edits it and sends it.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the investor-update-draft skill and the monthly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a monthly investor update agent in this workspace.
Create the agent agents/investor-update.md. Its job is to draft the monthly investor update from our metrics. It may use the PostgreSQL, Stripe and Google Docs connectors.
Create the skill skills/investor-update-draft/SKILL.md with these rules:
Add a cron trigger monthly-investor-update to kortix.yaml. It runs the investor-update agent on the 1st of every month at 06:00 with the prompt "Load the investor-update-draft skill and draft this month's investor update."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect PostgreSQL, Stripe and Google Docs. Use a read-only database user for PostgreSQL. Credentials are brokered server-side and never enter the agent's machine.
Reads active accounts, growth, burn and runway.
Reads MRR and revenue for the month.

Reads last month's update and drafts this month's.
Merge the change request, then start a session with the investor-update agent and send this prompt. Check the numbers against your own reports before you let the schedule take over.
Draft this month's investor update.
The change request added this trigger to kortix.yaml. From now on the agent
runs on the 1st of every month at 06:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: monthly-investor-update name: Monthly investor update draft on: cron: "0 0 6 1 * *" run: agent: investor-update prompt: Load the investor-update-draft skill and draft this month's investor update.The agent reads PostgreSQL, Stripe and every past update, and writes nothing back to any of them. Its one output is a new draft document. It never emails, shares or publishes the update. A founder edits the commentary, checks the numbers and sends it.
Each run ends with one new draft in the folder. This is what a run looks like in the session:
Drafted this month's update in the Investor Updates folder. MRR grew 6.2% month over month, 1.1 points under plan. Runway is 19 months. The draft marks one churned account as the likely driver for you to confirm.
Once it works, paste any of these into the same session.
Add a line chart of MRR and active accounts for the last 12 months to the draft, under the metrics table.
Read the open roles and fundraising notes in the Investor Updates folder and draft the asks section from them.
Every Monday, send me the month-to-date MRR, burn and active accounts against plan, so the update has no surprises.
The agent reads revenue and product data to draft a document, so the access is scoped and contained:
The monthly update now arrives as a draft with the numbers pulled, the comparisons done, and the narrative written in our format. The founder spends their time on the commentary and the send rather than on gathering and formatting, and the data is only ever read.