An NRR result above 100% can look reassuring while the team is losing customers. Expansion in a few large accounts may outweigh churn elsewhere. The total is useful, but you need the movements behind it before deciding what to do.
Read the movements separately
Net revenue retention measures the recurring revenue retained from a starting customer cohort after churn, contraction, and expansion. Exclude new customers added after the cohort starts. Use the same revenue basis and period throughout.
For an illustrative cohort starting at $50,000, subtract $4,000 churn and $1,000 contraction, then add $7,000 expansion. The result is $52,000 and NRR is 104%. Gross retention for that cohort is 90%, so the growth total does not remove the loss.
Ask which accounts explain the change
Look at how much of the result comes from a small number of customers. Separate segments, lifecycle stages, or products only where those groups help answer a meaningful question. Avoid slicing a small customer base into percentages that suggest more certainty than the data supports.
Check whether expansion reflects a broader rollout, price changes, or usage-based variation. The same revenue movement can have different implications for customer work.
Connect the number to account context
For a contracting account, review the customer’s reason and the outcome they were trying to achieve. For an expanding account, check whether adoption and support are keeping pace with the wider commitment.
This is the practical work behind “NRR intelligence”: explaining what changed, which accounts contribute, and which decisions need attention. It should not imply that a number can diagnose every account.
Use the review to choose action
A recurring portfolio discussion should end with a few accountable next steps. One account may need an adoption review, another a commercial clarification, and another no intervention at all.
Keep forecasts and reported results distinct. Do not use a positive aggregate NRR figure as evidence that every renewal is safe or that an individual team member performed well.
Ask what is inside the headline number
A portfolio-level result can conceal different customer stories. Expansion in a few large accounts can offset contraction elsewhere. That may be commercially important, but it does not establish that the wider customer base is progressing well. Review the movements behind the total before deciding what the result means.
Keep the starting group, period, revenue basis, and movement rules visible. Confirm whether reactivation is included and how account or plan changes are treated. Different reports can disagree because their definitions differ, rather than because one team has made an arithmetic error. Resolve that before discussing the operating response.
Investigate movements at the account level
Choose a material change and follow it to the underlying accounts. For contraction, ask what changed in the customer’s needs and usage. For expansion, check what value and commercial change the customer actually confirmed. For churn, review the decision and the recorded reasons without assuming the last support ticket caused it.
Use several views where they help. A customer segment, onboarding period, or use case may reveal a pattern that disappears in the total. Treat small groups carefully; one large account can dominate them. Pair the revenue view with customer context before turning the pattern into a broad explanation.
Turn the review into a bounded operational question
Suppose contraction is concentrated in a segment using one workflow. The useful next question is whether that workflow still serves the segment’s goal, whether implementation is incomplete, or whether another factor is involved. Assign an owner to inspect a sample and bring evidence to the next review.
Do not ask the team to “improve NRR” without deciding what they can investigate or change. An account intervention, a product issue review, and a pricing discussion have different owners and timescales. Keep the action connected to the evidence that motivated it.
Use the result to learn, not to assign credit too quickly
Revenue outcomes can change alongside product releases, price changes, staffing, and customer budgets. A movement that follows a new process is not proof that the process caused it. Record what the team did, what the customer confirmed, and what else changed during the period.
In the next review, ask whether the chosen intervention addressed the original concern and whether the account story is clearer. Keep that operational learning alongside the financial report. The number can tell you where to look; it cannot replace the investigation.
Put it into practice
- Review churn, contraction, and expansion separately.
- Check concentration and segment context.
- Investigate the accounts before choosing an intervention.
References & further reading
PUT THE IDEA TO WORK
Analytics & Reporting in atEaseAI
Connect customer context with the next step your team needs to take.