--- name: stripe-weekly-mrr-report description: "Every Monday: MRR, net new MRR split into new, expansion, contraction and churn, and active subscriptions, computed from Stripe the same way each week. Use when the user asks for this, or when it runs on a schedule." --- # Stripe weekly MRR report Every Monday: MRR, net new MRR split into new, expansion, contraction and churn, and active subscriptions, computed from Stripe the same way each week. For the founder who writes "MRR is up 4%" in the Monday update and then gets asked why. The agent rebuilds MRR from the live subscriptions, the way an investor would check it, then walks the week's subscription events to split the change into new business, upgrades, downgrades and cancellations. You get one number to quote and the four parts that explain it, with the biggest cancellation of the week named, so the follow-up question already has an answer. ## Two ways to get the data Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used. ## Route A: API or MCP server ### What you need - A restricted Stripe key with read access to Subscriptions, Events, Prices and Customers in `STRIPE_API_KEY`, or the Stripe MCP server connected to the live account. - The Stripe CLI (`stripe login`) works too for runs on your own machine. If something is missing, say what and stop; do not invent numbers. ### Steps 1. **List the paying subscriptions** (Stripe): Page through `GET /v1/subscriptions?status=active` and again with `status=past_due` (`limit=100`, `starting_after` for the next page, `expand[]=data.discounts`), or run `stripe subscriptions list --status active --limit 100`. Leave out `trialing`, `incomplete` and `canceled`: they don't pay yet, or anymore. 2. **Normalize every item to a month**: For each item take `price.unit_amount` times `quantity`, divide yearly prices by 12 and every price by `price.recurring.interval_count`, multiply weekly ones by 52/12, then apply the subscription's discounts while the coupon lasts. Skip metered prices, convert other currencies at one rate for the whole run, and sum. 3. **Read the week's subscription events** (Stripe): Call `GET /v1/events` for `customer.subscription.created`, `customer.subscription.updated` and `customer.subscription.deleted` with `created[gte]` set to last Monday 00:00. Stripe keeps events for 30 days, so a weekly run always sees the whole week. 4. **Split net new MRR**: Created and active, or a trial whose status went from `trialing` to `active`, is new. An update where the monthly amount rose is expansion and one where it fell is contraction (compare with `data.previous_attributes.items`). Deleted is churn. Check that last week's MRR plus net new lands within 1% of today's figure. 5. **Write the report**: MRR and its change in dollars and percent, the four parts with the number of subscriptions behind each, active subscriptions, and the largest cancellation and upgrade of the week. ## Route B: the browser ### What you need - Signed in to the Stripe Dashboard as a user with the Analyst role or higher (Administrator and Developer also see Billing analytics), with live mode on and the right account picked if you use Organizations. If something is missing, say what and stop; do not invent numbers. ### Steps Start at https://dashboard.stripe.com/billing. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears. 1. **Open the Billing overview**: Open `https://dashboard.stripe.com/billing` in live mode. The overview shows **MRR**, **MRR growth** and **Active subscribers**. Set the date range to the last 7 days (last Monday to today) with the comparison to the previous period. 2. **Explore MRR growth**: Click **Explore** on the **MRR growth** chart. The table under the chart splits the period into new, expansion, contraction and churn MRR, with reactivation and FX adjustment when they apply. Read each amount; a clickable cell lists the customers behind it, which gives the subscription count per part. 3. **Read active subscribers**: Back on the overview, read **Active subscribers** and its change for the same range. The Dashboard counts customers with positive MRR, not subscriptions, so label the figure as subscribers. 4. **Find the largest moves**: In the Explore table open the churn cell and the expansion cell for the week, sort the customers by MRR and note the largest cancellation and the largest upgrade. If Explore is not offered on your account, use **Report downloads** on the overview, download **Customer MRR changes** and filter the CSV to last week. 5. **Check the MRR configuration**: Click **Configure** on the overview and read whether recurring and one-time discounts are subtracted from MRR. Say which in the report, so nobody compares it with a figure computed the other way. Note: The Dashboard figure excludes taxes and metered items, counts subscribers rather than subscriptions, and converts foreign currencies at daily rates, so expect small differences from an MRR computed from the API. Explore drill-downs are not available on accounts that bill in several currencies; the Customer MRR changes download covers the same ground. ## The report - **MRR** today and the change against last Monday. - **Net new MRR** split into new, expansion, contraction and churn, with the subscriptions behind each. - **Active subscriptions** and the change. - The largest cancellation and the largest upgrade of the week, by MRR. - A note if last week plus net new doesn't add up to this week within 1%, with the likely cause (a currency, a backdated change). ## Post it to Briefkin When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on. ```bash [ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \ -H "authorization: Bearer $BRIEFKIN_TOKEN" \ -H "content-type: application/json" \ -d @- <<'JSON' { "v": 1, "event_id": "stripe-weekly-mrr-report/", "item_key": "stripe-weekly-mrr-report", "project": "Acme", "source": "Stripe weekly MRR report skill", "kind": "metric", "title": "MRR up $1,690 this week", "metric": { "label": "MRR", "value": 48210, "prefix": "$", "better": "higher", "period_start": "", "period_end": "" }, "glance": [ { "type": "Grid", "props": { "columns": 3 }, "children": [ { "type": "Stat", "props": { "label": "Net new MRR", "value": 1690, "prefix": "$" } }, { "type": "Stat", "props": { "label": "Active subscriptions", "value": 612, "delta": 2.3 } }, { "type": "Stat", "props": { "label": "Churned MRR", "value": 1120, "prefix": "$", "better": "lower" } } ] } ], "widget": [ { "type": "Table", "props": { "columns": [ "Movement", "MRR", "Subscriptions" ], "align": [ "left", "right", "right" ], "rows": [ [ "New", "+$2,140", 23 ], [ "Expansion", "+$980", 11 ], [ "Contraction", "-$310", 4 ], [ "Churn", "-$1,120", 9 ], [ "Net new", "+$1,690", "+14" ] ] } }, { "type": "Callout", "props": { "text": "Largest churn: a Team annual account worth $410 a month, feedback \"switched_service\".", "tone": "warn" } } ], "size": "md" } JSON ``` Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report. Set `period_start` and `period_end` to the window the number covers: the tile names it from them ("Last 7 days", "Today", "This month"). For a count right now (open items, a balance), send `"period_label": ""` so no period shows; for another name, send it as `period_label` (at most 24 characters). ## Run it on a schedule Suggested: Mondays at 8:00 (`0 8 * * 1`). From cron, with the agent signed in on that machine: ```bash 0 8 * * 1 claude -p "Run the stripe-weekly-mrr-report skill" # Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run ``` Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/stripe-weekly-mrr-report#schedule Source: https://briefkin.dev/skills/stripe-weekly-mrr-report