Every transformation business case includes an ROI number. Most of them are fiction, optimistic projections built to get a budget approved, never revisited once the money is spent. That is a problem, because the discipline of calculating ROI honestly is also the discipline that makes a transformation succeed. If you cannot measure the return, you cannot manage toward it.
The formula is simple: ROI = (incremental value created − total program cost) ÷ total program cost. The rigor is in three inputs: a real baseline, isolated impact, and honest total cost.
Step 1: Establish a Real Baseline
You cannot measure improvement without knowing where you started. Before the program begins, capture the baseline for the specific metrics you intend to move: direct channel revenue, conversion rate, customer acquisition cost, throughput, whatever the transformation targets. This sounds obvious, and almost no one does it properly. The baseline is what makes every later ROI claim defensible rather than anecdotal.
Step 2: Isolate the Impact
The hardest part. Businesses change for many reasons at once, market conditions, pricing, sales effort, so you have to make a credible case for how much of the improvement is attributable to the transformation. Techniques include before-and-after comparison against the baseline, holdout or control groups where feasible, channel-level analysis, and trend decomposition. You will rarely get to perfect attribution; aim for a defensible, conservative estimate you would be comfortable showing a skeptical CFO.
Step 3: Capture Total Cost of Ownership
Reported ROI is most often overstated because cost is understated. Total cost is not just the software. It includes implementation and integration, data migration, change management and training, internal team time, and, critically, the ongoing run and administration costs that continue long after go-live. Count all of it. A program that looks like a strong return on license cost alone can look very different on true total cost.
A Worked Example
Consider a real case. A Fortune 500 integrated resort invested $13M in a new website, booking engine, yield system, and customer data infrastructure. The pre-program baseline showed five years of declining direct revenue and ROAS. After the program, direct revenue rose by $36M incrementally, isolated against the prior trend and channel performance. On revenue alone, that is well over a 2x return on the total investment, before counting the downstream lifetime value of the customers acquired through the improved direct channel. The number is credible precisely because the baseline and the isolation were defined up front. (Full story: the direct channel turnaround.)
Building the Board-Ready Business Case
The same three inputs that let you measure ROI after the fact are what make a business case credible before it. A board-ready case states the baseline, the projected impact with conservative assumptions, the total cost of ownership, the payback period, and how the result will be measured. That last part matters: committing up front to how success will be judged is what separates a real business case from a budget request dressed up with a projection.
Building the business case for a transformation?
We build board-ready cases anchored to a real baseline and conservative, defensible numbers.
The Bottom Line
Digital transformation ROI is not hard because the math is complex, the formula is trivial. It is hard because it requires discipline: a real baseline, a credible isolation of impact, and an honest accounting of total cost. Do those three things and you get a number you can defend to a board and manage toward in execution. Skip them and you get the optimistic fiction that gives transformation its bad reputation. The rigor is the point.