Written by Josh @ Gleam
Two signals, one business
12 months
Bank balance
Noisy, backward-looking
MRR
Normalized, forward-looking
Most founders check their bank balance before they check their MRR. That's backwards.
Your bank balance is a lagging indicator. It tells you what already happened, distorted by whatever invoices landed this week, whatever refund went out yesterday, whatever annual plan just renewed. It's noisy, and it's already in the past by the time you look at it.
Monthly Recurring Revenue is the opposite. It's a normalized, forward-looking signal: if nothing changes, this is what you'll collect next month, and the month after that. Annual Recurring Revenue is just MRR × 12, the same signal projected out to the horizon investors and boards actually think in.
MRR (Monthly Recurring Revenue) is the normalized monthly value of your active subscriptions: what you'd collect next month if nothing changed. ARR (Annual Recurring Revenue) is that same number scaled to a year: MRR × 12.
Hiring, spending on ads, committing to a lease, extending runway estimates: all of these are bets on the future. Making them off a backward-looking bank balance means you're implicitly assuming this month looks like last month, without checking whether it actually does.
MRR tells you directly: is recurring revenue growing, flat, or shrinking, and by how much. A founder who knows their MRR moved from $18,200 to $17,400 this month can ask why immediately. A founder only watching the bank balance might not notice the shrinkage for two or three months, buried under one-off invoice timing.
There's a subtlety here that trips a lot of people up: MRR should come from your active subscriptions' actual prices, not from summing invoice totals. Invoice totals include proration, one-off charges, and timing artifacts that make month-to-month comparisons noisy. The right way to compute MRR is to normalize every active subscription's price to its monthly-equivalent value and sum those: a $200/year plan contributes about $16.67, a $50/month plan contributes $50, and so on. This is exactly the gap between what Stripe's own dashboard shows you and what it can't: it surfaces gross payment volume, not normalized MRR.
Get that calculation wrong and every downstream decision (a forecast, a churn rate, a "should we raise prices" conversation) inherits the noise.
If you're building this in a spreadsheet rather than pulling it from a tool that computes it for you, these are the mistakes that show up most often:
Each of these is a one-line rule once you know it, but they compound: a spreadsheet with two or three of these mistakes baked in can be off by a meaningful percentage without ever throwing an obviously wrong number.
Is MRR the same as ARR? No. MRR is the monthly figure; ARR is MRR × 12. They move together, but MRR is what you should check weekly, and ARR is what you put in a board deck or an annual plan.
What's excluded from MRR? One-off charges, setup fees, refunds processed as separate line items, and (depending on how you want to treat it) usage-based/metered revenue, since it isn't a fixed recurring commitment.
How do you calculate ARR from MRR? Multiply MRR by 12. If your MRR is $18,200, your ARR is $218,400. The reverse works too: divide ARR by 12 to get MRR.
Your bank balance answers "how much cash do I have right now." Your MRR and ARR answer "where is this business headed." You need both, but only one of them should be driving decisions about hiring, spend, and growth strategy, and it's not the one most founders check first.
Gleam Revenue computes this split automatically from your Stripe subscription data: real MRR and ARR, normalized correctly, in your inbox every morning. Start your free trial →