Renewal management is a ninety-day campaign that most teams start at day five. The renewal conversation starts ninety days before the contract ends. Review health at day ninety, have a value conversation at day sixty, present the proposal at day thirty. Day zero is a formality. Health review at ninety, value conversation at sixty, proposal at thirty: day zero is a formality.
QBRs are for the customer, not for you
The quarterly business review is not a report on your product's usage statistics. It is a strategic conversation about the customer's business and how you are helping them achieve their goals. If your QBR is a slide deck of login counts and feature adoption rates, you are doing it wrong.
The QBR that works: thirty minutes, three topics. Topic one is the customer's goals for the quarter and how you contributed. Topic two is what is not working and what you are doing about it. Topic three is what is next on your roadmap that maps to their needs. The customer should talk more than you do. If they are not engaged in the conversation, the QBR is a waste of both your time and theirs.
Support is a product feedback channel
Every support ticket is a product decision waiting to be made. A bug report is a quality issue. A how-to question is a UX issue. A feature request is a roadmap signal. If you are only resolving tickets without categorizing and analyzing them, you are throwing away your cheapest source of product intelligence.
Categorize every ticket: bug, UX confusion, feature request, or account issue. Review the categories weekly. If twenty percent of tickets are the same UX confusion, fix the UX. If ten customers request the same feature, consider building it. Support volume is a product health metric. Rising volume means your product is getting harder to use, not that your customers are getting needier.
Customer feedback should change your roadmap
If your roadmap looks the same after three months of customer feedback, you are not listening. Customer feedback should be the primary input to your product prioritization. Not the only input, but the primary one. The customers who use your product every day know things about it that you do not.
The system: collect feedback from support tickets, sales calls, customer success conversations, and NPS surveys. Categorize it by theme. Count the mentions. When a theme reaches ten mentions from different customers, it goes on the roadmap. This is not scientific, but it is better than building what the loudest customer asked for last week.
Renewals start ninety days before the contract ends
The renewal conversation does not start when the contract is up. It starts ninety days before. That is when you should be assessing health, identifying risks, and planning the expansion conversation. By the time the renewal date arrives, the outcome should already be determined by the value you have delivered.
The ninety-day renewal plan: day ninety, review the health score and usage data. Day sixty, have a value conversation with the champion: what have we accomplished together, what is next? Day thirty, address any concerns and present the renewal proposal. Day zero is a formality, not a negotiation. If you are negotiating on day zero, you started too late.
Expansion revenue is the cheapest revenue you will ever earn
Acquiring a new customer costs five to seven times more than expanding an existing one. Yet most early-stage companies spend ninety percent of their energy on new acquisition and ten percent on expansion. The math does not work. Your existing customers are your best growth channel.
The expansion playbook: identify the customers getting the most value, understand what else they need, and offer it before they ask. The signals for expansion readiness: high usage, multiple departments using the product, and a champion who is proactively engaged. The expansion conversation is not a upsell pitch. It is a strategic discussion about how you can help them more.
Frequently asked questions
When should the renewal process start?
Ninety days before the contract ends. Review the health score at day ninety, have a value conversation at day sixty, present the renewal at day thirty. By day zero, the outcome should already be decided by the value you delivered.
What does the day-sixty value conversation cover?
What have we accomplished together, and what is next. You are building the case file with the customer as co-author. A champion who can recite your value sells the renewal internally for you.
What if the health score is red at day ninety?
The renewal is now a save, and saves need people: executive sponsor calls, a recovery plan, visible fixes in sixty days. Do not send a renewal proposal to a red account; send help first.
How do I handle a customer who wants to negotiate at renewal?
Trade, do not concede: longer terms, case studies, or expanded scope in exchange for the number. A renewal negotiated on price alone tells you the value story was never documented. That is the real fix for next year.
What renewal rate should an early B2B company target?
Above ninety percent of the customers you should keep. Some churn is healthy: bad-fit customers cost more than they pay. Watch the renewals of the customers you wanted, not the blended rate.