Ask around the UAE market and almost every company of any size will tell you it has tried something with AI. A chatbot. A summarisation tool somebody in marketing pays for monthly. A proof of concept a vendor built, demoed once, and never mentioned again.
Ask what is running in production, who owns it, and what changed as a result — and the room goes quiet.
This is not a UAE problem specifically, but it is worse here than in smaller markets, because there is enough budget to keep starting things. The failures are remarkably consistent. In my experience they cluster in four places, and the model is not one of them. Getting past them is most of what my AI consulting work actually consists of.
1. The process was chosen because it was interesting
Almost every stalled pilot I have looked at automated something visible rather than something expensive. A customer-facing chatbot is exciting and demos well to a board. It is also the hardest thing to get right, has the highest cost of being wrong, and usually is not where the money is leaking.
The processes worth automating first are dull: quote preparation, document intake, reconciliation, first-line internal support, tender paperwork. They have volume, they have rules, someone can tell you what an error costs, and there is a named person who wants it fixed.
If nobody in the business can tell you what the current process costs per month, you are not ready to automate it. You are ready to measure it.
2. It was proved on the vendor’s data, not yours
A model that scores well on a clean sample will meet your abbreviations, your scanned PDFs, your supplier names in three spellings, your bilingual documents, and the exception that accounts for nine per cent of volume and was never written down.
Test on your own material before you sign anything. Not a curated set — a random slice of last month, including the ugly ones. If the vendor resists this, that is the answer.
Arabic deserves its own test. Most tooling is built and benchmarked in English, and performance on Arabic — especially with dialect, transliterated names or mixed-script documents — is often materially worse. A system that will meet Arabic in production has to be tested in Arabic before it goes live, not translated afterwards. The same principle applies to websites, and Arabic-second always shows.
3. It was shipped somewhere nobody goes
This is the quietest killer. The pilot works, the numbers are good, and it lives in a separate portal that the team has to remember to open. Adoption dies within a fortnight.
Whatever you build has to appear inside the tools the work already happens in: the CRM, the inbox, the WhatsApp thread, the ERP. If your team has to change where they work in order to use it, they will not use it.
4. Nobody was given ownership
Ask who can change a prompt, read the logs, and switch the thing off. If the answer is the vendor, you have rented a capability rather than acquired one. When the contract lapses or the consultant moves on, the system quietly rots — and because it never visibly breaks, nobody notices for months.
Before any of that, settle what happens to the data — what the UAE PDPL asks of you before you connect a model is the checklist I use. Handover is not documentation. It is somebody on your side who has made a change, watched what happened, and knows how to undo it.
What a project that reaches production looks like
Boringly, it looks like this: one process, chosen because it costs money; tested on real data including the exceptions; shipped into a tool people already open; owned by a named person who can turn it off. Six weeks, not six months. Then the second one.
The companies here that are getting real value from AI are not the ones with the most ambitious roadmap. They are the ones that finished something small, and then did it again. Often the first thing worth finishing is not AI at all but the data underneath it, which is why e-invoicing is quietly an AI-readiness project.
A question worth asking in your next vendor meeting
“Which of your UAE clients has this in production today, and can I speak to the person who owns it?” It is a simple question and it ends a surprising number of conversations.