Why a High Net Dollar Retention Rate Can Be Misleading
Net Dollar Retention above 120% is one of those numbers that makes investors lean forward, boards relax, and leadership teams feel like they’ve cracked the code. And in many cases, they have. But there’s a version of high NDR that tells a very different story underneath, and most teams never look closely enough to notice.
This isn’t an argument against high NDR. You should absolutely be chasing it. The point is that a number on a dashboard is not a business. The problem with NDR specifically is that it can hold steady, even look strong, while the foundation underneath it is thinning.
NDR Is a Lagging Indicator That Rewards Backward-Looking Optimism
NDR measures how much revenue you retained and expanded from your existing customer base over a period, usually a year. If you start with $1M in ARR from existing customers and end with $1.2M, your NDR is 120%. Simple math. Widely celebrated.
The problem is that it only tells you what happened. It doesn’t tell you why, and it definitely doesn’t tell you whether it’s repeatable. Boards love it because it’s clean. Revenue leaders love it because it’s defensible. But it says nothing about how you got there, and that gap is where risk quietly accumulates.
Three specific patterns can inflate NDR to a number that looks like retention health but is actually masking fragility. All three are common. All three are fixable if you know to look for them.
You Might Be Pricing Above What the Market Will Hold
Overpricing is not always the result of bad judgment. Sometimes it happens because you grew fast, your sales team was aggressive, and early customers paid rates the market has since normalized away from. The accounts are still with you. The contracts are still intact. But at renewal, you’re going to find out what those relationships are actually worth.
In the meantime, your NDR looks fine. Maybe great.
The tell is in your gross revenue retention rate compared to your NRR. If your GRR is quietly declining, or if your downsell rate is creeping up quarter over quarter, the expansion numbers might be covering it. High NRR with softening GRR is a specific warning sign that deserves more attention than most teams give it.
There’s also a customer sentiment signal. Accounts that are overpriced tend to show lower product adoption, less engagement with new features, and more friction at QBRs. They’re not expanding because they love you. They’re not churning because switching is painful. That is a category of customer that will leave the moment a credible alternative appears, or when a new procurement head decides to audit SaaS spend.
A high NDR built on overpriced, low-adoption accounts is a timer, not a trophy.
Expansion From Three Accounts Is a Portfolio Problem, Not a Growth Story
Concentration risk in NDR is underappreciated and genuinely dangerous. It’s possible to post 118% NDR on the strength of two or three enterprise accounts that expanded significantly while the rest of your base barely moved. The number reports as excellent. The underlying dynamic is that your “retention engine” is actually three bets.
What happens if one of those accounts gets acquired? Changes leadership? Decides to consolidate vendors? You don’t lose some NDR. You lose a structurally important chunk of your ARR in a single event.
The way to see this clearly is to look at your expansion ARR distribution. If the top 10% of accounts by size represent more than 50% of your total expansion, that concentration should be tracked as a risk metric alongside NDR itself. The aggregate number obscures what the cohort analysis reveals.
Most CS teams aren’t building visibility into this because their tooling doesn’t surface it easily. They’re looking at overall NDR by quarter, maybe segmented by tier. That’s not enough resolution to see concentration building.
Healthy NDR is wide, not just tall. It comes from a broad base of accounts showing consistent, modest expansion, driven by genuine adoption growth, headcount increases among customers, and feature uptake that corresponds to real usage. That kind of NDR is durable because it doesn’t depend on any single relationship staying intact.
Expansion ARR Is Not a Churn Offset
This is the subtlest pattern of the three, and the one most teams discover too late.
When a customer churns, that lost revenue gets subtracted from your NDR calculation. When a different customer expands, that gained revenue gets added. If expansion outpaces churn, your NDR still looks healthy, or even strong. The underlying churn is invisible in the aggregate.
Say you lose four $50K accounts in a quarter and expand two $150K accounts. Your net position is up $100K. Your NDR trends higher. Your churn report shows losses, but they’re a line item in a finance deck, not a central discussion in your CS operating review. The number tells the story you want to hear.
On Across The Funnel, Ryan Milligan, VP of Sales, Marketing & RevOps at QuotaPath, explained why tracking gross and net retention separately is the only way to make sure expansion revenue doesn’t mask a real churn problem:
“The reason you split it is because you want somebody to feel the pain of churn. And 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 not a great setup for the org.” – Ryan Milligan
This becomes a serious problem because churn is a leading indicator of product-market fit issues, onboarding failures, competitive pressure, and segment problems. If you’re not looking at gross churn as a standalone metric, and not tracking it by cohort, segment, and time-to-churn, you’re missing the signal that tells you where the business is actually breaking.
Aggressive upsell motion is valuable. But if it’s being used, even unintentionally, to paper over a churn problem, you’re compressing the timeline on a much harder conversation. The accounts that expand today don’t eliminate the onboarding failures that caused churn last quarter. Those failures will repeat.
What NDR Looks Like When It’s Actually Healthy
A strong NDR number backed by genuine retention health has a few characteristics that separate it from the inflated version. None of them are complicated, but all of them require you to look past the aggregate and build the habit of reading retention at a lower level of abstraction.
Expansion Is Distributed Across the Base
The accounts driving NRR growth should represent a wide cross-section of your customer base, not a handful of large accounts that happened to have a good year. If your top 20 expanding accounts represent more than 35% of total expansion ARR, that’s a concentration problem wearing a growth story as a costume. The fix is to track expansion ARR distribution as a standing metric, segmented by account size, industry, and cohort, so you can see whether growth is broadening over time or narrowing toward a smaller set of relationships you’re becoming increasingly dependent on.
GRR and NRR Are Read Together, Always
Gross Revenue Retention and Net Revenue Retention tell you different things, and reading one without the other is how retention problems stay invisible for quarters at a time. If you’re posting 118% NDR but your GRR has dropped from 88% to 84% over four quarters, the expansion math is flattering a retention problem, not indicating retention health. Teams that catch this early build a simple rule into their operating cadence: NRR never gets reported without GRR sitting next to it.
Product Adoption Is the Lead Indicator, Not a Footnote
The accounts that expand sustainably are almost always the accounts with deep product adoption, consistent login activity, and growing usage across features. When you plot expansion ARR against product engagement scores, the correlation should be obvious. If it isn’t, the expansion is coming from something other than product value, and whatever that something is, it’s fragile. The practical move is to identify the specific usage milestones in your product that historically precede expansion events, and build your CS motion around getting accounts to those milestones before the conversation about expansion ever starts.
On Across The Funnel, Irina Vatafu, Head of Customer Success at Custify, mentioned why tracking product usage is only half the job, the signal only becomes useful when your CS motion is built around acting on it before the conversation about expansion ever starts:
“Once we have the product usage data, we also have to help them understand the metrics and analyze them and act on them because it’s not enough to have the metric and to know what’s important. You also have to take action based on those.” – Irina Vatafu
Tools like Hyperengage are built specifically to surface those signals at the account level, but the discipline of tracking adoption as a leading indicator matters more than the tool you use to do it.
Churn Gets Its Own Dedicated Review
Gross churn should be a standing agenda item in your CS operating cadence, not something that gets absorbed into a net number and explained away by expansion. When churn is only ever visible as a net figure, the segments that are breaking stay hidden until the problem is large enough to move the aggregate. The better operating model is to track gross churn by cohort, segment, and time-to-churn separately, and treat any increase in gross churn as a signal worth investigating regardless of what net retention is doing that quarter.
Time-to-Expansion Is Getting Shorter
In a healthy retention motion, customers hit their first expansion event faster over time because onboarding is improving, adoption is accelerating, and the CS team has enough signal to identify the right moment to have the expansion conversation with precision. If your time-to-first-expansion is flat or lengthening, that’s worth diagnosing before assuming the growth rate will hold. Map the customer journey from contract signature to first expansion across your cohorts and look for where accounts are stalling. That’s usually where the onboarding or adoption problem lives.
The Aggregate Number Is the Wrong Unit of Analysis
The patterns above: overpricing, concentration risk, and churn masking, share a common root cause. They all thrive in environments where the primary retention metric is the aggregate NDR number, reviewed quarterly, with limited ability to drill into what’s actually driving it.
The teams that catch these problems early tend to have a different operating cadence. They’re tracking GRR and expansion ARR separately, always. They’re running cohort analysis by segment, not just by tier. They’re correlating product usage data with renewal and expansion outcomes so they can see which behaviors actually predict growth, and which accounts are quiet in ways that should concern someone.
None of this requires exotic tooling. It requires treating NDR as the output of a system, not the system itself, and building the visibility to understand what’s flowing into it. Platforms built specifically for post-sales teams, like Hyperengage, are designed to surface exactly this layer of signal, but the discipline of looking matters more than the tool you use to look.
The real work is deciding that the number on the dashboard is the beginning of the conversation, not the end of it.
Conclusion
There’s a difference between a business that earns 120% NDR and one that just reports it, and that difference almost always shows up eventually.
The teams that compound on retention success are the ones that don’t stop at the aggregate. They go one level deeper: which accounts are expanding and why, where churn is hiding, whether product adoption is actually driving the growth the number implies. That level of visibility is what separates a retention engine from a retention coincidence.
The number can be right for the wrong reasons, and in SaaS, wrong-reason growth tends to have an expiration date. The earlier you build the habit of questioning what’s behind your NDR, the better position you’re in when the number eventually tells you something you weren’t expecting.
