Mid-contract churn is revenue that leaves before the renewal date arrives. Because no renewal event occurred, the loss never touches renewal rate, and it is the single largest reason renewal rate and gross revenue retention disagree at the same company in the same period.
Where it comes from
Termination for convenience clauses give a customer a scheduled exit ramp that has nothing to do with the expiry date. Payment failure removes revenue without anyone deciding anything. Acquisitions consolidate the acquired company onto an incumbent vendor. Businesses close. Seat true-down rights, where the contract allows a customer to reduce quantity at a quarterly checkpoint, drain revenue from an account that technically remains a customer.
Only the first and last of those look like a customer success problem. The rest are business events, which is why a mid-contract churn number that is not split by cause tends to produce the wrong remediation plan.
It is harder to see than renewal churn
A renewal has a date on the calendar. Someone owns it, it appears in the renewal pipeline, and it gets reviewed. Mid-contract loss has no scheduled trigger, so nothing surfaces the account until the cancellation email arrives or the invoice ages past due.
The signal that does exist is usually the absence of one. ORM's read of its own customer base is that an account filing no support cases at all is at risk of churn, because nobody is using the product hard enough to hit friction. The same logic runs through ORM's view on deal slippage, where the earliest warning is no activity, no data changing, and no notes. Quiet accounts are not low maintenance. They are unmeasured, and the silence gets read as health.
How to measure it
Track mid-contract ARR lost as its own line, divided by beginning ARR for the period, and split it three ways.
- Voluntary early exit, where the customer invoked a right they negotiated. - Involuntary, where payment failed and collection did not recover it. - Structural, covering acquisition, insolvency, and business closure.
Report the three separately each month. The voluntary line is the one product and customer success can move. The involuntary line belongs to billing operations and usually falls fast once dunning and card updater coverage are fixed. The structural line is mostly a function of which segment you sell into, and the honest response is to price and forecast for it rather than to chase it.
Contract terms that reduce it
Removing termination for convenience from standard paper is the blunt lever, and it costs deal cycles. The subtler ones work better: notice windows that force a conversation before an exit becomes final, annual prepayment that removes monthly payment failure entirely, and quantity floors that cap how far a true-down can go. Each of those converts an unscheduled loss into a scheduled discussion, which is the only form of churn a renewal motion can actually defend against. Once the mid-contract line is visible and split by cause, net revenue retention stops moving for reasons nobody can explain after the fact.
Frequently Asked Questions
Why does mid-contract churn not show up in renewal rate?
Renewal rate divides by revenue available to renew in the period. An account that cancels in month five of a twelve month term never entered that denominator, so the loss is invisible to the metric. Gross revenue retention catches it because it measures against the whole beginning base.
What causes most mid-contract churn in B2B SaaS?
Three causes, and only one of them is about the product. Payment failure removes revenue without a decision. Business events such as acquisition and closure remove it without a conversation. Deliberate early exits cluster where the contract includes a termination for convenience clause.
How do you forecast something with no scheduled event?
Model it as a rate applied to the portion of the base that is not up for renewal, segmented by contract type and customer size. It behaves more like a hazard rate than a renewal decision, so it is estimated from historical monthly loss patterns rather than from an account by account renewal review.
Should involuntary churn be reported separately?
Yes. Failed payments respond to dunning, card updater services, and billing operations. Deliberate early exits respond to product and customer success work. Blending them into one number sends the wrong team after the problem.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like mid-contract churn into prescriptive action for your team.
Schedule a Demo