Monthly investor update drafted from your ChartMogul metrics

On the first of every month, your ARR, growth, churn and retention numbers become a written investor update draft in Google Docs, posted to Slack for review.

Agentic Task
ChartMogulGoogle DocsSlackFinanceOperationsAI ReportsContent Generation
PromptCreate

On the first of every month at 9:07am, draft our monthly investor and board revenue update so a founder only has to edit it rather than assemble it from scratch.

Start by pulling ChartMogul metrics for the month that just closed and for the month before it, so every comparison is computed from two real periods rather than estimated. Use All Key Metrics for the combined picture, then pull MRR, ARR, MRR Churn Rate, Customer Churn Rate, ARPA, LTV and Customer Count for the individual series. Set the start and end dates to cover both full months.

Then use List Activities for the just-closed month to find the movements that actually drove the change. Identify the largest new business wins, the largest expansions, the largest contractions and the largest churn events, and use them to explain the MRR movement rather than simply restating it.

Create the document with Google Docs Create Document, titled like "Investor and Board Update, <Month Year>, DRAFT FOR REVIEW". Then fill in the body with Batch Update Document using these sections: headline ARR and month over month growth; what drove the change, referencing the specific new business, expansion, contraction and churn movements from the activity list; retention and net revenue retention commentary drawn from the churn rates alongside expansion versus contraction; a key metrics section covering MRR, ARR, ARPA, LTV and customer count for both months side by side; and risks and watch items with two or three things worth flagging.

Never state a number that did not come from a ChartMogul metrics response. Do not extrapolate, forecast, or fill a gap with a plausible figure. If a metric is unavailable, say so in the draft instead of estimating it. ChartMogul returns monetary amounts as integers in cents, so convert and format them as readable currency before writing them into the document. Compute every month over month change from the two pulled periods. Anything qualitative, such as why a number moved or what to watch next, must be clearly framed as commentary rather than as a reported fact.

Finally, post the document link to Slack with Send a Message so the update can be reviewed before it goes out. Include the headline ARR figure and the month over month change in the message so the reviewer knows what they are opening.

Label the output a draft for review everywhere it appears: in the document title, at the top of the document body, and in the Slack message. This update is never sent to investors automatically.

Example output

Slack message posted after the draft is written: *Investor and Board Update, March 2026 (DRAFT FOR REVIEW)* Headline ARR $2.41M, up 4.2% from $2.31M in February. Net new MRR came mostly from two expansions and one new logo; one mid-market cancellation offset part of it. Draft ready for edits before it goes out: <link to Google Doc>

Additional information

What does this prompt do?
  • Pulls the month that just closed and the month before it from ChartMogul: ARR, MRR, churn rates, average revenue per account, lifetime value and customer count.
  • Finds the biggest new customers, upgrades, downgrades and cancellations of the month, so the update explains why revenue moved instead of just restating it.
  • Writes the whole thing into a new Google Doc: headline ARR, month over month growth, what drove the change, retention commentary and two or three risks worth watching.
  • Posts the document link to Slack so a founder can edit and approve it before anything reaches investors.
What do I need to use this?
  • A ChartMogul account with your subscription billing data already flowing into it.
  • A Google account, so the update can be created and filled in as a Google Doc.
  • A Slack workspace and the channel where the draft should land for review.
How can I customize it?
  • Move the timing. The first of the month is the default, but if your billing data takes a few days to settle, shift it to the third business day.
  • Change where it lands. Point the Slack message at a private founders channel or a direct message if the first read should not be public.
  • Reshape the sections. Add a cash or headcount section, ask for a shorter board summary alongside the full update, or set the tone you want investors to read.

FAQs

Does this send the update to investors automatically?
No, and that is deliberate. It always produces a draft labeled for review and posts the link to Slack. A person reads it, edits it, and decides when and how it goes out.
Where do the numbers in the draft come from?
Every figure is read straight from your ChartMogul metrics for the two months it pulls, and month over month changes are calculated from those two real periods. It will not estimate, forecast, or fill a gap with a plausible looking number. If something is unavailable, the draft says so.
What if our numbers are not final on the first of the month?
Move the schedule. Plenty of teams run it on the third or fifth business day instead, once billing has settled. The workflow always compares the most recently closed month against the one before it.
Can it explain why revenue changed, not just what it was?
Yes. It reviews the month's actual revenue movements, the largest new business, expansions, contractions and cancellations, and uses those to explain the change. That narrative is clearly framed as commentary, separate from the reported figures.
Do we still need this if we already get a weekly revenue summary?
They serve different readers. A weekly summary keeps the internal team current. This is the monthly narrative artifact investors and board members expect, written as prose with retention and net revenue retention commentary.

Related templates

Turn website roof inspection requests into JobNimbus leads

New roof inspection requests from your website form land in JobNimbus within a minute, with no duplicate records and nothing retyped by your team.

JobNimbus
Google Forms
Slack
Agentic Task
Triage new Jira Service Management requests before anyone opens them

Every new customer request gets a priority, triage labels, a friendly reply with the right help article, and a Slack ping only when it is truly urgent.

Jira Service Management
Jira
Slack
Agentic Task
Risk-check every dependency upgrade pull request in GitHub

When a bot opens a version bump pull request, we read the real documentation for that exact version and tell you whether it is safe to merge.

Context7
GitHub
Slack
Agentic Task
Launch an Ironclad contract when a HubSpot deal is won

The moment a deal hits Closed Won, the right contract starts in Ironclad, the link lands on the deal, and your sales channel hears who owns the next step.

Ironclad
HubSpot
Slack
Agentic Task
Weekly Ironclad contract renewal digest in Slack and Asana

Every Monday, find contracts renewing or expiring in the next 90 days, post a ranked digest to Slack, and open Asana tasks for the ones that need a decision now.

Ironclad
Slack
Asana
Agentic Task
Turn repeat support tickets into draft help articles

Every Friday, spot the questions your team keeps answering by hand and get a ready-to-review help article drafted from real fixes.

Jira Service Management
Confluence
Slack
Agentic Task

Stop assembling the investor update by hand.

The numbers, the movements behind them, and a full first draft can be waiting for you on the first of every month.