Managed agent · Stripe

“Why did MRR dip last week?”

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.

revenue
Revenue Analyst APP Mon 9:00 AM

Weekly revenue digest · Jun 22–29

  • Net revenue $48.2k, down 3.8% on the prior week
  • MRR down 2.1%: 5 churned, 2 set to cancel, 4 new
  • 9 failed charges ($3.1k), mostly insufficient funds
  • Recovery plan drafted for 7 past-due invoices, ready for your approval
You 9:04 AM

Why did MRR dip last week?

Revenue Analyst APP 9:05 AM

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 week, one digest that holds the whole picture.

Every number comes from your synced Stripe data, compared against the prior week. Movement shows the moment it happens.

Where revenue moved

Gross volume, refunds, and net, this week against last. A dip is a fact before it's a surprise.

Why MRR changed

Active subscription value split into new, churned, and set-to-cancel: the anatomy of every dip and climb.

Why payments failed

It groups failed charges by cause, so you see one expired-card wave, not thirty separate failures.

What's still unpaid

What's outstanding and for how long, oldest first: money you've earned that hasn't arrived.

What's being disputed

It flags new dispute patterns early, before they turn into a support problem.

The at-risk hand-off

When too much revenue is at risk, it hands the list to a recovery agent, explained below.

It works from your data, synced.

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.

  • stripe_charges
  • stripe_invoices
  • stripe_subscriptions
  • stripe_customers
  • stripe_payment_intents
  • stripe_balance_transactions
  • stripe_products
  • stripe_prices
  • + 3 more

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.

Hired in three steps.

01

Hire

Pick the Revenue Analyst from the gallery. It arrives ready: no build step, no prompt engineering.

02

Connect Stripe

One connection. Levain keeps your account synced, so the analyst always works from current data.

03

Read it in Slack

Schedule it for Monday mornings and post the digest to Slack. Reply in the thread; it goes straight back to the agent.

When revenue leaks, it calls for backup.

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.

01

It re-checks, live

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.

02

You approve, in words

It presents a numbered plan (retries, nudges, cancellation saves) and waits. Reply approve all, or approve 1 and 3. Nothing runs without your reply.

03

It executes only that

Approved actions run; the rest is skipped and reported. Amended, ambiguous, or unmentioned all mean not approved.

Ask it what you'd ask an analyst.

Every answer is a query against your synced data, not a recollection.

  • Why did MRR dip last week?
  • Which failure reason drove failed charges this week?
  • Who's carrying the most past-due balance right now?
  • How did refunds compare with the prior week?
  • Which subscriptions are scheduled to cancel?
  • Are we losing more to churn or failed payments?

Built to be trusted with your revenue data.

Reads, doesn't touch

The analyst works on read-only synced data. It has no write access to Stripe, so analysis can't move money.

Money moves only with approval

Recovery actions (retries, nudges, cancellation saves) run only after a human approves the plan.

Everything on the record

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.

Know what changed in your revenue before your first meeting.

Hire the Revenue Analyst, connect Stripe, and the first digest writes itself.