Skip to main content
QuantLab Logo
Glossary · Business

What is MRR?

MRR (Monthly Recurring Revenue) is the total predictable revenue your subscription business expects to collect every month — normalized so that an annual plan, a quarterly plan, and a month-to-month plan all show up as a single comparable monthly number you can forecast against.

What MRR means

MRR is the heartbeat of any subscription business. Unlike one-time sales, where revenue arrives in a lump and then you start over from zero next month, recurring revenue carries forward. A customer who pays you in January is, absent churn, still paying you in February — so MRR is less a measure of what you sold and more a measure of what you can reasonably expect to keep collecting.

The word that matters is recurring. MRR deliberately excludes anything that does not repeat on a predictable schedule: onboarding fees, professional-services work, one-off overages, and refunds. Stripping those out gives you a clean baseline that answers a single question — if we signed no new deals and lost no existing ones, how much would we bank next month?

Where the metric came from

MRR rose to prominence alongside the SaaS business model in the 2000s. When software shifted from a boxed product you bought once to a service you rented monthly, the old way of reporting revenue — booking the whole sale up front — stopped describing reality. Investors and operators needed a number that captured the durable, repeatable nature of subscription income, and MRR became the shared vocabulary.

It is now the default unit of measurement in the early-stage startup world. When a founder says "we just crossed ten K," they almost always mean ten thousand dollars of MRR, not ten thousand in lifetime sales. The metric is portable enough that two companies in completely different industries can compare growth rates simply by comparing how fast their MRR compounds.

How to calculate MRR

The base calculation is simple: take every active subscription, express its price as a monthly figure, and add them up. Forty customers on a $100/month plan plus ten customers on a $500/month plan equals $9,000 MRR. An annual contract worth $12,000 contributes $1,000 to MRR, because you divide the contract value by twelve to land in the same monthly unit as everyone else.

Where it gets useful is breaking MRR into its four moving parts. New MRR is revenue from brand-new customers. Expansion MRR is extra revenue from existing customers upgrading or adding seats. Contraction MRR is revenue lost to downgrades. And churned MRR is revenue lost to cancellations. Net new MRR for the month is new plus expansion minus contraction minus churn — and when that number stays positive even in a bad month, you have a durable business.

When MRR matters

MRR matters the moment money starts recurring. It is the number a board asks about first, the input that drives every cash-flow forecast, and the denominator behind retention metrics like net revenue retention. It also shapes day-to-day decisions: whether you can afford a new hire, how much runway a fundraise actually buys, and whether a pricing change helped or quietly bled expansion revenue.

The trap founders fall into is celebrating gross MRR growth while ignoring the churn component underneath. Adding $5,000 in new MRR feels great until you notice you also lost $4,000 to cancellations, leaving only $1,000 of real progress. Tracking the four components separately — instead of one headline number — is what separates an operator who understands their business from one who is flying blind.

At QUANT LAB

When we build a SaaS platform, MRR is not a spreadsheet someone updates by hand at month-end — it is a number the system computes from the source of truth. Because we wire Stripe directly into the application database, every subscription event (a new signup, an upgrade, a cancellation) updates MRR in real time and is attributed to the correct component automatically.

That matters because hand-rolled MRR dashboards drift. We have seen founders quote their investors an MRR figure that was off by 20 percent because annual plans were double-counted or refunds were never subtracted. The pragmatic builder's answer is to make the metric a byproduct of correctly modeled billing data, so the number you see on your dashboard is the same number your accountant would arrive at. If you are unsure whether to build that in-house or assemble it from off-the-shelf tools, our build vs buy framework walks through the math.

Talk to the engineer who would build it

If you want subscription metrics that compute themselves from real billing data instead of a fragile spreadsheet, book a 30-minute conversation — not a pitch.

SaaS platform development