Monday revenue standup tying bookings to recognized MRR

Every Monday at 8:57am, run a revenue standup for our leadership Slack channel that ties last week's bookings to last week's recognized revenue. Use a cron trigger for this. ChartMogul does not emit outgoing webhooks and is not available as a poll source, so a schedule is the only way to anchor this workflow.

Start in ChartMogul. Use All Key Metrics and MRR to pull the trailing seven days, and pull the seven days immediately before that as well so I have a week-over-week comparison rather than a single snapshot. Then use List Activities for the trailing seven day window and break the MRR-affecting movements out by type: new business, expansion, contraction, churn and reactivation. Keep the customer name and the amount on every movement so you can name accounts later in the write-up. ChartMogul returns money as integers in cents, so convert to whole currency units before writing anything, and page through the activities until the full window is covered.

Then go to HubSpot and use Search Deals to find every deal that moved to closed won inside the same seven day window. Filter on the deal stage being closed won and the close date falling inside the window. Bring back the deal name, the amount, the associated company and the deal owner for each one.

Now write a short narrative that connects the two systems. Cover four things. First, what the sales team closed in the CRM last week, as a booked total and a deal count. Second, how much of that showed up as recognized MRR in ChartMogul, and where the two numbers do not line up, call out the gap and the most likely reason for it, such as annual contracts billed up front, delayed start dates or normal billing lag. Third, which named accounts drove the biggest expansions and the biggest contractions, with the amount next to each name. Fourth, how net new MRR compares with the prior week, given as both an absolute change and a clear direction.

Post the result to the leadership channel using Send a Message in Slack. Lead with the net new MRR number on its own line, then a one-line verdict on whether we are ahead or behind pace, then the narrative kept to a handful of short paragraphs or tight bullets. It should be readable straight in the channel without anyone needing to click through to another system.

One important guardrail. ChartMogul already ships a native Slack destination that posts raw MRR movements, so do not build a metrics dump. The value here is the written interpretation plus the join to HubSpot closed won, which the native integration cannot do. Every number in the message should be traceable back to one of the two systems, and if either system returns nothing for the window, say so plainly rather than reporting a zero as though it were a real result.