Gross revenue retention (GRR) measures the percentage of starting recurring revenue retained from existing customers after accounting for churn and downgrades only, without including expansion revenue. Where NRR can exceed 100% because of upsells and expansions, GRR is capped at 100% and measures only how well you are retaining existing contracts.

GRR is the floor of your retention performance. It tells you what percentage of your revenue base you keep when expansion is stripped out. A company with 95% GRR and 110% NRR is retaining its base well and expanding from it. A company with 80% GRR and 105% NRR is masking serious churn problems with aggressive upsell activity that may not be sustainable.

Tracking GRR separately from NRR reveals the composition of your retention story. Strong NRR on weak GRR means expansion is compensating for churn, which is a fragile model: if expansion slows, the underlying churn becomes visible. Strong GRR on moderate NRR means you are retaining most of your base with moderate expansion, which is a healthier foundation.

GRR is particularly valuable for assessing product-market fit and customer success programme effectiveness. It isolates the retention question from the expansion question, showing whether customers are fundamentally satisfied enough to stay regardless of whether they are buying more. It is the metric most directly controlled by customer success and product teams.

In a B2B pipeline model, this is only useful if it changes resourcing or prioritization. A clean definition helps the team decide where to push harder, where to cut waste, and which funnel step deserves attention next. It usually becomes more useful when it is defined alongside NRR, Churn, and Retention.

GRR — example

Two SaaS companies have the same 108% NRR. Company A has 98% GRR: it retains 98% of its base and grows the remainder through expansion. Company B has 85% GRR: it loses 15% of its base annually but compensates with aggressive upsells to remaining customers. Company A's NRR is stable and sustainable. Company B's NRR is fragile: if the customers being upsold start churning at higher rates as well, NRR collapses. Investors favour Company A's profile significantly.

A B2B company cleans up how it uses GRR after noticing that leadership likes the headline number but cannot explain what operationally caused it to move. They rebuild the logic so the term maps back to specific pipeline actions and owners. They also make sure it connects cleanly to NRR and Churn so the definition is not trapped inside one team.

Frequently asked questions

How should teams benchmark GRR without using a misleading average?

There is rarely one universal benchmark for GRR. The useful approach is to compare it by source, segment, stage, and time period, then ask whether the number is supporting the business outcome you actually care about. Because grr is tied to gross revenue retention — recurring revenue kept from existing customers over a period, excluding upsells and expansions., a "good" number only matters if quality stays intact at the next step of the funnel.

Why can GRR change even when the team did not change much on purpose?

Start by checking inputs before you blame the headline result. In most B2B teams, grr shifts because audience quality changed, the handoff process changed, follow-up speed changed, or the measurement logic changed. Segmenting the number usually shows the real cause faster than debating the blended average.

What review cadence makes GRR useful instead of reactive?

Review cadence should match how quickly the team can act on the number. Fast-moving paid or outbound metrics deserve frequent checks, while slower pipeline or retention metrics benefit from weekly or monthly review with context. Ownership should sit with the team that can change the inputs, but the definition itself should stay consistent across functions.

How do you avoid hiding problems inside one blended GRR number?

The first useful breakdown is usually source or audience quality, then stage or offer type depending on the workflow. A single company-wide number often hides whether the problem is top-of-funnel fit, handoff quality, or conversion discipline. Break grr down where decisions are made, not where dashboards are easiest to build.

What should a team compare against GRR before taking action?

If you only pair GRR with one other concept, use NRR. It gives context for whether the number is strong for the right reason or simply flattering one step of the process while hurting the next. Looking at the terms together usually produces better decisions than trying to optimize GRR in isolation.