.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Understanding Gross Revenue Retention Rate a Critical SaaS Metric for Sustainable Growth
A SaaS company can report strong growth while quietly weakening at its core. New bookings may rise, large accounts may buy more products, and net revenue retention may remain above 100%. Yet the installed base can still be shrinking beneath the surface as customers cancel, downgrade, reduce seats, or scale back usage.
Gross Revenue Retention Rate, or GRR, answers the more demanding question: how much recurring revenue would remain if existing customers did not expand at all? That question matters because expansion is optional. Renewal is not. A business that needs upsells to replace avoidable losses is running faster simply to hold its ground.
Monetizely's position is clear: GRR should be the gate that every pricing decision must clear before a company pursues expansion through packaging, cross-sell, or higher usage. Sustainable SaaS growth starts with a pricing model customers will renew at their original commitment.
Net retention can conceal the revenue customers are quietly taking away
Net Revenue Retention Rate, or NRR, includes expansion revenue from the existing customer base. That makes it valuable for assessing account growth. It also makes NRR a forgiving metric.
Consider a company that begins the year with $2 million in annual recurring revenue, or ARR, from a customer cohort. It loses $200,000 when customers churn and another $80,000 through seat reductions. The remaining customers then buy $250,000 of additional products.
NRR would be 98.5%. The company would appear close to retaining all of its starting revenue. GRR, however, would be 86%, revealing that the company lost 14 cents of every recurring dollar before expansion entered the picture.
GRR therefore isolates the durability of the original customer commitment. It asks whether the original package, meter, price, and customer fit still hold at renewal. Logo retention cannot answer that question. A $200,000 account that renews at $50,000 counts as retained in a logo metric, while GRR correctly records the $150,000 reduction.
A common calculation exposes the difference between resilience and expansion
For management purposes, GRR should be measured on a consistent 12-month customer cohort and capped at 100%. The numerator retains only recurring revenue from the opening cohort after churn and contraction. New customers and expansion revenue do not belong in the calculation.
The table below shows the logic using the $2 million cohort described above.
The difference between 86.0% GRR and 98.5% NRR is not a reporting nuance. It is the difference between a product that retains its initial value and one whose expansion motion is covering for a renewal problem.
Companies must also define their treatment of price increases, migrations, acquisitions, credits, and usage changes before publishing the rate. A customer that accepts a 10% price rise without changing product scope should not make a weak renewal base look healthier than it is. The internal rule should be simple: GRR must show whether the value originally sold is still being retained.
Public disclosures place durable retention in a demanding range
There is no universal GRR benchmark because public companies calculate the metric differently. Some include revenue contraction, while others count only full customer churn. Even so, public disclosures provide useful reference bands when operators compare like with like.
The following exhibit places four B2B software companies into practical retention bands using their latest disclosed rates as of September 7, 2026.
Yext’s disclosure is especially instructive. Its total GRR was 88% at April 30, 2026, but the rate was 71% for its sub-$50,000 ARR cohort and 89% for customers above that threshold. The gap shows why a blended company rate is not enough: one segment can be structurally fragile while another remains sound.
Weave reported 89% GRR at December 31, 2025, Vertex reported 94% at December 31, 2025, and ServiceTitan reported more than 95% across fiscal 2024 through fiscal 2026. Those rates are not directly interchangeable because their definitions differ. They do establish a useful operating standard: once a company falls below 90% on a strict definition that includes contraction, it should treat pricing and product fit as an executive issue rather than a customer-success issue alone.
Pricing should respond to the pattern between GRR and NRR
GRR does not tell leaders to cut price whenever retention slips. Price cuts may preserve a renewal that was never healthy, while reducing the resources available to serve the account. The metric instead identifies where the commercial design has broken: the wrong customers were acquired, the package oversold, the meter created anxiety, or the price exceeded the value delivered.
The relationship between GRR and NRR helps identify the appropriate response.
A 94% GRR and 104% NRR business has a different problem from an 84% GRR and 104% NRR business. The first has a solid base and modest expansion. The second has an account-growth engine that may be masking broad dissatisfaction, excessive discounting, or an acquisition strategy that brings in poor-fit customers.
Monetizely's position is that GRR should set the order of operations. Management should first protect the recurring revenue already under contract, then use package upgrades, cross-sell, and usage growth to build NRR. Reversing that order produces a familiar failure mode: the company celebrates account expansion while customer cohorts quietly become less valuable every year.
The five pricing decisions determine whether revenue survives renewal
The Monetizely 5-Step Pricing Framework treats pricing as a sequence of linked business decisions: goals and segmentation, packaging, pricing metric, price points, and operationalization. The sequence matters because a retention problem rarely begins with the number on the order form.
Goals and segmentation come first because a company cannot assess GRR properly with one blended customer base. A software vendor selling to a 20-person professional-services firm and a 2,000-person enterprise should not assume that both customers buy for the same reason, use the same features, or tolerate the same contract structure.
Packaging comes next. Customers often downgrade because they were sold features they did not use, or because the package forces them to buy far more than the job requires. A good package makes the renewal decision easier by matching the offer to a defined customer segment. A poor package creates shelfware, discount pressure, and eventual contraction.
The third step, choosing the pricing metric, has the closest connection to GRR. The meter determines what a customer feels they are committing to. A seat-based metric can support high GRR when value is tied to regular user access. A consumption metric can damage GRR when customers cannot predict their bill or cannot connect usage to value. Conversely, a flat subscription can weaken economics when a small group of intensive users consumes far more service than the price supports.
Price points follow only after the company has established who it serves, what each segment receives, and what it charges for. The rate must fit the value delivered and the buyer's willingness to pay. Raising the number before resolving a package or meter problem often accelerates churn in the very cohorts management needs to understand.
Operationalization completes the system. Finance, product, sales, customer success, and billing must use the same package definitions, account segments, and revenue data. Otherwise, GRR becomes an annual spreadsheet exercise rather than a management measure.
| Step in the 5-Step Pricing Framework | Question management must answer | GRR failure if the answer is weak |
|---|---|---|
| Goals and segmentation | Which customers must we retain, and what job are they hiring us to do? | Blended rates conceal weak segments |
| Packaging | What offer does each customer segment actually need? | Customers renew less, downgrade, or carry unused features |
| Pricing metric | What are customers paying for, and does the meter track their value? | Bills feel unfair, unpredictable, or disconnected from results |
| Price points | What commitment can each segment justify at renewal? | Discounts rise, contraction increases, and renewals become contentious |
| Operationalization | Can teams quote, bill, measure, and explain the offer consistently? | Billing disputes and poor data obscure the real retention problem |
GRR is therefore not merely a customer-success KPI. It is the proof point for the third step of pricing design. A pricing metric earns its place only when the customers who accepted it at purchase continue to accept it at renewal.
Operators usually make predictable mistakes with this metric:
Treating GRR as a lagging scorecard. By the time an annual GRR number falls, the product, pricing, and customer-fit decisions that caused the decline may be 12 to 18 months old.
Reporting one blended rate. A company with 95% GRR in enterprise accounts and 72% GRR in smaller accounts does not have an 84% retention problem. It has two different businesses with different pricing needs.
Allowing expansion to influence the gross metric. Expansion belongs in NRR. Including it in GRR makes the measure unable to identify the revenue at risk.
Comparing headline rates without comparing definitions. Vertex includes downgrades and reduced usage in GRR, while Weave and ServiceTitan use more limited definitions centered on terminated customers or churn. A rate is only useful when its construction is clear.
Treating every downgrade as a price objection. A downgrade can stem from poor onboarding, missing workflow fit, weak product adoption, a bad initial package, or a genuine budget constraint. Discounting before identifying the cause gives away revenue without fixing the problem.
Using GRR only for customer-success compensation. Product managers, sales leaders, and pricing teams all influence whether the original deal remains worth renewing. Accountability should match that reality.
Strong GRR management starts with a monthly cohort view and an executive review every quarter. The report should show the rate by customer segment, package, pricing metric, tenure, contract size, and sales channel. A company should also show the absolute ARR lost, since a one-point decline on a $500 million base is not the same operating event as a one-point decline on a $20 million base.
The review should begin with the revenue that left, not with the percentage. Leaders need to inspect the largest contractions, the fastest-declining cohort, and the package with the weakest first-renewal performance. That creates a direct link between customer evidence and the next pricing decision.
Yext’s split between sub-$50,000 and larger customers demonstrates why this discipline matters. The overall figure did not reveal the full issue; the segment view did. A useful GRR system makes that type of gap visible early enough to change the offer before it becomes embedded in the installed base.
Leaders should make retained revenue the test of commercial quality
Put a strict GRR floor into annual planning. Fund growth investments only after management has stated the minimum retained revenue rate required for each major segment.
Make first renewal a formal product-and-pricing milestone. Review the first 12-month renewal cohort separately from mature accounts, because early contraction exposes overselling and weak onboarding faster than an all-customer average.
Require every major pricing change to include a retained-revenue forecast. The proposal should show which cohorts may renew more readily, which may contract, and what evidence supports the expected result.
Use GRR to decide where not to scale. If a segment persistently fails to retain its original commitment, pause acquisition spending in that segment until the offer has been redesigned.
Give the executive team one shared retention record. Product, sales, finance, and customer success should work from the same cohort definitions and ARR movements so that commercial debates center on evidence rather than competing dashboards.
Footnotes
- https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
- Yext, Form 10-K for the fiscal year ended April 30, 2026. (sec.gov)
- Weave Communications, Form 10-K for the year ended December 31, 2025. (sec.gov)
- Vertex, Form 10-K for the year ended December 31, 2025. (sec.gov)
- ServiceTitan, Fiscal Year 2026 Annual Report and proxy filing, filed May 5, 2026. (sec.gov)