What is Monthly Recurring Revenue (MRR)?

Monthly Recurring Revenue, abbreviated as MRR, is the normalized monthly revenue generated from active subscriptions. It is the foundational financial metric for SaaS businesses: a measure of predictable, contracted revenue that allows companies to model growth, plan headcount, and assess business health without the noise of one-time payments or usage spikes.

MRR is calculated by multiplying the number of active paying customers by the average revenue per account per month. Annual contracts are normalized by dividing the total contract value by twelve. The result is a consistent, comparable number that can be tracked week over week and month over month.

The components of MRR

MRR does not move as a single number. It is the net result of several flows happening simultaneously.

New MRR is the revenue added from customers who signed up or converted from a free plan in a given period. Expansion MRR reflects upgrades and seat additions from existing customers. Contraction MRR captures downgrades. Churned MRR is the revenue lost when customers cancel. Net New MRR is the sum of these four components, and it is the number that reveals whether a business is growing, flattening, or shrinking.

MRR vs. ARR

ARR, or Annual Recurring Revenue, is MRR multiplied by twelve. It is the preferred metric for companies with predominantly annual contracts, where monthly normalization can obscure the underlying contract value. For companies with a mix of monthly and annual billing, both metrics are useful: MRR for short-term trend analysis, ARR for investor reporting and strategic planning.

Why product teams have more influence over MRR than they realize

MRR is typically treated as a finance and sales metric, but the decisions that move it are largely product decisions. Activation rate determines how many trial users convert to paid. Feature adoption depth determines whether customers stay or churn. The quality of the onboarding experience determines how quickly new users reach the value that justifies continued payment.

Expansion MRR in particular has a strong product dependency. Users who have discovered and adopted multiple features are less likely to churn and more likely to upgrade when they encounter usage limits. This is why product teams focused on feature adoption and in-app guidance have a measurable impact on the expansion motion, even in companies with dedicated sales teams.

The lag between a product improvement and its appearance in MRR data can be weeks or months, depending on billing cycles. This does not diminish the relationship. It means that product teams need leading indicators: activation rate, feature adoption, time to value, to know whether their work is moving the underlying drivers before the revenue data confirms it.