Daily revenue snapshot (automated)

AI-generated daily revenue snapshot. Yesterday's new MRR, expansions, churn, and notable events from Stripe — every morning.

Use this template How automations work

Runs dailyScheduledDelivered to Slack, Email

Daily revenue snapshot

Active

Trigger: Runs daily
Instructions: Write a single-paragraph daily revenue snapshot covering the past 24 hours.
Delivery: Slack · Email

Example output

A realistic sample of what this automation delivers. Your version draws on your own data.

Daily revenue snapshotRuns daily · Sent to Slack, Email

Sample output

Last 14 days

Revenue / day

$14,820+12%($13,200)

New customers

5+1(4)

Net new MRR

$1,840+14%($1,610)

Failed payments

4-1(5)

Yesterday’s revenue: $14,820 from 22 charges. MTD $284K (78% of plan, day 21/31).

New customers: 5 — $1,840 net new MRR (Acme $340, RegionalCo $290, NorthwindCo $620, two SMB).
Expansion: 3 seat additions, +$240 MRR. Largest: PlanetMedia (+8 seats).
Refunds: 1 — $99, accidental upgrade reversed within an hour.
Failed payments: 4 charges retried, 2 recovered, 2 still in dunning.

Trailing 7-day average net new MRR: $1,940/day, +14% vs. the previous 7.

Copy, paste, customize.

Drop this into a Basedash automation. AI fills in the numbers from every source you've connected.

Instructions

Write a single-paragraph daily revenue snapshot covering the past 24 hours.

Format:

"Yesterday we added $<net new MRR> in net new MRR — $<new> new, $<expansion> expansion, $<contraction> contraction, $<churn> churn. Notable: <one-line highlight>."

Then add a second paragraph only if anything material happened: a > $5K deal, a churn worth naming, a refund > $1K. Keep the entire post under 100 words.

Powered by these sources.

Basedash automations read across every connected source in a single run. These are the ones this template tends to use most.

Frequently asked questions

What's in a daily revenue snapshot?

Net new MRR with its components (new, expansion, contraction, churn) and a one-line callout for material events from the past 24 hours. The whole report should be readable in under 30 seconds.