Back to Growth Notes

Your team says AI is everywhere. The measured number says otherwise. Somewhere between "we use ChatGPT" and "AI runs the workflow" lives a gap, and that gap is costing you more than you think.

Your team says AI is everywhere. Somewhere between that answer and what actually runs in production lives a gap your own impression has been hiding for months, and you have been nodding along because everyone has a ChatGPT tab open.

Here is the uncomfortable part. Nobody lied on purpose. People said “we use AI” because someone on the team drafts emails with it, or because a demo went well last quarter, or because saying no to the question feels like admitting the company is behind. So the answer moved to yes. The workflow did not. As a result, leadership is making a call on AI investment based on a number that reflects hope, not fact. And hope is not a measurement.

Because the question “do you use AI” answers one thing: does at least one person, somewhere, sometimes, open a chat window. It does not answer what actually matters: does AI run inside the process, connected to your systems, checked against a source, with someone accountable for what it costs and what happens when it is wrong.

The gap, measured

Most teams estimate themselves at 60 out of 100 on AI integration, because everyone uses ChatGPT and someone ran a pilot last year. When integration is measured across every function independently, seven dimensions at a time, the score sits closer to 34.

That is not a rounding error. That is the difference between a business that has adopted a tool and a business that has integrated a capability. The first shows up in a survey. The second shows up in the numbers.

Using tools and integrating AI into the workflow are two very different things.

Where the gap actually lives

The gap rarely shows up as one dramatic failure. It compounds across seven places, quietly, unnoticed in any single week.

Commercial AI. One person uses a chatbot to draft outreach. Nothing is connected to the CRM, so the value leaves when that person is on holiday.

Operations and back-office. A pilot automated one report. The other forty reports nobody counted are still manual.

Product and build. Developers use an AI coding tool, but nobody changed the review process, so the output is trusted at the same rate as before, which is to say not verified at all.

Data foundation. The AI that could answer a question from your own documents cannot, because those documents live in six systems that do not talk to each other.

Governance and trust. Nobody can say which provider sees which data, under what terms, with what retention. The question has not been asked, let alone answered.

Adoption and value. The tool that was rolled out with a training session is used by the three people who were in the room. Everyone else reverted within a month.

AI strategy and ownership. Nobody owns the decision of what gets automated next, so it defaults to whoever asks loudest, not whoever has the clearest business case.

Why the estimate is always high

People answer the question with the most visible case in mind, not the average one. The one person who built something clever with an agent becomes the mental picture for “how AI-integrated we are,” and the other six dimensions where nothing has changed do not come to mind, because nothing changing does not produce a memorable moment.

That is not dishonesty. It is how estimation works when there is no number to check it against. The fix is not asking people to guess more carefully. The fix is measuring instead of asking.

What changes once you know the real number

A measured score does three things a guess cannot. It tells you which of the seven dimensions is actually the weak one, instead of the one that feels weak. It gives you a number to check progress against in six months, instead of a vague sense of “better.” And it stops the budget conversation from being about tools and starts it being about the dimension where the business case is strongest.

Most organisations do not need more AI. They need to know, honestly, where the 34 actually sits, and which one of the seven dimensions moves the number that matters first.

The ODB Way

At ODB Growth, the first move is never a recommendation. It is a measurement. The AI Integration Scan scores the same seven dimensions above, independently, in eight minutes, and hands back a number instead of an impression.

Then the work starts where the gap is real, not where it feels biggest. Objective first: which of the seven moves a business number. Then the process. Then the technology. If it does not move a number, it is a demo, no matter how confident the self-assessment was.

Onno de Bel

Onno de Bel

AI Engineer & Architect | ODB Growth

Ready to build something
that moves a number?

Let's find out where AI actually pays in your process, and build it.

Plan a Growth Call