.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.
What Is Expansion Revenue and Why Is It Critical to Your SaaS Growth Strategy
A SaaS company can report strong bookings and still build a fragile growth model. When most growth depends on winning entirely new accounts, the company must recreate demand every quarter, carry high acquisition costs, and hope that pipeline conversion remains steady. Expansion revenue answers a more durable question: are customers who already chose the product finding enough additional value to spend more over time?
That question reaches beyond customer success. It tests whether the package fits the buyer, whether the price meter rises with use, whether product launches create clear reasons to buy more, and whether sales coverage is focused on accounts with real headroom. It also separates revenue created by deeper adoption from revenue created by one-time price increases. Monetizely's position is clear: expansion revenue should be the main diagnostic for a SaaS pricing metric because it shows whether the way a company charges rises alongside realized customer value. Net revenue retention remains indispensable, but it is too netted to direct pricing on its own.
Expansion revenue is the additional recurring revenue generated from customers that were already active at the start of a measurement period. It includes more seats, more usage, added modules, a move to a higher plan, or a contract price increase. It excludes revenue from new logos.
The unit should match the company's revenue model. A seat-based vendor will usually track expansion ARR. A consumption business may track incremental recurring revenue from the same customer cohort, or annualized consumption, provided it uses one consistent method. Snowflake, for example, measures product revenue from a continuing customer cohort and reported a 125% net revenue retention rate as of January 31, 2026.
The key discipline is to track expansion separately from losses. A customer that adds $100,000 of ARR but later removes $40,000 of scope generated $100,000 of gross expansion and $60,000 of net change. Both facts matter. The first reveals the product's ability to create new value; the second reveals whether the account is keeping that value.
The following exhibit shows the relationship among expansion revenue, gross retention, and net retention.
| Measure | Formula | Worked example: starting cohort ARR = $10.0M | What it tells management |
|---|---|---|---|
| Gross expansion ARR | Upsells + cross-sells + added use + price lift | $1.8M | How much new recurring value existing customers created |
| Expansion rate | Gross expansion ARR ÷ starting cohort ARR | $1.8M ÷ $10.0M = 18% | Whether the installed base is growing before losses |
| Gross retention rate | (Starting ARR - contraction - churn) ÷ starting ARR | ($10.0M - $0.4M - $0.2M) ÷ $10.0M = 94% | How much of the starting base stayed before expansion |
| Net revenue retention | (Starting ARR + expansion - contraction - churn) ÷ starting ARR | ($10.0M + $1.8M - $0.4M - $0.2M) ÷ $10.0M = 112% | The net economic performance of the customer cohort |
| Relationship between rates | NRR = GRR + expansion rate | 94% + 18% = 112% | Why NRR alone cannot show the source of account growth |
The exhibit makes the management issue plain: a 112% NRR can come from exceptional adoption with moderate churn, or from modest adoption paired with nearly perfect retention. Those cases call for different pricing and product decisions.
For this reason, we recommend reporting three forms of expansion separately:
A company that blends these movements into one number cannot tell whether customers are buying more software, paying more for the same software, or merely absorbing an annual increase.
Public SaaS disclosures show why NRR is a useful starting point but an incomplete pricing measure. CrowdStrike defines dollar-based net retention as the ARR of the same subscription-customer group after renewals, expansion, contraction, and churn, excluding new customers. Its reported NRR was 115% as of January 31, 2026. That number confirms that the installed base grew on balance. It does not reveal how much gross expansion was required to overcome contractions and churn.
Workiva provides a clearer example of the value of a paired view. As of December 31, 2025, it reported 97.2% gross retention and 112.8% net retention. The implied difference was 15.6 percentage points of expansion from the existing base. Workiva also states that its net retention includes upselling, cross-selling, pricing changes, and periodic price increases in multi-year renewals.
Public disclosures also establish useful reference ranges. The table below is not a universal benchmark. It is a practical set of public-company reference points that shows the distance between a shrinking base, a stable base, and an installed base that funds material growth.
| Reported NRR range | What the range usually indicates | Recent B2B SaaS reference points |
|---|---|---|
| Below 100% | Existing-customer losses exceed expansion. New-logo growth must cover the shortfall. | Asana reported 96% dollar-based net retention as of January 31, 2026. (sec.gov) |
| 100% to 111% | The base is holding or growing modestly, but expansion is unlikely to create major operating leverage on its own. | monday.com reported 110% net dollar retention for the three months ended December 31, 2025. (sec.gov) |
| 112% to 119% | Expansion is a meaningful contributor to growth and can support investment in targeted account development. | Workiva reported 112.8% as of December 31, 2025; Confluent reported 114% as of December 31, 2025; CrowdStrike reported 115% as of January 31, 2026. (sec.gov) |
| 120% and above | Existing customers are adding substantial new use cases, capacity, products, or organizational reach. | Snowflake reported 125% as of January 31, 2026. (sec.gov) |
The pattern matters more than the headline. A company at 115% NRR with 99% gross retention and 16% expansion has a different operating model from one at 115% NRR with 90% gross retention and 25% expansion. The former has a durable base and moderate headroom. The latter may have an attractive product but a retention problem that will eventually limit growth.
Confluent's disclosure shows another important point. It reported 114% dollar-based NRR as of December 31, 2025, while moving more of its business toward consumption-based cloud offerings. Its filings describe NRR as including retained, expanded, contracted, and attrited customer value, and note that the revenue mix shift can affect the measure. A pricing team should therefore inspect the underlying customer movements before treating a change in NRR as evidence that a new meter succeeded or failed.
Expansion revenue is not created by a dashboard. It is created when the product, package, and meter give a customer a sensible way to spend more as its needs increase.
Monetizely's 5-Step Pricing Framework places that decision in sequence: goals and segmentation; packaging; choosing the pricing metric; finding price points; and operationalizing the model. The order matters. A company first decides which buyers it serves and what each group needs. It then builds offers for those groups, chooses what customers will pay for, sets the rate, and makes billing, quoting, and reporting work in practice. As discussed in Monetizing Agentic AI, the pricing metric is the hinge between a product's value and its revenue model.^1
Step 3, choosing the pricing metric, deserves particular attention. A price metric should rise when customers receive more of the value that caused them to buy. When that link is weak, expansion becomes a sales event that requires negotiation, discounting, and executive escalation. When the link is strong, the customer can expand through normal adoption.
The following comparison shows what a primary meter should capture.
| SaaS model | Primary meter that can support natural expansion | Customer event that increases value | Pricing implication |
|---|---|---|---|
| Collaborative work software | Active users or managed teams | A department adopts the product, then rolls it out to other teams | Per-seat pricing works when each additional participant receives direct value |
| Cybersecurity platform | Protected endpoints, identities, or cloud assets | The customer secures more devices, adds workloads, or deploys new protection modules | A base platform charge can support the account, but the main meter should scale with protected scope |
| Data platform | Compute, storage, data transfer, workloads, or committed capacity | The customer moves more applications and data workloads to the platform | Consumption can align revenue closely to realized technical use |
| Compliance software | Covered entities, filings, controls, or regulated workflows | The customer expands into new jurisdictions, business units, or reporting obligations | A meter tied to the compliance burden is stronger than a generic user count |
The lesson is not that every SaaS company should move to usage pricing. Seat pricing is powerful when the user is the unit of value. Consumption is powerful when consumption is the unit of value. The central requirement is more demanding: every company needs one named primary meter that captures the most repeatable form of customer growth.
The public examples reflect this logic. CrowdStrike identifies endpoints and cloud modules as key drivers of subscription revenue. Snowflake derives product revenue from customer consumption of compute, storage, and data-transfer resources. monday.com attributes expansion to customers adding users and products as adoption moves across departments. Each company has more than one route to account growth, but each has a clear way for a larger customer footprint to produce more revenue.
A company-wide expansion rate can flatter a weak strategy. Suppose an enterprise cohort of 50 accounts starts with $8 million in ARR and generates $2 million of expansion, while 4,000 smaller accounts begin with $12 million and generate only $240,000. The blended expansion rate is 11.2%, yet the two segments require different commercial models.
The enterprise cohort may justify account teams, modular add-ons, executive business reviews, and planned cross-sell motions. The smaller cohort may require simpler packaging, in-product upgrade paths, and a meter that customers can understand without procurement support. Treating both groups as one installed base produces an average that nobody can act on.
monday.com provides a public example of why segmentation matters. As of December 31, 2025, its overall net dollar retention was 110%, while customers with more than $50,000 in ARR and more than $100,000 in ARR each reported 116%. The higher figure does not mean that large accounts are inherently better. It means the company can see that larger accounts have a distinct expansion pattern and should be managed accordingly.
Five recurring reporting errors turn a useful metric into a false comfort
Teams usually misread expansion revenue before they misprice the product. The most common errors are straightforward, but each can send management toward the wrong decision.
Treating NRR as gross expansion. NRR nets expansion against contraction and churn. A team that sees 110% NRR cannot know whether its problem is weak adoption, poor retention, or both.
Counting new-customer revenue as expansion. Revenue from a new subsidiary, acquired company, or newly created account can inflate the number unless account-family rules are set before reporting begins.
Calling price increases product-led growth. A 7% renewal uplift and a 7% increase in protected endpoints are economically different. Both belong in total expansion, but they should never sit in the same reporting line.
Using bookings in one quarter and recognized revenue in the next. A mixed basis can make a pricing change look successful simply because contract timing changed.
Measuring only the total company average. Expansion differs sharply by segment, product, tenure, industry, and sales motion. A blended number can hide a failing customer group until renewal pressure becomes visible.
Choosing a meter because billing can support it today. Operational feasibility matters, but an easy meter that does not track value will cap long-term expansion. Billing systems should enable the strategy, not define it.
The discipline belongs directly in Step 3 of Monetizely's 5-Step Pricing Framework. Before setting a rate, leadership should ask a more fundamental question: when a customer doubles the value received, what measurable change should cause revenue to rise?
One executive dashboard keeps price, product, and customer success accountable
Expansion revenue becomes useful when it creates shared accountability rather than another finance report. The dashboard should show movements by cohort and by source, with product and commercial owners looking at the same numbers.
| Dashboard line | Required cut | Executive question it answers | Primary owner |
|---|---|---|---|
| Gross expansion rate | Segment, product, customer tenure | Are existing customers finding additional reasons to spend? | Chief Product Officer and Chief Revenue Officer |
| Adoption expansion | Seats, usage, assets, workflows, or modules | Is the primary meter rising through real product use? | Product and Customer Success |
| Product expansion | Add-on, premium tier, cross-sell | Which launches create a credible next purchase? | Product Marketing and Sales |
| Price expansion | Renewal, contract amendment, migration | How much growth came from rate changes rather than broader adoption? | Pricing and Finance |
| Contraction and churn | Same cohort cuts | What value is failing to stick, and where? | Customer Success and Product |
A shared dashboard changes the operating conversation. Product leaders can see whether feature adoption creates paid growth. Sales leaders can distinguish true cross-sell demand from discount-supported renewals. Finance can forecast existing-customer revenue with more precision than a single NRR line allows.
Growth leaders should manage expansion as a designed system
Set a three-year growth plan that separates new-logo ARR, adoption expansion, product expansion, and price expansion. A single ARR target does not reveal which engine must do the work.
Allocate customer-success capacity by expansion potential, not account count. A $500,000 account with three credible next use cases deserves a different service model from a low-spend account with no realistic path to broader adoption.
Require every major product investment to state its expansion mechanism before funding. The business case should identify the target cohort, the paid event, the expected time to adoption, and the primary meter affected.
Make account-family rules a finance policy rather than a sales judgment. Clear rules for subsidiaries, acquisitions, and reorganizations prevent revenue reporting from changing with quota pressure.
Review expansion sources at the executive level each quarter. If price expansion becomes the dominant source while adoption expansion falls, leadership should treat that as an early warning about product value and future renewals.
Sources
- https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
- Snowflake, Fiscal 2026 Form 10-K, year ended January 31, 2026. (sec.gov)
- CrowdStrike, Fiscal 2026 Form 10-K, year ended January 31, 2026. (sec.gov)
- monday.com, Fiscal 2025 Annual Report on Form 20-F, year ended December 31, 2025. (sec.gov)
- Workiva, Fiscal 2025 Form 10-K, year ended December 31, 2025. (sec.gov)
- Confluent, Fiscal 2025 Form 10-K, year ended December 31, 2025. (sec.gov)