The Investor Update You Send At Midnight

It is 11:47 PM on the first Sunday of the month. Your founder is in a Google Doc titled Investor Update June. The cursor is blinking under the heading Metrics. The CRM tab is open, the Stripe dashboard is open, the cohort sheet from your head of growth is open. The previous month's update is open in a fourth tab, copied as a starting template.

The doc will ship at 1:14 AM. It will go to forty-three angels, two seed funds, and the lead from your Series A. The ARR number will be three days stale because the close has not landed. The churn number will be the founder's best guess against a query they ran on Friday. The asks section will get one line because there is no time to draft three.

Investor relations is a function. Most Series A and B founders have not staffed it. The update goes out late, the metrics are inconsistent across months, and the relationship with the people who wired the last round runs on the founder being awake at midnight on the first of the month. On the org chart, IR sits nowhere. In the calendar, it eats one Sunday a month and three follow-up evenings.

The monthly update is six hours the founder pretends is two

Ask any founder how long the investor update takes. The answer is around two hours. Time it for a quarter. The honest number is four to seven hours, split across two evenings and a Sunday afternoon. That is sixty to eighty hours a year of CEO time on a document that goes to people who already wrote the check.

Walk through the steps. Pull ARR from the CRM, reconcile against the Stripe MRR view, flag the gap. Pull burn from the bank, but only if the close has finished, otherwise estimate. Pull new logos, expansions, and churn from three places that disagree. Rebuild the cohort retention chart because the one from May is stale.

Then the writing starts. Draft the narrative. Draft the asks. Format the deck or doc. Send. Eight to twelve data sources, four to six metric definitions the founder has to reconcile in their head, and a writing job that competes with the board pack for the same week of every month.

The investor update almost always loses, which is how it ends up shipping at 1 AM on a Monday three days after the founder promised it. The downstream cost is harder to see. Stale updates train your investors not to read them, which is how warm intros from existing backers stop happening, which is how the next round becomes a cold outbound problem instead of a referral problem. The function is real. Nobody is staffed against it.

Hiring a chief of staff is the slow answer

The standard fix is a chief of staff. Loaded comp in the US runs one hundred forty to two hundred twenty thousand a year. Months one through three go to learning the metrics, the cap table, the investor list, and the founder's voice. Months four through six are when the update starts going out on time, written by the chief of staff with the founder editing. The narrative quality is good. The data still gets assembled by hand because the underlying systems did not change.

A part-time IR consultant is faster to start and stops at a different wall. Four to eight thousand a month buys you ten to fifteen hours of senior IR time and a clean format within sixty days. The narrative gets professional. The founder still writes the first draft because the consultant does not have access to the CRM, the GL, or the product analytics.

Both versions assume the work is human bottleneck work. Pull the data, reconcile the definitions, write the narrative, format the deck, send. On a Series A company that is six to eight hours a month before the CEO writes a single sentence about strategy. No chief of staff and no IR consultant clears that pile and also writes a narrative that sounds like the founder.

What a fractional AI investor relations function does

Hand the CRM, the Stripe account, the GL, the product analytics, the cap table, the investor list, and the last twelve months of updates to an agent that runs on a fixed cadence. The agent does the work a chief of staff and a junior analyst would do together. The narrative reads like the founder because the agent has been trained on the founder's last twelve updates. The cadence is monthly for the formal update, weekly for the internal dashboard, ad hoc for one-off investor questions.

Metric assembly with one source of truth. ARR, MRR, net new, expansion, gross churn, net churn, burn, runway, headcount. Each metric has a single definition, a single source, and a reconciliation rule when sources disagree. The agent runs the pull on the last business day of the month and flags any metric where two sources disagree by more than two percent for the founder to resolve.

Narrative drafted against the last twelve months. The agent reads the previous twelve updates, identifies the storyline the founder has been telling, and drafts the next chapter against the current numbers. The wins section is built from the CRM and the product analytics. The lowlights section is built from the churn list and the pipeline slippage. The asks section is drafted from the open hires, the partnership pipeline, and the customer intro list. The founder edits instead of starts.

Investor-specific follow-ups. When the lead from your last round asks a question, the agent drafts the answer using the same data the update was built from. The follow-up goes out the same day, not on the next Sunday. The same shape the renewal motion takes on the customer side applies to investors. Relationship cadence is a function, not a memory test.

Data room kept current as a side effect. Every monthly update writes the historical metrics to the data room in the format the next diligence process will ask for. By the time you open the round, the data room is twelve months ahead of where it would be if you started populating it the week the term sheet arrived. Diligence stops being a four-week scramble. The same evidence trail that ships the audit on the finance side ships the data room on the IR side.

Internal dashboard the founder opens on Tuesdays. The same data feeding the monthly update powers a weekly internal view of the same metrics. The founder sees the slippage in week two of the month, not week one of the next month. The mid-month course correction stops being a thing the CFO catches by accident.

The unit economics of the investor update

Sixty to eighty hours of CEO time a year on the monthly update, plus another twenty to forty hours on ad hoc investor questions and the data room refresh before the next round. Call it one hundred hours of CEO time a year on IR mechanics. At a Series A founder's loaded value, that is the difference between closing one more customer deal a quarter and not. The hours come out of the same week every month, which is the week the board pack also ships, which is why both land late.

Layer in the chief of staff or IR consultant spend most companies eventually add. Forty-eight to one hundred ninety-two thousand a year, depending on which version you ran with. The narrative quality goes up. The data assembly cost stays roughly the same because the underlying integration work was never done.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to one senior contractor than a team. The CEO hours come back, the chief of staff hire gets deferred or scoped to higher-impact work, and the monthly update lands on the second business day of the month with a draft narrative the founder can ship in twenty minutes of editing. Same shape we ran for the content function. Function, not headcount.

The harder number to put a range on is the warm intro economics. Investors who read every monthly update send warm intros. Investors who skim every third update do not. The conversion from existing backer attention to next-round referrals is the part of IR that pays for the function five times over, and it only works if the updates are consistent for twelve months in a row.

What changes after the sprint

Picture the same first Sunday of next month, fourteen days after the 14-day sprint ships. The metric pack is in the founder's inbox at 8 AM on the first business day. Every metric reconciled across sources, every gap flagged with a one-line explanation. The draft narrative is written against the last twelve updates and the current numbers, three to five paragraphs of wins, two paragraphs of lowlights, and three drafted asks built from the open hires and the customer intro list.

The founder spends thirty minutes on the editing pass. The update ships at 10:30 AM on the second business day of the month. The investor who replies with a question gets a same-day answer with the supporting data attached. The lead from the last round opens the update, the warm intro for the partnership conversation goes out three days later.

If your investor update is currently a midnight Sunday draft that ships three days late with metrics nobody trusts, the version where it goes out on the second business day with a narrative your investors read is fourteen days away. The IR function is real. You can staff it like a hire, or you can scope a sprint and have it running this month. The work is the same. The math is not.