Why Artificial Intelligence Projects Fail After The Pilot.

The pilot works, the rollout does not, and the technology was never the problem.

Published 4 September 2026 · 2 minute read · By Cortex

A pattern repeats often enough to be predictable. A company runs a pilot. The pilot works, sometimes impressively. Six months later the system is either unused or quietly switched off, and the conclusion drawn is that the technology was not ready.

The technology was almost always ready. Three other things went wrong.

The problem was chosen for its demonstrability. A pilot is selected because it will show well, which is a different property from mattering. Summarising documents demonstrates beautifully and rarely changes a week. The work that actually consumes a company tends to be unglamorous, distributed across several systems, and invisible in a demonstration.

Nobody priced the alternative. A pilot that saves four hours a month is a success in a report and a rounding error in a business. Without a figure attached to the problem before the build, there is no way to tell whether the result is worth maintaining, and anything not obviously worth maintaining will eventually stop being maintained. What that figure looks like when it is done properly is published as a finding priced in the company's own hours and rates.

Adoption was treated as a training issue. A system used by the person who commissioned it and nobody else is the most common outcome of a successful pilot. Adoption is decided by whether the system sits inside the tools people already work in and whether it survives the first week of exceptions, both of which are design decisions made long before the training session.

All three failures share a cause: the order was wrong. The technology was chosen first and the problem was found afterwards.

The order that works is unglamorous. Establish where time, margin and information are being lost. Price each one in the organisation's own hours and rates. Rank by value against feasibility. Only then decide what to build, and build the thing that survives the twelve month question rather than the thing that demonstrates well in March. That is the order Cortex works in, on every engagement.

Every engagement begins with the Cortex AI Audit. The diagnostic that follows it is paid work, and the picture it produces is the asset.

Begin

Every Engagement Begins With An Audit.

Nine minutes. Six steps. A number built from your own hours and rates. Nothing to install, and no call unless you ask for one.

Your score appears on screen. The written report arrives by email.