Value Realization

Value realization is the work of achieving and measuring the benefits that were promised during the sale. The commercial case for it is simple: a business case that overstates value produces a renewal conversation that nobody wants to have. The operational difficulty is that the people who made the promise and the people who have to deliver it are usually in different departments with different incentives.

The value realization gap

Large technology programmes often fall short of what was promised. BCG's study of digital transformations found that 70% fell short of their objectives. The wider pattern in B2B purchases is covered in our 2026 research.

Source. BCG, Flipping the Odds of Digital Transformation Success, 29 October 2020—a survey of 825 senior executives plus BCG data on 70 companies. The figure is about digital transformations, not every technology purchase.

The recurring causes of that gap are unglamorous:

• No baseline: nothing was measured before implementation, so improvement cannot be shown
• Partial adoption: the team uses two of the six capabilities the case relied on
• Priorities moved: the driver that justified the purchase stopped mattering
• Nobody owns measurement: the case is filed, not tracked

The fourth cause is the one an organisation can fix without buying anything. Someone has to be accountable for reporting actual benefit against promised benefit, on a schedule, with the authority to say the number is behind.

The lifecycle

Before the sale

Document the expected outcomes as metrics, with a baseline and a date, in the business case. Agree with the buyer which figures will be reported and who will supply them. A case that names its measurement sources up front is much harder to inflate.

During implementation

Map delivery milestones to value milestones; the first of these is the customer's time to value. Track adoption, because adoption is the leading indicator that determines whether the benefit arrives at all. Look for a first real win and verify it with the buyer's numbers rather than announcing it.

After go-live

Review quarterly, compare actual against promised, record where value arrived that the case did not anticipate, and say clearly when a driver is failing. A value review that only reports good news stops being read within two quarters.

Leading and lagging indicators

Adoption is the leading indicator: licences activated, workflows actually run, people trained, processes followed. Benefit is the lagging one: hours released, cost removed, revenue influenced. A review that reports only lagging indicators tells you in month nine what you needed to know in month two, which is why the quarterly review should open with adoption and close with benefit.

A worked example

A business case promises £240,000 a year in benefit. That figure is a run-rate once the system is fully in use, which means the first year does not deliver it. A realistic ramp is 20%, 45%, 70% and 100% of a quarter's share of the annual figure, or £12,000, £27,000, £42,000 and £60,000 across the four quarters.

So year one is planned at £141,000, not £240,000. That distinction alone prevents the most common false alarm in post-sale reviews, where a customer is described as 59% short in year one when the plan never expected otherwise.

Actual results come in at £9,000, £22,000, £31,000 and £38,000: £100,000 against a plan of £141,000, or 71% of plan, with a gap of £41,000. The fourth quarter is also the useful signal. £38,000 annualises to £152,000, so even if performance holds at the current rate, year two lands £88,000 below the promise.

That is the number to act on. A 71% quarter is a conversation; a run-rate that cannot reach the promise is a re-planning exercise, and it is much cheaper to have it in month twelve than at renewal.

How this shows up in a real deal

It appears in the second or third quarterly business review, when the customer's sponsor has changed and the new sponsor asks what the original case promised. If the vendor's only answer is a slide from the sales cycle, the relationship resets to a procurement negotiation. Teams that keep a live value tracker, with the promised drivers, the baseline, and the current figure on one page, get the same question and answer it with a number. In renewal deals the difference between those two positions is usually several points of price.

Reading further

How to build a CFO-ready business case for SaaS covers setting measurable drivers before the sale, which is where realization is decided. The value selling framework for enterprise sales places realization as the fifth stage of a cycle rather than an afterthought. The hidden cost of ungoverned value modeling puts a number on what happens when models are built and then abandoned. Your best deals are dying in procurement is about the earlier end of the same problem, and what value engineering means sets out the practice that links the two. If you are evaluating software for this, value realisation platforms are one of the five approaches compared in the value selling tool comparison.