Expansion Revenue: How to Find It, Forecast It, and Capture It (With a Customer Health Score)
Leah Clapper

Expansion revenue is the additional recurring revenue a company earns from existing customers through upsells, cross-sells, added seats, add-ons, and usage growth, excluding new customers and renewals at the same value.
Teams grow it by measuring it account by account, finding expansion signals early, scoring customer health against real outcomes, and running a planned motion with clear ownership.
Most revenue plans lean on new customers. Marketing generates leads, sellers work them, and the board watches new logo counts. Meanwhile, the customers who already bought sit in a different part of the organization, managed by a different team under a different set of goals.
Many of those customers have budget, an internal sponsor, a deployed product, and evidence of whether it works. They are the most informed buyers a company will ever have, and in many companies they are approached only when the contract is about to end.
Expansion changes that picture. It is revenue growth inside accounts the company already serves, through more seats, higher tiers, new modules, new products, and new use cases. Its economics differ from acquisition.
The relationship exists, so the cost of reaching the buyer is lower. The product is in use, so the customer can judge value from their own data. What replaces the cost of finding a new buyer is a harder requirement: proof that the customer is getting value from what they bought first.
The guide is written for customer success leaders, account management and sales leaders, revenue operations teams, and finance partners.
It gives no benchmark expansion rates, because the achievable rate depends on how much room a product has to grow inside an account. It shows how to measure and segment your own.
What Is Expansion Revenue?
Expansion revenue is the increase in recurring revenue from existing customers during a period, from upgrades, added seats or units, cross-sells, add-ons, and usage growth.
Recurly's glossary explains the measurement rules: track expansion only for customers who were active at the start of the period, treat revenue from customers acquired during the period as new business, and count decreases from existing customers as contraction.
Read their expansion revenue definition and formula for the standard calculation and worked example.
Sources of expansion
Source | What changes | Example | Usual trigger |
|---|---|---|---|
Upsell | More of what the customer has | Higher tier or more capacity | Usage nearing a limit |
Added seats or units | More users or entities | A new team adopts the product | Hiring or reorganization |
Cross-sell | An adjacent product or module | A second product line | A need the current product does not cover |
Add-on | An optional capability | An advanced feature pack | A specific use case |
Usage growth | Metered consumption rises | Higher volume on the same plan | Business growth |
Price uplift | Higher price on the same scope | Contracted increase | Contract terms |
For the difference between the two main motions, read cross-selling vs upselling.
What does not count?
Revenue from a new customer.
A renewal at the same value.
Downgrades, which are contraction.
Lost customers, which are churn.
A price increase applied across the whole base, which teams treat differently. Decide whether to count it, record the decision, and report it consistently.
Expansion, retention, and net retention
Retention is keeping the revenue you have. Expansion is growing it. Gross revenue retention measures how much of the starting revenue remains after contraction and churn, and it cannot exceed 100%.
Net revenue retention adds expansion, and it can exceed 100%. For the formulas, see gross revenue retention and net revenue retention.
Worked Example 1: An ARR Bridge That Shows Expansion
Illustrative example. The figures are hypothetical, in millions of dollars of annual recurring revenue.
Line | Amount |
|---|---|
Opening ARR | 5.0 |
New customers | +1.0 |
Expansion | +0.9 |
Contraction | -0.2 |
Churn | -0.3 |
Closing ARR | 6.4 |
Arithmetic and metrics:
Closing ARR: 5.0 + 1.0 + 0.9 - 0.2 - 0.3 = 6.4.
Expansion rate: 0.9 / 5.0 = 18%, using the opening ARR of the existing customers, not total company ARR.
Net revenue retention: (5.0 + 0.9 - 0.2 - 0.3) / 5.0 = 5.4 / 5.0 = 108%.
Gross revenue retention: (5.0 - 0.2 - 0.3) / 5.0 = 4.5 / 5.0 = 90%.
Net new ARR: 1.0 + 0.9 - 0.2 - 0.3 = 1.4.
Expansion share of gross new ARR: 0.9 / (1.0 + 0.9) = 47%.
The company grew 28% (6.4 / 5.0 - 1), and almost half of its gross new ARR came from existing customers. Net retention of 108% looks strong, while gross retention of 90% shows that 10% of the starting base was lost to contraction and churn. Reporting both prevents expansion in a few large accounts from hiding losses across many small ones.
Measure at the account level
If one customer adds $2,000 in monthly recurring revenue and another downgrades by $1,500, expansion is $2,000 and contraction is $1,500. Netting them first reports $500 and conceals both.
Calculate each account's change over the period, count positive differences as expansion, negative differences as contraction, and cancelled accounts as churn.
Segment the rate
Compare expansion rate by segment, by product, and by customer tenure, and compare with your own history. Enterprise and self-serve accounts expand differently, products with more adjacent surface expand more, and a two-year customer has different headroom from a two-month one.
A single-product company with per-seat pricing has a structural ceiling that a multi-product company does not, so benchmarks from other businesses can mislead.
Why Expansion Is Different From New Business
Expansion rests on proven value, existing relationships, and available data, which changes how it should be approached.
Dimension | New business | Expansion |
|---|---|---|
Buyer knowledge | Evaluates a promise | Has evidence from using the product |
Access | Must be earned | Relationship exists |
Data available | Public and third-party signals | Usage, support, and account history |
Main risk | No fit or no budget | Value not realized yet |
Typical owner | Sales | Customer success, account management, or both |
Timing | Driven by buyer need | Driven by adoption, growth, and events |
Expansion readiness depends on value
An account that has not reached the outcome it bought is usually a retention situation. A pitch for more of a product that is not delivering tends to harden doubts. Check adoption and outcomes before approaching an account for expansion.
Finding Expansion Opportunities
Find expansion with signals that show readiness and whitespace maps that show where the account has room to grow.
Signals that suggest an account is ready
Signal | What it suggests | Typical expansion motion | Who acts |
|---|---|---|---|
Usage approaching a limit | Capacity constraint | Upsell to a higher tier | Account manager |
New team or region onboarding | Broader adoption | Added seats or units | Customer success |
New executive or sponsor | Priorities under review | Business case for new use cases | Account executive |
Strong adoption of a core feature | Value realized | Cross-sell an adjacent module | Customer success |
Hiring pattern in a relevant function | Growth | Capacity or capability expansion | Account manager |
Funding, acquisition, or expansion into new markets | New requirements | Multi-entity or regional expansion | Account executive |
Champion promoted or moved | New advocate in a new place | Land in the new group | Account executive |
Support requests for missing capability | Unmet need | Cross-sell or add-on | Customer success |
Contract milestone approaching | Natural decision point | Package expansion with renewal | Account manager |
Signals that suggest caution
Low adoption, a silent champion, a cluster of high-severity support issues, an unresolved commitment, and a recent budget freeze point to retention work first. Treat them as inputs to the health score and as reasons to delay an expansion pitch.
Worked example 2: a whitespace map
Illustrative example. A company sells three products to 40 customers. Each customer could buy any of the three, so there are 40 x 3 = 120 customer-product cells. Today, customers hold 22 products in total.
Penetration: 22 / 120 = 18.3%.
Unowned cells: 120 - 22 = 98.
The map shows 98 places to grow. It does not show which are ready. Rank them with fit and health: customers with strong adoption of a related product, a relevant trigger event, and an engaged stakeholder come first. A whitespace map shows where the headroom is, and signals and health decide the order.
Account plans and org maps
Expansion in larger accounts is a multi-stakeholder effort. Map the buying committee, find a sponsor for each new use case, and keep an account plan with goals, risks, and next steps. See account planning with AI agents for how plans stay current.
Building a Customer Health Score
A customer health score summarizes how likely an account is to renew and grow, using a small set of signals that move before the outcome.
It is useful only if it has been validated against real renewals, churn, and expansion.
Choosing components
Component | Example signals | What it tells you |
|---|---|---|
Product usage | Active users per licensed seat, feature depth and breadth | Whether the customer gets value |
Adoption breadth | Teams and use cases active | Whether the product is embedded |
Support | Severity and trend of tickets, escalations | Whether friction is building |
Relationship | Champion engaged, executive sponsor active, number of stakeholders, people changes | Whether the people who bought are still there |
Commercial | Payment timeliness, downgrade requests, seat growth | How secure the revenue is |
Sentiment | Survey results, account team notes | How the customer feels |
Planhat's guide to customer health scores lists the same components and gives the principle for choosing signals: each should move before the outcome, not alongside it, and someone should be able to act differently because of it.
Read their customer health score guide for models, weighting, tiers, and the validation method used below.
Worked example 3: calculating a score
Illustrative example. Weights are set by segment and sum to 100%.
Component | Weight | Account score (0 to 100) | Contribution |
|---|---|---|---|
Product usage | 30% | 80 | 24.0 |
Adoption breadth | 20% | 60 | 12.0 |
Support | 15% | 90 | 13.5 |
Relationship | 15% | 50 | 7.5 |
Commercial | 10% | 70 | 7.0 |
Sentiment | 10% | 60 | 6.0 |
Total | 100% | 70.0 |
The account scores 70 out of 100. The composite hides the cause of the weak spot: relationship is 50. A useful score decomposes, so a reader can see that the champion's engagement is the issue and the support picture is fine.
If the score moves, the team should be able to see which signal moved and which evidence caused it.
Set weights by segment
Login frequency may be decisive for a daily-use tool and nearly meaningless for a quarterly reporting product.
Build separate models for meaningfully different segments, keep the number of signals small, and keep weights coarse, since precision implies a confidence the data may not support.
Worked Example 4: Validating the Score With a Backtest
Illustrative example. Planhat recommends a simple validation: look back at what the score said 90 days before churn and before expansion, and check how well it separated outcomes.
Suppose 100 accounts were scored 12 months ago. The table shows what happened next.
Health band | Accounts | Expanded | Expansion rate | Churned | Churn rate |
|---|---|---|---|---|---|
Green (75 or above) | 40 | 14 | 14 / 40 = 35.0% | 1 | 1 / 40 = 2.5% |
Yellow (50 to 74) | 40 | 8 | 8 / 40 = 20.0% | 4 | 4 / 40 = 10.0% |
Red (below 50) | 20 | 1 | 1 / 20 = 5.0% | 6 | 6 / 20 = 30.0% |
Total | 100 | 23 | 11 |
Totals: 14 + 8 + 1 = 23 expanded and 1 + 4 + 6 = 11 churned.
What the backtest shows:
Green accounts expanded at 35% and churned at 2.5%.
Red accounts churned at 30% and expanded at 5%.
The score separates outcomes in the right direction, so it is a candidate for prioritizing work. If churned accounts had been mostly green 90 days before cancelling, the signals would need to change.
Also check precision at the top of the risk list: of the accounts flagged most at risk, how many actually churned? A score that marks a large share of the base red catches most churn and prioritizes nothing.
Re-run the validation each quarter, since a score that is not revalidated decays as the product, segments, and buyers change.
Use the score in two directions
Use | Action |
|---|---|
Green with expansion signals | Start an expansion motion |
Green without signals | Keep value visible, build a plan, watch for triggers |
Yellow | Address the weakest component first |
Red | Run a retention plan, and delay expansion pitches |
Forecasting Expansion Revenue
Forecast expansion with its own pipeline, its own win rate, and its own timing. Expansion deals behave differently from new business.
Worked example 5: required expansion pipeline
Illustrative example. The target is $1.2 million of expansion bookings in the period. The team's value-based win rate on qualified expansion opportunities is 40%.
Required qualified expansion pipeline: $1.2M / 0.40 = $3.0M.
Coverage: 1 / 0.40 = 2.5 times the target, which gives $3.0M when applied to the $1.2M target. (Check: 2.5 x $1.2M = $3.0M.)
Compare that with the current qualified expansion pipeline. The method matches new business coverage. See renewal forecasting with revenue agents for how renewals and expansion interact in the forecast.
Forecast considerations
Segment by motion. Seat growth, cross-sell, and usage uplifts have different win rates and cycle lengths.
Time to close. Expansion tied to a renewal date has a built-in deadline.
Health weighting. Weight opportunities by account health, since healthy accounts convert at higher rates.
Separate from renewals. Report renewal, expansion, and contraction on separate lines.
Use history. Calibrate rates from past quarters, and recalibrate each period.
Capturing Expansion: Running the Motion
A repeatable expansion motion has a trigger, a plan, a stakeholder map, a business case, and a clear owner.
Detect the trigger. A signal, a usage threshold, or a calendar event starts the motion.
Check health. Confirm adoption and outcomes before approaching the account.
Review account history. Look at past purchases, open issues, and prior conversations.
Map stakeholders. Identify the sponsor, the economic buyer, and new stakeholders for the new use case.
Prepare the case. Link the offer to the customer's own usage data and stated goals.
Engage in sequence. Use a coordinated sequence across channels, and align the account team so the customer hears one message.
Agree a plan. Set a dated next step and a mutual plan for evaluation and approval.
Close and onboard. Hand over to implementation, and track adoption of the new scope.
Learn. Record what worked, and update signals and health weights.
Ownership models
Model | How it works | Strength | Risk |
|---|---|---|---|
Customer success led | CSM owns the relationship and expansion | Deep product and value knowledge | May lack commercial skills or capacity |
Account executive led | Sales owns expansion deals | Commercial skill | May lack day-to-day context |
Hybrid | CSM surfaces and shapes, AE negotiates and closes | Combines strengths | Needs clear handoffs and aligned goals |
Whatever the model, align incentives, define who owns each stage, and avoid contacting the same customer from three directions.
For coordination across renewal and expansion, read enterprise expansion and renewal coordination.
Timing with renewals
Some teams combine expansion with the renewal conversation, and others separate them. Combining can simplify a decision, and it can also tie a healthy renewal to a contested expansion. Decide by account health and by how decisions are made inside the customer.
Common Mistakes
Pitching expansion to unhealthy accounts. It can deepen retention risk.
Netting expansion against contraction. Both movements disappear.
Reporting only net retention. Gross retention shows the losses.
Using total company ARR as the denominator for expansion rate. It understates the rate.
Building a health score without validating it. A decoration carries false authority.
One global score for every segment. Signals mean different things in different products.
Ignoring non-usage signals. The budget owner may never log in.
No owner. Three teams contact the same account, or none does.
Waiting for the renewal. Expansion signals appear throughout the term.
Using price increases as expansion without disclosure. Decide, document, and report consistently.
No feedback loop. Won and lost expansion deals should improve signals and scores.
Expansion in Enterprise Accounts
Enterprise expansion involves multiple business units, entities, and stakeholders, so it needs account-level context.
Multiple entities and hierarchies. Resolve parent and subsidiary accounts so expansion in one unit is not mistaken for a new customer.
Procurement and security. New scope may need new reviews.
Several sponsors. Each business unit may need its own champion and case.
Long timelines. Plan expansion across quarters and align with budget cycles.
Usage across entities. Aggregate usage and adoption across the whole account.
Coordination with renewals. Contract dates differ across entities.
For monitoring across the lifecycle, see revenue agent renewal and expansion monitoring.
The context gap in expansion
Enterprise revenue teams lose deals when deal-moving signals are scattered outside the CRM, across the warehouse, inbox, call transcripts, and product data, with no system built to unify them into action.
Rox calls this the context gap. For expansion, the consequence is that renewal and expansion opportunities are identified too late.
The usage spike sits in the warehouse, the new executive appears in the inbox, and the unmet need is mentioned on a call, and no one connects them.
How AI Supports Expansion
AI can watch signals across systems, prepare account research, and draft plans. People decide what to pursue and how.
Task | What AI contributes | Control to keep |
|---|---|---|
Signal monitoring | Watches usage, email, calendar, and call data for expansion and risk signals | Review signal definitions |
Account research | Gathers news, org changes, and account history | Check key facts |
Prioritization | Ranks accounts by fit, health, and signals | Validate against outcomes |
Preparation | Drafts briefings and questions | Review with the account team |
Follow-up | Drafts messages and tasks | Approve before sending |
How Rox Supports Expansion?
Rox is a warehouse-native revenue orchestration platform. Its context graph unifies internal and external signals from the warehouse, inbox, call transcripts, product data, and external sources into a single system of context. That foundation suits expansion, which depends on signals that live outside the CRM.
Cross-sell and Upsell
Rox's Cross-sell and Upsell capability is built around account signals. A team defines the signals that matter to what it sells, reviews them alongside the customer's account history, and uses them as inputs to automations that research potential opportunities.
An automation can generate a report, email the rep, and create an opportunity for review. To prepare for the conversation, Rox can generate questions to validate the business need and identify the economic buyer, and create an executive briefing with a recommended sales play and open questions.
The material is reviewed and refined with the account team before anyone engages the customer.
Account-level agents
Rox assigns one dedicated revenue agent to each account. The agent retains account context and monitors signals continuously, so changes in usage, stakeholders, or conversations are visible when the account team looks.
Rox positions this persistent, account-specific attention as a way to spot expansion and surface risk across the lifecycle, from first outreach through renewal and expansion.
At Rox, revenue orchestration means combining automated tasks with intelligence across roles, systems, and stages into an end-to-end revenue motion that reasons about what to do next.
Human oversight
AI-generated outputs are informational and should be reviewed by authorized personnel before action. Features described as automated operate within user-defined parameters and require initial configuration and ongoing oversight.
Validate any health score or signal against your own renewal and expansion history, review briefings with the account team before engaging a customer, and keep a person responsible for pricing and commitments.
See how Rox turns account signals into opportunities for review: Explore Rox Cross-sell and Upsell.
A 30-Day Plan to Start an Expansion Motion
Week 1: Define. Write the expansion definition, the exclusions, and the rule for price increases. Build the ARR bridge for the last two quarters.
Week 1: Segment. Calculate expansion rate, net retention, and gross retention by segment.
Week 2: Map. Build a whitespace map by customer and product, and list the expansion signals you can observe today.
Week 2: Score. Draft a health score with three to five signals per segment, and decide the tiers.
Week 3: Validate. Backtest the score against last year's churned and expanded accounts, 90 days before the outcome.
Week 3: Assign. Choose the ownership model and define handoffs.
Week 4: Run a pilot. Pick 10 to 20 accounts with strong health and signals, prepare a briefing for each, and run the motion.
Week 4: Review. Track win rate, cycle time, and what the signals predicted, and refine.
Conclusion
Expansion revenue is growth inside accounts that already know the product, and its quality depends on whether those accounts have realized value.
The measurement is straightforward when the rules are clear: count positive account-level changes among customers active at the start of the period, keep contraction and churn on separate lines, and report gross and net retention together.
In the worked example, net retention of 108% sat beside gross retention of 90%, and almost half of gross new ARR came from expansion.
Finding expansion takes two views: signals that show readiness and a whitespace map that shows headroom, with a health score deciding the order.
A score earns trust only through validation. In the backtest, green accounts expanded at 35% and churned at 2.5%, while red accounts churned at 30%, a pattern that shows the score pointing in the right direction.
Forecast expansion with its own win rate, so a $1.2 million target at 40% needs $3.0 million of qualified pipeline, and run the motion with a trigger, a health check, a stakeholder map, a business case, and a clear owner.
For enterprise teams, the signals that decide expansion sit across the warehouse, inbox, call transcripts, and product data.
Rox's warehouse-native system of context, Cross-sell and Upsell capability, and account-dedicated agents are built to bring those signals together, with people reviewing the outputs and owning the customer conversation.
To start, build the ARR bridge for the last two quarters, draft a health score, and backtest it before you use it to choose accounts.
Talk to the Rox team about turning account signals into expansion opportunities: Visit Rox.
Frequently Asked Questions
What is expansion revenue?
Expansion revenue is the additional recurring revenue from existing customers during a period, from upsells, added seats or units, cross-sells, add-ons, and usage growth. It excludes new customers, renewals at the same value, and decreases.
How do you calculate expansion revenue?
For customers active at the start of the period, sum each account's positive recurring revenue change. Exclude new customers, and count decreases as contraction and cancellations as churn. Calculate at the account level so gains and downgrades do not net out.
What is the expansion rate?
Expansion revenue divided by the starting recurring revenue of the existing customer cohort. In the worked example, $0.9M of expansion on $5.0M of opening ARR is 18%. Do not include new business in the denominator.
How does expansion affect net revenue retention?
Expansion is the only component that can push net revenue retention above 100%. Net retention equals starting revenue plus expansion minus contraction minus churn, divided by starting revenue. Report gross retention beside it, since expansion in a few accounts can mask losses elsewhere.
What is the difference between upsell and cross-sell?
An upsell moves a customer to more of what they already buy, such as more seats or a higher tier. A cross-sell adds something adjacent, such as a second product or module. Upsells usually rest on usage evidence, and cross-sells depend more on fit.
What is a customer health score?
A composite score that summarizes how likely an account is to renew and grow, built from signals such as usage, adoption breadth, support, relationship strength, commercial behavior, and sentiment. It is useful only after it has been validated against real outcomes.
How do I validate a customer health score?
Look back at what the score said about 90 days before accounts churned and before they expanded. If churned accounts were mostly green, change the signals. Check precision at the top of the risk list, and repeat the validation each quarter.
Which signals show an account is ready to expand?
Usage nearing a limit, a new team or region onboarding, a new executive or sponsor, strong adoption of a core feature, hiring in a relevant function, funding or expansion, a champion who moves, support requests for missing capability, and contract milestones. Check health before acting.
When should I avoid pitching expansion?
When adoption is low, the champion is silent, high-severity support issues cluster, or the customer has not reached the outcome they bought. Treat those accounts as retention work first.
How do I forecast expansion revenue?
Use a separate pipeline, win rate, and timing. Divide the expansion target by the value-based win rate on qualified expansion opportunities. A $1.2 million target at 40% needs $3.0 million of qualified pipeline. Weight by account health and separate renewals from expansion.
Who should own expansion?
It depends on the company. Customer success led, account executive led, and hybrid models all exist. Define who owns each stage, align incentives, and avoid contacting the same customer from several directions.
Why is enterprise expansion harder?
Enterprise accounts have multiple entities, business units, procurement reviews, and long timelines, and the signals sit across the warehouse, inbox, call transcripts, and product data. Account-level context and a current stakeholder map matter more.
Can AI help with expansion?
AI can monitor signals, gather account research, rank accounts, and draft briefings and follow-up. AI-generated outputs are informational and should be reviewed by authorized personnel before action. People decide what to pursue and own pricing and commitments.
How does Rox support expansion?
Rox's Cross-sell and Upsell capability lets a team define account signals, review them with account history, and use them to trigger automations that research opportunities and create them for review. It can generate discovery questions and executive briefings that the account team reviews before engaging the customer. A dedicated agent per account monitors signals continuously.
Similar Articles
We build with the best to make sure we exceed the highest standards and deliver real value.

