Contents
To improve net revenue retention, work the five lines that move it: churned customer ARR, churned product ARR and product decrease ARR on the loss side, new product ARR and increased product ARR on the gain side. Start with renewals six months out and seats already paid for, then run expansion as tracked deals that begin with the customer's champion. Updated November 2026: added the lever table, renewal timing and terms, expansion signals, and a worked NRR bridge.
What are the levers that improve net revenue retention?
Eight levers, each tied to one waterfall line, one measure and one first action. Net revenue retention is an output, so improving it directly is like improving gross margin without looking at the cost lines. Pick the lever that touches the line costing you the most points.| Lever | NRR component it moves | What to measure | First action |
|---|---|---|---|
| Work renewals six months out | Churn (churned customer ARR) | Renewal ARR flagged at risk six months before the renewal date | Create renewal opportunities a year ahead and review risk at the six-month mark |
| Give large renewals a named owner | Churn and contraction | GRR for accounts with a named renewal owner vs. invoice-only renewals | Assign an owner to every annual or multiyear renewal above a size you set |
| Manage renewal terms | Churn | Renewal rate on auto-renew vs. manual renewal; accounts facing a 10%+ uplift | List every account with a contracted increase of 10% or more and start that conversation early |
| Read support patterns | Churn | Accounts with zero cases or seven or more cases in the last 12 months | Review both groups against the renewal calendar |
| Deploy purchased seats | Contraction (product decrease ARR) | Licensed seats minus active seats, in dollars, by account | Sort by the unused-seat dollars and work the top of the list before renewal |
| Land secondary modules | Contraction (churned product ARR) | Module usage by account | Find modules with little use and fix the rollout before the renewal opens |
| Usage-triggered upsell | Expansion (increased product ARR) | Accounts crossing your utilization or volume threshold | Open an opportunity with an owner and a close date the day an account crosses |
| Cross-sell through the champion | Expansion (new product ARR) | Accounts that own one product and show expansion signals | Build the business case with the champion and the group that gains most |
How early should you work a renewal to protect NRR?
About six months before the renewal date, which is when real risk shows up in the data. At ORM we start predicting renewal outcomes as soon as the renewal opportunity exists in Salesforce, typically 12 months out. At that point most renewals look safe. Risk comes into focus around six months before the date, and if a renewal is truly at risk the signal gets louder as the date approaches.Six months is enough time to work with the customer and fix their business case. Thirty days is not. If the first contact a customer gets is an invoice 30 days before renewal, you have put that renewal at more risk. I have watched this play out: when the renewals team is a finance function that sends invoices, gross retention tends to run lower than at companies with a dedicated customer success team. CS costs more, so put it where the dollars are. A $100 monthly auto-renewal does not need the same treatment as a large annual or multiyear contract.
One warning on models. If 90% of your customers renew, a model that predicts everyone renews is 90% accurate and useless. The value is in naming the 10 in every 100 that are most at risk so someone acts on them.
Which renewal terms put NRR under pressure?
Manual renewals and large contracted price increases. The biggest split we see is between customers on auto-renew and customers who are not. Auto-renew does not guarantee the renewal, but those accounts renew more reliably, so the manual ones deserve earlier attention.Price uplifts count toward NRR when they land, and they also add pressure. A contracted increase of 10% a year or more puts strain on the renewal, especially in an account that is under-using what it bought. If you plan to raise prices, segment the base first and give notice early, as covered in how to raise prices at renewal without losing customers.
Support history is the third term to read, and it runs against intuition. A customer with zero support cases in a year is a churn risk. So is one with seven or more. A customer with three to five resolved cases, usually tier two or tier three, tends to be the happiest account you have, because it is engaged and getting help. The full pattern is in how to use support tickets to predict churn.
Which lever stops contraction fastest?
Product decrease ARR, because the fix is deployment work rather than a new sale. Contraction at renewal often traces back to seats a customer bought and never rolled out. The buyer sees a line item nobody can defend internally, and the renewal comes down to the count they actually use.That problem is visible months ahead. Compare licensed seats to active seats by account, sort by the gap in dollars, and work the top of that list: department onboarding, use case expansion inside the account, and removing whatever blocked rollout the first time. Every seat in production before the renewal is a seat you keep at full price.
Churned product ARR is the second stop for the same reason. A customer dropping one module while keeping the platform is telling you exactly which part of your product failed to land. If product usage says the customer uses only a fraction of what you sell, treat that as risk unless the part they use is business critical.
Where does expansion that lifts NRR come from?
Accounts with room to grow and a champion willing to build the case. The signals that predict expansion are different from the ones that predict churn: the customer's business growing, new funding, positive comments on an earnings call, adoption of more product features, and interest in your other products showing up in web or marketing engagement.Product footprint matters both ways. A customer using many parts of your system is a good expansion candidate. A customer who has bought everything you sell is likely sticky but hard to upsell. A customer who has bought one thing has upside, though narrow adoption can also be a risk sign, so check usage before you pitch.
Who acts on the signal decides whether it turns into revenue. There is usually an internal champion. Start there, then build the business case with the group that has the most to gain from the expansion. The sooner that case exists, the better.
How do you build expansion revenue you can forecast?
Trigger opportunities from usage thresholds and run them as real deals with stages and close dates. Expansion that first appears during a renewal negotiation is a bargaining chip, and it gets traded for a signature.Write the threshold down as a number: seat utilization above a set level, a second department active, a volume metric crossing a tier boundary. When an account crosses it, create an opportunity with an owner and a date, and hold it to the same pipeline coverage discipline you apply to new business. Expansion runs against an existing buying relationship, which is why it becomes forecastable once it is tracked. The trigger table and coverage math are in how to build an expansion pipeline.
Give expansion its own stage weights. New business, expansion and renewal behave differently, and one set of weights across all three produces a forecast that misses. ORM targets 95% accuracy on new and expansion revenue, updated as the quarter moves and without manual adjustment.
How much does each lever move the number?
In the illustrative bridge below, five lever wins take NRR from 100.0% to 108.0% and GRR from 86.0% to 90.5%. The company and every figure are illustrative. Beginning ARR is $10,000,000.| Waterfall line | Baseline | Lever applied | After | NRR change |
|---|---|---|---|---|
| Churned customer ARR | -$800,000 | Renewals worked six months out save $250,000 | -$550,000 | +2.5 pts |
| Churned product ARR | -$200,000 | Module rollout fixed in at-risk accounts saves $50,000 | -$150,000 | +0.5 pts |
| Product decrease ARR | -$400,000 | Shelf seats deployed before renewal save $150,000 | -$250,000 | +1.5 pts |
| Increased product ARR | +$900,000 | Usage-triggered upsell adds $200,000 | +$1,100,000 | +2.0 pts |
| New product ARR | +$500,000 | Champion-led cross-sell adds $150,000 | +$650,000 | +1.5 pts |
| Ending ARR from the base | $10,000,000 | $10,800,000 | +8.0 pts | |
| NRR | 100.0% | 108.0% | ||
| GRR | 86.0% | 90.5% |
Two things to read from it. The three loss-side levers deliver 4.5 of the 8 points, and they are also the only ones that move GRR. And every point of NRR is worth $100,000 on this base, which is the number to put next to the cost of a CS hire. For where 100% or 108% sits against your peers, see what is a good net revenue retention rate. Benchmarkit's 2025 report puts the B2B SaaS median at 101% NRR and 88% GRR.
Why does NRR improve while the business gets weaker?
Because expansion sits in the numerator and can outrun losses for several quarters before the base runs out of accounts to expand. A company with concentrated expansion in ten large accounts and steady bleed across two hundred small ones posts a healthy NRR right up until one of the ten leaves.Read NRR beside gross revenue retention every month. GRR strips expansion out and cannot exceed 100%, which makes it the load-bearing number for retention work. Then check concentration: what share of your expansion ARR came from your top five accounts. Above half, your NRR is a story about a handful of relationships rather than a repeatable motion. If the number has already fallen, why net revenue retention dropped walks the month-by-month diagnosis.
How do you stop churn from eating expansion gains?
Attack it where the dollars are, one segment at a time. Cut churned customer ARR by segment, contract size, acquisition channel, and tenure. The loss usually concentrates in one or two cells, and the concentration names the fix.A cohort that churns hard in months 10 to 14 has an onboarding problem, because those accounts never reached a result worth renewing. A cohort that churns after a champion change has a single-threading problem. A cohort concentrated in one acquisition channel has a fit problem you can solve at the top of the funnel by disqualifying earlier. These need different owners, and one company-wide retention initiative across all of them wastes most of the effort.
How does NRR connect to the revenue plan?
Ending ARR is a forecast output, so every waterfall line needs a modeled number rather than an assumption. Most annual plans forecast new bookings carefully and treat retention as a flat percentage carried over from last year. That single assumption often carries more dollars than the entire new business target.Model churn ARR and expansion ARR by month with the same rigor you apply to new deals, then reconcile to ending ARR. Renewals are easier to forecast than new business: you usually know the amount and the date, and in our data most renewals close within about 30 days either side of the renewal date. When conditions change, buyers cut seats and drop modules at renewal, and a flat retention assumption hides that until ending ARR misses. Building the revenue forecast with retention as a modeled line gives you the warning early enough to respond, and how to forecast net revenue retention covers the component model.
What should you measure monthly?
Six numbers: GRR, NRR, expansion concentration, seat utilization gap, renewal ARR flagged at risk six months out, and the count of accounts crossing your expansion trigger. The first two report the outcome. The other four move before it does, which makes them the ones worth arguing about in a monthly review.Structure the review around the waterfall rather than the percentage. In ORM we reconcile the base month by month: beginning ARR (last month's ending ARR), churned customer ARR, churned product ARR, product decrease ARR, new customer ARR, new product ARR, increased product ARR, ending ARR. A meeting that opens with the NRR number spends its hour debating whether the number is right. A meeting that walks each line from beginning to ending ARR spends its hour on the movements, and every movement has an owner. Ask that owner what changed since last month. This reconciliation is the part teams skip and the part that makes the metric operational instead of decorative.
Frequently Asked Questions
What is the fastest way to improve net revenue retention?
Work the renewals you already have. That revenue is in the base and needs no new buying decision. Flag at-risk renewals about six months before the renewal date, when ORM sees risk come into focus, and close the gap between seats bought and seats used before the customer cuts the count. Expansion takes a full sales cycle, so it moves NRR later even when it moves it further.
Can NRR improve while churn gets worse?
It can, and it happens often. NRR adds expansion revenue to the numerator, so a strong upsell quarter can carry the number above 100% while the underlying loss rate accelerates. Read NRR next to gross revenue retention every month. GRR excludes expansion and cannot exceed 100%, which makes it the honest read on whether the base is leaking.
What is the difference between GRR and NRR?
Gross revenue retention counts only losses: churned customers, dropped products and seat or usage decreases. It tops out at 100%. Net revenue retention starts from the same base and adds expansion from upsell and cross-sell, so it can exceed 100%. Improving NRR means moving both: GRR through renewal and adoption work, the gap above it through expansion.
Is 95% net revenue retention good?
It is below the market middle. Benchmarkit's 2025 report puts median B2B SaaS NRR at 101%, and 95% means the existing base shrinks 5% a year before any new logo is added. Whether it is a problem depends on your ACV and segment, so compare it to the right band, then find which waterfall line is costing you the points.
Does net revenue retention include new customers?
New customer ARR sits outside NRR. The metric measures only the customers you had at the start of the period, so a new logo added mid-year never enters the numerator or the denominator. New customer ARR still belongs on the monthly waterfall, because ending ARR has to reconcile and a team can hit its growth number while every retention line weakens.
How often should NRR be reviewed?
Monthly, as a reconciling waterfall from beginning ARR to ending ARR. ORM tracks churned customer ARR, churned product ARR, product decrease ARR, new customer ARR, new product ARR, and increased product ARR as separate lines each month. Reviewing only the quarterly NRR percentage hides which of those lines actually moved and who owns the fix.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo



