Reference
Expansion MRR Definition
Learn the governed definition of Expansion MRR, including upsell MRR, cross-sell MRR, existing-customer movement rules, and ClariLayer Drift Risk.
Metric 7 of 16
Recurring revenue
Expansion MRR
Expansion MRR measures recurring monthly revenue added from existing customers through upgrades, seat growth, package changes, or cross-sell activity during a defined period.
Governed formula
sum(positive recurring monthly revenue movements from existing customers in the period)
- Classify expansion from the same movement spine used for MRR, NRR, and retention reporting.
- Exclude new-customer MRR unless the governed definition explicitly treats reactivation or acquisition as expansion.
Upgrade Expansion MRR
Counts monthly recurring revenue added when an existing customer moves to a higher package or plan.
Useful for packaging reviews, but it needs plan migration rules to avoid double counting.
Seat Expansion MRR
Counts monthly recurring revenue added from additional seats, users, or capacity on an existing subscription.
Useful for product adoption motions, but only when quantity and price changes are separated.
Cross-sell Expansion MRR
Counts monthly recurring revenue added from new recurring products sold to existing customers.
Useful for account growth, but it depends on a governed existing-customer boundary.
Decisions to lock
What qualifies a customer as existing for expansion purposes?
Reactivations, acquisitions, and account hierarchy changes can make new revenue look like customer expansion.
Which movement events distinguish expansion from correction, migration, or new business?
Expansion totals drift when billing corrections and product migrations are not separated from true growth.
How are mid-period upgrades, ramp schedules, and currency changes normalized?
Movement timing and normalization decide which month receives expansion and how much value is recognized.
Validation questions
- Do expansion movements reconcile to the net change in MRR for existing customers?
- Are upgrades, seat growth, cross-sell, migrations, and billing corrections classified as separate movement types?
- Can each expansion amount be tied to an account, subscription, product, effective date, and prior monthly value?
Common drift traps
- Reactivated customers are counted as expansion even though they were outside the retained cohort at period start.
- Package migrations create both contraction and expansion movements that are not netted or labeled consistently.
- Sales opportunity amount is used as expansion MRR before billing activation confirms the recurring monthly value.
Source-system boundary
Existing-customer movement spine
Billing platform, Contracts, CRM, Data warehouse
The governed definition should state existing-customer eligibility, movement event types, product filters, and monthly normalization.
Context-layer proof
ClariLayer's context layer should attach Expansion MRR to customer eligibility, movement event type, effective date, and recurring monthly value so sales and success agents can distinguish true growth from migrations or corrections.
- Governed signals
- existing-customer boundary, movement event type, effective date, monthly normalization rule
- Review cadence
- Review after pricing, packaging, account-hierarchy, or billing-event changes.
ClariLayer Drift Risk
Expansion MRR is high risk because the same positive movement can represent upsell, cross-sell, migration, correction, or reactivation.
Ambiguity
5/5The label does not reveal whether upgrades, seat growth, cross-sell, reactivation, or migration movements are included.
Source-system dependency
4/5The metric depends on billing events, contract terms, CRM account status, and warehouse movement classification.
Time-window sensitivity
4/5Effective dates, ramps, and mid-period changes decide which month receives the expansion movement.
Governance need
4/5Expansion MRR influences sales credit, success programs, and growth decomposition, so movement rules need approval.
AI-agent risk
An AI agent can overstate account growth if expansion MRR is not tied to the approved existing-customer boundary, movement taxonomy, and monthly normalization rule.