"We have that covered."
It is the most common sentence in enterprise software conversations right now. A platform is in place. A team is building on top of it. Something ships every few weeks. The sentence is usually true about the thing the speaker has in mind, and that is exactly what makes it worth examining.
Because the sentence is rarely about one tool. It is a way of saying the buying is done, the thinking has been done, and the organisation can stop shifting for a while. That wish predates AI by decades. What AI has added is a reason to believe it. If a model can answer anything, the stack looks finished. The wand has arrived.
It has not. The question is not whether the build is good. Plenty of them are. The question is what it is built over.
Enterprise AI is deployed where the work was already written down
Look at where it actually sits. Deloitte's State of Generative AI in the Enterprise survey, published in January 2025 from 2,773 director-to-C-suite respondents, asked organisations to name the function hosting their most advanced initiative. IT came first at 28%, then operations at 11%, customer service at 10%, cybersecurity at 8%, marketing at 8% and product development at 7%.
That is a coherent picture. Support tickets, code, documents, contracts, logs, transcripts. Every one of those is a place where the work already exists in written form, at volume, with structure. AI is very good there and the returns are real.
Now notice what is not on the list. No function that answers a question the organisation has never answered before. No function where the useful knowledge lives in people's heads and has never been typed anywhere.
Adoption is nearly universal. Impact is not.
The scale of adoption is no longer in doubt. McKinsey's The state of AI in 2025, published in November 2025 from 1,993 respondents across 105 nations, found 88% of organisations using AI regularly in at least one function.
The same survey found that 39% report any effect on enterprise-level EBIT, and around 6% attribute more than 5% of EBIT to AI. Roughly two-thirds have not begun scaling across the enterprise at all.
BCG's Widening AI Value Gap: Build for the Future 2025 study of 1,250 firms, published in September 2025, arrives in the same place from a different direction. 5% of companies are achieving value at scale. 60% report minimal revenue and cost gains despite substantial investment.
Gartner expects the next wave to run into the same wall. In June 2025 it forecast that more than 40% of agentic AI projects will be cancelled by the end of 2027, citing escalating costs, unclear business value and inadequate risk controls.
None of this says the technology does not work. It says the technology works on a certain kind of problem, most organisations have pointed it at that kind of problem, and the effect on the business has been narrower than the adoption numbers suggest.
Your tools manage what has been said. The hard part is what has not been thought.
The constraint is what the system can reach, not what it can do
The most useful diagnostic in the recent research is not about models at all. It is about supply.
Gartner surveyed 1,203 data management leaders and reported in February 2025 that organisations will abandon 60% of AI projects unsupported by AI-ready data through 2026. In the same research, 63% either lacked appropriate data management practices for AI or were unsure whether they had them. Harvard Business Review Analytic Services, in research published in March 2026 with 230 respondents, found that 7% of enterprises describe their data as completely ready for AI.
Read those figures carefully. They are usually treated as a data engineering problem, which is to say a problem that more pipelines will fix. Some of it is. But there is a harder version underneath, and it does not yield to engineering.
An organisation's most consequential knowledge is not badly formatted. It was never recorded. Why a regulator's tone changed in a meeting nobody minuted. Why the last integration failed in a way the post-mortem did not name. What the head of a business unit believes about a market and has never said in a forum where it could be challenged. Which assumption three senior people are quietly working around.
That material is not dark data waiting for a better connector. It is not data. It exists as human understanding, held by particular people, and it stays there unless something deliberately brings it into contact with other people's understanding.
Your people are already telling you where the gap is
There is a signal most organisations have and do not read.
UpGuard's State of Shadow AI Report, published in November 2025 from 1,500 security leaders and employees across seven countries, found that fewer than 20% of workers use only company-approved AI tools. Around 90% of security professionals themselves use unapproved ones.
The usual reading is a governance failure. There is a second reading. People route around the sanctioned stack at the exact points where the sanctioned stack does not do what they need. Shadow use is a map of unmet demand, drawn by the people closest to the work.
If you want to see what this looks like on a live question inside your organisation, talk to us.
What has to exist for the gap to close
The gap is not a missing feature. It is a missing process, and processes have requirements.
People have to be able to contribute understanding, not just answers. It matters whether a contribution rests on research, on expert fact, on lived experience, on values or on gut-feel. Two people can write nearly the same sentence from completely different ground. A system that stores the sentence and loses the ground has thrown away the part that mattered.
Contributions have to be able to act on each other. Someone must be able to build on, challenge or reframe what another person put in, and that relationship has to be preserved rather than flattened into a summary.
Disagreement has to survive. Tension between two well-grounded positions is information about the question. A process that resolves it early to look decisive has destroyed the most valuable thing in the room.
And it has to accumulate. Understanding built in March should be the starting point in September, not something that has to be rebuilt from scratch because the workshop output expired with the workshop.
That set of requirements is what Hunome is for. Each Spark carries characterisations, like its knowtype, the contributor's own account of how they know what they are contributing. A SparkMap holds the perspectives, their grounds and the connections between them, so understanding accumulates instead of resetting. The Shared Understanding Index measures whether people are building understanding together, which is a different thing from measuring whether they agree. What comes out is deliberative intelligence: the full picture of what the organisation now understands about a question and how it got there.
The part that is actually yours
Here is the competitive fact underneath all of this. Everything your competitors can get from a model, you can also get from a model, and quickly. The gap between two organisations running the same class of system on the same public material is small and closing.
What no one else can get is the understanding your organisation produces about circumstances nobody has documented. Not what any one person already knows: that is thin, partial and often wrong. The understanding that arises when the people who each hold a piece of the situation think it through together and see where their reasoning meets and where it does not. That understanding did not exist before the process. It cannot be bought, copied or scraped, because it is made, not found.
That is what Hunome is built for. It is where your people think together on the questions the stack cannot answer, and it makes the result usable: what the organisation now understands, where the people who matter actually stand, and what the reasoning was when the decision was made. When conditions change, you go back to the reasoning, not to a vote count or a slide.
Your AI build covers the documented, and it should. Deciding whether you are right about anything runs on the rest. Hunome is the rest.