Where revenue moved
Gross volume, refunds, and net, this week against last. A dip is a fact before it's a surprise.
Every Monday it explains what changed in your revenue, why, and what needs attention. It writes the digest from your Stripe data, posts it to Slack, and answers your follow-ups in the thread.
Weekly revenue digest · Jun 22–29
Why did MRR dip last week?
Two churned subscriptions carried it: Acme ($890/mo) and Northwind ($540/mo), both after failed renewals. Both sit in the recovery agent's plan, ready for your approval.
Every number comes from your synced Stripe data, compared against the prior week. Movement shows the moment it happens.
Gross volume, refunds, and net, this week against last. A dip is a fact before it's a surprise.
Active subscription value split into new, churned, and set-to-cancel: the anatomy of every dip and climb.
It groups failed charges by cause, so you see one expired-card wave, not thirty separate failures.
What's outstanding and for how long, oldest first: money you've earned that hasn't arrived.
It flags new dispute patterns early, before they turn into a support problem.
When too much revenue is at risk, it hands the list to a recovery agent, explained below.
Connect Stripe once, and the analyst always works from your live account, so every figure in the digest is your own revenue, churn, and past-due, current to the day.
It never invents a number. If Stripe doesn't have the data, the digest says so. Selling on Shopify too? Hire the E-commerce Analyst alongside it: different systems, one workspace.
Pick the Revenue Analyst from the gallery. It arrives ready: no build step, no prompt engineering.
One connection. Levain keeps your account synced, so the analyst always works from current data.
Schedule it for Monday mornings and post the digest to Slack. Reply in the thread; it goes straight back to the agent.
Finding the leak is only half the job. When at-risk volume passes 2% of weekly gross (or 10 invoices), the analyst hands the list to the Dunning Recovery agent, a second managed agent that turns it into collected revenue, with you in the loop.
Before it proposes anything, it re-fetches each invoice from Stripe and drops what's already paid or voided. Synced data lags; plans shouldn't.
It presents a numbered plan (retries, nudges, cancellation
saves) and waits. Reply approve all, or
approve 1 and 3. Nothing runs without your reply.
Approved actions run; the rest is skipped and reported. Amended, ambiguous, or unmentioned all mean not approved.
Every answer is a query against your synced data, not a recollection.
The analyst works on read-only synced data. It has no write access to Stripe, so analysis can't move money.
Recovery actions (retries, nudges, cancellation saves) run only after a human approves the plan.
Every run is logged step by step. Each digest is published as an artifact you can open, share, and audit.
Every agent runs on the Levain platform, inside the guardrails you
set.
See how the platform works.
Hire the Revenue Analyst, connect Stripe, and the first digest writes itself.