Renewal conversations are useful because they force clarity. The customer has to decide whether the product is worth continuing to pay for, and the vendor has to explain why the relationship should continue.
That is precisely why renewal is a poor place to discover, for the first time, whether the customer achieved what they bought.
By then, most of the customer journey has already happened.
Renewal shows the consequence, not necessarily the cause
When a renewal is at risk, the visible problem is commercial. The contract may reduce, the customer may delay, procurement may challenge price, a competitor may appear or the account may churn.
It is tempting to treat the renewal event as the problem. Often it is the point where an earlier problem becomes impossible to ignore.
Perhaps the expected outcome was never defined clearly. Perhaps sales and post-sale carried different versions of success. Perhaps implementation went live but the customer never reached meaningful adoption. Perhaps adoption happened but the evidence of business value never reached the stakeholder who needed it. Perhaps the original value was achieved and the customer now needs a new reason to continue.
Those are different situations, and a renewal process cannot fix all of them at the last minute.
Work backwards from the proof the customer will eventually need
Imagine the renewal conversation goes well. What would need to be true?
The customer can explain the result they achieved. There is credible evidence behind that explanation. The relevant stakeholders understand it. Remaining gaps are known rather than surprising. The next period has a reason to exist.
Now work backwards.
What would have needed to be visible earlier for that conversation to be easy? Which adoption signals would matter? What implementation milestones would matter? What customer behaviour would indicate progress? When should the first evidence of value have appeared, and who would need to see it?
This changes renewal from an isolated commercial event into the end of a longer evidence chain.
Risk scores are more useful when the route is understandable
A churn or health score may tell us that an account looks risky. It does not necessarily tell us why, or whether the cause is still changeable.
A customer that never reached a critical capability needs one kind of response. A customer with strong usage but weak executive value recognition needs another. A customer whose strategy has changed may need a completely different commercial conversation. A customer that has already achieved the original outcome may be ready for a new journey rather than a rescue plan.
The classification becomes more useful when it sits on top of an understandable route.
The journey needs evidence attached to it
The working route I use at Routeability is:
Outcome sold → Handoff → Deployment → First value → Adoption → Provable outcome → Renewal → Expansion
The important word is "provable".
A vendor can help a customer create value without being able to demonstrate it clearly. That can become a commercial problem when budgets are reviewed, leadership changes or procurement asks what the investment produced.
The evidence does not have to be a perfect ROI model. It does need to be credible enough for the relevant customer stakeholder. For some products that might be a financial measure. For others it may be risk reduction, operational improvement, time saved, capacity created or a business capability that did not exist before.
The form will vary. The discipline is to decide what evidence matters before renewal forces everyone to reconstruct it.
The useful intervention may sit much earlier
This is one reason Customer Success problems can be misdiagnosed.
The account is struggling at renewal, so the renewal process gets redesigned. The CSM is spending too much time chasing evidence, so the CSM process gets redesigned. The value story is weak, so a new QBR template is created.
Those changes may help. They may also be compensating for a break that happened upstream.
If the outcome was vague at the point of sale, the QBR cannot manufacture it later. If implementation never connected technical milestones to the customer's objective, a value deck cannot recover all of that context automatically. If product telemetry was never designed around the behaviours that matter, the CSM may be doing manual reconstruction every quarter.
The diagnostic question is therefore: where did the route first become unreliable?
Earlier visibility creates more options
When a problem is visible while the customer is still implementing or adopting, the business has more options. The plan can change, the right stakeholder can be brought in, the outcome can be clarified, a missing capability can be addressed, better evidence can be collected or a poor assumption can be discarded.
As renewal gets closer, the range of credible interventions narrows and the problem becomes more commercial.
That is the thinking behind the Revenue Diagnostic I am developing through Routeability: trace the route before jumping to the fix. What did the customer buy? How is value expected to happen? What evidence exists today? Where does confidence weaken? Which problem is observed and which is still only a plausible explanation? What remains unknown?
The question I would ask before renewal season is not simply, "Which accounts are red?"
It is:
For which customers can we already show a credible line from what they bought to what they have achieved?
Renewal should confirm a value story the organisation has been building with the customer. It should not be the moment everybody starts trying to find one.


