Back to the journal

Guides et conseils

Proving an AI project pays off: full cost, real gain

58% of CIOs face growing pressure to deliver savings from AI, and 13% see strong value from it. A one-page sheet, built with the business, to weigh the full cost of an AI project against its real gain.

Author
Tomorrow Solutions
Published
November 2, 2026
Reading
5 min
Proving an AI project pays off: full cost, real gain

This year, I worked with lawyers at a large industrial group who built their own AI agents for recurring legal reviews.

The first one used to fill in a review sheet by hand for contracts of more than a hundred pages. Two days of work, by her own estimate. With the agent, two to three hours.

The second one spent more than a week, and not alone, on a report that comes back every six months. The agent now produces the groundwork in a few minutes. Human review time remains, and she does not delegate it.

These are their own estimates, not a measurement. But they share something that matters: a precise task, chosen by the business, whose cost the teams knew before they started.

That is exactly what most AI projects lack.

Pressure is rising, proof is missing

On 19 October, Gartner published its 2027 CIO and Technology Executive Agenda survey of 2,002 CIOs and technology executives. Three figures sum up the situation.

  • 58% of CIOs face increased pressure to deliver cost savings from AI.
  • 51% expect total cost of ownership to rise.
  • 13% say their enterprise has realised significant or transformational value from AI.

So AI is being asked to cut costs, while its own cost is rising and its value is rarely demonstrated.

The Deloitte AI Institute, in a survey of 3,500 executives published on 29 October, shows where attention goes: 71% of companies track their total inference and API spend, 51% track token volume, 44% track per-unit inference cost. Technical cost is tracked. Business gain, much less.

Why value stays invisible

Activity gets measured. Number of people trained, active users, prompts sent. Training teams is useful, and so is tracking usage. None of these figures says whether a task costs less than before.

The task was never chosen. A project launched on « AI for legal » or « AI for finance » has no point of comparison. A project launched on « the review sheet for contracts over a hundred pages » has one.

The cost is incomplete. The licence is visible. Team time to build, test and review is far less so, as are change management and support. A gain compared with a licence alone always looks good.

Weighing full cost against real gain

The method fits on one page. It is filled in with the business before launch, then updated on the decision date.

  1. The task: which one, in which team, takes too long today or generates too many errors?
  2. The indicator: processing time, rework rate, cases per person. Only one, chosen by the business.
  3. The baseline: how long the task takes today, and how many times a month.
  4. The full cost: licences, team time to build and test, change management, support.
  5. The real gain: time saved, human review included, multiplied by how often the task occurs.
  6. The thresholds: the gain that justifies scaling, and the one below which you stop.
  7. The decision date and the decision-maker: a named business owner who decides on the planned date.

The fifth point makes the difference. An agent that produces a report in a few minutes but needs a day of checking does not deliver the same gain as one whose output can be reviewed in an hour. Review time is part of the cost.

Sorting a portfolio of projects

According to Gartner, a use case has roughly a one in five chance of succeeding. A CIO who has launched ten projects should therefore expect to keep a small share of them. The question is which ones, based on facts.

With the sheet, sorting becomes possible: keep the projects whose real gain exceeds their full cost, adjust those that come close, stop the others. Gartner shows the exercise is still rare: 31% of CIOs have criteria to decide that a pilot will not move into production, and 17% to stop a low-value initiative already deployed.

Stopping a project that does not prove its value is not a failure. It frees the budget for one that creates value.

IT cannot prove it alone

The pressure for savings lands on the CIO. But value shows up in the business: only the teams who do the task know what it costs and what has changed.

That is what the two lawyers at the start show. The agents with the most traction are the ones the business builds and tests on its own work. Gartner also recommends involving business leaders, who are willing to walk away from low-value investments. The message from Gartner analyst Alicia Mullery fits in three words: « Volume is not value. »

Where to start

If you do only one thing this month: list your AI projects in progress and, for each one, look for three pieces of information. The target task, its baseline, its full cost. Those missing one are your first priorities.

I help business leaders and CIOs put this measurement in place and sort their AI projects, with the teams who do the work. Let’s talk about your projects.

Sources

Continue reading

Other perspectives on enterprise AI adoption

  1. 01

    Microsoft Copilot in Outlook: Transforming an Email Thread into a Plan

    The article explains how Microsoft Copilot in Outlook can transform complex email threads into clear and actionable plans by identifying decisions, actions, responsible parties, deadlines, and risks, rather than merely summarizing the exchanges. This feature enables a shift from mere understanding to execution by structuring information for better coordination and task tracking. The adoption of Copilot for this use case is facilitated by its simplicity, frequent use, and the time savings it provides, all while remaining under human control.

    May 2, 2026
  2. 02

    RTFCE Method: How to Structure Your Microsoft Copilot Prompts

    The article introduces the RTFCE method for effectively structuring prompts used with Microsoft Copilot to enhance the quality of the responses obtained. This method is based on five key elements: Role, Task, Format, Constraints, and Examples, allowing vague requests to be transformed into clear and actionable instructions. By adopting this approach, users can achieve more precise and useful results, thereby facilitating the adoption and integration of Copilot into professional workflows.

    May 2, 2026
  3. 03

    Microsoft Copilot in Outlook: How to Move Beyond Generic Responses

    The article explores the use of Microsoft Copilot in Outlook, emphasizing that to transition from generic responses to truly useful emails, it is crucial to configure Copilot with the user's context, role, and style. It suggests methods for personalizing Copilot, such as analyzing personal writing style and adapting the tone according to situations, while reminding of the importance of human validation and the tool's limitations. In conclusion, when used effectively, Copilot can enhance the quality of communication and save time, but it requires an appropriate framework and method.

    May 2, 2026

Turn this analysis into a decision.

A 30-minute diagnostic identifies the main friction point in your AI program and the next useful checkpoint.

Book a diagnostic