What renewal management means, the renewal lifecycle as a five-stage pipeline (review at 90 days, classify at 60, resolve, commercial at 30, confirm), how to run it in Salesforce and what Salesforce cannot see, the four renewal KPIs with formulas, and the three ways a renewal process looks fine while losing accounts.
Short answer
What is renewal management?
Renewal management is giving every contract that is due to renew an owner, a risk read and a plan, ninety days before the date. It is a pipeline with stages, not a calendar with reminders. The stages are 90 days (review), 60 days (classify: safe, at risk, lost), 30 days (commercial done), and the date itself, which should be a formality. The KPI that tells you the process works is how many of the renewals you lost were flagged at risk sixty days out.
Most SaaS teams manage renewals the way people manage dentist appointments: a date exists, somebody may or may not remember it, and the outcome is discovered on the day. This is the process that replaces that, the stages, the exit criteria for each, the four KPIs, and the three failure modes that make a renewal process look like it is working when it is not.
A renewal is a decision the customer makes on a schedule you set, and the decision is usually made weeks before anyone tells you. By the time a customer says they are not renewing, the champion has already stopped logging in, the usage has already dropped, and the replacement has often already been chosen. The renewal conversation at thirty days is not a negotiation; it is being informed.
The renewal process exists to move the conversation to where the decision actually happens, which is sixty to ninety days out, and to make sure the decision is made with your best information in front of the customer rather than their worst month.
| Stage | Starts | Exit criterion |
|---|---|---|
| Review | 90 days out | Date and terms confirmed, owner named, health read done, open issues listed |
| Classify | 60 days out | Account tagged safe, at risk, or lost, with the reason written down |
| Resolve | 60 to 30 days out | Every open issue on the at-risk list has an owner and a date, or a decision that it will not be fixed |
| Commercial | 30 days out | Terms proposed and accepted, expansion or downgrade agreed, paperwork sent |
| Confirm | Before the date | Signed, or auto-renewal acknowledged in writing by the customer |
The exit criteria are the process. A stage without one is a label, and a renewal that sits in “Review” for eighty days because nobody defined what reviewing means is the most common way this pipeline decays.
Three buckets, and the reason written next to each. Safe: usage stable or rising, no open problems, champion in place. At risk: one or more of those is false and there is something you can do about it. Lost: the customer has told you, or the signals say the decision is made and there is nothing left to fix. The point of the third bucket is to stop spending the next sixty days on accounts that are gone and spend them on the ones that are not.
The at-risk list is where the money is. Each account on it gets a plan with a date: the ticket closed by Friday, the executive call booked next week, the unused module either adopted or removed from the renewal so the customer is not paying for something they do not use. A renewal saved by removing a module is still a renewal.
The mechanics are straightforward: create a renewal opportunity when the original deal closes, close date equal to the renewal date, amount equal to the current contract value, stages named after the pipeline above. Reports on that object give you gross and net renewal rates and the age of every renewal in each stage.
What Salesforce cannot do is classify the account, because the classification comes from usage, support and billing, and Salesforce holds none of those unless something writes them in. The teams that make this work either sync a health score into the opportunity or run the pipeline from a tool that reads the signals directly and writes the stage back. The teams that do neither have a renewal pipeline whose stages are updated when somebody remembers, which is the calendar again with extra fields.
| KPI | Formula | What it tells you |
|---|---|---|
| Gross renewal rate | renewed value ÷ value up for renewal | How much contracted revenue survived, before expansion |
| Net renewal rate | (renewed + expansion) ÷ value up for renewal | Whether upsell at renewal covered the losses |
| Early confirmation share | renewals confirmed 30+ days out ÷ all renewals | Whether the commercial stage is finishing on time |
| Flagged-loss share | churned renewals flagged at risk at 60 days ÷ churned renewals | Whether the process saw the losses coming |
The last row is the one to watch first. A flagged-loss share near zero with real churn means the classification step is not reading the signals; the process is running, and it is blind. Fix that before tuning anything else, because every other stage acts on the classification.
Renewal management is the process of making sure every contract that is due to renew has an owner, a risk read, and a plan, early enough that the plan can change the outcome. In SaaS it covers the 90 days before a renewal date: confirming the date and the commercial terms, reading the account's health, resolving open problems, and getting the renewal confirmed rather than assumed. The opposite of renewal management is finding out an account left when the invoice bounced.
The renewal lifecycle is the sequence every contract goes through: signature, adoption, a value check partway through the term, a renewal window that opens 90 days before the end date, a decision, and either a new term or an exit. Renewal lifecycle management means treating that sequence as a pipeline with stages and exit criteria, the way a sales team treats new business, instead of a date on a calendar.
Ninety days before the renewal date for annual contracts, which is enough time to fix a problem that would otherwise decide the outcome. Sixty days is the point at which the account should be classified as safe, at risk, or lost, and thirty days is the point at which the commercial conversation should already be finished. For monthly plans there is no renewal window to speak of; the equivalent is the failed-payment window, which is measured in days.
Create a renewal opportunity when the original contract closes, with a close date equal to the renewal date and an amount equal to the current contract value, then move it through renewal-specific stages (90-day review, at-risk, commercial, confirmed). The trap is that Salesforce only knows what someone typed: it will hold the renewal date and the amount, but the health read that decides the stage has to come from product usage, support and billing, which live elsewhere. Sync those signals into the opportunity or run the stages from a tool that reads them.
Gross renewal rate (renewed contract value divided by contract value up for renewal, ignoring expansion), net renewal rate (the same with expansion included), renewals confirmed before the 30-day mark as a share of all renewals, and the share of churned renewals that were flagged at risk 60 days out. The last one tells you whether the process saw the losses coming; a process that flags nothing and loses accounts is a calendar, not a process.
Renewal management is about a decision the customer makes: whether to continue a term contract. Dunning is about a payment that failed on a plan the customer had not decided to leave. They need different responses. A renewal at risk needs a conversation about value; a failed card needs a card-update link and a retry schedule. Mixing them, for example by sending a renewal pitch to a customer whose card simply expired, is how a billing error becomes a cancellation.
The stage names and windows are the ones Exeechain uses on its own renewals board, where each contract is timed to its actual renewal date from billing and classified from the connected signals rather than typed in. The KPIs are standard definitions; the flagged-loss share is the one we added, because a renewal process that cannot show it saw the losses coming cannot be improved. The retention curve and gross revenue retention guides cover the metrics that sit around renewal rate.
Keep reading
Retention metrics
8 min read · Sep 20, 2026
Customer success
8 min read · Sep 20, 2026
Churn prediction
9 min read · Sep 20, 2026
First scores in 15 minutes. Full accuracy in 24 hours. From $299/mo. Renewal dates from billing, risk from usage and support, the save drafted for approval.
Not ready to switch? Size your leak from your MRR and churn rate, with no billing access at all.