# The demo works. Then what?

From pilot to live · No. 1 · Octopus research team · 17 November 2026

Issue 1 of From pilot to live, our weekly note for decision-makers in the Kingdom. It is the short version of our article on why AI pilots stall: four places a pilot gets stuck, and five questions to put to any pilot you sponsor. The full article adds the survey figures behind it.

This is the first issue of From pilot to live. Every Tuesday we take one question we hear from decision-makers in the Kingdom and answer it from what we have seen in delivery. We start with the most common one: why does a pilot that worked in the demo never reach daily operations?

## Where pilots stall

Most AI pilots are built to prove that a model can do one task: draft a reply to a customer, forecast next month's demand, answer a policy question. They usually succeed, because the task was chosen to succeed and the data was prepared by hand.

Operations asks a different question. Can this run every day, on live data, inside the systems people already use, with someone accountable when it gets something wrong? A pilot rarely has an answer, because nobody was asked to design one.

We see the stall happen in four places.

### 1. The data was curated, not connected

The pilot ran on a clean export. Production means reading from the ERP, the CRM or a shared inbox, with all their gaps and formats. That integration work is often bigger than the model work, and it was not in the pilot plan.

### 2. Nobody owns it after the demo

The innovation team built it, IT has to run it, and the business has to use it. When no single person is accountable for the outcome, the pilot waits for a decision that never comes.

### 3. Compliance arrives late

Data residency, personal data and cybersecurity controls get reviewed after the design is fixed. The review finds a problem, and the redesign takes longer than the pilot did.

### 4. The work around it never changed

A model that drafts a reply saves time only if the process expects a draft. If approvals, handoffs and forms stay the same, people do the old work plus one new step, and usage drops after the first month.

None of these is a model problem. Each is a design decision that has to be made before the build starts, by people who understand the operation and the technology.

In the coming weeks we take them one at a time: where AI agents fit in an organisation and who stays accountable for them, what PDPL and NCA controls ask of an AI project, how to choose where to start, where Arabic language AI is ready and where to check twice, and why adoption decides the return.

**Checklist: Five questions to ask about any pilot**

1. Which live system will it read from, and which will it write to?
2. Who is accountable for the result once it is live? Write down a name.
3. Has anyone confirmed where the data will be stored and processed?
4. Which step in today's process disappears or changes when it goes live?
5. What number will tell you, three months from now, that it worked?

If you have a pilot that has stalled, we can look at it with you and tell you plainly what it would take to reach operations. [Book a session](https://pioctopus.ai/en/contact)

- The full article: [Why AI pilots stall before operations](https://pioctopus.ai/en/insights/why-ai-pilots-stall)
- [AI strategy, investment and value realisation](https://pioctopus.ai/en/services/ai-strategy-value)
- [Operations and service re-engineering with AI](https://pioctopus.ai/en/services/intelligent-operations)

[All issues](https://pioctopus.ai/en/newsletter)

---
Web page: https://pioctopus.ai/en/newsletter/pilot-to-operations
Arabic version: https://pioctopus.ai/newsletter/pilot-to-operations.md
Index for AI agents: https://pioctopus.ai/llms.txt
