Artificial intelligence is now deployed almost everywhere. Copilots, assistants, text or code generators: few companies have launched nothing. Yet the economic results often take their time.
This gap isn't a paradox. It's a signal. It says one simple thing: spreading a tool isn't transforming the work. Value doesn't come from access to AI, but from what you do with it.
The apparent paradox of massive adoption
The observation is widely shared. A recent Kyndryl study, reported by Le Monde Informatique, surveys more than a thousand executives about their readiness for AI. A large majority say they have integrated AI into their processes.
But only a minority consider their teams truly ready. And few organizations reach the goals they had set. The gap between usage and readiness is the real subject.
This gap shows up everywhere. We readily measure the number of licenses or active users. We rarely measure what these uses actually change in the work.
Spreading a tool isn't transforming the work
The confusion is natural. A widely used tool gives the feeling of a transformation underway. Spread reassures. Yet it proves nothing about the value created.
A generative system handles language fluently. This ease impresses. But the fluency of an answer says nothing about its reliability, nor about its effect on a real process.
The same gap exists at the scale of the organization. An available AI isn't an integrated AI. Spread is visible and fast. Maturity is slow, quiet, and far harder to achieve.
What AI really shifts: the infrastructure of work
To get out of this confusion, we have to look at AI differently. Not as one more tool, but as a layer of infrastructure that runs through the organization.
Infrastructure doesn't create value by its mere presence. Electricity changed nothing as long as it was bolted onto workshops designed for steam. Value came when the workshop was rethought around it.
AI follows the same logic. Grafted onto an unchanged process, it speeds up one step and stops there. Integrated into rethought work, it changes how information flows and how decisions are made.
A concrete example: the tool added, the process unchanged
Take a common case. A team adopts a simple AI tool to draft its reports, emails or records. Each person saves a few minutes per task.
The gain is real, but it stays local. The process itself hasn't moved. The same approvals, the same re-entries, the same back-and-forth remain around the accelerated step.
A few months later, disappointment sets in. The tool is used, even appreciated, but the overall result hasn't changed. A task was equipped, the work wasn't transformed.
This gain stays fragile as long as you stop there. A tool becomes stable and effective when you rework the way of doing things itself, in short iterations, fed by users' feedback. It's that work, not the tool alone, that makes it last.
Real value is born of rethought work
The tipping point lies elsewhere. Before adding AI, you have to break real work down into tasks. Then decide, for each one, what should be removed, simplified, assisted or kept under human responsibility.
Often, the most useful step isn't to automate, but to remove. An approval that has become pointless, an avoidable re-entry, a document no one reads: AI shouldn't speed them up, it should make them superfluous.
It's on this condition that time saved becomes a real gain. Not a few minutes on a task, but a process that's shorter, clearer and more reliable.
From organizing the work to a tool the whole team keeps growing
Nothing was frozen all at once. The tool was born from a better organization of the work. It became a prototype, then an application the whole team uses, then a system connected to the company chat. And it's still growing.
This climb, we walked it on ourselves, on our own pipeline for handling incoming requests. It all starts far from the code. We prepare the idea, the plan and the instructions with advanced conversational AIs, such as Fable 5 or ChatGPT.
Then comes a prototype of a particular kind. At its core, a reference base that describes the business, its rules and its way of working. Around it, commands that automate entire steps. This reference base isn't a dead document: we test it, we correct it, we enrich it in short iterations.
When the tool proves its value, it leaves the hands of a single person. We build a web application connected to an AI model. What lived in an expert's tool becomes a tool the whole team uses every day.
We go further still. We connect this application and its reference base to the company chat, Teams or Slack, by plugging in an agent already prepared for that role, such as Hermes. Everything ends up connected: the team, its messaging, the application and the reference base. The tool comes to where people already work.
And this is where the story gets interesting. The reference base keeps living, fed by users' feedback. Every real use refines a rule, fills a gap, fixes a forgotten case. The tool improves along with the people who use it.
The final step adds supervised automation. Agents analyze a request, propose a decision, execute it within a bounded scope, then check the result. The human keeps a hand on the wheel: setting the rules, approving sensitive actions and taking responsibility.
A controllable path, not a major overhaul
This path is nothing specific to our business. It maps out a route open to any company: a chosen scope, a step-by-step climb, value measured before widening.
At every step, two things stay protected. Your budget, because you only industrialize what has proven its value. And your control, because you keep a hand on your data, your decisions and your ability to take the tool back.
AI deployed everywhere gives an impression of movement. The real movement is elsewhere, less visible: it lies in reorganizing the work around the tool.
So the right question isn't "where to put AI", but "what work do we want to transform". The first leads to scattered uses. The second leads to value.
A simple test settles it. Remove AI from one of your processes. If you only lose the speed of a step, you equipped a task. If the process itself becomes heavier again, then you've begun to transform it.
This test also applies to those who support you. A good partner has walked this path on itself before proposing it to you. That's often what separates the tool sold from the work truly transformed.