NRR was never a bad metric. The issue is what it became used for. Expansion revenue is disproportionately easy to concentrate in a handful of accounts, a few enterprise customers signing bigger deals can carry an entire book’s NRR, even while renewal rates among the broader base are quietly deteriorating. Leadership teams optimizing purely for NRR can end up rewarding expansion-heavy motions while under-resourcing the unglamorous, account-by-account work of keeping mid-market and smaller customers from drifting away.<\/p>\n
The result is a CS org that looks financially healthy on a slide but whose actual customer base is thinning. GRR does not let that happen, because it has nowhere to hide. If churn and contraction are real problems, GRR reports them directly, without a growth story to offset them.<\/p>\n
<\/p>\n
![\"\"](\"https:\/\/scubes.net\/pages\/wp-content\/uploads\/2026\/08\/GRR_Image1_TheBlend-1024x576.png\")
<\/h2>\n
<\/p>\n
What Makes GRR a Cleaner Signal<\/strong><\/h2>\nGRR is often described as \u201cthe ceiling”; it can never exceed 100%, and every point below that is lost revenue, full stop. That ceiling is precisely what makes it useful. It cannot be flattered by expansion, so it becomes an honest read on whether the product, the onboarding, the support motion, and the value delivered are actually sticking.<\/p>\n
It is also a better predictor of long-term health than most teams give it credit for. Benchmarks across SaaS put healthy GRR somewhere in the 90\u201395% range, and companies that consistently sit below that tend to have a leakier bucket than their NRR numbers suggest, meaning they are spending disproportionately on new logo acquisition just to stand still. A business retaining 85% of its revenue base needs meaningfully more new bookings to hit the same growth target as one retaining 95%, even if their NRR numbers look identical this quarter. GRR is the metric that tells you which of those two businesses you are actually running.<\/p>\n
<\/p>\n
![\"\"](\"https:\/\/scubes.net\/pages\/wp-content\/uploads\/2026\/08\/GRR_Blog_Image2_Ceiling-1024x640.png\")
<\/p>\n
<\/p>\n
<\/p>\n
Why This Should Sit With CS, Not Just Finance<\/strong><\/h2>\nThere is a reasonable argument that GRR is finance metric dressed up as a CS one it is, after all, a revenue calculation. But the inputs to GRR are almost entirely things Customer Success teams influence day to day: onboarding quality, time-to-value, health scoring accuracy, escalation handling, and how early a team catches a churn risk before it becomes a lost logo.<\/p>\n
Handing GRR ownership to CS is less about adding another number to a dashboard and more about aligning incentives with what the team can actually control. NRR ownership tends to pull CS teams toward expansion conversations which are important, but are also the easier, more pleasant half of the job. GRR ownership pulls attention back toward the harder half: the at-risk accounts, the quiet churners, the customers who never file a support ticket because they have already checked out.<\/p>\n
<\/p>\n
Making It Operational, Not Just an OKR<\/strong><\/h2>\nThe teams that get real value out of GRR are not the ones that simply add it to a quarterly OKR. They build the underlying muscle: health scores weighted toward leading indicators rather than lagging ones, renewal risk reviews that happen well before the renewal date, and clear ownership for who intervenes when an account’s usage trend turns downward. Gainsight and similar platforms make this operationally possible, but the platform is not the point the discipline of watching GRR-relevant signals earlier in the account lifecycle is.<\/p>\n
It also changes how a CS team is staffed and measured. If GRR is the primary success metric, then time spent on proactive check-ins with flat, low-risk accounts may matter less than time spent triaging the handful of accounts showing early churn signals. That is a genuinely different way to allocate a CSM’s calendar than an NRR-driven org would.<\/p>\n
<\/p>\n
In Practice: What This Looks Like for Our Clients<\/strong><\/h2>\n\nS Cubes in Practice: Mid-market B2B SaaS client<\/strong><\/p>\nA mid-market B2B SaaS client came to us reporting a healthy NRR, but their CS leadership could not explain why new bookings kept climbing while the sales team’s job kept getting harder. When we implemented Gainsight and rebuilt their health scoring around leading indicators rather than lagging ones, the real picture emerged: GRR was sitting closer to 84%, with churn concentrated in a segment of smaller accounts that expansion revenue from a handful of larger customers had been quietly masking. Once GRR became the metric their CSMs were measured against, renewal risk reviews moved earlier in the account lifecycle, and within two quarters the team had cut churn in that segment meaningfully without touching the expansion motion that was already working.<\/p>\n<\/div>\n
\nS Cubes in Practice: Enterprise Client<\/strong><\/p>\nAn enterprise client we worked with had the opposite problem: GRR ownership sat with finance, and CS had no visibility into it until a renewal was already at risk. We helped integrate their Gainsight and Salesforce environments so that usage, support, and financial data fed into a single account view, and worked with their leadership to hand GRR ownership to the CS org alongside NRR. That single change in accountability shifted how CSMs prioritized their calendars flat, low-risk accounts got lighter-touch check-ins, while accounts with early usage decline got escalated automatically. The result was a CS team that could finally see the floor it was standing on, not just the ceiling it was chasing.<\/p>\n<\/div>\n
<\/h2>\nThe Contrarian Caveat<\/strong><\/h2>\nNone of this means NRR should be discarded. Expansion revenue is real, and a business that only tracks GRR risks becoming conservative to a fault, under-investing in the upsell motions that fund growth. The healthiest approach treats GRR and NRR as a pair GRR as the floor that must be defended, NRR as the ceiling that gets built on top of it. A team that nails GRR but never expands anything is leaving revenue on the table. A team that nails NRR while GRR quietly erodes is borrowing against a customer base that will eventually run out of goodwill.<\/p>\n
<\/p>\n
![\"\"](\"https:\/\/scubes.net\/pages\/wp-content\/uploads\/2026\/08\/GRR_Image3_FloorAndCeiling-1024x576.png\")
<\/p>\n
The reason GRR deserves the \u201cnorth star\u201d label is not that it is more important than every other metric a CS team tracks. It is that it is the hardest one to fake, and the first one to show real trouble. In a market where retention has become more valuable than growth-at-any-cost, that kind of honesty is worth building a strategy around.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
For a few years now, Net Revenue Retention has been the metric every Customer Success team was told to obsess over. It sits on almost every SaaS board deck, it drives comp plans, and it has quietly become the number CS leaders are judged by. There is just one problem with that: NRR is very […]<\/p>\n","protected":false},"author":1,"featured_media":346,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_angie_page":false,"page_builder":"","footnotes":""},"categories":[1],"tags":[21,36,24,19,34,35,38,39,37,8],"class_list":["post-335","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","tag-churnprevention","tag-csops","tag-customerretention","tag-customersuccess","tag-grossrevenueretention","tag-netrevenueretention","tag-revenueoperations","tag-revops","tag-saasmetrics","tag-gainsight"],"featured_media_src_url":"https:\/\/scubes.net\/pages\/wp-content\/uploads\/2026\/08\/GRR_LinkedIn_Cover_Landscape-1-zoomed-1-1024x422.png","_links":{"self":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts\/335","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/comments?post=335"}],"version-history":[{"count":2,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts\/335\/revisions"}],"predecessor-version":[{"id":342,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts\/335\/revisions\/342"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/media\/346"}],"wp:attachment":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/media?parent=335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/categories?post=335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/tags?post=335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/p>\nThere is a reasonable argument that GRR is finance metric dressed up as a CS one it is, after all, a revenue calculation. But the inputs to GRR are almost entirely things Customer Success teams influence day to day: onboarding quality, time-to-value, health scoring accuracy, escalation handling, and how early a team catches a churn risk before it becomes a lost logo.<\/p>\n
Handing GRR ownership to CS is less about adding another number to a dashboard and more about aligning incentives with what the team can actually control. NRR ownership tends to pull CS teams toward expansion conversations which are important, but are also the easier, more pleasant half of the job. GRR ownership pulls attention back toward the harder half: the at-risk accounts, the quiet churners, the customers who never file a support ticket because they have already checked out.<\/p>\n
<\/p>\n
Making It Operational, Not Just an OKR<\/strong><\/h2>\nThe teams that get real value out of GRR are not the ones that simply add it to a quarterly OKR. They build the underlying muscle: health scores weighted toward leading indicators rather than lagging ones, renewal risk reviews that happen well before the renewal date, and clear ownership for who intervenes when an account’s usage trend turns downward. Gainsight and similar platforms make this operationally possible, but the platform is not the point the discipline of watching GRR-relevant signals earlier in the account lifecycle is.<\/p>\n
It also changes how a CS team is staffed and measured. If GRR is the primary success metric, then time spent on proactive check-ins with flat, low-risk accounts may matter less than time spent triaging the handful of accounts showing early churn signals. That is a genuinely different way to allocate a CSM’s calendar than an NRR-driven org would.<\/p>\n
<\/p>\n
In Practice: What This Looks Like for Our Clients<\/strong><\/h2>\n\nS Cubes in Practice: Mid-market B2B SaaS client<\/strong><\/p>\nA mid-market B2B SaaS client came to us reporting a healthy NRR, but their CS leadership could not explain why new bookings kept climbing while the sales team’s job kept getting harder. When we implemented Gainsight and rebuilt their health scoring around leading indicators rather than lagging ones, the real picture emerged: GRR was sitting closer to 84%, with churn concentrated in a segment of smaller accounts that expansion revenue from a handful of larger customers had been quietly masking. Once GRR became the metric their CSMs were measured against, renewal risk reviews moved earlier in the account lifecycle, and within two quarters the team had cut churn in that segment meaningfully without touching the expansion motion that was already working.<\/p>\n<\/div>\n
\nS Cubes in Practice: Enterprise Client<\/strong><\/p>\nAn enterprise client we worked with had the opposite problem: GRR ownership sat with finance, and CS had no visibility into it until a renewal was already at risk. We helped integrate their Gainsight and Salesforce environments so that usage, support, and financial data fed into a single account view, and worked with their leadership to hand GRR ownership to the CS org alongside NRR. That single change in accountability shifted how CSMs prioritized their calendars flat, low-risk accounts got lighter-touch check-ins, while accounts with early usage decline got escalated automatically. The result was a CS team that could finally see the floor it was standing on, not just the ceiling it was chasing.<\/p>\n<\/div>\n
<\/h2>\nThe Contrarian Caveat<\/strong><\/h2>\nNone of this means NRR should be discarded. Expansion revenue is real, and a business that only tracks GRR risks becoming conservative to a fault, under-investing in the upsell motions that fund growth. The healthiest approach treats GRR and NRR as a pair GRR as the floor that must be defended, NRR as the ceiling that gets built on top of it. A team that nails GRR but never expands anything is leaving revenue on the table. A team that nails NRR while GRR quietly erodes is borrowing against a customer base that will eventually run out of goodwill.<\/p>\n
<\/p>\n
<\/p>\n
The reason GRR deserves the \u201cnorth star\u201d label is not that it is more important than every other metric a CS team tracks. It is that it is the hardest one to fake, and the first one to show real trouble. In a market where retention has become more valuable than growth-at-any-cost, that kind of honesty is worth building a strategy around.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
For a few years now, Net Revenue Retention has been the metric every Customer Success team was told to obsess over. It sits on almost every SaaS board deck, it drives comp plans, and it has quietly become the number CS leaders are judged by. There is just one problem with that: NRR is very […]<\/p>\n","protected":false},"author":1,"featured_media":346,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_angie_page":false,"page_builder":"","footnotes":""},"categories":[1],"tags":[21,36,24,19,34,35,38,39,37,8],"class_list":["post-335","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","tag-churnprevention","tag-csops","tag-customerretention","tag-customersuccess","tag-grossrevenueretention","tag-netrevenueretention","tag-revenueoperations","tag-revops","tag-saasmetrics","tag-gainsight"],"featured_media_src_url":"https:\/\/scubes.net\/pages\/wp-content\/uploads\/2026\/08\/GRR_LinkedIn_Cover_Landscape-1-zoomed-1-1024x422.png","_links":{"self":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts\/335","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/comments?post=335"}],"version-history":[{"count":2,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts\/335\/revisions"}],"predecessor-version":[{"id":342,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts\/335\/revisions\/342"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/media\/346"}],"wp:attachment":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/media?parent=335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/categories?post=335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/tags?post=335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
S Cubes in Practice: Mid-market B2B SaaS client<\/strong><\/p>\n A mid-market B2B SaaS client came to us reporting a healthy NRR, but their CS leadership could not explain why new bookings kept climbing while the sales team’s job kept getting harder. When we implemented Gainsight and rebuilt their health scoring around leading indicators rather than lagging ones, the real picture emerged: GRR was sitting closer to 84%, with churn concentrated in a segment of smaller accounts that expansion revenue from a handful of larger customers had been quietly masking. Once GRR became the metric their CSMs were measured against, renewal risk reviews moved earlier in the account lifecycle, and within two quarters the team had cut churn in that segment meaningfully without touching the expansion motion that was already working.<\/p>\n<\/div>\n S Cubes in Practice: Enterprise Client<\/strong><\/p>\n An enterprise client we worked with had the opposite problem: GRR ownership sat with finance, and CS had no visibility into it until a renewal was already at risk. We helped integrate their Gainsight and Salesforce environments so that usage, support, and financial data fed into a single account view, and worked with their leadership to hand GRR ownership to the CS org alongside NRR. That single change in accountability shifted how CSMs prioritized their calendars flat, low-risk accounts got lighter-touch check-ins, while accounts with early usage decline got escalated automatically. The result was a CS team that could finally see the floor it was standing on, not just the ceiling it was chasing.<\/p>\n<\/div>\n None of this means NRR should be discarded. Expansion revenue is real, and a business that only tracks GRR risks becoming conservative to a fault, under-investing in the upsell motions that fund growth. The healthiest approach treats GRR and NRR as a pair GRR as the floor that must be defended, NRR as the ceiling that gets built on top of it. A team that nails GRR but never expands anything is leaving revenue on the table. A team that nails NRR while GRR quietly erodes is borrowing against a customer base that will eventually run out of goodwill.<\/p>\n <\/p>\n The reason GRR deserves the \u201cnorth star\u201d label is not that it is more important than every other metric a CS team tracks. It is that it is the hardest one to fake, and the first one to show real trouble. In a market where retention has become more valuable than growth-at-any-cost, that kind of honesty is worth building a strategy around.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" For a few years now, Net Revenue Retention has been the metric every Customer Success team was told to obsess over. It sits on almost every SaaS board deck, it drives comp plans, and it has quietly become the number CS leaders are judged by. There is just one problem with that: NRR is very […]<\/p>\n","protected":false},"author":1,"featured_media":346,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_angie_page":false,"page_builder":"","footnotes":""},"categories":[1],"tags":[21,36,24,19,34,35,38,39,37,8],"class_list":["post-335","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","tag-churnprevention","tag-csops","tag-customerretention","tag-customersuccess","tag-grossrevenueretention","tag-netrevenueretention","tag-revenueoperations","tag-revops","tag-saasmetrics","tag-gainsight"],"featured_media_src_url":"https:\/\/scubes.net\/pages\/wp-content\/uploads\/2026\/08\/GRR_LinkedIn_Cover_Landscape-1-zoomed-1-1024x422.png","_links":{"self":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts\/335","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/comments?post=335"}],"version-history":[{"count":2,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts\/335\/revisions"}],"predecessor-version":[{"id":342,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/posts\/335\/revisions\/342"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/media\/346"}],"wp:attachment":[{"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/media?parent=335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/categories?post=335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scubes.net\/pages\/wp-json\/wp\/v2\/tags?post=335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/h2>\n
The Contrarian Caveat<\/strong><\/h2>\n
<\/p>\n