The renewal opened, as always, 90 days before the contract end date. The account manager emailed the main contact and got an auto-reply: she had left in the spring. Her replacement had never logged in. Weekly active users had fallen by a third since June, two tickets had been tagged "frustrated", and finance had chased a late invoice twice. Every fact was recorded somewhere. None had reached the renewal owner, and the customer's notice window had already closed on a non-renewal letter.
That is renewal leakage: the share of churn, contraction and save discounts that was visible early enough to act on and was not. The customer did not surprise you. Your systems did.
SaaS Capital's 2025 B2B SaaS Retention Benchmarks, drawn from more than 1,000 private companies, put median gross revenue retention at 91 percent and median net revenue retention at 101 percent: these separate medians describe the survey, not any one company or the preventable portion of churn. Gartner's survey of 243 CSOs and senior sales leaders, published in May 2025, found that 73 percent were prioritizing growth from existing customers. When the growth plan lives in the base, every avoidable loss at renewal costs more than it looks.
The signals are not subtle. Research from Sturdy, reported by ChurnZero in June 2023, found a 51 percent chance that an account churns within 12 months after its champion leaves, that 65 percent of accounts with an executive change did not renew, and that accounts were 33 percent more likely to renew when the CS team acted within 48 hours of an executive change. The article does not disclose the Sturdy sample or study method, so treat the figures as directional: the signal arrives early, and its value decays fast.
Most teams still hear it late. TSIA wrote in May 2026 that only 22 percent of organizations use AI for health scoring; its public article does not state the survey denominator. The evidence exists, spread across product, support, billing and email, and nothing connects it to a date and an owner. That makes renewal leakage a systems problem.
Diagnosis: why renewal signals arrive too late
When a renewal is lost, the post-mortem usually finds the signal months earlier. Five patterns keep it from the renewal owner.
1. The calendar sets the clock, not the risk
Most renewal processes start a fixed 90 or 120 days before the contract end date, for every account. That treats a healthy account and a slipping one the same way, and it measures the wrong deadline: the one that matters is the notice deadline, which can fall 30 to 90 days before the end date. Vendr, which advises software buyers, recommends starting renewal preparation 90 to 120 days before a contract ends; this is buyer-side advice, not a measured benchmark. Your customer may be evaluating alternatives before your process opens.
2. The champion leaves and the CRM still lists them
Contact records rarely update themselves. A champion changes jobs, the email starts bouncing, and the CRM shows the same primary contact for months. The U.S. Bureau of Labor Statistics reported in September 2026 that median tenure with a current employer was 4.1 years in January 2026, so on a three-year contract the person who signed may well be gone before the second renewal. ChurnZero's own research, in the same 2023 article, found only about half of CS organizations had a documented play for key contact changes.
3. Usage is reviewed at the QBR, not every week
Product usage is the best early signal most teams have, and the one most often read on the slowest cycle. Falling weekly active users, a purchased feature never adopted, or seats below the contracted amount are visible in product data within days. Reviewed only at a quarterly business review, they arrive up to three months late. The change matters more than the level: an account steady at low usage is a different problem from one falling fast.
4. The health score averages the signal away
A composite score that blends usage, sentiment, support and surveys into one number can hide a single sharp change. An account with strong usage and a champion who just left may still read green. The score is built to summarize, and renewal risk usually starts as one specific event.
5. Commercial signals sit in finance
Failed payments, late invoices, a stalled purchase order or a new procurement contact asking about terms all signal a change in how the customer sees the spend. They live in billing or finance's inbox, not the CS platform. A failed payment needs prompt attention, but it is not proof of voluntary churn. Route it to finance and CS without counting every payment failure as preventable renewal loss.
Framework: the Renewal Runway
The Renewal Runway replaces a fixed renewal calendar with one question per account: does the time left before the notice deadline exceed the time a save has historically needed for an account like this one? If not, it escalates now.
It has three parts. Available runway is the days from today to the notice deadline, not the end date. Required runway is how long saves have taken for accounts of similar segment, size and risk type, measured from your own labeled renewals. Signal events are the changes that move an account from routine to at risk, sorted into five families, each with a source and an owner.
| Signal family | Example events | Where it lives | Who should see it |
|---|---|---|---|
| People | Champion or sponsor leaves, email bounces, new executive, buying contact changes | Email, CRM contacts, job-change data | CSM within 48 hours |
| Usage | Weekly active users falling, core feature unused, seats below contract | Product analytics | CSM weekly |
| Service | Escalated tickets, repeated issues, negative survey comments | Help desk, surveys | CSM and support lead |
| Commercial | Failed or late payments, procurement questions, consolidation requests | Billing, finance inbox | CSM and finance |
| Value | No outcome review in two quarters, goals from the sale never measured | CS platform, meeting notes | CSM and CS leader |
A signal event lengthens the required runway, because a save after a champion change takes longer than a routine renewal. When available runway falls below required runway, the account escalates with a named owner and a date, stating which signal fired and what changed since last week, so the owner starts from evidence rather than a color.
Renewal leakage then becomes measurable. For each renewal that churned, contracted or closed with a save discount, compare the date of the first signal with the date of the first escalation. If the first signal left at least the required runway before the notice deadline but the first escalation did not, classify the loss as potential process leakage, then review whether action could realistically have changed the outcome. Price the total with the leak ledger to rank it against other gaps.
Illustrative example, with made-up round numbers: a $15M ARR company reviews 60 renewals from two quarters. Twelve churned or contracted, losing $900K, and six renewed only with save discounts worth $150K. In eight of the losses and four of the discounts, the first signal arrived at least 75 days before the notice deadline, but escalation came with less than 75 days remaining. The revenue at risk on those twelve accounts is a candidate leakage amount, not an independently measured save opportunity or the full $1.05M. The rest is a product or market question, not a renewal one.
Implementation: six steps to hear renewal risk early
Make the notice deadline a field. For every active contract, store the end date, notice period and calculated notice deadline on the account or renewal record, and count available runway to that deadline. Teams often find contracts whose effective deadline is weeks earlier than the date they had been working to.
Label your last 20 renewals. Have the CS team label roughly the last 20 renewals as renewed cleanly, saved late or churned, and record when the first risk signal appeared and when someone acted. This gives you your own required runway by segment and a leakage baseline, a starting point rather than a benchmark.
Wire people signals first. Contact changes are the highest-value, cheapest signal to capture: email bounces, declined meetings, new names on tickets and job-change data from an enrichment provider. Match each to the right account, which depends on clean identity resolution, and route it to the CSM within 48 hours.
Track usage change weekly. Compute week-over-week and 60-day changes in active users, core feature use and seat utilization per account, and alert on the size of the change. A 30 percent drop over 60 days is a suggested starting point, not a benchmark; tune it against your labeled renewals.
Bring commercial signals out of finance. Pipe failed payments, invoices more than 30 days late and procurement questions into the account timeline the CSM sees, and agree with finance which events notify CS and which stay with collections.
Give every escalation an owner and a date. When available runway falls below required runway, assign one named owner and an escalation date. After each renewal, record whether the escalation worked and feed the result back into required runway. Our NRR early-warning system post covers signal scoring in depth.
Workflow: who owns each stage of the renewal runway
Give each stage one owner and one output.
Signal events from all five families land on the account timeline with source and timestamp. Owner: CS operations or RevOps, who check daily that each feed still arrives.
Accounts whose available runway is below required runway are listed with what changed since last week. Owner: the CS leader, in a 30-minute review with CSMs.
The named owner builds a save plan within a set number of days: who to meet, what value to show, which sponsor to involve. Owner: the CSM or account manager.
Any discount or term change offered to save a renewal is a recorded decision with a reason and an approver. Owner: the CS leader with finance.
Every lost, contracted or discounted renewal is checked against its first signal and escalation dates, leakage is reported in dollars by account, and required runway is updated. Owner: RevOps with the CS leader.
Board narrative: how to report renewal leakage
Boards hear about churn every quarter. Renewal leakage shows them the part the company could have prevented.
"Of the ARR we lost or discounted at renewal this half, we can show which accounts had a clear risk signal more than a save cycle before we acted. That is our renewal leakage, and we know the amount and the accounts."
"The signals were recorded, but in systems the renewal owner did not watch, and our process started on a fixed date rather than on risk. Champion changes reached the CSM weeks late."
"Every account now has a notice deadline, a required runway based on our own history and a named owner when it slips. We will report leakage each quarter, and we expect the gap between first signal and first action to shrink."
Cross-domain: where renewal leakage connects to the rest of the engine
Renewals are where every earlier gap shows up as a number, so the fix cannot sit in customer success alone.
Renewal Radar tracks each renewal against the runway a save has historically needed for an account like it, escalates on account signals rather than the contract date, assigns a named owner and an escalation date, and shows what changed since last week. It escalates and schedules; it never commits your team to a discount or a concession. Upstream, the Churn Signal Watchtower scores the individual signals, showing each one and when it fired. Downstream, the Board Report Engine reports retention from the same numbers.
Each is one of the nine systems a revenue engine needs. Each starts read-only, logs every action with its reason, and is tested on around 20 of your own past cases before going live; for Renewal Radar, your last 20 renewals marked renewed, churned or saved late. It ships at 85 percent or it does not ship. The full set is on the systems page.
Frequently asked questions
What is renewal leakage?
Renewal leakage is recurring revenue lost at renewal that earlier action could have kept. It includes churned accounts, contractions and save discounts where a clear risk signal, such as a champion leaving or usage falling, appeared well before anyone acted. It is the preventable share of churn, as opposed to churn caused by product fit or market changes that no renewal process could have reversed.
What are the early warning signs of customer churn?
The most reliable early warning signs are a champion or executive sponsor leaving, a sustained fall in active users or core feature use, seats dropping below the contracted amount, escalated or repeated support tickets, failed or late payments, and no outcome review for two quarters or more. A single sharp change in one of these usually matters more than a gradual dip in a composite health score.
How early should you start the renewal process?
Start based on risk and the notice deadline, not a fixed number of days before the end date. Healthy accounts can follow a standard cycle, often 90 to 120 days out. Accounts with a risk signal should start as soon as the time left before the notice deadline is shorter than the time saves have historically taken for similar accounts, which can mean six months or more.
What should you do when a champion leaves a customer account?
Act within days, not at the next renewal. Confirm who now owns the budget and the outcome, introduce yourself and an executive sponsor, and offer a short review of the results achieved so far. Update the contact roles in the CRM, flag the account for weekly review, and check whether the departing champion has joined a company that could become a new customer.
How do you measure renewal risk in the CRM?
Store the contract end date, notice period and notice deadline as fields, then calculate the days left before the notice deadline. Compare that with the time saves have taken for similar accounts in your history. Record each risk signal as a dated event on the account, so the renewal owner sees what fired and when instead of relying only on a health score color.
Sources: SaaS Capital, 2025 retention benchmarks; Gartner, 2025 survey; ChurnZero on Sturdy research (sample and method undisclosed); TSIA, 2026 (denominator undisclosed); BLS, 2026 tenure; Vendr renewal guidance (buyer advice). Hook preview and Recurly link supplied with the draft were unavailable at review; their figures were removed.
