Expansion MRR: Additional MRR from existing customers through upgrades, add-ons, seat increases or price increases.
Formula
Expansion MRR = Sum of (MRR increase from existing customers this period) Computable definition
The canonical formula in the GASP formula grammar. The MCP server compiles it to SQL over the datasets listed below.
sum(field.mrr_change where field.event_type = 'expansion') Unit: currency
Breakdowns
by_segment: one row persegmentvalue
Notes: by_segment returns one row per customer segment, which shows where expansion comes from.
Data requirements
Grain: Per event, aggregate monthly · Frequency: Daily sync · Aggregation: aggregate (month) · Staged: no · Main source: Billing.
| Field | Dataset | Type |
|---|---|---|
event_date | revenue_event | date |
event_type | revenue_event | string |
mrr_change | revenue_event | decimal |
Example SQL (Postgres)
SELECT (SELECT COALESCE(SUM(mrr_change), 0) FROM revenue_event WHERE event_date >= :period_start AND event_date <= :period_end AND event_type = 'expansion') AS expansion_mrr Access: recommended
sensitivity tier confidential,
access scope unscoped.
Guidance your policy engine enforces.
From an agent: with the GASP MCP server, call
lookup_metric({ "name": "Expansion MRR" }) or generate_query({ "metric": "Expansion MRR", "adapter": "<your adapter JSON>" }).
What It Tells You
How much revenue you grow from customers you already have, which usually costs far less than winning new ones.
Related Metrics
Connected in the GASP relationship graph.
Upstream: what drives this
- Customer Health Score drives Expansion MRR (Customer Success)
- QBR Completion Rate drives Expansion MRR (Customer Success)
- Product Qualified Accounts drives Expansion MRR (Product)
Downstream: what this drives
- Expansion MRR component of Expansion Revenue Rate (Customer Success)
- Expansion MRR component of Net New MRR (Core)
- Expansion MRR component of NRR (Core)
- Expansion MRR measures Customer (Entity)
- Expansion MRR measures Subscription (Entity)