ClariLayer Docs

Contraction MRR

Reference

Contraction MRR Definition

Learn the governed definition of Contraction MRR, including downgrade MRR, partial recurring loss, churn boundaries, migration handling, and ClariLayer Drift Risk.

Recurring revenue

Contraction MRR

High Drift Risk

Contraction MRR measures recurring monthly revenue lost from existing customers through downgrades, seat reductions, package reductions, or other partial recurring decreases during a defined period.

Governed formula

sum(negative recurring monthly revenue movements from retained existing customers in the period)

  • Keep contraction separate from full churn so partial losses and account exits remain explainable.
  • Use the same movement timing, currency, and product filters as the governed MRR definition.

Downgrade Contraction MRR

Counts recurring monthly value lost when customers move to lower packages or plans.

Useful for packaging and value reviews, but migration rules must identify true downgrades.

Seat Contraction MRR

Counts recurring monthly value lost from lower quantities, seat reductions, or capacity cuts.

Useful for adoption analysis, but it requires quantity changes to be separated from price changes.

Product Contraction MRR

Counts recurring monthly value lost when an existing customer removes one product but keeps another.

Useful for product health, but full account churn must remain classified separately.

Decisions to lock

Where is the boundary between contraction and churn?

Partial reductions and full exits drive different operating actions and must not share one loss bucket.

Do billing credits, corrections, pauses, and price concessions count as contraction?

Temporary or corrective records can inflate contraction when they are not governed as separate event types.

How are migration bundles and product swaps netted across a customer?

One migration can create negative and positive lines that should not be interpreted as separate churn and expansion events.

Validation questions

  • Can contraction movements reconcile to retained customers whose recurring value decreased but did not fully churn?
  • Are credits, pauses, corrections, and concessions excluded or separately labeled?
  • Do product migrations net to the expected customer-level movement instead of double counting loss?

Common drift traps

  • A full cancellation is recorded as contraction because the account record remains active after the subscription ends.
  • Credits and billing corrections are treated as recurring loss movements without checking whether recurring value changed.
  • A product swap creates contraction in one product view and expansion in another without a customer-level bridge.

Source-system boundary

Existing-customer loss movement spine

Billing platform, Contracts, CRM, Customer success platform, Data warehouse

The governed definition should state partial-loss boundaries, event types, migration handling, and monthly normalization.

Context-layer proof

ClariLayer's context layer should pin Contraction MRR to the approved partial-loss boundary, movement event taxonomy, migration handling, and monthly value change so teams can separate recoverable downgrades from churn.

Governed signals
partial-loss boundary, movement event taxonomy, migration handling, monthly value change
Review cadence
Review after cancellation, downgrade, billing-credit, packaging, or migration-process changes.

ClariLayer Drift Risk

Contraction MRR is high risk because negative movements can represent true downgrades, corrections, pauses, concessions, or full churn.

Ambiguity

5/5

The metric is ambiguous unless the boundary between contraction, churn, credit, pause, and migration is explicit.

Source-system dependency

4/5

The calculation relies on billing movement records, contract state, CRM account status, and success classifications.

Time-window sensitivity

4/5

Effective dates, credits, pauses, and downgrade timing can move contraction between reporting periods.

Governance need

4/5

Contraction MRR drives retention intervention and revenue decomposition, so movement rules need ownership.

AI-agent risk

An AI agent can send the wrong retention signal if contraction MRR is not separated from churn, billing corrections, pauses, and migration movements.

Related metric definitions