NRR (Net Revenue Retention)
Definition
NRR (Net Revenue Retention), also known as Net Dollar Retention (NDR), measures the percentage of revenue retained over a given period within a cohort of existing customers, after accounting for expansions, contractions, and churn. This metric reveals a company’s ability to grow from its existing customer base, independent of new acquisitions. An NRR above 100% means expansion revenue outweighs losses from churn, generating organic growth without acquiring new customers.
NRR calculation and formula
NRR is calculated using the formula: (Initial MRR + expansion - contraction - churn) / Initial MRR × 100. Expansion includes upgrades, upsells, and cross-sells. Contraction represents downgrades and license reductions. Churn accounts for lost customers. For example, with an initial MRR of €100K, +€20K expansion, -€5K contraction and -€10K churn, the NRR is 105%: the company grows 5% on its existing base before any new customer acquisition.
Interpretation and benchmarks
NRR benchmarks vary by market segment. In Enterprise SaaS, an NRR above 120% is considered excellent, reflecting strong expansion potential within large accounts. In SMB, an NRR of 90–100% is acceptable given structurally higher churn. The best public SaaS companies report NRRs of 130% or more. An NRR below 100% indicates a contracting customer base, requiring constant acquisition to maintain revenue.
NRR vs GRR
GRR (Gross Revenue Retention) measures retention excluding expansions: (initial MRR - contraction - churn) / initial MRR. GRR can never exceed 100%. Comparing NRR and GRR reveals the business dynamic: a large gap indicates strong expansion capacity but also potentially high churn hidden by upsells. A low GRR with a high NRR can indicate a fragile model that relies on expansion to offset customer departures.
Levers to improve NRR
Improving NRR requires activating several levers. Reduce churn through solid onboarding, proactive Customer Success, and early detection of attrition signals. Drive expansion by identifying upsell opportunities, continuously demonstrating value, and creating natural paths to higher-tier offerings. Minimize contractions by promptly addressing satisfaction issues and offering alternatives to downgrades. Alignment between Product, CS and Sales around NRR ensures a coordinated approach.
Impact on valuation
NRR strongly influences the valuation of SaaS companies. Investors favor models with a high NRR because they generate predictable, capital-efficient growth. A company with 120% NRR can sustain double-digit growth even with modest customer acquisition. Market analyses show that publicly traded SaaS companies with NRR above 120% trade at valuation multiples 25% higher than those with NRR below 100%. This metric has become a key indicator in investment due diligence.
Operational monitoring of NRR
Monitoring NRR requires a robust data infrastructure. RevOps must track MRR movements by category (new, expansion, contraction, churn) and by cohort. Segment analysis (account size, industry, product) identifies where NRR is performing or underperforming. Leading indicators (product engagement, NPS, feature usage) predict future NRR trends. Real-time dashboards enable CS teams to prioritize their actions on at-risk accounts or those with high expansion potential.
Related terms
Continue exploring with these definitions
API (Application Programming Interface)
An API, or Application Programming Interface, is a set of rules, protocols, and tools that enable different software applications to communicate with one another. It defines the methods and data formats a program can use to interact with another system, service, or software component. APIs are the backbone of modern software architecture, enabling interoperability, modularity, and integration across heterogeneous systems.
Backend Architecture
Back-end architecture is the technical framework—the invisible but essential backbone—of any modern application. It encompasses all the software components, servers, databases, and services that run behind the scenes to process requests, manage data, and orchestrate business logic. Unlike the front-end, which handles the visible user interface, the back-end operates on the server side and ensures the application functions properly as a whole. This architecture directly determines a system's performance, scalability, security, and maintainability.
Webhook
A webhook is a communication mechanism that allows an application to automatically send data to another application as soon as a specific event occurs. Unlike traditional methods in which an application must regularly poll a server to check for new information, a webhook reverses that logic by adopting a push-based approach. The source application takes the initiative to notify recipient applications at the exact moment a state change or event happens. This technology is akin to an intelligent notification system that eliminates the need for constant monitoring and significantly improves the efficiency of exchanges between computer systems. The term webhook stems from the analogy with hooks used in programming—those attachment points that let you insert custom code at key moments during a program's execution. In the web context, these hooks become HTTP endpoints that enable applications to communicate asynchronously and in an event-driven way. This architecture is founded on the core principle of decoupling, where the sender and receiver do not need to be active at the same time or maintain a persistent connection.
Frequently Asked Questions
Have questions about the lexicon? We have the answers.
Leonard
Co-founder
Let's talk about your project
Our team of experts will respond promptly to understand your needs and recommend the best solution.