Start customer success renewals six months before the date, not 60 days. Your buyer may already have your seat count. Run four checkpoints: usage at six months, the value case at four, the signer at three and the file at two. An AI agent does the prep. People keep price and terms.
Your buyer may count first
The average organization uses only 54% of its provisioned SaaS licenses, according to Zylo's 2026 SaaS Management Index, which calls the rest "46% unused or underutilized." Zylo is a SaaS management vendor that sells this analysis to the IT and procurement teams who review your renewal.
Zylo's advice to them: use the renewal to "potentially reduce license seats." The same index says the average organization manages 211 SaaS renewals a year. By our math that is roughly four a week, and yours is one line in the queue.
Two limits on the 54%. It is a portfolio average, so it says nothing about your product. And it comes from companies that pay Zylo to measure license use, so by our reading it is a picture of buyers who count. Not all of yours do. Ask your champion.
Now picture an illustrative 200-seat contract running at that average:
An illustrative contract at Zylo's 54% average, not customer data.
If your CSM last looked at seat usage at kickoff, the first person to bring up those 92 seats is likely to be the buyer, at the point in the cycle where you have the least time to change it. Then you are negotiating from the buyer's spreadsheet, on their schedule.
When should customer success start a renewal?
Customer success should start a renewal six to nine months before the renewal date. Base AI's renewal marketing guidance places the decision to renew, expand or churn in that window, based on adoption, sentiment and visible ROI. A CSM who starts 60 days out is negotiating a decision the customer has mostly made.
The renewal marketing glossary entry notes that most B2B companies treat renewal as a conversation in the 30 to 60 days before contract end. Six months is the latest start for the runway below. With nine months available, push each checkpoint back.
A reminder knows a date. It doesn't know that 92 seats are idle or that the signer has never seen a value case. Base AI's retention automation guidance is blunt: "Calendar-driven automation just adds noise."
A renewal plan decides things for each account. Which seats to activate. Which stakeholder needs the value case. When a person has to step in.
The checkpoints are our recommendation, not an industry standard. At each one, an AI agent does the prep and a person makes the call.
The runway, our recommendation. Terms come in the final 30 days.
Six months out: usage. The agent flags the gap between the contract and active seats and used features. The CSM decides what to do with it.
Four months out: the value case. The agent builds a customer-facing value case for every account. The CSM adds the story where it's needed.
Three months out: the signer. The agent checks who has seen the value case. The CSM reaches the signer and names who owns the commercial conversation.
Two months out: the file. The agent prepares it: seat utilization, the value case, the seat plan and who engaged. The named owner takes the conversation in the final 30 days.
Idle seats have three honest outcomes: activate them, reassign them or plan to give them back. Our view is that a vendor offering to right-size 30 of those 92 seats six months out keeps its credibility. One defending them a month out, against the buyer's own report, risks the seats and the price discussion.
Utilization cuts the other way too. Zylo tells buyers that a particularly high rate may mean they need more licenses. Route those accounts to an expansion play. Base AI's expansion solution scores accounts on usage maturity for that handoff.
How Vidyard reached every account
Built by hand, a value case reaches only the top accounts. Per the story of Vidyard, a Base AI customer, reps pulled data and compiled decks one account at a time, and high-quality QBRs were limited to select accounts. In the team's words: "It depended on the rep, and it wasn't consistent."
Vidyard built automated QBR hubs that pull customer data together for every account, designed in AI Studio through prompting. The story reports 100% QBR coverage: "Personalized QBRs for every customer, SMB included."
As Vidyard's customer story reports it. No renewal result yet.
We claim no renewal result. Vidyard's renewal hubs are, in the story's words, "in progress." It shows the precondition: a value case in front of every account. Base AI's retention solution is built for this, with QBRs generated on demand in a customer-facing hub.
When AI hands off: terms stay human
Your champion is often not the person who signs. So write the AI agent's handoff rule down in advance. Any one of our three conditions moves the account to a person:
The utilization gap found at six months hasn't narrowed.
The signer or economic buyer hasn't engaged with the value case.
The customer has raised price, scope or a competitor in any channel.
The final 30 days belong to the named owner. Zylo's 2026 index reports that 79% of IT leaders encountered price increases at SaaS renewal in the past 12 months. A price increase from you lands on a buyer who has most likely absorbed one already. That isn't a message to hand to an agent.
Measure a renewal runway by whether it reached each account in time, not by reminders sent. Reminders only prove the calendar worked. Track four numbers per renewing account: runway coverage, utilization gap closed, signer reached and surprises. Report them as leading indicators in your renewal forecast.
Runway coverage: accounts renewing in the next 90 days with a value case the customer has opened.
Utilization gap closed: seat utilization at six months compared with two months.
Signer reached: accounts where the economic buyer engaged before the three-month mark.
Surprises: renewals where the buyer raised usage data your team hadn't shown them. The target is zero.
We don't have a benchmark for what this does to renewal rates, and no Base customer has published one. Compare accounts that ran the full runway with those that didn't, over two or three cycles.
Pull every account renewing in the next six to nine months. Add one column: seat utilization today. Sort it from lowest to highest.
The top five rows are your first runway. Run the first checkpoint on them this week, before their procurement team runs it for you.
Key Takeaways
Buyers may count first. Per Zylo's 2026 index, the average organization uses 54% of provisioned licenses.
Start six months out. By 60 days, the customer has mostly decided.
Run four checkpoints. Usage, value case, signer and file, split between agent and CSM.
Keep terms human. Price, terms and escalations never go to an agent.
Frequently asked questions
When should customer success start a renewal?
Customer success should start a renewal six to nine months before the renewal date. Base AI's renewal marketing guidance places the customer's decision to renew, expand or churn in that window, based on adoption, sentiment and visible ROI. A CSM who starts 60 days out is negotiating a decision the customer has mostly made, sometimes with a utilization report already in hand.
How do AI agents help with customer success renewals?
AI agents help with customer success renewals by building the value case from usage data months before the renewal date. They flag the gap between active and contracted seats, publish a customer-facing value case for every account, keep each renewal plan on schedule and hand an account to a person when it needs one. People keep price, terms, exceptions and executive escalations.
How many SaaS licenses go unused or underutilized?
According to Zylo's 2026 SaaS Management Index, the average organization uses 54% of its provisioned licenses, leaving 46% unused or underutilized. Utilization was 47% the year before. Zylo is a SaaS management vendor, its figures come from more than 40M licenses under its management, and 54% is a portfolio average, not a figure for any single product.
Can a customer's procurement team see unused seats before the vendor's CSM?
A customer's IT or procurement team may see unused seats first. SaaS management vendors such as Zylo sell license utilization analysis to IT and procurement teams, and Zylo advises buyers to use the renewal to "potentially reduce license seats." Not every customer runs such a tool, so ask your champion at the six-month checkpoint whether theirs does, and count the seats yourself before the renewal conversation starts.
What should a customer success renewal playbook include?
A customer success renewal playbook should run on a timeline, not a reminder. Base AI's Renewal Runway, a recommendation rather than an industry standard, has four checkpoints: usage truth at six months, the value case at four, the signer and risk check at three, and the file at two. An AI agent flags, builds and prepares; the CSM decides, and the CSM or account manager named at three months owns the final 30 days.
Which parts of a customer success renewal should stay human?
Price, terms, exceptions and executive escalations should stay with people. Base AI's success automation guidance keeps difficult renewals, executive escalations, complex expansion cases and strategic relationship work with CSMs. An AI agent can still prepare the file: seat utilization by team, the value case and what the customer did with it, the agreed seat plan, and every stakeholder who engaged.
Customer experiences that drive NRR.
Building and scaling your advocacy program is easy when you can manage campaigns, rewards, track, and report - all within one AI platform.
