Gross Revenue Retention vs Net Revenue Retention

Gross revenue retention, or GRR, shows how much recurring revenue you keep from an existing customer cohort before counting expansion. Net revenue retention, or NRR, shows how much you keep after counting expansion, contraction, and churn. The difference matters because expansion can make a customer base look healthy even when some customers are downgrading or leaving.

GRR answers a defensive question: how much revenue did we keep without upsells? NRR answers a broader question: did the existing customer base grow or shrink after all account movement? A SaaS team should usually track both because each metric catches a different risk.

GRR = (starting MRR - contraction MRR - churned MRR) / starting MRR. NRR = (starting MRR + expansion MRR - contraction MRR - churned MRR) / starting MRR. Multiply either result by 100 to express it as a percentage.

Suppose a cohort starts with $100,000 in MRR. During the period, it expands by $12,000, contracts by $4,000, and churns $6,000. GRR is 90% because the cohort retained $90,000 before expansion. NRR is 102% because expansion raised retained revenue to $102,000 after all movement.

• GRR excludes expansion MRR.
• NRR includes expansion MRR.
• Both calculations should use the same starting cohort.
• New customers acquired after the start date should not be included.

A company with strong NRR and weak GRR may be expanding successful accounts while losing or shrinking others. That can still produce growth, but it can hide customer-fit problems. A company with strong GRR and modest NRR may retain customers well but lack natural expansion paths. That can be healthy for a simple product, but it limits growth from the installed base.

For planning, GRR helps you understand the leak in the base. NRR helps you understand whether expansion offsets that leak. If your forecast depends on high NRR, the team needs a credible expansion motion. If your forecast depends on high GRR, the team needs strong onboarding, support, product value, and renewal discipline.

The most common mistake is calculating NRR with new customer revenue included. That turns retention into a growth metric and hides whether the original customer base retained value. Another mistake is treating NRR above 100% as proof that churn is no longer a problem. A company can have high NRR because a few large accounts expanded while many smaller accounts churned.

Segment the metrics when possible. Enterprise customers, small businesses, annual contracts, monthly subscriptions, and usage-based plans can produce different retention patterns. Blended NRR is useful for a top-level dashboard, but segment-level GRR and NRR help teams decide what to fix.

In Aura Revenue, you can approximate retention quality by changing the churn input and growth input. For a more detailed spreadsheet, split churned MRR, contraction MRR, and expansion MRR into separate columns. That structure lets you calculate GRR and NRR each month from the same customer cohort.

Use GRR to pressure-test the downside case. Use NRR to test whether expansion can carry part of the growth plan. Both numbers should be treated as educational planning inputs, not guarantees of future revenue.

A retention bridge starts with one cohort and explains how that cohort moved. Begin with starting MRR from customers active at the beginning of the period. Add expansion MRR from those same customers. Subtract contraction MRR and churned MRR from those same customers. The result is ending retained revenue for the cohort.

The bridge should not include new customers acquired during the period. New customers belong in total MRR growth, not retention. Keeping the boundary clean makes GRR and NRR more trustworthy. If a dashboard mixes new customer revenue into retention, leadership may miss a weakening customer base until acquisition slows.

• Choose a fixed starting customer cohort.
• Record expansion, contraction, and churn separately.
• Exclude new customers from retention metrics.
• Use the same cohort period when comparing GRR and NRR.

GRR and NRR should lead to decisions. If GRR falls, ask whether cancellations are concentrated in onboarding, renewal, plan fit, product gaps, customer segment, or payment failure. If NRR rises while GRR falls, ask whether expansion from a few accounts is masking broader customer dissatisfaction. If GRR is strong but NRR is flat, ask whether packaging, usage limits, seat expansion, or add-ons create enough natural expansion.

A useful retention review ends with owners. Product may own activation gaps. Customer success may own renewal risk. Marketing may own poor-fit acquisition. Finance or operations may own clean definitions. Without ownership, retention metrics become interesting numbers rather than operating tools.

Use the calculator to understand sensitivity, then use a cohort spreadsheet to diagnose the cause. The calculator can show how lower churn changes the forecast, but the operating data explains how to lower churn responsibly.

Place GRR and NRR near the top of a SaaS dashboard, but do not show them alone. Put them beside starting MRR, net new MRR, churned MRR, contraction MRR, expansion MRR, and customer count. This prevents a strong headline retention number from hiding the movement that created it.

For early teams, a monthly table is enough. Track the current month, trailing three months, and trailing twelve months when you have enough history. The goal is to create a stable operating view that can survive changes in pricing, packaging, acquisition channels, and customer mix.

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.