When Does Customer Success Become Value Realisation Rather Than Adoption Reporting?

When does customer success become value realisation rather than adoption reporting?

A fairly straightforward question to answer as it happens. In fact, throw it to an AI colleague, Chat, Claude, Gemini or one of many others and they pretty much all say the same thing: “Customer success becomes value realisation when adoption stops being the outcome and starts being the evidence”. AI then goes on a long-winded rant justifying its answer whilst still giving itself enough wriggle room for us to spend further tokens challenging it, correcting itself, yet still being correct enough in the first place for us to keep using it.

AI did pretty well, although I would say adoption is part of the chain of evidence, not the evidence itself.

But that’s not really the question we’re posing, is it?

AI has just focused on the ‘When’ and taken this question as a chronological challenge.

The real question lies beneath. ‘What has changed in the business, that necessitates Customer Success to move beyond adoption reporting towards value realisation’. And for that, we must delve a little deeper.

But first, let’s touch on the ‘When’?

The question itself hints at a journey undertaken, SAP term this ‘The Customer Value Journey’ (CVJ). Part of the Customer Lifecycle, the CVJ is the underlying chronological path that a customer takes. Although not quite a journey of the scale of the Odyssey, nonetheless, it still requires strong leadership, smart strategy and teamwork (spoiler alert for those of us without a background in the Greek Classics: something Odysseus could have done with!)

As this is an independent SAP publishing platform, let’s base our ‘adoption vs value’ question on SAP’s Customer Value Journey (CVJ):

Discover — explore potential
Select — build the vision
Adopt — deliver the promise
Derive — maximize value
Extend — innovate and grow
Influence — shape the portfolio (running across the whole journey)

(In April 2026, SAP announced the creation of an operational team, The Customer Value Group, and added concrete service portfolios, The Success Plans, to manage this path. Although the term ‘CVJ’ is less prominent than before, the six definitions above are still the official blueprint for how SAP maps a customer’s progression from a prospect to a lifelong advocate).

The first step on the chronological journey to value is “Licence Metrics”. Sitting in the Select phase, this is when the SAP sales team and the customer agree on the number of licences required. Once implemented and successfully live, we enter the Adopt phase.

Known as the Deliver the Promise phase, this starts with the customer using the solution and “Licence Consumption” begins.

“Feature and Functionality consumption” is then the bridge that connects “Licence Consumption” to “Solution Adoption”. It tracks which capabilities within the software are being used, how often, and by whom.

Moving into the Derive phase to maximise value, the customer must adopt the solution. Strong solution adoption means usage has become a habit and it’s fully embedded into the customers’ processes and operations.

Good adoption reporting takes the feature and functionality consumption metric and overlays dataflow, operating procedures and user behaviour.

Take SAP SuccessFactors Performance & Goals. The licence metric is based on active user profiles, so a customer with 9,250 active users against 10,001 purchased licences would appear to have a very healthy, 92.49% licence consumption.

Having over 90% licence consumption gives customers solid green ticks in SAP for Me and the Customer Success team are seeing the same positive result in Gainsight.

But good adoption reports should investigate: Are employees creating and updating goals? Are managers reviewing progress and providing feedback? Are performance reviews being completed? Are continuous performance activities being used throughout the year, or does everyone simply log in when the annual review cycle arrives?

Great. But so what?

Are managers now having better performance conversations? Are employees clearer on their goals? Has performance improved? Has unwanted attrition reduced? Has the organisation become better at identifying and developing its high performers?

“Adoption Reporting” is a very useful utilisation metric… but it’s still just operational data.

Qualify, quantify, articulate

As solution adoption strengthens, the focus shifts further into the Derive phase and towards: “Value Realisation”.

I break value realisation into 3 steps. Qualify, Quantify and Articulate.

Qualify — Has something changed? Work with the customer to confirm something meaningful has changed through adopting and consuming the solution’s functionality. Not assumed change. Evidenced change.

Quantify — What was that change worth? Help the customer put a number against that value. Time saved. Cost reduced. Revenue increased. Risk avoided. Whatever matters to their business.

Articulate — Can the customer state and understand the value of that change? Help the customer put that success into words. A simple statement of value that their stakeholders can understand and rally around.

The QQA framework isn’t there so Customer Success can prove that the software created $Xm of value. It’s a discipline for working with the customer to establish whether value exists, what contributed to it, what it’s worth, and whether the customer agrees. Because ultimately, who gets to say value was created? Not the Customer Success Manager!

Qualify, quantify, articulate the value, and we haven’t just delivered a solution. We’ve helped the customer unlock the full lifetime value of the decision to buy it in the first place.

The next step on the path is “Value Extension”, sitting in the Extend phase. This is where innovation, growth and potential further purchase help the customer extend the barriers of the value they are deriving from having selected and adopted the solution. And once they look beyond the current horizon, they start the cycle again with Discover.

So, we’ve established when customer success becomes value realisation rather than adoption reporting. It is indeed when adoption stops being the outcome and starts being part of the chain of evidence.

But why this focus on proving a customer’s business is more efficient, effective, attractive from using said product/solution?

What is this maniacal focus on customer success? Afterall, Customer Success teams don’t create success… Although, they can create the condition for it.

So, what has changed in the business, that necessitates customer success to move beyond licence consumption and adoption reporting towards value realisation?

Three things have changed:

1 – The customer has changed

For a while now, we’ve known that customers don’t buy software, they buy outcomes. Software is just one part of the equation. What people do around the software matters just as much as the software itself. But with greater interconnected businesses and more commercially sophisticated departments and leaders, comes greater individual responsibility and accountability for investment decisions. A customer stakeholder or sponsor isn’t just simply implementing software; they’re increasingly expected to defend the outcome.

Talking of customer stakeholder, they are not the same person they were before. They’re not even in the same department! Like many other technological advancements, SaaS has democratised the buying power of the software. By reducing the dependence on IT as the gatekeeper, the “Business” is increasingly choosing and funding the technology. The outcome of this is the person buying the solution is much closer to the business outcome and therefore much more exposed if it doesn’t happen.

Twenty years ago, an IT leader might have been accountable for whether the system worked. Today, a CFO isn’t merely accountable for whether the finance platform runs; they’re accountable for the performance of Finance, particularly regarding its financial data integrity and compliance.

2 – The economics have changed

Two things customers are very reluctant to change, ERP and Payroll. Everything else is less certain. Historically vendors benefitted from technological lock-in. But now with cloud architecture, APIs, data portability and AI, many solutions are easily replaceable.

As part of that technological evolution, vendors have evolved from software sales to recurring revenue companies. Previously, vendors could sell the licence, implement the technology and demonstrate that people were using it. Commercial success had largely already happened. In recurring revenue, the customer makes the buying decision at every contract term, with the aforementioned CFO having to demonstrate the value at each turn. The original business case no longer gets a free pass.

Stickiness and value are becoming less synonymous, so adoption reporting becomes insufficient when continued usage is no longer adequate justification for continued investment.

Ultimately, the vendor hasn’t finished selling after the initial sale, and the customer hasn’t finished buying. Whilst the term ‘post-sales’ is still the industry standard for everything that happens after a contract is signed, it is increasingly seen as outdated.

3 – The evidence has changed

It is still easier to count licences and report on solution adoption than it is to qualify, quantify and articulate value. Better reporting, increased analytics and now AI, give both customer and vendor exceptional visibility into consumption, behaviour, process and performance. In the SAP world, a customer with WalkMe, Signavio and LeanIX, and SAP for Me as the admin control tower can manage their account, map processes, track performance, monitor behaviours, detect active applications, highlight technical debt and fix process friction.

Yes, very important, but still just operational data, not customer-realised value.

And here, I must touch on AI again. AI is shortening the expected time-to-value. It isn’t just improving the ability to interrogate, analyse and report on value, it’s changing expectations and how quickly value should appear. If something promises more efficiency and effectiveness, customers are expecting near instantaneous evidence rather than after a three-year transformation programme.

Whilst AI-enhanced analytics makes adoption reporting incredibly sophisticated it also makes “So what changed?” much harder to avoid. More commercially sophisticated leaders ask that question more often. Subscription economics makes vendors pay attention to it. Ease of replaceability and increased choice makes the consequence of failing the test more significant. And stakeholder accountability makes it personal.

Ironically, with these AI operational insights, the more we can measure, the less acceptable it becomes merely to report what was used. Although there exists an AI paradox where the easier it is to create a convincing value story, the more important it is that the customer believes it.

So, in conclusion, customer success becomes value realisation rather than adoption reporting when adoption stops being the outcome and starts being part of the chain of evidence.

Why? Because the customer has matured, the economics have evolved and our ability to understand what is happening has improved with them.

The challenge for Customer Success is to help the customer make the connection between what they’re doing with the software, what changed as a result and what that change is worth.

This is why customer success has never really been about just product adoption. It’s about helping customers qualify, quantify and articulate the link between the software, the customer’s desired outcome and the value realised.

I started this article talking about a chronological path, the Customer Value Journey and Odysseus. I’ll finish it with a final thought…

The destination isn’t adoption. Adoption just tells you you’re moving.

Michael Crawley is an independent advisor specialising in Customer Growth & Success. He writes here in a personal capacity. Articles are vendor- and firm-neutral.

Next: meet Michael Crawley — or meet all sapperment experts.