GRR Is the Metric Your Board Should Actually Care About
NRR gets all the attention. It's the number on the investor deck and the one CS leaders post about. I've had some strong NRR quarters and I'm proud of them.
But if you gave me one number to judge the health of a CS organization, I'd pick gross revenue retention every time.
NRR can hide a leak
NRR mixes two different things: the revenue you kept and the revenue you added. A handful of big expansions can cover a steady drip of churn and downgrades underneath. You can report a great NRR while losing a real share of your base every year, and the day your expansion motion has a slow quarter, the leak shows up all at once.
GRR has nowhere to hide. It tops out at 100% and asks one question: did the customers who paid you last year keep paying you? I think it's the most honest number in Customer Success.
A low GRR is usually a value problem
When I stepped into my current role, gross retention was well below where it needed to be. The natural instinct in that spot is to get more commercial. More renewal calls, earlier discount conversations, tighter forecasting.
That treats the symptom. In my experience, customers rarely decide to leave in the 90 days before their contract ends. They decide in the first few months after they sign, when they never quite reach the point where the product becomes part of how they work. The renewal conversation is just where you find out.
So we stopped asking how to save renewals and started asking what the customers who renew have in common.
Find your Value Events
That question led us to what we call Value Events: specific moments in the customer's journey that line up with renewal. Not logins. Moments where the customer actually got what they bought the product for. The first time they used an insight in a real decision. The first time a result showed up in a leadership meeting. The first time a second team asked for access.
Once you can name those moments, a lot of other work gets clearer. Onboarding gets rebuilt around reaching the first Value Event quickly instead of touring features. The health score starts tracking whether those moments are happening, which is the same argument I make in why CS should measure outcomes instead of logins. And CSMs know what good looks like for every account at every stage.
We redesigned onboarding around the jobs customers were hiring the product to do, with enablement built for each persona instead of one generic training. Within six months, GRR was up by double digits. We didn't get there by working harder at renewal time. We got there because more customers reached the moment that made renewing obvious.
Why a board should care
For an executive team, GRR is the floor everything else stands on. Expansion is great, but it's much cheaper and more predictable to grow a base that isn't eroding. Every point of GRR is revenue you don't have to replace with new logos, and new logos are expensive. If you're trying to get your CFO on board, agreeing on shared definitions with Finance is the place to start.
It's also an early read on product-market fit. If customers keep paying without being upsold, the product is doing its job. If they stay only because a CSM talked them into it, that problem will surface eventually.
Where I'd start
Report GRR and NRR side by side, every time, so one can't show up without the other. Pull the last year of renewals and churns and look for the behaviors that separate them; those are your Value Event candidates. Then look at onboarding and ask how many days it takes a new customer to reach the first one, and work that number down. Finally, rebuild the health score so it reflects value rather than activity. If you need a refresher on the rest of the dashboard, I've written about the CS metrics I think actually matter.
NRR tells you how fast you're growing. GRR tells you whether it'll last. The best CS teams watch both, but they start with the one that doesn't flatter them.
I'm also putting together a CS metrics and board reporting pack with GRR and NRR definitions, a retention calculator and a one-page board report. You can find it on the Resources page.
If your retention numbers aren't where you want them, I'm happy to talk through what I'd look at first.

