Grow › Revenue

MRR or payments, this month's movements, revenue at stake and runway

Updated 1 Nov 2026 · 5 min read

Grow › Revenue reads your own Stripe customer data (see Stripe customer data), read-only. Grow appears in the sidebar once your product is past PMF or has 10 paying accounts (a product paid per use counts an account as paying when it paid in the last 12 months). Every number says where it came from; Full dashboard in Stripe opens Stripe itself. It never replaces Stripe.

Until customer data is read, the page says Connect Stripe customer data and links to Settings › Connections. While the first read runs it says Reading customers and payments; the jobs tray shows it. If your Stripe has no subscriptions or one-time payments (Stripe Connect payouts, app-store revenue), it says No subscriptions or one-time payments in your Stripe yet and your totals still show on Today. A failing read says so with Reconnect, and the numbers keep the last good read's date; after you delete customer data they read From Stripe until {date}.

Sold per use? If your product has no subscriptions (a flat price per order, election or event, paid through Checkout), see Sold per use below. A product with subscriptions keeps everything in this section.

MRR (from Stripe) is each active or past-due subscription's price × quantity, turned into a month (yearly ÷ 12, weekly × 52 ÷ 12), less its discounts. A trial counts 0. A metered price uses its last paid invoice. Each currency is shown on its own, never converted. Test-mode data is marked as test.

Paying accounts, split by segment (see below), with this month against last.

This month's movements: new, expansion, reactivation, contraction and churn, which add up to the net change. Pick a segment to see only its accounts.

Revenue at stake: your open problems and initiatives, ranked by the MRR of the paying accounts whose feedback is linked to them. Feedback is matched to an account by a one-way key of the email, never the email itself. A problem with no linked paying account says so; it is never estimated.

Net revenue retention: this month's MRR from the accounts that paid 12 months ago, against what they paid then, with n. It is the Expansion beats churn health check.

Runway is cash in the bank ÷ monthly net burn, from your own numbers (entered at the check-in or on this page by the owner or a product admin). It is never estimated, never in Ask Mind's answers, never shown to viewers and its amounts never go into the audit log. Over 30 days old, it asks to be updated.

Segments (Revenue › Segments) group paying accounts by rule over your own Stripe: a plan, a metadata value (one key you choose) or a seat count. Rules run in order; the first match wins; the rest is Other, never hidden. Mind suggests segments from your plans, by rule (no AI). Editors add, edit, reorder and retire segments; a retired segment stays in your history.

One-time payments. A product with subscriptions that also takes one-off payments keeps its MRR as MRR; Revenue adds one line, One-time payments: this month, the last 12 months and how many accounts. A one-time payment that paid a subscription's invoice is never counted twice.

Account names are fetched live from Stripe for you and your editors when a list shows accounts. Grow doesn't store them; People keeps only the first name and last initial. If Stripe is slow, the rows read Names unavailable right now. Viewers see totals only.

Test a price before you change it

Editors: Draft a pricing test (2 AI credits; Growth and Scale: included) drafts a test from your cancel reasons, revenue at stake, open questions, revenue per account by segment and competitors' public prices (each with the date it was read). Mind never invents a price: it proposes one of your Stripe prices or a competitor's public one, cited, or leaves Your price to test. The audience is a main segment and its paying accounts, counted from Stripe. The line is yours: a suggestion is shown, you set it. The test opens in Learn › Tests: pick the Stripe price whose new subscriptions it counts, set the line and the deadline, and Start locks them. Results count each new subscription to that price after the start, from Stripe. If Mind's draft doesn't hold to your numbers, the template's stands and the credits go back. It works from subscription prices and revenue per account, so a product paid per use has little to draft from.

Sold per use

A product with payments but no subscriptions gets a different page, without the words MRR, NRR, expansion or contraction. The key needs Read on Customers and Charges (or PaymentIntents), and Invoices if you send invoices; Subscriptions, Products and Prices aren't needed. A key that falls short is refused in Stripe's words, for example Charges: Read is missing, and nothing is read until it is enough.

  • Mind's read, one sentence: "$1,960 so far this month from 4 paying accounts, 3 of them repeat. Last month: $2,940."
  • Tiles: revenue this month so far, beside last month and the same month last year; paying accounts this month, new and repeat; the repeat rate; revenue per paying account.
  • Revenue by month: the last 12 months as bars, the current month lighter while it runs, with a table for screen readers.
  • Revenue by segment over 12 months, and Revenue at stake: per problem and initiative, what the paying accounts whose feedback is linked paid in 12 months ("Not estimated" when no paying account is linked).
  • Every number has a Why?: what it counts, its n, and "from Stripe, read 8:00". Other currencies are counted apart and never converted.

Mind reads every payment that went through, less any refund, and adds it to that customer's month. It never keeps a single payment, a card or a description. A checkout with no Stripe customer is matched by its email's one-way key; no name can be looked up, so it shows as "Account 1a2b". Payment intents carry no refunds, so with a PaymentIntents-only key Mind counts what was received; a refund made after the read window (the last 3 months on a daily read) isn't seen.