Cost is tracked as a financial discipline. Value rarely is. We trace where the value chain breaks, independent of the vendors who built it.
Risk priced before the deal closes.
Margin recovered. No new capital.
An independent number, not an estimate.
Value recovered from what's already deployed.
It isn't a technology problem. It's a measurement problem.
Every dollar leaving without return, identified and sized.
Technology already in place, unmapped to business outcomes.
Prioritised by impact. Delivered in five weeks. Yours to keep.
The short version is above. For anyone who wants the process and a live example before signing off, it's here.
Three illustrative profiles. Pick one, then open any bar for the evidence behind it.
Most organisations know their technology spend is underperforming. Few understand why, or that the shortfall is measurable, structural, and recoverable. These pieces set out both.
The diagnostic is a single engagement with a single output: a financially expressed, evidence-graded assessment of what a technology investment is actually returning. The roles that commission it share one thing in common. They are making consequential decisions and need a number they can defend.
A technology value number, whether you're buying, holding, or selling. The diagnostic is structured to serve all three points in the investment cycle.
Before capital is committed, an independent, evidence-graded read on whether the technology estate is recoverable value or embedded risk, expressed in terms an investment committee will recognise.
Technology spend is a significant, often under-scrutinised operating cost. Identifying what it's returning and what dormant capability can be activated without new capital is a direct input to EBITDA improvement.
Value identified before a process opens is multiple-able; the same value found during buyer due diligence becomes a discount. The narrative is built on the seller's timeline.
What you get: an independent, evidence-graded assessment expressed as leakage recovered and opportunity activated, structured for the investment committee, the information memorandum, or both, in five weeks at fixed scope.
Technology risk surfaced before it becomes a deal problem. Findings that emerge late in a transaction create price renegotiations, conditions precedent, and sometimes deal failure. The diagnostic surfaces governance gaps, licence exposure, unmet compliance obligations, and transformation spend that hasn't delivered, early and evidence-graded rather than as opinion.
What you get: an independently produced risk and value assessment, not generated by either party to the transaction, with each finding's evidence basis stated so it can be challenged, defended, and relied on by advisors on both sides.
A return figure the board can act on. The technology team can report on delivery and uptime. It cannot produce a financially expressed return figure independent of its own interests, and that independence is the point: the board isn't asking whether the technology works, it's asking whether the investment is performing.
What you get: a board-ready report expressing return on IT investment in terms the board and investors recognise, findings graded by evidence quality, and a recovery roadmap sequenced by financial impact.
Margin recovery without a new capital programme. The most common source of recoverable margin in an established estate isn't operational inefficiency, it's value already paid for and left unclaimed.
Unactivated platform capability. Already licensed, already deployed; the return hasn't been claimed because configuration was never finished.
Duplicate and redundant spend. Acquisitions and decentralised purchasing leave overlapping tools; consolidation is recoverable at next renewal.
Vendor contracts above market. Without independent benchmarks, renewals run on the vendor's terms and the premium compounds each cycle.
What you get: a quantified leakage and recovery figure with a phased roadmap, immediate, short-term, and strategic actions sequenced by financial return. No new capital required.
An independent number to take to the board. The challenge for technology leaders is rarely capability, it's credibility: a figure produced by the team being evaluated will always carry that perception. An external, evidence-graded assessment removes it. The findings are yours to present; the independence is ours to provide.
What you get: an externally produced assessment you can present without qualification, evidence-graded, assumptions explicit, and a roadmap you can own and execute.
Every role above is dealing with the same underlying problem. Technology investment is significant, the question of what it's returning is legitimate, and the answer doesn't currently exist in a form that survives scrutiny from a board, an investor, or a buyer. The Value Signal Diagnostic was built to produce that answer.
Technology budgets have never been larger, and that alone has started to worry boards. Not because spend is high, but because so little of it can be traced through to a financial result. Systems get built, projects get closed out on schedule, and the return that justified the business case in the first place quietly fails to show up.
The scale of the shortfall shows up consistently across independent studies: roughly 7 in 10 digital transformation efforts miss their stated objectives, and a review of over 5,400 large IT projects put average realised value at 44 cents for every dollar of benefit expected going in. Neither figure is a fringe result. This is what happens on average. We use the term Value Gap for that cumulative shortfall between what a technology portfolio was projected to return and what it actually has.
It was never really about the technology
The reflex, when a system underperforms, is to blame the system. The research doesn't support that reflex. One review spanning 86 firm-level studies concluded that mismanagement, not the technology itself, is the most consistently overlooked cause of underperformance, and other work tracing return variance across companies found organisational factors, not differences in the software, explaining most of the gap between firms. Put two organisations on the same platform and you can still get two very different financial outcomes. Something other than the technology is doing the work of explaining that difference.
Think of value creation as a chain with three links: money has to become a working asset, the asset has to change how the business operates, and that operational change has to show up in the numbers. Break any one link and the rest of the chain stops mattering. Delivery can still be declared a success. The return simply never shows up on the other end.
The same four leaks, on repeat
None of this is a one-time event that eventually gets fixed. It's closer to a cycle that resets with every new investment.
Spend nobody's tracking piles up. New licences, subscriptions, and shadow tools slip in under governance's radar with every cycle. Some estimates put 10 to 30 percent of total technology spend against outcomes nobody can confirm.
Approval keeps running the same play. Close to half of executives admit to inflating projected benefits to get a business case over the line, and there's no sign that incentive has softened.
Go-live opens a fresh gap, every time. Process changes stall, adoption undershoots, nobody instruments benefit tracking, and the person accountable moves to a new role before any of it gets resolved. The spend already happened. The value never gets collected.
Renewals quietly reset the price upward. With no outside benchmark to push back against, vendors set the terms at every renewal, and the premium compounds year over year.
Governance investment and executive attention haven't made much of a dent in these four patterns, which suggests something underneath all of them is going unaddressed. That's what part two picks up.
Ask most technology leaders what their estate costs and you'll get an answer instantly. Ask what it's returning and the conversation stalls, even at organisations that track a huge amount of operational data. More dashboards rarely close that gap, because the shortfall isn't really about how much you're measuring. It's about whether you're measuring the thing that actually determines financial return.
Going live isn't the same as paying off
Most budget cycles close the moment a system ships, on the assumption that delivery is a reasonable stand-in for value delivered. It isn't, and the gap between the two is arguably the field's most persistent unsolved issue: almost nobody builds the infrastructure to check, after the fact, whether an investment actually produced what it was funded to produce. That absence feeds on itself. Every new business case gets built on top of a track record nobody can actually see, justified by assumptions that were never checked against what really happened last time, so the same mistakes keep resurfacing and the shortfall keeps growing.
Different technology, different mechanism
There's a detail most diagnostic work skips past: technology doesn't create value through one universal pathway. A tool that unlocks a new capability pays off through a different route than one that automates an existing task, and both are different again from something built to reduce risk or enforce a policy. Checking adoption numbers, or even usage numbers, tells you almost nothing about whether that specific value-creating pathway is actually working.
Take a CRM rollout that hits every adoption target on paper and still never moves revenue, because the underlying sales process it was meant to change stayed exactly the same. The programme dashboard is green from end to end. The P&L doesn't move.
Plenty of data, not much proof
This isn't a case of too little information. If anything, most organisations are drowning in operational data about their technology estate and still can't answer the one question that matters, because none of that data was ever connected to the question of return. Cost reporting is thorough. Return reporting barely exists. A synthesis spanning three decades of IT productivity research lands on the same conclusion: underperformance traces back to the organisational conditions surrounding a system far more often than to the system itself. The tools change every few years. This particular failure mode doesn't.
Once you accept that the measurement gap is structural rather than a data shortage, the next move is building an instrument aimed at the right question, which is what part three sets out.
Most reviews stop at "was it built, was it adopted." That's the wrong pair of questions for a portfolio-level answer a board can actually rely on. The question that matters is narrower and harder: what specific mechanism was this technology meant to use to generate financial value, and is that mechanism actually running today? Answering it properly, across an entire estate, takes a purpose-built instrument rather than a more detailed version of the same status report.
Follow the mechanism, not the rollout
Deployment is usually where the assessment stops. A mechanism-first approach keeps going, asking of every asset in the estate: what's the actual pathway by which this is supposed to generate financial return, and is that pathway open? Some assets unlock a capability that didn't exist before. Others automate labour, cut friction, enforce a policy, or protect institutional knowledge, and each of those pathways fails in a different way when it fails. Treating all of them as interchangeable is a big part of why so much value never gets recovered.
Three moments when this stops being optional
Three situations turn this from a good idea into something that needs an answer now.
Pre-exit. Before it's an operating issue, the Value Gap is a valuation issue. Whatever recoverable value gets identified before a sale process opens can be reflected directly in the multiple. The diagnostic pre-empts what a buyer would find, produced by someone with no stake in either side of the deal.
Margin. Recovering value from something already deployed doesn't require new capital or carry delivery risk, because the spend already happened. What's missing is simply a way to find where the chain broke between that spend and the return it was meant to produce.
Board. Being unable to say what the technology estate is actually returning has stopped being acceptable. What's needed is an answer built to survive challenge: evidence graded by strength, assumptions stated up front, findings that can be tested.
None of this has to stay this way
The research doesn't leave much ambiguity here: technology investment underperforms because the conditions that turn spend into financial performance go missing, get mismanaged, or never get measured in the first place, not because the technology itself is faulty. Those conditions can be found, sized, and managed. Once that happens, a technology estate stops behaving like a cost centre that has to keep justifying itself and starts behaving like an asset that produces a measurable return.
The Value Gap isn't a technology problem. It's a measurement problem, and measurement problems can be solved.
Know the range. Understand the assumptions. Close the gap.
No. Most recoverable value sits inside platforms you've already purchased and licensed. The diagnostic finds it and shows you how to activate it; it doesn't sell you anything new.
No. It's used often in that moment, but just as often by a CFO or operating team who simply wants an honest answer on whether technology spend is earning its keep.
Very little. A handful of short interviews spread across five weeks, no data migrations, and no ongoing dependency once the findings are handed over.
Warren Gabryk, personally, from commissioning through to delivery. This isn't scoped by a principal and handed to a delivery team.
Yes. It's produced outside of any vendor, integrator, or internal team with a stake in the existing technology estate, so the findings aren't shaped by an incentive to protect or replace anything specific.
A board ready plan that itemises exactly where value is leaking and where it's stranded, each finding graded by confidence, with a recommended action and a realistic recovery timeline attached.
One engagement. One output. Complete transparency on what your technology investment is actually worth.