How to Improve Net Revenue Retention in B2B SaaS

Net revenue retention is the metric that separates SaaS companies that compound from those that tread water. The median NRR for B2B SaaS sits around 105-110%, meaning most companies barely grow from their existing customer base after accounting for churn and contraction.¹ The companies hitting 120%+ NRR aren't just better at upselling. They've solved a different problem entirely.

Most NRR improvement advice focuses on expansion: upsells, cross-sells, usage-based pricing, seat expansion. That matters. But expansion is the ceiling. Churn and contraction are the floor. And if your floor is dropping, raising the ceiling doesn't help.

The fastest path to durable NRR improvement isn't selling customers more. It's making sure the product fits each customer's actual workflow well enough that they never consider leaving or downgrading.

Key Takeaways

• Median B2B SaaS NRR is 105-110%; 120%+ is considered best-in-class (Bessemer, 2024)¹
• 67% of SaaS churn correlates with low product adoption, not pricing or competition (Gainsight, 2024)²
• A 5% increase in customer retention produces 25-95% increase in profits (Bain & Company)³
• Per-workflow customization in a first-party deployment hit 90.8% adoption and 89% day-30 retention⁴
• The underrated NRR lever: reduce churn and contraction by closing the workflow fit gap

What Is Net Revenue Retention and Why Does It Matter? #

Net revenue retention measures how much revenue you retain and grow from your existing customer base over a period, typically 12 months. The formula: starting MRR plus expansion minus contraction minus churn, divided by starting MRR.¹ An NRR of 110% means your existing customers are worth 10% more this year than last year, before counting any new sales.

NRR matters because it determines whether your business can grow from existing customers alone. Companies with 120%+ NRR can theoretically stop selling to new customers and still grow. Companies with 90% NRR need to acquire 10% of their revenue base in new customers just to stay flat. That's a fundamentally different business.

Investors have caught on. NRR has become one of the top metrics public SaaS companies report and private ones optimize around. But how to actually improve it is where most advice gets shallow.

Why Most NRR Advice Focuses on the Wrong Lever #

The standard NRR playbook centers on expansion revenue: implement usage-based pricing, add premium tiers, drive seat expansion, cross-sell adjacent products. This advice isn't wrong. Expansion matters. But it's incomplete in a way that costs companies significant NRR points.

NRR has two sides. Expansion lifts the number. Churn and contraction pull it down. Most SaaS companies optimize for one side and accept the other as a cost of business.

Here's what that costs: Bain & Company found that a 5% increase in customer retention produces a 25-95% increase in profits.³ The range is wide because the impact compounds. Retained customers expand over time, cost less to serve, and refer others. Every percentage point of churn you eliminate delivers returns for years.

If your gross churn is 15% annually and your expansion is 20%, your NRR is 105%. You could increase expansion to 25% for a 110% NRR. Or you could reduce gross churn from 15% to 10% for the same 110% NRR. The second path is more durable because retained customers continue to generate expansion revenue in future periods. Reducing churn once pays dividends repeatedly.

What Actually Drives Churn and Contraction in B2B SaaS? #

Gainsight's research found that 67% of SaaS churn correlates with low product adoption rather than product quality, pricing, or competitive alternatives.² The customers who leave aren't usually unhappy with your product's quality. They're not using enough of it to justify the cost.

Low adoption doesn't mean the product is bad. It means the product doesn't fit the customer's specific workflow well enough to become part of their daily operations. A CMMS platform that serves roofing companies, hospitals, and manufacturing plants can't serve all of them equally well with one interface. The hospital's compliance workflow looks nothing like the roofing company's job scheduling process.

When the CFO runs the next cost-optimization cycle, the tools with low daily usage get cut first. It doesn't matter that your product has 200 features if the customer's team only uses 8 of them and the other 192 don't match how they actually work.

Contraction follows the same pattern. Customers downgrade when they realize they're paying for capacity they don't use. If half the licensed seats in an account log in less than twice a month, that account will contract at renewal. Not because they dislike the product, but because the product only fits half the team's workflows.

How Workflow Fit Directly Impacts NRR #

The connection between workflow fit and NRR runs through adoption. When the product matches how each specific user actually works, adoption increases. When adoption increases, the account becomes harder to cut or downgrade.

In a first-party deployment on a YC-backed CMMS platform, customers were given the ability to build their own workflow-specific apps on top of the existing product. A roofing company built a job margin calculator. A hospital built an inspection workflow with compliance sign-offs. A fleet operator built a maintenance scheduler around their specific routes and parts inventory.

These weren't generic features. They were tools built by each customer to match their own operational reality. The results: 90.8% of users adopted at least one custom workflow app. 89% were still using them 30 days later.⁴

That level of adoption changes the NRR equation entirely. Accounts where users open the product every day because it fits their specific workflow don't churn during cost-optimization reviews. They don't downgrade because "we're not using it enough." They become the accounts that expand because more teams see the value and want access.

Six Steps to Improve NRR Through Workflow Fit #

Step 1: Segment your churn data by adoption, not by revenue #

Most SaaS companies analyze churn by account size, industry, or contract type. Start segmenting by daily active usage per user role. Accounts where fewer than 40% of licensed seats log in weekly are at elevated churn risk regardless of account size. This segmentation tells you where the workflow fit gap is widest.

Step 2: Map the workarounds in low-adoption accounts #

Talk to the users in your lowest-adoption segments. Not the champion who renewed the contract, but the field workers, operators, and coordinators whose seats are underutilized. Ask one question: "What does your typical workday look like, and which parts happen outside our platform?" Every spreadsheet, manual process, or shadow tool represents a workflow your product doesn't serve.

Step 3: Quantify the customization backlog #

Count the feature requests in your backlog that follow the pattern "I need the product to work slightly differently for my specific context." This category represents the per-customer customization demand that your roadmap will never fully address. The size of this backlog is a direct proxy for your NRR risk from workflow mismatch.

Step 4: Evaluate whether customization can be additive #

The trap most SaaS companies fall into is adding global configuration options that change the core product for everyone. Additive customization gives each customer their own layer without affecting anyone else's experience. Per-customer workflow apps, marketplace-based app distribution, and CS-deployed custom solutions all achieve this without touching the core product.

Step 5: Instrument adoption at the workflow level, not the feature level #

Feature adoption metrics ("X% of users clicked this button") don't tell you whether a customer's daily workflow is served. Instrument whether each user role has at least one daily-use workflow inside your product. Track workflow completion rates, not just page views. The metric that predicts NRR is "does this person do their actual job inside our product?" not "did this person see our newest feature?"

Step 6: Make your CS team builders, not escalation managers #

Customer success teams who can ship custom workflow solutions same-day, without filing engineering tickets, directly close the gap between what the product does and what each customer needs. This changes the CS conversation from "I'll file a feature request" to "let me build that for you right now." The NRR impact comes from solving problems before they become churn conversations.

Footnotes #

1. Bessemer Venture Partners. "Cloud Index: NRR Benchmarks for B2B SaaS." 2024. ↩ ↩² ↩³

2. Gainsight. "Why Customers Churn: The Adoption Connection." 2024. ↩ ↩²

3. Bain & Company. "The Economics of Customer Loyalty." Harvard Business Review. ↩ ↩²

4. Gigacatalyst first-party deployment data. 946 users, 670+ microapps, 90.8% adoption, 89% day-30 retention, 2025. ↩ ↩²