Skip to content

ROI deliverable: cost and return by use case

The ROI deliverable shows what each use case costs and what it returns. It is measured in time and stated in cost, at a rate built on your teams’ own profiles. The method is detailed in how to measure the ROI of AI.

Measure What it tells you
Cost Paid licences against actual usage, and what AI consumes, tool by tool.
Hours returned The time saved each month, per use case, given as a range.
Value in euros Hours returned converted at the rate of each of your teams’ profiles.
The decision For each use case: plan, do, or do not do, with the cost of inaction.

The Value screen shows the hours returned each month and what AI consumes. The “Show in euros” switch converts hours at your profiles’ rates. The period, tool and department filters work as on the other screens.

  • No gain promised in advance. ROI is measured on your usage, once the exports are connected.
  • A range, not a round figure. Time saved depends on the tasks: the Cockpit gives a low and a high.
  • The source of every figure. “Measured” when the export establishes it, “reported” when it comes from an interview.

Why measure in hours before talking in euros?

Section titled “Why measure in hours before talking in euros?”

Because time is measured in usage, and the value of an hour depends on who gains it. The Cockpit first counts the hours given back, then converts them at the rate built on your teams’ profiles. It never applies a universal rate: an average rate laid over jobs that do not cost the same would give a figure that nobody in your company would recognise.

Hours given back. The deliverable states the time AI frees up on a task; it does not promise a cut in your costs, which the audit does not measure. What your teams do with that time remains your decision.

No. No gain is put in figures in advance: the deliverable is built on your actual usage, once your exports are connected and your interviews are done.

To see what the tool shows on your own tools, book a call.