The demonstration is the easy part

What the pilot actually proved

A pilot proves that a model can produce a plausible answer on a clean example. That is not nothing, but it is the smallest part of the problem, and it is the part that has been getting easier every year while the rest has not moved.

The work a business actually runs on is not clean. It can arrive late, in the wrong format, from an older system, with an exception attached that nobody ever wrote down.

Where it stops

A pilot needs to address the exceptions, the systems of record and the question of who approves its actions. Each changes what the production system has to do, beyond producing a plausible answer.

None of the three appear in a demonstration, because a demonstration is built to avoid them. That is why the meeting goes well and the project does not.

What a system has that a pilot does not

A system has an owner inside the business, an approval path for anything it changes, and a record of what it read and what it did. It runs where the data already lives, so nothing has to be copied out to make it work.

It needs somebody accountable as the process changes and the people who understand the rules move on.

And it has a way of being wrong safely: a case it does not recognise is handed to a person with the working attached, rather than answered confidently.

Building for continuing operation

Start where the work is

We start by sitting with the people who do the job, and writing down how it actually runs. What gets built comes from that, not from a template and not from whatever the model happens to be good at.

Then stay

Lyrion scopes, builds and operates its systems. Staying involved means learning from production and bringing that understanding back into the work.