AI investment ROI is one of the most recurrent questions in banking and industrial executive teams — and one of the worst answered. The typical answer is "hard to say, we do not have enough data yet". That answer tells you the measurement structure was not built at the same time as the investment.
A typical mistake is to measure ROI only against build cost. This ignores operational cost (model calls, monitoring, maintenance, governance work, data-product upkeep) and indirect cost (capability building, integrations, user training). Another classic mistake is to measure value only as "hours saved". This metric over- or under-estimates reality — depending on which hours are assumed freed and what is done with them next.
AI-Koutsi uses a four-part model that produces a reliable view of use-case and portfolio ROI.
At portfolio level each use case is scored on the four dimensions. This enables a portfolio view: "in Q2 we expect 4.3 M euro of impact, of which 2.1 is direct saving, 1.2 revenue growth, 0.8 risk reduction and 0.2 option value". This is an unusually strong conversation in the executive team — much stronger than "we invest 8 M euro in AI this year".
ROI requires a baseline. Without a T0 measurement before use-case deployment you can never claim the improvement came from AI. This is one of the most important reasons AI-Koutsi starts everything with a maturity assessment and a portfolio baseline. Continuous measurement means use-case impact is measured at least quarterly and portfolio impact is reported to the executive team monthly.
Another important metric is the implementation rate: how much of the potential use-case portfolio is actually in production. High maturity without implementation rate means the company has good capabilities but a weak portfolio. AI-Koutsi reports maturity and implementation rate separately, so the two are not conflated in the discussion.