Net Revenue Retention: Why Expansion Revenue Changes the Model

Net revenue retention, or NRR, measures how much recurring revenue remains from an existing customer cohort after expansion, contraction, and churn. It ignores new customers so you can see whether the installed base is growing or shrinking on its own.

The formula is: NRR = (starting MRR + expansion MRR - contraction MRR - churned MRR) / starting MRR. Multiply the result by 100 to express it as a percentage.

Suppose a customer cohort begins the year with $100,000 in MRR. During the year, customers upgrade for $18,000 of expansion MRR, downgrade by $5,000, and cancel $7,000. Ending retained revenue from that original cohort is $106,000. NRR is 106%.

An NRR above 100% means existing customers are expanding enough to offset downgrades and cancellations. That does not mean the business is guaranteed to grow, because new customer acquisition, pricing, margins, and costs still matter. It does mean the revenue base is healthier than a business that must replace lost MRR before it can grow.

A simple MRR model with one growth input and one churn input is easier to understand, but real SaaS growth often comes from a mix of new customers and existing account expansion. Strong NRR can make growth more capital efficient because some new revenue comes from customers you already acquired.

Low NRR creates the opposite problem. The sales team may add impressive new bookings while the installed base quietly contracts. In that case, a top-line forecast can look healthy until renewal pressure catches up. Operators should compare gross new MRR with churned and contracted MRR every month.

Investors and acquirers pay attention to NRR because it says something about product value, account expansion, customer success, and revenue durability. Benchmark reports often segment NRR by company size, contract value, market, and stage, so a single universal target is not responsible guidance.

Use benchmark data as directional context only. A $29 per month self-serve SaaS product and a $60,000 per year enterprise workflow platform can have very different retention patterns. Aura Revenue keeps the public calculator simple, but the methodology page explains how to interpret churn and growth assumptions when expansion revenue is part of the story.

To calculate NRR, start with a fixed customer cohort and ignore new customers added after the start date. Record the cohort starting MRR, expansion MRR, contraction MRR, and churned MRR over the measurement period. The cohort boundary matters because adding new customers would hide whether existing customers are expanding or shrinking.

Use revenue numbers, not customer counts. NRR answers a revenue question: how much recurring revenue did the original customer base retain after upgrades, downgrades, and cancellations? If you use customer counts, you are calculating retention behavior, not net revenue retention.

The cleanest dashboard shows NRR next to gross revenue retention. Gross revenue retention excludes expansion and shows how much revenue remains before upsells. NRR includes expansion. Together, they show whether growth inside accounts is covering churn or whether churn is being masked by upsells.

• Use a fixed starting cohort.
• Keep new customers out of the NRR calculation.
• Separate expansion from contraction.
• Compare NRR with gross revenue retention.

NRR helps operators decide where growth comes from. If NRR is above 100%, the installed base grows before new sales. That can support more durable growth because customer success, product adoption, and pricing expansion contribute to revenue. If NRR is below 100%, the company must replace lost recurring revenue before it grows.

NRR also reveals packaging issues. A product with strong usage growth but flat NRR may not have pricing that scales with customer value. A product with high contraction may have plan limits that push customers down instead of up. A product with high churn and high expansion may depend too much on a small set of successful accounts.

When you use Aura Revenue, model NRR effects by adjusting growth and churn assumptions, then move to the template for a more precise split between new MRR, expansion MRR, contraction MRR, and churned MRR.

A useful NRR review asks why the installed base expanded or contracted. Did expansion come from more seats, higher usage, premium features, or price changes? Did contraction come from downgrades, lower usage, budget pressure, or customers moving to a smaller plan? Did churn concentrate in a plan, cohort, industry, or account size?

NRR also belongs in product strategy. If customers expand after adopting a specific workflow, that workflow may deserve better onboarding and stronger packaging. If customers downgrade after hitting a confusing limit, the pricing page and in-app prompts may need revision.

Treat NRR as a customer value signal, not just a finance metric. Revenue retention improves when customers keep finding reasons to use more of the product.

After you read this guide, open the Aura Revenue calculator and change one assumption at a time. Keep starting MRR fixed, then adjust growth, churn, or the forecast period to see which input changes the outcome most. That exercise turns the concept into a planning habit.

For a deeper model, copy the SaaS revenue forecast template and split the monthly movement into new MRR, expansion MRR, contraction MRR, churned MRR, ending MRR, and ARR run rate. The calculator is best for fast scenario thinking. The template is better when you need operating detail.