Both metrics claim to describe how well a company keeps what it already sold, and both are calculated correctly at most companies. They still disagree inside the same period, because they score different populations against different denominators.
What each one actually measures
| Renewal rate | Gross revenue retention | |
|---|---|---|
| Denominator | Revenue available to renew in the period | Recurring revenue at the start of the period |
| Population | Contracts that reached an expiry date | Every account in the base |
| Captures mid-contract loss | No | Yes |
| Captures contraction at renewal | Yes | Yes |
| Primary audience | Renewals and customer success leadership | Finance, board, investors |
Why renewal rate reads higher
Three effects push it up. Mid-contract cancellations and payment failures fall outside the denominator entirely. Multi-year contracts keep large accounts out of the renewal population for years at a time, which removes exactly the accounts most likely to be stable. And early renewals pulled forward into the period usually arrive because the customer wanted something, which means they close.
None of that makes renewal rate dishonest. It makes it narrow. A renewals team hitting 95% on the book it was handed is doing good work, and that fact says nothing about whether the base eroded.
When to use each
Use renewal rate as an operating metric. It is the right scorecard for renewal coverage, for save rate, and for whether the team is starting conversations early enough to change outcomes.
Use gross revenue retention as the reporting metric. It is what investors compare across companies, it is what stress tests a plan against the scenario where new sales stop, and it is the one that reconciles to the ARR waterfall without adjustment.
Reporting both without confusing anyone
Publish the bridge, not only the two rates. Beginning ARR splits into available to renew and not yet renewable. Renewal outcomes land on the first portion, mid-contract losses on the second, contraction on both. Ending retained ARR divided by beginning ARR gives gross revenue retention, and the difference from renewal rate is now a labeled line rather than an argument.
That bridge is also what keeps a forecast honest. Projecting the base forward on renewal rate alone assumes nothing is ever lost between expiry dates, which overstates surviving revenue every period and compounds across a multi-year plan. Anyone building a revenue forecast should model the two populations separately, then check that the retained base ties to net revenue retention once expansion is layered back on.
Frequently Asked Questions
Which metric is usually higher?
Renewal rate, almost always. It excludes mid-contract cancellations, payment failures, and losses from accounts still inside their term, so the population it scores has already survived long enough to reach an expiry date. A visible gap between the two at the same company is normal rather than a red flag.
Can you compare your renewal rate to a published GRR benchmark?
No. The denominators are different populations, so the comparison flatters you by construction. Benchmark renewal rate against renewal rate and gross revenue retention against gross revenue retention, and state which base each number used.
Which one belongs in a board deck?
Gross revenue retention, because it answers the question an investor is actually asking about base erosion. Keep renewal rate in the operating review where it belongs, as the scorecard for how the renewals team performed against the book it was given.
How do the two reconcile?
Start with beginning ARR, split it into the portion available to renew and the portion still inside its term, apply renewal outcomes to the first and mid-contract losses to the second, then add contraction from both. The result is gross revenue retention, and the bridge shows exactly where the gap between the two metrics came from.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like gross revenue retention vs renewal rate into prescriptive action for your team.
Schedule a Demo