SaaS Gross Revenue Retention: How to Calculate GRR

SaaS Gross Revenue Retention (GRR) tells you how much recurring revenue you keep from the customers you already had at the start of a period, after churn and contraction but before any expansion. The core formula is simple:

GRR = (Starting Recurring Revenue - Churned Revenue - Contracted Revenue) / Starting Recurring Revenue x 100

If you start a month with $100,000 in MRR, lose $4,000 from cancellations, and lose another $2,000 from downgrades, your GRR is 94%. New customers and expansion from existing customers don't affect that number.

That last point is what makes GRR useful. Net Revenue Retention (NRR) can rise above 100% when existing customers expand their spending. GRR cannot. It gives you a cleaner view of whether the revenue you have already earned is sticking around.

This guide explains how to calculate SaaS GRR using MRR or ARR, how to handle discounts, payment failures, pauses, multi-year contracts, foreign exchange, and usage-based pricing, and how to use cohort analysis to find the source of revenue leakage. It also covers GRR benchmarks, common calculation mistakes, and practical ways to improve retention without confusing GRR with NRR or logo retention.

---

What Is SaaS Gross Revenue Retention?

Gross Revenue Retention, usually abbreviated as GRR, measures the percentage of recurring revenue retained from a starting customer base over a defined period. It includes revenue lost through customer churn and contraction, but it does not include expansion revenue.

GRR is also called Gross Retention Rate or Gross Dollar Retention in some SaaS reporting environments. The terminology varies, but the basic idea is the same: start with a fixed recurring-revenue base and measure how much of it remains after losses.

For example, suppose your company begins the quarter with $1 million in recurring revenue. During the quarter:

• Customers cancel $60,000 of recurring revenue.
• Existing customers downgrade by $40,000.
• Existing customers expand by $150,000.
• New customers add another $200,000.

For GRR, only the first three starting-base figures matter, and expansion is excluded. New business is excluded too.

GRR is therefore:

**($1,000,000 - $60,000 - $40,000) / $1,000,000 x 100 = 90%

The company retained 90% of its starting recurring revenue before considering any expansion or new sales.

The 100% Ceiling

GRR cannot exceed 100% under the standard definition because expansion revenue is excluded from the calculation.

If a customer paying $1,000 per month upgrades to $1,500, GRR still treats that account as contributing its original $1,000 baseline. The extra $500 is expansion revenue and belongs in NRR, not GRR.

If the same customer downgrades from $1,000 to $800, GRR records $200 of contraction. If the customer cancels completely, GRR records the full $1,000 as churned revenue.

That ceiling makes GRR easy to interpret:

• 100% GRR: No starting recurring revenue was lost to churn or contraction.
• 95% GRR: The business retained 95% of its starting recurring revenue.
• 80% GRR: The business lost 20% of its starting recurring revenue.
• Below 100%: Some revenue from the starting cohort was lost.

A GRR above 100% generally indicates that the calculation has included expansion revenue or otherwise differs from the standard definition.

Why GRR Matters

NRR answers the question, "How much did our existing customer base change after both losses and expansion?"

GRR asks a narrower question: "How much of the recurring revenue we started with did we keep?"

That distinction matters when diagnosing a SaaS business. A company can report strong NRR because a smaller group of customers is expanding rapidly while another group is cancelling or downgrading. GRR exposes those losses instead of allowing expansion to offset them.

GRR also helps product, customer success, finance, and revenue teams look at the same problem from different angles. A declining GRR can point toward poor onboarding, weak product adoption, pricing pressure, competitive displacement, implementation problems, or billing failures. The metric doesn't tell you which problem exists, but it tells you that revenue is leaking from the existing base.

---

The Gross Revenue Retention Formula

The standard SaaS GRR formula is:

GRR = (Starting Recurring Revenue - Churned Revenue - Contraction Revenue) / Starting Recurring Revenue x 100**

You can use MRR for a monthly calculation or ARR for an annual calculation.

Monthly GRR Formula

Monthly GRR = (Starting MRR - Churned MRR - Contraction MRR) / Starting MRR x 100

For example, with $100,000 in starting MRR, $4,000 in churn, and $2,000 in contraction:

**($100,000 - $4,000 - $2,000) / $100,000 x 100 = 94%

Annual GRR Formula

For an annual measurement, use ARR or another consistently defined annual recurring-revenue baseline:

Annual GRR = (Starting ARR - Churned ARR - Contraction ARR) / Starting ARR x 100**

If starting ARR is $5 million, churn is $250,000, and contraction is $150,000:

**($5,000,000 - $250,000 - $150,000) / $5,000,000 x 100 = 92%

The company retained 92% of the recurring revenue that existed at the beginning of the measurement period.

What Belongs in the Formula?

The hardest part of GRR usually isn't the arithmetic. It's deciding which revenue movements belong in each category.

The key is consistency. Define your revenue categories once, document them, and use the same rules across reporting periods.

---

How to Calculate SaaS GRR Step by Step

A reliable GRR process starts with a clean starting cohort rather than a simple comparison between this month's total MRR and last month's total MRR.

Step 1: Establish the Starting Recurring Revenue

Choose the measurement period and freeze the starting customer base at the beginning of that period.

For a monthly GRR calculation, this might be the recurring revenue from active customers at 12:00 a.m. on the first day of the month, depending on how your billing and finance systems define the reporting cut-off.

For an annual calculation, use the recurring revenue baseline established at the start of the year.

Do not mix new customers into the starting base simply because they signed up during the reporting period.

Step 2: Identify Churned Revenue

Find every account in the starting cohort that stopped generating recurring revenue during the measurement period.

If a customer began the period at $3,000 MRR and cancelled completely, that account contributes $3,000 of churned MRR.

If a customer reduced its contract from $3,000 to $0, the full $3,000 is churn.

Step 3: Identify Contraction Revenue

Next, identify starting-cohort accounts that remained customers but reduced recurring spend.

Examples include:

• A plan downgrade from $2,000 to $1,500 per month: $500 contraction.
• A reduction from 50 seats to 40 seats at $20 per seat: $200 contraction.
• Removal of a $300 monthly add-on: $300 contraction.

If the customer later expands again, that later increase is treated as expansion for the relevant measurement period rather than as a way to erase the original contraction in the GRR calculation.

Step 4: Exclude Expansion and New Business

This is where many GRR calculations go wrong.

Suppose the starting cohort produces $10 million in ARR. During the year, existing customers add $2 million of expansion ARR and new customers add another $3 million. Neither amount belongs in GRR.

Adding those figures would turn the metric into something closer to NRR or a broader revenue-growth measure.

Step 5: Apply the Formula

Once the starting revenue, churn, and contraction values are clean, calculate the retained revenue and divide it by the starting revenue.

For example:

• Starting ARR: $10,000,000
• Churned ARR: $700,000
• Contraction ARR: $300,000
• Expansion ARR: $2,000,000
• New ARR: $3,000,000

GRR is:

($10,000,000 - $700,000 - $300,000) / $10,000,000 x 100 = 90%

Expansion and new ARR don't change the result.

Step 6: Reconcile the Result

A strong finance process doesn't stop after calculating the percentage. Reconcile the result back to account-level movements.

The retained revenue implied by GRR should equal the starting revenue less the qualifying churn and contraction movements. If the numbers don't reconcile, investigate issues such as duplicated accounts, billing-period mismatches, currency conversions, credits, plan changes, or incorrect revenue classifications.

---

GRR Calculation Example: Monthly SaaS Business

Consider a B2B SaaS company measuring October performance.

At the beginning of October, the starting MRR is $100,000.

During the month:

• Two customers cancel, creating $4,000 of churned MRR.
• Three customers downgrade or reduce seats, creating $2,000 of contraction MRR.
• Five existing customers expand by $8,000.
• Four new customers add $6,000 of new MRR.

Only the first three starting-base figures are relevant to GRR, and the $8,000 expansion is excluded.

Step 1: Calculate Retained MRR

Retained MRR = $100,000 - $4,000 - $2,000 = $94,000**

Step 2: Calculate Monthly GRR

GRR = $94,000 / $100,000 x 100 = 94%

The company's October GRR is 94%.

The new customers and expansion revenue still matter for overall growth, but they don't improve GRR.

What If We Included Expansion?

If you added the $8,000 expansion to the calculation, you would get:

**($100,000 - $4,000 - $2,000 + $8,000) / $100,000 x 100 = 102%

That isn't GRR. It is the basic NRR calculation before considering any other adjustments.

This example shows why the distinction between GRR and NRR matters. A business can have GRR below 100% and NRR above 100% at the same time.

---

GRR Calculation Example: Enterprise SaaS Using ARR

Now consider an enterprise SaaS company that begins the year with $5 million in ARR.

During the year:

• Churned ARR: $250,000
• Contraction ARR: $150,000
• Expansion ARR: $750,000
• New ARR: $1,000,000

The retained starting ARR is:

$5,000,000 - $250,000 - $150,000 = $4,600,000**

Annual GRR is:

**$4,600,000 / $5,000,000 x 100 = 92%

The company retained 92% of its starting ARR.

If the $750,000 of expansion is included, NRR becomes:

($5,000,000 - $250,000 - $150,000 + $750,000) / $5,000,000 x 100 = 107%

So the same company can report 92% GRR and 107% NRR. Those figures aren't contradictory. They answer different questions.

---

GRR vs NRR vs Logo Retention

SaaS teams often discuss retention as if there were one universal metric. There isn't. GRR, NRR, and logo retention measure different dimensions of the customer base.

Why GRR and NRR Should Be Viewed Together

Imagine two companies that both start with $10 million in ARR and finish the year with 115% NRR.

Company A** loses $300,000 through churn and contraction, then generates $1.8 million of expansion ARR.

• GRR = ($10M - $0.3M) / $10M = 97%
• NRR = ($10M - $0.3M + $1.8M) / $10M = 115%

Company B loses $3 million through churn and contraction, then generates $4.5 million of expansion ARR.

• GRR = ($10M - $3M) / $10M = 70%
• NRR = ($10M - $3M + $4.5M) / $10M = 115%

The NRR is identical, but the underlying businesses are very different.

Company A has a relatively stable revenue base and meaningful expansion. Company B is losing a much larger share of its starting revenue and needs substantial expansion to offset those losses.

Neither GRR nor NRR is sufficient on its own. Together, they give you a better view of both revenue durability and expansion potential.

GRR vs Logo Retention

Logo retention can hide the financial impact of losing a high-value customer.

Suppose a company has 100 customers. Ninety-five small accounts pay $100 per month, while five enterprise customers pay $10,000 per month. The five enterprise accounts represent a much larger share of revenue despite representing only 5% of the customer count.

If several small accounts cancel, logo retention may look weak while GRR remains relatively strong. If one or two enterprise accounts cancel, logo retention may barely move while GRR takes a much larger hit.

That is why revenue-weighted retention metrics are especially important when contract values vary widely.

---

SaaS GRR Benchmarks: What Is a Good GRR?

There is no single GRR target that applies to every SaaS company. A reasonable target depends on customer segment, contract length, ACV, product category, customer concentration, pricing model, and how the company defines its recurring revenue base.

Published benchmark ranges also vary by methodology and sample. Treat any benchmark as a directional reference rather than a universal pass-or-fail standard.

As a practical planning framework, many SaaS teams use ranges such as these:

These aren't universal industry standards. A 92% GRR may be excellent for one business and disappointing for another.

Enterprise SaaS GRR

Enterprise software often has annual or multi-year contracts, formal implementation processes, multiple stakeholders, and integrations that increase switching costs. Those characteristics can support stronger gross retention.

At the same time, enterprise GRR can be volatile because a small number of large accounts may represent a significant percentage of ARR. A single $500,000 account can have a much greater effect on annual GRR than dozens of small customers.

For enterprise SaaS, examine GRR alongside customer concentration, renewal rates, contract duration, and cohort retention.

Mid-Market SaaS GRR

Mid-market businesses sit between enterprise and SMB models. Customers may have annual contracts and meaningful product adoption, but switching decisions can happen faster than in highly integrated enterprise environments.

Look beyond the headline percentage. If GRR is declining, determine whether the cause is customer downsizing, failed implementations, competitive losses, budget pressure, or weak adoption.

SMB and Self-Serve SaaS GRR

SMB-focused products often have more month-to-month subscriptions and lower switching costs. Billing failures can also represent a meaningful portion of lost revenue.

For this segment, monthly GRR can be noisy. It helps to track rolling periods and cohorts rather than reacting to every individual month's movement.

How to Use Benchmarks Correctly

Don't set a GRR target simply because another SaaS company reports a higher number. Instead, compare your result with businesses that have similar economics.

Consider:

1. Customer segment and ACV.
2. Monthly versus annual contracts.
3. Self-serve versus sales-led acquisition.
4. Product category and switching costs.
5. Customer concentration.
6. Usage-based versus fixed subscription pricing.
7. The maturity of your customer base.

Then compare your current GRR with your own historical cohorts. A business moving from 82% to 88% may be making meaningful progress even if another segment routinely reports higher retention.

---

Seven Complex GRR Edge Cases

Real billing data rarely fits the clean examples found in financial-modeling guides. Discounts, payment failures, pauses, currencies, and usage-based contracts can all complicate the calculation.

1. One-Time Setup and Professional Services Fees

Implementation, onboarding, consulting, and custom development fees generally aren't recurring revenue and should be excluded from GRR.

Suppose a customer pays $50,000 in the first year: $40,000 for the software subscription and $10,000 for implementation. If the customer renews the software for $40,000 the following year, the recurring revenue retention is 100%.

Treating the implementation fee as part of recurring revenue would make the renewal look like a $10,000 contraction even though the software subscription was fully retained.

2. Contractual Discounts and Promotions

Discounts require a clear policy because the baseline should reflect the recurring revenue recognized under the commercial terms you're using for the metric.

If a customer signs a $1,000 monthly plan for $500 during a defined introductory period, decide whether your reporting policy treats $500 as the contractual recurring baseline during that period. Apply the same policy consistently across customers and periods.

If an existing customer paying $1,000 receives a reduction to $800 as a retention concession, the $200 reduction is contraction for GRR purposes.

The important thing is to distinguish a genuine pricing change from a one-time credit or accounting adjustment and document the treatment.

3. Involuntary Churn

Involuntary churn occurs when a subscription stops because of a failed payment, expired card, outdated billing details, bank decline, or another payment issue rather than an explicit cancellation.

For official GRR, revenue that is actually lost from the starting recurring base should generally count as churn regardless of why the customer left.

Operationally, however, separate voluntary and involuntary churn. A billing failure may be recoverable through retries, account updater services, or a customer payment update, while a customer who deliberately cancels requires a different retention response.

Don't assume a fixed percentage of churn is always involuntary. Measure it using your own billing data.

4. Subscription Pauses

Some SaaS products allow customers to pause subscriptions temporarily.

The correct treatment depends on the contractual and revenue policy your company uses. If the customer remains an active contractual relationship at a reduced recurring charge, the reduction can be treated as contraction. If the customer fully terminates the subscription, it may be treated as churn.

The important point is to avoid creating a custom rule that changes from month to month. Document the treatment and apply it consistently.

If a customer moves from $2,000 MRR to a $200 holding fee during a pause, the recurring-revenue reduction is $1,800. When the customer resumes and returns to $2,000, the increase should not retroactively erase the earlier movement in historical GRR reporting.

5. Foreign Exchange Movements

If customers pay in EUR, GBP, AUD, or another currency while management reports SaaS metrics in USD, exchange-rate movements can change the reported dollar value without any change in the customer's contract.

A constant-currency approach can help isolate operational retention from FX movements. For example, if a customer continues paying EUR 1,000 per month but the EUR-to-USD exchange rate changes, the customer's local-currency recurring revenue has not contracted.

Choose a consistent FX policy with your finance team and use it across the relevant retention reports.

6. Multi-Year Contracts and Early Cancellations

Enterprise customers may sign three-year contracts but pay annually. GRR should reflect the recurring revenue that is actually lost from the starting baseline when the cancellation or reduction takes effect, based on the company's contractual and revenue definitions.

For example, if a customer has a $100,000 annual recurring commitment and terminates the subscription at the end of Year 1, the relevant $100,000 reduction belongs in the period in which the recurring contract ends under the company's measurement policy.

Don't retroactively rewrite earlier GRR periods simply because a later cancellation occurred.

7. Usage-Based SaaS

Usage-based businesses create a different challenge because revenue can change without a formal contract downgrade.

A customer might spend $10,000 in one month and $7,000 the next because usage changed. Calling the entire $3,000 difference contraction can make GRR extremely volatile if the metric is intended to measure durable contractual retention.

For consumption businesses, the company should define a baseline that fits its business model. That may involve committed recurring revenue, minimum spend, contracted ARR, or a clearly documented normalized usage measure.

Don't force a traditional seat-based GRR formula onto a consumption model without first deciding what recurring baseline the metric is supposed to represent.

---

How Cohort Analysis Makes GRR More Useful

A company-wide GRR number tells you how much revenue was retained. It doesn't tell you when customers started leaking revenue or whether newer customers retain better than older ones.

Cohort analysis fills that gap.

A cohort groups customers according to a common starting point, such as signup month or quarter. You can then measure how the original recurring revenue from each cohort changes over time.

For example:

The exact values above are illustrative rather than industry benchmarks. The purpose of the table is to show how a retention curve can be structured.

What to Look for in a GRR Cohort

A sharp early decline can point to problems with onboarding, sales qualification, product expectations, or time-to-value.

A gradual decline over several months may indicate weak adoption, insufficient product depth, competitive pressure, or customers reaching a point where the product no longer justifies its cost.

A curve that stabilizes suggests that the customers who remain after the early-risk period are retaining more consistently.

Don't assume every cohort should follow the same curve. Customer mix, pricing changes, product releases, and acquisition channels can all change retention behavior.

Compare Cohorts by Acquisition Channel

Cohort analysis becomes even more useful when you split customers by acquisition source.

For example, customers acquired through paid search may have lower first-year GRR than customers acquired through referrals. That could indicate a mismatch between the search audience and the product's ideal customer profile.

You can also compare:

• Customer segment.
• Plan or pricing tier.
• Acquisition channel.
• Industry.
• Geographic market.
• Sales representative or sales motion.
• Product version at signup.
• Onboarding path.

This turns GRR from a reporting metric into a diagnostic tool.

---

Common SaaS GRR Calculation Mistakes

Even simple formulas produce misleading results when the underlying data is inconsistent.

Mistake 1: Adding Expansion Revenue to GRR

This is the most common conceptual error. If upsells, cross-sells, or seat expansion appear in the numerator, you're no longer calculating standard GRR.

Use NRR when you want to measure the combined effect of churn, contraction, and expansion.

Mistake 2: Including New Customers

New customers have no starting-period revenue in the cohort being measured. Their revenue belongs in new business metrics, not GRR.

Adding new MRR to GRR can make a declining customer base appear healthier than it really is.

Mistake 3: Comparing Total MRR Across Months

A simple month-over-month MRR comparison includes new business, expansion, churn, contraction, and potentially pricing or FX effects. It isn't automatically a GRR calculation.

GRR requires a defined starting cohort and isolates losses from that cohort.

Mistake 4: Mixing Recurring and Non-Recurring Revenue

Implementation fees, consulting, training, and one-time services should not be treated as recurring subscription revenue merely because they appear on the same invoice.

Separate them in the billing and finance data model.

Mistake 5: Changing Definitions Mid-Year

If one quarter treats paused subscriptions as churn and another treats them as contraction, the resulting trend isn't reliable.

Create a written metric definition covering revenue types, cancellations, downgrades, pauses, discounts, credits, FX, and usage-based accounts.

Mistake 6: Looking Only at the Company-Wide Number

A single GRR percentage can hide major differences between customer segments.

Break the metric down by cohort, plan, customer size, industry, and acquisition source when the dataset is large enough to support meaningful comparisons.

Mistake 7: Treating a Benchmark as a Target Without Context

A GRR benchmark from a large enterprise SaaS company may be irrelevant to a low-priced, month-to-month self-serve product.

Use benchmarks to create a starting point, then prioritize your own historical trends and peer group.

---

Five Practical Ways to Improve SaaS Gross Revenue Retention

Improving GRR means reducing the recurring revenue that leaves the existing customer base. The right intervention depends on why customers churn or contract.

1. Reduce Involuntary Churn

Payment failures are operational problems as well as retention problems. A customer may still value the product but lose access because a card expires or a transaction is declined.

A practical recovery process can include:

• Card and account updater services where supported.
• Automated payment retries based on the failure type and billing schedule.
• Clear email and in-app payment reminders.
• A simple payment-method update flow.
• Monitoring recovered revenue separately from unrecovered churn.

Don't measure the success of dunning by the number of emails sent. Measure recovered recurring revenue and the resulting reduction in involuntary churn.

2. Improve Time to Value

Customers are more likely to retain a product when they reach a meaningful outcome quickly.

Start by identifying the activation event that correlates with durable usage. Depending on the product, that could be importing data, inviting a team, completing a workflow, connecting an integration, or publishing the first project.

Then remove unnecessary steps between signup and that event.

Useful improvements include:

• Shorter setup forms.
• Guided onboarding.
• Product templates.
• Better default configurations.
• Integration setup assistance.
• Contextual education inside the product.

The goal isn't to make onboarding longer or more elaborate. It's to help customers reach useful product value sooner.

3. Give Customers a Clear Path to the Right Plan

Contraction isn't always a sign that a customer wants to leave. Sometimes the customer needs fewer seats, less usage, or a different feature mix.

A well-designed pricing structure can let customers move to a lower-cost plan while keeping the relationship active. That still creates contraction, so it doesn't magically improve GRR, but it can be preferable to full churn and gives the customer a path back to expansion later.

Review downgrade patterns regularly. If customers repeatedly remove the same feature or reduce the same type of seat, that may reveal a pricing or packaging problem rather than isolated customer behavior.

4. Monitor Product Usage and Customer Health

Retention teams should look for leading indicators rather than waiting for a cancellation request.

Useful signals can include:

• Declining active users.
• Reduced use of core workflows.
• Falling API or transaction volume.
• Unused seats.
• Increasing support friction.
• Failed implementation milestones.
• Long gaps between meaningful product activity.

A health score is useful only when it leads to action. If a customer's usage drops, define what the customer success team should do next and measure whether the intervention changes retention outcomes.

5. Analyze Cancellation and Downgrade Reasons

Your cancellation flow is one of the richest sources of retention information.

Ask customers why they're leaving, but keep the choices specific enough to analyze. Common categories include price, missing functionality, low usage, poor experience, company closure, internal budget changes, and switching to another product.

Then connect those reasons to revenue impact.

If "too expensive" represents 5% of lost logos but 25% of lost ARR, pricing deserves attention. If "missing feature" is concentrated among a particular segment, product planning may be the better response.

The objective isn't to make cancellation difficult. It's to understand why revenue leaves and give customers reasonable alternatives when a lower-cost plan, pause, training, or support intervention genuinely solves the problem.

---

How to Build a Reliable GRR Reporting Process

A useful GRR metric should be repeatable. Two analysts looking at the same customer data should arrive at the same result.

Start with a metric definition that answers these questions:

1. What counts as recurring revenue?
2. What timestamp establishes the starting baseline?
3. How are cancellations classified?
4. How are partial downgrades classified?
5. How are pauses handled?
6. How are discounts and credits treated?
7. How is foreign exchange handled?
8. How are usage-based accounts normalized?
9. How are multi-year contracts measured?
10. Which revenue categories are explicitly excluded?

Then build the calculation from account-level movements rather than relying only on aggregate MRR changes.

A useful account-level dataset might include:

Once the account-level data reconciles, calculate the aggregate metric and then segment it.

Monthly, Quarterly, or Annual GRR?

The right reporting frequency depends on the business model.

Monthly GRR can be useful for self-serve businesses with large customer volumes and frequent subscription changes. However, it can also be noisy.

Quarterly GRR can provide a smoother management view for businesses with fewer, larger accounts.

Annual GRR is particularly useful for enterprise SaaS because it aligns with many annual renewal cycles and gives enough time for meaningful contract movements to occur.

Many companies track more than one view: monthly operational retention for fast feedback and annualized retention for strategic reporting.

---

What GRR Can and Cannot Tell You

GRR is powerful, but it isn't a complete retention strategy.

GRR Can Tell You

• How much starting recurring revenue was retained.
• Whether churn and contraction are getting better or worse.
• How customer segments differ in revenue retention.
• Whether revenue losses are large enough to threaten the existing base.
• How retention changes across cohorts.

GRR Cannot Tell You

• Why customers churned without additional qualitative or categorical data.
• Whether expansion opportunities are strong.
• Whether new customer acquisition is efficient.
• Whether customer counts are stable.
• Whether customers are profitable.
• Whether a product has strong overall growth.

That's why GRR should sit alongside NRR, logo retention, customer acquisition metrics, churn analysis, and cohort reporting rather than replace them.

---

Key Takeaways for SaaS Teams

SaaS Gross Revenue Retention is fundamentally a measure of revenue durability.

The standard calculation is:

GRR = (Starting Recurring Revenue - Churn - Contraction) / Starting Recurring Revenue x 100

Remember the core rules:

1. Start with a clearly defined recurring-revenue cohort.
2. Subtract churned recurring revenue.
3. Subtract contraction from customers that remain active but spend less.
4. Exclude expansion revenue.
5. Exclude new customer revenue.
6. Exclude non-recurring fees from the recurring-revenue baseline.
7. Apply consistent policies for discounts, pauses, FX, multi-year contracts, and usage-based pricing.
8. Compare GRR with NRR and logo retention rather than using any one metric in isolation.
9. Use cohort analysis to find when revenue loss occurs.
10. Connect churn and contraction data to specific product, customer success, pricing, and billing actions.

A strong GRR doesn't mean customers never change plans or that every account is equally healthy. It means the recurring revenue you started with is holding up well. When GRR falls, the next step isn't to chase the percentage itself. Find the revenue movements behind the decline, identify the customers and cohorts responsible, and fix the underlying cause.

For SaaS companies evaluating billing automation, payment recovery, subscription management, or other retention infrastructure, independent software reviews can help compare the tools that support those workflows. Saasbonus provides hands-on software comparisons designed to help teams evaluate SaaS products before committing budget and implementation time.