How to handle a renewal with data: a practical guide
A step-by-step guide to running a renewal on evidence: the four numbers to gather, when to start, and what to do when the usage data is unflattering for you.
Handling a renewal with data means walking into the conversation with a defensible account of what the customer paid, what they actually received, and what the next term is worth, assembled from product usage and the original business case rather than from a relationship and a slide.
Why most renewals are argued without evidence
The renewal conversation is usually the first time anyone revisits the promise that won the deal. A business case was built during the evaluation, a number was quoted, procurement approved it, and then the document went into a folder. Eighteen months later a different person at the customer asks whether the spend is justified, and the account team answers with adoption statistics and goodwill.
That answer fails for a structural reason. Adoption is a measure of your product's activity. The buyer's question is about their own outcome. A chart showing weekly active users does not tell a CFO what changed in the business, and the CFO is increasingly the person deciding.
Two findings from the 2026 State of B2B Buying Behavior report explain why this matters more than it used to. Deals die to indecision rather than to competitors, 61% of losses against 14% (Ebsta and Pavilion, across 4.2 million opportunities). And under 1% of deals carry a business case at all, though roughly half of those above $100k do (Minoa Research, around one million deals). A renewal is a purchase decision with the same failure mode. Absent a clear account of value, the safest thing for the buyer is to delay, flat-renew, or trim.
The four numbers to gather before the conversation
You do not need a data warehouse. You need four figures, each traceable to something the customer would recognise.
1. What was promised. Pull the original business case. Which use cases were in play, which drivers were quantified, and what annual return was claimed. If no business case exists, that is your first finding, and it changes the shape of this renewal: you are establishing a baseline rather than proving a result.
2. What was delivered. For each promised driver, the actual figure. Hours saved, tickets deflected, cycle time reduced, revenue influenced. Some of this is in your product. Some of it only the customer has, which is why you ask early rather than the week before.
3. What the gap is, honestly. Delivered against promised, driver by driver. Expect some drivers to overshoot and some to miss. A renewal deck where every number lands exactly on target reads as constructed, because it is.
4. What the next term is worth. The forward case, not the backward one. Which use cases are not live yet, what they would be worth, and what it would take to turn them on. This is the part that converts a renewal into an expansion conversation.
When to start
Ninety days before the renewal date for a six-figure account, and earlier if the champion has changed.
The reason is not negotiating leverage. It is that gathering number two above almost always requires something from the customer, and asking for it under time pressure turns a value review into an audit. Teams that start at ninety days get the data as a collaboration. Teams that start at thirty get it as a favour, or not at all.
If your champion has left, start earlier still and assume nothing carries over. The person who believed the original business case is gone, and their replacement inherited a line item with no story attached.
Running the conversation
Open with the gap, not the wins. Leading with your strongest number signals that the rest of the deck is selected, and a finance audience will read it that way. Leading with an honest account of where you fell short buys the credibility to be believed on where you did not.
Then move through the drivers in the order the customer cares about, not the order that flatters you. Attribute carefully: if a metric improved and your product was one of four changes that year, say so. Overclaiming a shared result is the fastest way to lose the room, and the claim you most need them to accept is usually the modest one.
Close on the forward case. The question you want on the table is not "was this worth it" but "what is the next year worth", and those are different conversations with different owners.
When the data is unflattering
Sometimes the numbers are bad. The usual causes are shallow adoption, a use case that was never switched on, or an original business case that was optimistic.
Say so first, in your own words, before the customer finds it. Then separate the explanation from the excuse. "Two of the four use cases never went live, here is what it would take to turn them on and what they are worth" is a plan. "Adoption has been challenging" is not.
A renewal where you name the shortfall and bring a credible remediation plan frequently survives. A renewal where the customer discovers the shortfall in your own deck rarely does.
What to automate and what not to
Assembling the numbers should be automatic. Pulling the original business case, mapping delivered outcomes against promised drivers, and flagging the gaps is repetitive work that gets done badly under time pressure, and it is the first thing to break when one person owns forty accounts. Platforms that carry the original case into the account and track outcomes against it, Minoa among them, exist to remove that step.
The judgement should not be automatic. Which gaps to lead with, how hard to push attribution, and whether this account is a renewal or an expansion conversation are decisions that depend on the relationship. Automating the assembly is what creates the time to make those decisions properly.
FAQ
How far ahead of the renewal date should I start?
Ninety days for a six-figure account, and earlier if the champion has changed or the account has had an incident. The constraint is not negotiation time, it is that proving delivered value usually needs data only the customer holds. Asking for it with three months to go reads as a joint review. Asking with three weeks to go reads as an audit, and you are likely to get a worse answer or no answer at all.
What if there was never an original business case?
Then this renewal is where you build the baseline rather than where you prove a result. Quantify what the customer has received over the past term using whatever evidence exists, agree the figures with them, and write them down as the starting point for the next term. You lose the ability to show promise against delivery this cycle, but you gain it for every cycle after. Under 1% of B2B deals carry a business case, so this is the common case rather than the exception.
Who should own proving value at renewal, customer success or sales?
Whoever owns the commercial outcome, with the other contributing data. The failure mode is splitting it: customer success reports on adoption, sales negotiates on price, and nobody presents a single account of value. The practical test is which function can answer "what did this customer get for their money last year" without scheduling a meeting to find out.
How do I justify a price increase with delivered value?
By making the comparison explicit and forward-looking. Show delivered value against the prior term's cost, then show the next term's projected value against the new price. A buyer will accept an increase when the ratio holds or improves and the numbers are ones they recognise. They will reject it when the only argument is a published list price, because that is a statement about your business rather than theirs.
Does proving value actually change renewal outcomes, or is it theatre?
The honest answer is that the evidence is strongest for a narrower claim than vendors usually make. What the data supports is that quantified, auditable cases are what a champion needs to get spend approved internally, and that deals without one are the ones most likely to stall undecided. A value review will not save an account that has not adopted the product. It changes the outcome where the value is real but unarticulated, which is a large share of flat renewals.
Ready to get started? Book a demo to see Minoa in action.