Adopted on hype instead of fit
We start from the objective and the process, and we'll tell you when AI is the wrong answer for it.
Guide
A study of 33 European organisations found 7 reasons AI projects fail. Each one has a fix you can put in place before you buy, at launch or after it.
What goes wrong
The tool gets chosen because peers or vendors are using it. "We need an AI strategy" gets mistaken for having one.
What to do
Name the business objective before you choose a tool. Then ask whether you'd do this if no competitor had announced it.
Organisations in the study often followed trends without a thorough evaluation. Firms under 500 people lacked the expertise for due diligence. In enterprises of over 10,000, department managers felt pressure to be seen innovating.
What goes wrong
The business case counts licences and build effort. Maintenance, retraining, governance and expert time are left out.
What to do
Before approval, build a whole-life cost model with lines for maintenance, retraining, governance, compliance and expert time.
Cost models across the study left out maintenance, model retraining, continuous optimisation, governance overhead and compliance updates. The time process experts spent in workshops went uncounted too.
What goes wrong
The hours and headcount savings get assumed at approval, and nobody checks them afterwards.
What to do
Measure the process as it runs today first. Then book a post-launch review and budget time to tune.
Several organisations saw the savings they expected only after they used post-launch data to remove bottlenecks, rebalance work or tune the thresholds at which the AI decides.
What goes wrong
The business case compares the project with zero. It doesn't count what standing still costs.
What to do
Add a cost-of-inaction line to every business case.
Turnover, customer perception and missed innovation were rarely priced in. A product manager in the study noted that people left doing the same repetitive tasks may eventually change jobs.
What goes wrong
Hours are released and nobody decides where they go, so they drift into other work.
What to do
Before launch, decide where the released hours go and who agrees it.
The strongest organisations moved the time to growth work such as customer conversations, and redesigned roles as well as cutting cost. Others asked their staff what they'd do with the time and got good ideas.
What goes wrong
The project ends at go-live. So nobody monitors, retrains or improves the system.
What to do
Name an accountable owner and give them the time. Set the review cadence and the handover.
The best organisations planned scaling, retraining and retirement from day one, and treated automation as a capability that keeps changing.
What goes wrong
The team doesn't know enough yet to judge or run AI, so recruiting looks like the answer. We've found a new hire needs months to learn your business before they can help.
What to do
Bring in expertise that starts from your process and leaves the knowledge behind. Pair it with a named internal owner.
Smaller firms in the study lacked in-house expertise, so popularity filled the gap.
Ask them before you approve any new AI project.
A strong answer is one objective, in one sentence, that the business would pursue whatever competitors do.
A strong answer has volume, handling time, errors and rework measured, and a case that says which of the two it is.
A strong answer prices every line before approval. Licences and the build are two of them.
A strong answer puts a cost-of-inaction line in the case, set against the cost of the project.
A strong answer is an agreed use for the released hours, signed off by a named person.
A strong answer names one owner with protected time and a review cadence.
A strong answer names who has the skills today, or brings in outside expertise that works with a named internal owner and leaves the know-how behind.
Answer all 7 for one AI project and get a score out of 100 and your 3 weakest areas. It takes about 2 minutes.
Take the 7-question checkState the business objective in one sentence and apply the "no competitor announced it" test.
Measure the baseline process: volume, handling time, error and rework rates.
Decide whether this is a proof of concept or a scalable investment, and say so in the case.
Cost the whole life: licences, build, maintenance, retraining, governance, compliance and expert time.
Price the cost of inaction: turnover, customer perception, missed innovation.
Agree where released hours will go and who signs that off.
Assess in-house skills honestly. If there's a gap, plan how and how fast it closes.
Name one accountable owner for the result and protect their time.
Set a balanced scorecard: processing time, error rates, throughput, rework and employee experience. For generative AI, add how often it makes things up and how often a person overrides it.
Review post-launch data, remove bottlenecks and tune thresholds.
Check what time was recovered after checking and rework, where it went, and whether a customer outcome improved.
Plan retraining, scaling and retirement as a standing cycle.
Researchers at LUT University followed European organisations as they adopted RPA, low-code platforms and generative and agentic AI.
Damian Kedziora, Dominik Siemon and Joanna Kedziora, Identifying and Overcoming Challenges in Intelligent Process Automation, California Management Review, volume 68, issue 4, 6 May 2026. DOI 10.1177/00081256261434509.
We help with the business case, build the system and run it after launch.
We start from the objective and the process, and we'll tell you when AI is the wrong answer for it.
Our estimates put the running cost and the hours your team gives the project next to the build price.
We agree the starting numbers before the build and report against them every month after launch.
We price what the process costs today, so doing nothing has a number next to it.
We agree with the business unit lead where the released hours go before the build starts.
We stay on after launch with a monthly scorecard and tuning, and hand over to a named owner.
Our engineers work from your process with your people, and leave the documentation and the know-how with your owner.
8 builds, each measured after launch in hours, euros or days.
7 questions, about 2 minutes. You get a score and your 3 weakest areas, each with what to do next.
Open our summary in the assistant you use, or copy the prompt.