A CRO I worked with last year ran his renewal forecast the same way every quarter. Thirty days before each contract expired, a CSM would email the customer, ask if they were "still happy," and report back a yes or a no. The yeses went in the forecast at full value. The nos triggered a panic. He called this his renewal process. It was really a coin flip with a calendar reminder attached.
The quarter I met him, three accounts that were marked "green, will renew" churned in the same two weeks. Total value lost: about $340,000. None of it was a surprise to anyone who looked at the usage data, because all three had stopped logging in months earlier. The data was sitting in the product. Nobody had built the system that surfaced it before the renewal date arrived.
That gap is what renewal management actually is. Not the renewal conversation, which any decent CSM can run. The system that tells you which renewals are at risk, when, and what to do about each one while you still have time to act. Most B2B SaaS companies under $30M in ARR do not have this system. They have a calendar reminder and a hope. Here is how to build the real thing.
What renewal management actually is
Renewal management is the operational process that takes a customer from "signed" to "re-signed" without anyone scrambling. It owns the renewal timeline, the risk scoring, the forecast, and the playbook for each risk tier. It is a RevOps function that happens to live close to customer success, the same way lead routing is a RevOps function that lives close to sales.
People confuse it with three other things, so let me draw the lines clearly. Renewal management is not customer success operations, though they overlap. CS ops builds the whole back office for the CS team. Renewal management is the specific slice of that focused on getting contracts re-signed. It is not your churn rate either. Churn is the number you report after the fact. Renewal management is the work you do before the fact to make that number better. And it is not the same as the renewal conversation, which is the last five percent. By the time someone is on a renewal call, the outcome is mostly already decided by what happened in the ninety days before it.
The simplest test: can someone on your team tell you, right now, which renewals in the next two quarters are at risk and why? If the answer takes more than an afternoon to pull together, you do not have renewal management. You have renewal hope.
Renewals lost in one quarter by a client whose accounts were marked "green" while the usage data said they were dead. The signals existed. No system surfaced them in time.
Why the 30-day model fails
The most common renewal process in B2B SaaS is what I call the 30-day fire drill. Someone notices a contract is expiring in a month, the CSM reaches out, and whatever happens next happens fast. This model has one fatal flaw: at 30 days, you are out of time to fix anything real.
There is a finding from renewal forecasting work that I quote to founders constantly. Renewal risk that surfaces at 90 days before renewal almost always existed at six months as well. The champion who went quiet, the usage that dropped off, the new admin who never got trained: all of that was visible months earlier. The 30-day model is not catching risk. It is confirming losses you already booked without knowing it.
The math gets worse when you look at volume. The average organization handles around 211 renewals a year, close to one every business day. If your only process is a manual outreach 30 days out, you are running a fire drill every single day, and the fires you are racing to put out started burning a quarter ago. No team wins that game. They just burn out playing it.
The fix is not more urgency. It is moving the work earlier and making it systematic, so the renewal date becomes a formality instead of a deadline.
The renewal timeline that actually works
Good renewal management runs on a clock that starts long before the contract date. The specific days vary by deal size and sales cycle, but the shape is consistent. Here is the timeline I set up for clients, built around four checkpoints.
The two checkpoints that matter most are the ones nobody runs: T-120 and T-90. This is where renewal forecasting tools agree the work belongs. The serious processes run risk scoring at two fixed points, six months and three months out, where an automated signal meets a human read of the account. By the time you hit 60 and 30 days, you are executing decisions you already made, not discovering new ones.
One client cut their surprise churn almost in half just by moving the first touch from 30 days to 120 days. Same team, same product, same customers. The only change was when they started looking. That is the whole game.
The risk signals to score on
A risk tier is only as good as the data behind it. Most teams score renewals on the CSM's gut, which is exactly the feelings-based forecast that blows up in board meetings. The fix is to score on signals you can pull automatically, then let the CSM adjust from there.
The signals that predict churn earliest are the behavioral ones. Login frequency is the clearest: a customer who logged in daily and drops to weekly is telling you something months before they tell you in words. Product usage depth matters more than logins alone, because a customer using one feature is far easier to replace than one wired into your platform across five. Support patterns cut both ways, where a spike in angry tickets is bad but total silence from a once-active account can be worse. And the single strongest signal is relationship: when your champion goes quiet or leaves, or a new admin you have never trained shows up, your renewal just got fragile no matter what the usage says.
This is where a real customer health score earns its place. A good health score is just these signals rolled into one number that updates on its own and feeds your renewal tiers. Salesforce built a churn prediction system that reads over 300 variables to flag at-risk accounts up to six months before renewal, and it lifted their gross retention by three points over 18 months. You do not need 300 variables. Five good ones, scored consistently, beat a spreadsheet of green cells colored in by hope.
A renewal you forecast at 30 days is a renewal you already lost or already won.
The work that changes the outcome happens at 120 and 90 days, when you still have room to fix a quiet champion or a usage drop. Move your process earlier and the renewal date stops being a deadline and starts being a formality.
Who should own renewals
This is the fight every leadership team has, and the answer matters more than people think because the wrong owner quietly drags down your renewal rate. The three common models are the AE owning it, the CSM owning it, or a dedicated renewals specialist owning it.
The data leans one way. In one industry debate, 63% of the audience voted that customer success should own the renewal and only 13% backed sales. More usefully, companies where CS owns renewals tend to see meaningfully higher renewal rates than those where sales leads, because a renewal is a retention motion, not a hunting one. The skills that win new logos are not the skills that quietly confirm existing value and keep a relationship warm.
But the honest answer depends on your gross retention. There is a clean rule of thumb I use. If your gross revenue retention is above 95%, let CS own renewals and free up sales to chase new logos, since your renewals are mostly administrative. If GRR sits below 90%, you have a real commercial problem at renewal, and that needs someone who can run a negotiation, which usually means sales or a dedicated renewals specialist. The product matters too. Something hard to rip out, like a system of record, renews more easily and suits CS ownership. Something easy to switch needs a sharper commercial hand.
Whoever owns it, the handoff has to be clean. The single biggest renewal leak I see is a fuzzy line between the AE who closed the deal and the CSM who has to renew it, which is the same problem as a broken sales-to-CS handoff. If the customer hears one story at signing and a different one at renewal, you have already lost trust before the conversation starts.
The benchmarks to hold yourself to
Numbers give you something to aim at, so here are the ones that matter for a B2B SaaS renewal program. Read them as targets, not as comfort.
Gross renewal rate is the cleaner measure of your renewal machine because it strips out expansion and shows you what you keep before any upsell. A median B2B SaaS company lands around 88 to 90% gross. Best in class pushes past 95%. The gap between those two numbers, on a $10M ARR base, is roughly $500K to $700K a year. That is the prize for building a real process instead of running fire drills.
Net renewal rate, where expansion is included, is where the bigger story lives. Top performers run net retention above 120%, which means the install base grows even with some churn baked in. That only happens when your renewal process also surfaces the expansion conversation on healthy accounts, which a 30-day scramble never has time to do. If you want to go deeper on that number, I wrote a full breakdown of net revenue retention and how to move it.
Building the system without buying Gainsight
You do not need a six-figure platform to run this. Most companies under $20M in ARR can build a working renewal management system on tools they already pay for, plus some glue. Here is the stack I deploy for clients.
Your CRM is the home base. Renewal date, contract value, owner, and risk tier all live as fields on the account record in HubSpot or Salesforce. If renewal dates are not a structured field in your CRM today, that is step one, because you cannot run a timeline off contracts buried in a folder. The product usage data is the fuel. You need logins, feature adoption, and active seats flowing back into the CRM, which is a reverse ETL job that pushes warehouse data onto the account record. The automation layer is the clock. A workflow in n8n or your CRM's native automation watches the renewal date and fires the T-120, T-90, T-60, and T-30 tasks to the right owner, so nobody has to remember. That is the whole system: a place to store it, data to score it, and a clock to run it.
This is exactly the kind of build we do in our CRM and RevOps work and our AI automation work. The unglamorous truth is that 80% of the value comes from the data plumbing and the timeline, not from any fancy AI churn model. Get the boring parts right first.
Renewals still a quarterly surprise?
Book a free 30-minute audit and we will show you the three signals your current process is missing and the timeline we would build first.
Book an audit →Frequently asked questions
What is the difference between renewal management and customer success?
Customer success drives the customer toward outcomes across the whole relationship. Renewal management is the specific operational process that gets the contract re-signed: the timeline, the risk scoring, the forecast, and the play for each tier. CS is the broader job. Renewal management is the system that makes the renewal part of that job predictable instead of a scramble.
When should we start managing renewals as a formal process?
Earlier than most teams think. Once you pass roughly 50 active accounts or your renewal forecast starts missing by more than 15%, the manual approach breaks. You do not need a hire on day one. You need a renewal date field in your CRM, a basic risk score, and a timeline that starts at 120 days. The process matters more than the headcount at first.
Who should own the renewal, sales or customer success?
It depends on your gross retention. Above 95% GRR, let customer success own it, since renewals are mostly confirming value your product already delivers. Below 90% GRR, renewals carry real commercial risk and need sales or a dedicated renewals specialist who can run a negotiation. The product matters too: something hard to switch away from suits CS ownership.
How early can we actually predict a churn?
Most churn is visible up to six months before the renewal date. The signals are behavioral: a drop in login frequency, shrinking feature usage, a champion who goes quiet, or a new admin who was never trained. These show up long before a cancel email. The reason teams get surprised is not that the signals were missing. It is that no system was watching for them.
Do we need an expensive platform like Gainsight to do this?
No. Companies under $20M in ARR can run a solid renewal system on their existing CRM plus an automation tool. You need three things: renewal data as structured fields, product usage flowing into the account record, and a workflow that fires the timeline tasks automatically. A dedicated platform helps at scale, but the process and the data plumbing deliver most of the value first.
The bottom line
Renewals are the cheapest revenue you will ever book and the easiest to lose to neglect. The companies that keep 95% of their base are not better at renewal conversations. They are better at knowing which renewals need a conversation, and when, while there is still time to change the outcome. That is a system, not a skill, and it is buildable on tools you already own.
If your renewal forecast is really a feeling, and your churn keeps showing up as a surprise, the fix is not a bigger CS team. It is a process that starts at 120 days. That is the system we build, and we are happy to show you where yours is leaking.