Renewal management is the operational discipline of carrying a customer from “signed” to “re-signed” without losing revenue you already earned. Done well, it is not a 30-day scramble before the contract date — it is a forecast you maintain all year, a risk signal you act on a quarter early, and a process that turns the renewal into a non-event. This is a how-to: the steps below assume a B2B SaaS book of business and a CSM (or CS Ops) who owns the number.
Prerequisites
- A source of truth for contract dates. The renewal date, ARR, term, and auto-renew clause live in your CRM (HubSpot, Salesforce) or CS platform (Gainsight, ChurnZero — pick one and make it authoritative). If two systems disagree on the renewal date, you have no process.
- A health score you trust. See customer health score. Renewal forecasting leans on it; a score nobody believes is worse than no score.
- A segmentation model. Tech-touch accounts under a threshold (say, under $15K ARR) get an automated motion; high-ARR accounts get a named owner and a playbook. See customer segmentation.
Step 1 — Build the renewal forecast
Pull every account with a renewal date in the next four quarters into one view. For each, record ARR up for renewal, current health score, and a renewal likelihood category. Use three categories, not a false-precision percentage:
- Commit — high health, champion engaged, no open escalations. You expect this to renew at or above current ARR.
- Best case — renewal probable but a risk exists (usage dip, champion change, pricing pushback). Needs work.
- At risk — active churn signal. Needs an intervention plan now.
Forecasted renewal ARR = sum of Commit + a haircut on Best case (50-70% is a sane starting weight) + near-zero on At risk until the signal clears. Refresh weekly for the current quarter, monthly beyond.
Step 2 — Surface risk early (the 120-day rule)
The single most impactful move in renewal management is moving the risk conversation earlier. A renewal “discovered” 30 days out is already lost or already safe — you have no time to change the outcome. Open the renewal motion 120 days before the contract date for high-ARR accounts, 90 days for mid-market.
Risk signals to monitor continuously, not at renewal time:
- Usage decline. A drop in active seats or core-feature usage over a trailing 30-60 days. This is the earliest and most reliable signal.
- Champion departure. Your champion left or changed roles. Re-establish a new sponsor immediately; a renewal with no internal advocate is a coin flip.
- Support/escalation load. A spike in tickets, or an unresolved P1, going into the renewal window.
- Value gap. The customer never reached the outcome they bought. See time to value — a customer still pre-value at renewal will not renew on faith.
- Silence. No logins from the buying committee, no response to QBR scheduling. Disengagement predicts churn better than any complaint.
Wire these into alerts in your CS platform so the CSM is paged when a signal fires, not when the date arrives.
Step 3 — Run the renewal play
For At risk and Best case accounts, run an explicit sequence:
- Diagnose. Name the specific risk in one sentence (“champion left, no replacement; usage down 40% QoQ”). Vague risk gets vague intervention.
- Re-establish value. Hold a value-realization review tied to the outcome the customer bought — not a feature demo. Bring usage data and the original success criteria.
- Multi-thread. Add a second and third contact at the account. Single-threaded renewals die when the one person you know leaves.
- Handle commercials early. Surface price increases, seat true-ups, and multi-year terms 90+ days out. A pricing surprise at the contract date is a self-inflicted churn cause.
- Get a verbal commit, then paper it. A signed order form on the last day with no prior conversation is not a renewal you managed — it is one you got lucky on.
Step 4 — Close and capture the why
On renewal, record the outcome and the reason. For churned and downsold accounts, run a structured loss reason (price, product gap, champion loss, M&A, no value realized). Feed it back into onboarding and product. A renewal program that does not capture why accounts leave cannot reduce at-renewal churn — it can only react to it. See customer churn and churn rate calculation.
Success criteria
- GRR is trending up quarter over quarter (the leaky-bucket measure; see NRR vs GRR).
- Zero “surprise” churns — every churn was forecast At risk at least 60 days prior.
- Forecast accuracy within 5-10 points of actual renewed ARR by mid-quarter.
Common pitfalls
- Treating renewal as a date, not a process. Guard: the 120-day open in Step 2 and a year-round forecast in Step 1.
- Trusting auto-renew to do the work. Auto-renew reduces churn on healthy accounts and hides risk on unhealthy ones. Guard: run the full play on At risk accounts regardless of the auto-renew clause.
- Single-threading. Guard: the multi-thread requirement in Step 3 — no high-ARR renewal proceeds on one contact.
- Confusing renewal with expansion. They are different motions. Secure the renewal first; pursue expansion revenue from a position of strength, not as a bargaining chip to save a renewal.
Related
- Customer health score — the input to the forecast
- Customer churn — the outcome you are preventing
- NRR vs GRR — how renewals show up in retention metrics
- Expansion revenue — the upside motion after the renewal is secure