Every VP of Customer Success knows the number. 110% net revenue retention is the benchmark that separates the high-performers from the average, the teams that get budget from the ones that fight for it, the companies that compound their ARR from the ones that tread water. It comes up in board meetings, in investor decks, in every SaaS benchmarks report published in the last five years.
What almost nobody writes about is what it actually takes to get there and stay there.
The NRR meaning is straightforward: it measures the percentage of recurring revenue retained from your existing customer base over a given period, accounting for expansion, contraction, and churn. If your NRR is above 100%, your existing customers are growing your business even without a single new logo. Above 110%, and you’re in the territory where the best B2B SaaS companies operate.
But the math is simple. The operations behind it are not. This post is about the four structural things that 110%+ NRR teams consistently have in place, and where the gaps quietly appear for teams who are still chasing the number on the roadmap.
Onboarding Is the First Place NRR Gets Won or Lost
The most common mistake in thinking about net revenue retention is treating it as a renewal-time problem. It’s not. By the time you’re at a renewal conversation, the outcome has already been largely determined, usually 90 to 180 days earlier.
Onboarding is where the foundation gets set. A customer who reaches their first meaningful outcome within 30 days is a fundamentally different renewal risk than one who “went live” but never actually changed how they work. These two customers look identical on your dashboard for months. They only diverge when one renews easily and the other sends a cancellation email you didn’t see coming.
The question worth asking is not whether your customers completed onboarding, but whether onboarding delivered a real business result. Completion rates measure activity. What you need to measure is whether the customer’s core use case is actually working.
She was describing what happened when product and customer success aligned on a shared NRR target, with pricing and packaging built to reflect real customer progress. The outcome she described was not a new methodology, it was a structural alignment: both teams measured success against the same number, which meant onboarding was no longer just an implementation step. It was the first chapter of a retention story.
Teams that hit 110% treat customer onboarding as an NRR activity, not a setup task. The question they ask is not “did we get them onboarded?” but “do we have evidence they got value?”
Expansion Cannot Depend on a Human Remembering to Check
The second thing 110%+ teams have in place is a structured way to detect expansion signals before those opportunities slip away quietly.
This is where the math on NRR versus GRR gets instructive. A team with solid gross retention, say 92%, still needs meaningful expansion to clear 110%. If your average customer isn’t expanding meaningfully, the only path to 110% is near-perfect retention, which very few companies sustain across a real customer base. The realistic path to 110% requires both: you protect the base and you grow it.
Most CS teams know this. Where it breaks down is in the mechanics. Expansion conversations happen when a CSM has time, when a QBR comes around, when a renewal is approaching and someone notices there’s an upsell opportunity they should have surfaced six months earlier. By then, the conversation is reactive and the customer feels like they’re being sold to.
The teams that sustain 110% don’t find expansion opportunities by having attentive CSMs. They find them because they have a system that surfaces behavioral signals: a customer approaching a usage tier limit, a team whose adoption has climbed steeply over 60 days, a user base that has expanded significantly since the original deal. These signals already live in your product data. The question is whether anyone is reading them, and whether they’re being read in time to act.
Real-time account signals delivered to CSMs in their existing workflow, before renewal windows open, is what separates proactive expansion from opportunistic upselling. The former compounds. The latter caps.
Your Health Score Is Either a Leading Indicator or a Story You’re Telling Yourself
The third structural piece is signal quality. Specifically, whether your customer health scoring is built on leading indicators or lagging ones.
This is a harder conversation than it sounds, because most teams believe they have a health score. What they often have is a monthly updated number derived from a set of inputs that made sense when they built it, that nobody fully trusts, that CSMs use to justify their existing views rather than to update them.
A health score that tells you an account is at risk at the same time your CSM is hearing the word “cancellation” is not a health score. It’s a confirmation of what you already know too late.
The accounts that matter most for NRR, the mid-size customers renewing in Q3, the accounts that haven’t complained but have quietly reduced usage, the ones where the original champion just changed roles, these are the accounts that require leading indicators. Behavioral signals like usage trajectory, not just current usage, engagement quality across multiple contacts, not just login frequency, support sentiment trends well before the NPS survey goes out.
Ryan Milligan, VP of Sales, Marketing & RevOps at QuotaPath, made a point that cuts to the core of this on the Across the Funnel Podcast:
“If you just do net revenue retention, sometimes you can have a massive expansion that overshadows all of your churn and contraction and it’s just like, it’s not a great setup for the org. But for orgs that want comp plans that are a little more up funnel, I am seeing more teams use implementation and adoption as components of the variable comp plan, so that an account manager cares about adoption well before renewal.”
This is not just a comp plan observation. It is an argument about where NRR actually gets shaped. If the only signal your team tracks is renewal health, and if adoption is measured only when it affects a deal, you will consistently be surprised by churn you should have seen coming. Building in early signals, and building accountability around them well before the renewal window, changes the behavior of the whole team.
CS and Revenue Teams Need the Same Definition of Success
The fourth structural piece is one that often gets treated as a culture conversation when it is actually an operational one: ownership.
Net revenue retention is a number that requires multiple functions to move it. Churn is owned by CS. Expansion is often contested between CS and account management. Product influences adoption. Marketing runs campaigns into the install base. RevOps tracks the data. If each of these teams is optimizing for a slightly different thing, NRR becomes nobody’s number. It gets reported on but not owned.
The teams that sustain 110% have resolved this through operational clarity, not through team culture speeches. They have defined which signals trigger which team, who is accountable for expansion at which account tier, how product and CS communicate on at-risk accounts, and what the handoff looks like when a CS conversation becomes a commercial one.
This is unglamorous work. It involves deciding things like: who owns the expansion conversation for a customer in their second year? Who gets the alert when usage drops? What does “at-risk” mean across three different CS tiers? But that unglamorous clarity is exactly what separates teams that post 110% consistently from teams that hit it once and regress the next quarter when churn ticked up and expansion dried out and nobody could explain exactly why.
Customer success operations and shared success metrics across functions are not nice-to-haves at the 110% level. They are the infrastructure the number requires.
Where NRR Quietly Breaks Down
It’s worth being honest about the failure modes, because they’re not always visible until the quarter is over.
The most common way a team slips from 110% to 103% is not one dramatic churn spike. It’s a collection of smaller things: a few accounts that expanded last year don’t expand this year, a handful of churns that weren’t predicted because the signals were there but nobody read them, a new logo cohort that onboarded poorly and is quietly disengaged heading into their first renewal. None of these individually changes the number much. Together, they do.
The second failure mode is a high NRR number masking a GRR problem. If your gross revenue retention is sitting at 78% and your NRR is 108%, you have a customer base that is expanding at a rate that is covering a serious retention problem. This tends to catch up with teams when expansion slows, which it will eventually, and the underlying churn becomes visible. Sustainable 110% requires both a healthy floor and real expansion on top of it.
The third is treating NRR as an annual metric. Most B2B SaaS teams report NRR quarterly or annually, but the signals that move it are weekly. A customer who disengages in March will be an at-risk renewal in September. The gap between when the signal appears and when it gets addressed is where NRR erodes.
Hyperengage is built for post-sales teams who want to close that gap, by bringing product signals, CRM data, and customer communication into a single view that makes the early indicators visible before they become renewal problems.
Conclusion
110% NRR is not a goal you set and then work backward to explain. It’s an output of four specific operational investments: onboarding designed to deliver real value, expansion systems that surface signals before opportunities close, health scoring built on leading indicators that CSMs actually trust, and cross-functional ownership of the same number. Get all four in place, and 110% becomes repeatable. Miss any one of them, and you’ll be searching for the explanation in a post-mortem the quarter after you needed it.
