How to Improve Net Revenue Retention

In 2019, a growth equity investor named David Skok published a piece of analysis that reframed how the most sophisticated SaaS investors in the world thought about company valuation.

He was not writing about revenue growth, not about gross margin, not about CAC payback period or burn multiple or any of the standard metrics that dominate SaaS board decks and fundraising conversations. He was writing about a single number that, in his analysis of hundreds of SaaS investments, predicted long-term company value more reliably than any other metric in the stack.

Specifically, he showed that SaaS companies with NRR above 120% were valued at multiples two to three times higher than comparable companies with NRR below 100%, holding revenue growth rate roughly constant. The revenue growth was the same, the business model was the same. The market was the same, the difference in valuation was explained almost entirely by one variable: whether the existing customer base was expanding faster than it was contracting.

The logic underneath that finding is straightforward once you see it clearly. A company with 110% NRR does not need to acquire a single new customer to grow its revenue. Its existing customer base is doing the growing for it. Every dollar of new customer acquisition goes on top of a base that is already expanding. The compounding is structural, it is baked into the existing relationships rather than dependent on the continuous performance of acquisition channels.

A company with 90% NRR is running a business where every dollar of new customer acquisition is partially consumed by the revenue eroding from the existing base. The treadmill runs faster, the burn rate increases. The growth story becomes a story about replacing what is being lost rather than compounding what already exists. Investors price that difference. Dramatically, the valuation gap between 90% NRR and 110% NRR is not a rounding error. It is the difference between a business that sells at four times revenue and one that sells at twelve times revenue.

That is not a small number to leave on the table because nobody engineered the expansion mechanics deliberately. NRR is not a metric you monitor, it is a metric you engineer. Most founders treat NRR as an outcome, a number that reflects how well their product retained and expanded customers over a given period. That framing is accurate but incomplete. NRR is an outcome of specific, buildable, repeatable mechanics that exist at the product level, the pricing level, and the customer relationship level simultaneously. When those mechanics are engineered deliberately, NRR climbs. When they are left to chance, NRR reflects whatever the market decided your product was worth to them without any systematic effort to capture more of that value over time.

The comfortable assumption underneath most early-stage SaaS NRR conversations is that expansion will happen naturally as customers grow and need more. Sometimes it does. More often it does not, because natural expansion requires the customer to proactively seek out a higher tier, a larger seat count, or an additional product line without being shown a clear reason to do so at the right moment. Customers who are happy with their current usage level do not spontaneously upgrade. They maintain their current relationship with the product indefinitely until something prompts a change.

That prompt is what NRR engineering provides, it is the deliberate, systematic set of mechanisms that create the right expansion opportunity at the right moment in the customer lifecycle, anchored to demonstrated value rather than sales pressure, and built into the product and pricing architecture rather than dependent on the initiative of individual customer success conversations.

Engineering NRR past 110% does not require a large CS team, it does not require aggressive upselling or manufactured urgency. It requires three specific expansion plays, each targeting a different dimension of customer value, each buildable in a single sprint, and each compounding with the others once they are live simultaneously.

Measuring NRR Without Understanding What Moves It

Most founders who track NRR understand the formula. Monthly recurring revenue at the end of the period divided by MRR at the beginning of the period from the same customer cohort, expressed as a percentage. Above 100% means expansion exceeded contraction. Below 100% means contraction exceeded expansion.

What most founders do not understand is the decomposition underneath that number. NRR is the net result of four distinct forces pulling in opposite directions simultaneously. Expansion revenue from existing customers upgrading or buying more. Contraction revenue from existing customers downgrading. Churn revenue from customers who cancelled entirely. And reactivation revenue from customers who cancelled and came back.

Most NRR improvement conversations focus on reducing churn because churn is the most visible and emotionally salient of the four forces. A cancellation notification arrives in the inbox. A downgrade shows up in the billing report. The pain is immediate and attributable. Expansion, by contrast, is silent when it is absent. No notification fires when a customer who could have upgraded did not. No alert fires when a customer who could have added five seats added none. The absence of expansion does not hurt in the same way that churn hurts even though its financial impact over a twelve-month period is equally significant.

Snowflake understood this asymmetry early and built their entire revenue architecture around it. Their NRR has consistently sat above 130% for multiple consecutive years, making it one of the most documented examples of deliberate expansion engineering in enterprise SaaS. The mechanism is their consumption-based pricing model. Every customer who uses Snowflake more generates more revenue automatically without a sales conversation, without an upgrade prompt, and without a renewal negotiation. The expansion is structural. It is built into the pricing architecture rather than dependent on the customer success team identifying upgrade opportunities and manually pursuing them.

Most SaaS products cannot immediately adopt consumption-based pricing. But every SaaS product can adopt the principle underneath it. Design the commercial relationship so that as the customer succeeds more with the product, the revenue they generate grows proportionally and automatically rather than staying flat until someone initiates an upgrade conversation.

The Three Expansion Plays That Engineer NRR Past 110%

Each of the three plays targets a different expansion lever, they are not mutually exclusive. The founders who push NRR above 120% are almost always running all three simultaneously.

The first play is usage-triggered seat expansion. This play applies to any product where the value increases as more team members use it. The mechanism is simple. Define the usage threshold at which a single-user or small-team account is extracting enough value from the product that expanding to additional seats would be immediately justified by the incremental value delivered. Then build an in-product prompt that fires automatically when the account crosses that threshold, showing the primary user specifically how many times in the last thirty days they have shared work with, mentioned, or collaborated with someone who does not have a seat.

The prompt is not a sales message. It is a usage reflection, it shows the customer the collaboration activity they have already generated and calculates what a seat for each frequent collaborator would cost relative to the value of the collaboration already happening. The customer is not being asked to imagine future value. They are being shown documented present value and offered a simple way to formalise it.

Asana built this mechanic into their product growth motion during their scale phase and attributed a significant proportion of their seat expansion revenue to in-product prompts that fired based on collaboration frequency rather than calendar-based outreach. The seat expansion felt natural to the customer because it was anchored to behaviour they had already demonstrated rather than a prediction about future usage they might generate.

The second play is milestone-triggered tier upgrade. Every SaaS product has a natural ceiling in each pricing tier where a customer’s usage or outcomes approach the limit of what that tier offers. Most products handle this by waiting for the customer to hit the limit, triggering a hard paywall, and hoping the friction of the block motivates an upgrade rather than a cancellation.

The alternative is a soft milestone prompt that fires before the limit is reached. When a customer is at seventy percent of their current tier’s capacity, an in-product notification appears that shows them their usage trajectory, projects when they will reach the ceiling based on their current growth rate, and presents the next tier as a proactive upgrade with a specific benefit statement rather than a reactive response to a block they did not anticipate.

The timing makes all the difference. A customer who upgrades at seventy percent capacity is upgrading from a position of momentum. They are growing, the upgrade feels like a natural continuation of success. A customer who hits the hard limit at one hundred percent is upgrading from a position of friction. The upgrade feels like a tax on their growth. The conversion rate on momentum-based upgrade prompts is consistently higher than friction-based paywall conversions because the emotional context of the decision is fundamentally different.

The third play is outcome-anchored cross-sell sequencing. This play applies to products that have multiple product lines, add-ons, or complementary offerings. The standard cross-sell motion is time-based. A customer has been on the platform for ninety days, so a cross-sell email goes out. That sequencing ignores the most important variable in cross-sell conversion timing. The customer’s demonstrated outcome with the primary product.

A customer who has achieved a specific, measurable outcome with the core product is in the highest possible state of receptivity to a cross-sell offer because their confidence in the vendor is at its peak. They have evidence that the product works. They have a relationship built on delivered value. A cross-sell at that moment is not a sales interruption. It is a logical extension of a relationship that has already proven its worth.

Define the outcome signal for your primary product. The moment a customer achieves it, trigger the cross-sell sequence with a message that references the specific outcome they just achieved and positions the additional product as the natural next step to compound that result further. HubSpot runs this play with exceptional precision. The moment a HubSpot Marketing customer reaches a specific lead generation milestone, the Sales Hub cross-sell sequence triggers automatically, framing the Sales Hub as the logical tool to convert the leads the Marketing Hub just generated. The cross-sell is earned by the primary product’s success rather than initiated by the sales team’s calendar.

What 110% NRR Does to the Business Over 36 Months

The compounding arithmetic of NRR above 100% is worth making explicit because it is the clearest possible argument for treating NRR as an engineering priority rather than a monitoring metric.

Consider two companies. Both start January with one million dollars in annual recurring revenue. Both grow their new customer ARR by thirty percent per year. Company A has 95% NRR. Company B has 115% NRR.

After twelve months, Company A has one million three hundred thousand dollars in ARR from new customers minus fifty thousand dollars of net contraction from the existing base, producing approximately one million two hundred and fifty thousand dollars in total ARR. Company B has one million three hundred thousand dollars in ARR from new customers plus one hundred and fifty thousand dollars of net expansion from the existing base, producing approximately one million four hundred and fifty thousand dollars in total ARR.

After thirty-six months the gap is not a rounding error. It is a fundamental difference in business scale, valuation multiple, and financial trajectory. Company B’s existing customer base is effectively self-funding a portion of its growth without requiring additional acquisition spend. Company A’s existing customer base is consuming a portion of its growth, requiring acquisition to run faster simply to maintain pace.

OpenView Partners published their SaaS benchmarks in 2023 showing that companies with NRR above 110% commanded revenue multiples averaging 11.4 times trailing twelve-month revenue at exit or fundraising. Companies with NRR between 90% and 100% commanded multiples averaging 4.2 times. The same revenue. The same growth rate. A 7.2 times multiple difference explained by one metric and the expansion mechanics that drive it.

That multiple difference is not theoretical, it is the documented outcome of engineering the three expansion plays above versus leaving expansion to chance in a product that retains but does not grow its existing revenue base systematically.

Build the Expansion Stack Before Your Next Fundraise or Exit Conversation

NRR improvement is not a twelve-month project. The three plays above can each be designed, built, and shipped in a single sprint. The compounding starts the day the first one goes live.

Here is the build sequence. Sprint one: instrument the usage data required to fire the seat expansion and milestone upgrade prompts. If you cannot see collaboration frequency and tier utilisation percentage in your analytics today, that instrumentation is the sprint priority. Sprint two: build the seat expansion prompt at the seventy percent collaboration threshold and the tier upgrade prompt at the seventy percent capacity threshold. Measure the in-product conversion rate on both prompts for thirty days before optimising. Sprint three: define your primary product outcome signal and build the cross-sell trigger that fires when a customer achieves it. Connect it to the appropriate sequence in your email automation tool.

A practical AI prompt to design all three plays for your specific product: open Claude and paste this: “My SaaS product does [describe your product]. My current pricing structure is [describe your tiers and limits]. My primary product outcome, the thing my best customers achieve that demonstrates the product is working, is [describe the outcome]. Design all three NRR expansion plays for my product. For the seat expansion play, define the collaboration threshold and write the in-product prompt copy. For the milestone upgrade play, define the capacity threshold and write the upgrade prompt copy. For the cross-sell play, define the outcome signal trigger and write the first message in the cross-sell sequence. Keep every piece of copy under 75 words and write it as if it is coming from the product, not from a sales team.” Use the output as your first draft for all three plays and refine based on your specific product voice before shipping.

The Startup Growth OS treats NRR as the metric that determines whether your growth compounds or grinds. Acquisition brings customers in. Activation converts them into active users. Retention keeps them paying. But NRR determines whether the revenue those customers represent grows over time or stays flat until something goes wrong. A business with 110% NRR is a fundamentally different financial asset than a business with 95% NRR. Not because the product is better. Because the expansion mechanics were engineered deliberately rather than left to customer initiative.

Engineer the expansion. Build the stack. Let the multiple follow.

Sam Femi
Seamless Life HQ

P.S. The valuation multiple gap between 95% NRR and 115% NRR is not built in a fundraising conversation. It is built in the product sprints that happen twelve to twenty-four months before that conversation. Those sprints are happening today whether you are engineering them deliberately or not. Take the Free Startup Growth Assessment