Contraction MRR

What Contraction MRR Measures

Contraction MRR is the monthly recurring revenue lost when existing customers downgrade — fewer seats, a lower tier, or a smaller deployment — without canceling outright. It shows up as a negative component of the ARR waterfall alongside churn, and it's distinct from churn rate because the customer is still paying. They just liked you less than they used to. Most SaaS finance teams track four MRR movements each month: new, expansion, contraction, and churn. Contraction is the one that sneaks up on you.

How Contraction MRR Is Calculated

Contraction MRR = sum of (prior MRR − current MRR) for every customer whose subscription decreased in the period, where current MRR > $0. A customer who cancels entirely contributes to churned MRR, not contraction MRR. A customer who reduces from $10k/month to $7k/month contributes $3k to contraction MRR.

Net MRR movement formula:

Net New MRR = New MRR + Expansion MRR − Contraction MRR − Churned MRR

Contraction rate = Contraction MRR ÷ prior period total MRR. At a $550k MRR base, $22k in contraction is 4% monthly. Annualized, 4% monthly contraction creates serious drag on net revenue retention even when new logo growth looks clean.

Contraction MRR Worked Example

A Series B SaaS company opens Q3 with $600k MRR. Three customers downgrade during the quarter:

• Customer A: $15k → $10k/month (reduced seat count by 30%)
• Customer B: $8k → $4k/month (downgraded from Enterprise to Pro tier)
• Customer C: $5k → $2k/month (cut deployment from 500 to 200 users)

Total contraction MRR: $12k/month, or $36k across the quarter. If expansion MRR is $25k in the same period, the company is net negative on its existing base — gross revenue retention is trending below 95%, which signals churn risk at every upcoming renewal.

When Finance, CS, and Sales Teams Use Contraction MRR

Finance and RevOps track contraction MRR as part of the monthly close. Customer success teams watch it as a leading indicator: a seat reduction today often precedes a full cancellation at renewal by 60-90 days. Product teams use contraction patterns to identify which features drove the downgrade — reduced usage on a paid tier is almost always visible in product telemetry before the commercial ask comes in.

Sales leadership cares because contraction directly offsets net new ARR. A sales team adding $1M in new ARR while the base contracts $400k is running to stand still, and the board math makes that visible immediately.

Common Contraction MRR Manipulation Patterns

The most common timing exploit: companies recognize contraction only at the renewal date, not when the customer requests it or signals intent. A customer who tells CS in March they're cutting seats but renews in September doesn't appear in contraction MRR until September. This inflates NRR in the interim and creates a cliff at renewal — visible to any auditor pulling raw contract data against CRM records.

CS teams sometimes reclassify customers headed toward full cancellation as contractions instead — a legitimate save, or pure metric reclassification depending on whether the customer was actually leaving. The company retains the logo but takes revenue loss. This is precisely why logo retention and revenue retention are tracked as separate numbers.

Contraction MRR also tells you nothing about cause. A rep who oversold seats in the original deal generates identical contraction MRR to a rep who lost an internal champion to a reorg. The fix is root-cause tagging at the contract level — competitive pressure, budget cut, reduced usage, product gap — logged in CRM at the time of downgrade, not reconstructed six months later at renewal.