Good AI consulting in the UAE starts with one task, not a strategy. The firm measures what that task costs you today, tests more than one model on your real cases, settles where your data is allowed to go, and builds the first working piece inside the tools your team already uses. At the end you have numbers, a decision and a fixed price to go live. If what you get instead is a deck and a demo, you bought a presentation.

I run Skcript Applied Labs, a small team of senior engineers that does this work for companies in Dubai, Abu Dhabi, Riyadh and across the Gulf. So I have an obvious interest here. I'll try to write the guide I would want to read if I were the one hiring.

What good AI consulting looks like

Almost every company I talk to has the same story. They bought the licences. They ran a pilot. It looked great in a meeting. Then it stopped, and the team went back to doing the work by hand. I wrote about the reasons in Why AI pilots stall, and they shape everything below.

Good AI consulting closes those gaps on purpose. In practice that means five things.

It starts from a money number

Before anyone talks about models, someone should sit with the people who do the task and write down how long one item takes, how many come in each week, how often something goes wrong and what that costs. That gives you the money number: what the task costs today and what it would be worth to fix.

If a firm can't tell you which number it plans to move, it can't tell you whether it moved it. I go into how we count this in Cost per task, not cost per token.

It tests on your work, not a leaderboard

Public benchmarks measure what model makers chose to measure. They tell you little about your supplier invoices or your Arabic and English customer emails. A good firm builds a test set from 100 to 200 of your real cases, messy ones included, with the right answers attached. Then it runs several models through the same set and shows you the scores side by side, with cost per task and where the data goes. Here is how we test AI models on your work.

It builds the real thing, small

A chat window that never touches your ERP, inbox or ticketing tool is not a system. The hard part of AI work is the connection: reading the right record, writing back safely, following your access rules and failing in a way a person can catch. The first thing a consultant builds should be the first working piece of the real system, not a demo you throw away.

It says no when the answer is no

Some tasks are better solved with a rule, a better form or a process change. Some happen too rarely to be worth automating. A consultant who never tells you that is selling, not advising. I wrote a whole post on when not to use AI, and I think every firm you talk to should be able to give you their version.

It ends with a decision

The output of a pilot is a decision you can trust: go live, change the approach, or stop. That needs before and after numbers measured the same way, a fixed price for the rollout and the result it must hit, agreed in writing.

How to choose an AI consulting company in Dubai or the wider UAE

Here are the questions I would ask any firm before signing, including us.

Who owns them?

This year the big AI labs started running their own deployment teams. That is good news, because it tells every board that the hard part of AI is the engineering, not the model. But a firm owned by a model maker, or paid by one, will naturally start from that model. Ask plainly: do you earn more if we pick one vendor over another?

Will they show you a scorecard?

Ask to see what a model comparison looks like before you start. It should have accuracy on your cases, the type of mistakes each model makes, cost per task, speed and where the data goes. If the answer is "we use the best model", ask which one, tested on what.

Who is on the first call, and who builds it?

Big programmes create a lot of meetings. Ask whether the engineers on your first call are the people who will build the work. On our side they are, and I am on that first call too.

What do you keep if it stops?

If the pilot shows the task isn't worth doing, you should still keep the starting numbers and the test set. The test set alone is useful, because you can use it to check any AI tool you try later.

What is the price, and what is fixed?

Ask for a fixed price for a defined first step and a fixed price for the rollout before you commit to it. Open-ended discovery phases are where budgets disappear.

Data residency: the question to ask early

"Our data can't leave the UAE" is the first thing most security teams tell me. It is a fair starting point, and it is also where a lot of pilots get stuck, because nobody pins down what it means for the task in front of them.

That one sentence hides three questions. Where is the data stored? Where does the model actually run? And who else can see it, keep it or learn from it?

The trap is that storage and processing are not the same thing. Many AI services let you store files and logs in a UAE region while the request itself is processed wherever the model has capacity. So don't ask a vendor "do you have a UAE region?" Ask "for this exact model, in this exact setup, where does my request get processed?" Get the answer in writing.

The rules also differ by who you are. The federal data protection law, the DIFC and ADGM laws, health data rules and sector regulators all point in different directions, and for many companies the strictest rule is their own internal policy. I go through this in detail in Keeping your data in the UAE, and the law side in PDPL and DIFC AI compliance in the UAE. Neither is legal advice, but they will help you ask the right questions.

A good consultant settles this in the first days of the work, not after the demo. In our pilots we sort your test cases by how sensitive they are, test only setups that meet the rule for that data, and record where the data goes on the scorecard next to accuracy and cost. Sometimes the answer is to run an open model on servers you control. Sometimes it is to keep one sensitive step with a person and let AI handle the rest.

Why a fixed-price 10-day pilot

AI work has a reputation for open-ended spend. I think a short, fixed-price pilot on one task is the honest way to start, and here is what ours looks like.

Before day one we agree on one task and you name one owner on your side. Day one goes on measuring the task as it runs today and writing the success line together. Days two and three build the test set from your real cases. Days four and five test the models and produce the scorecard, and if the results are poor, that is the point to stop. Days six to eight build the first working piece inside your tools, with a person approving anything important. Day nine runs it on the current week's work. Day ten is the readout.

You leave with the starting and new numbers, the test set, the model scorecard, the working first piece, a runbook, and a fixed price and 4 to 6 week plan for the full rollout. Or a plain recommendation to stop. The full day-by-day breakdown is in What a 10-day pilot actually delivers.

The 10-day AI pilot has one fixed, published price: USD 7,500, about AED 27,500. If you go ahead with the rollout within 30 days, the fee counts toward it. If you already tried AI and it never went live, there is also a 5-day pilot check-up that tests what you have on your real work and tells you why it stalled.

From pilot to production

A pilot proves one task works on real data with honest numbers. It does not get that task live for your whole team, connected to every system, with every rare case covered. That is what the rollout is for.

The thing that makes the rollout smooth is decided at the start: nothing built in the pilot gets thrown away. The test set keeps checking every change. The working piece grows into the full system. The owner you named on day one becomes the person who runs it. I wrote a step-by-step version of this in the AI pilot to production playbook.

After launch, models keep changing. When a better one ships, we run it through your tests and switch only if it wins on accuracy and cost per task. Building the system so a model can be swapped without starting again is part of the job.

When not to use AI at all

I'd rather lose a project than build the wrong thing, so here is the short list.

  • When a rule will do. If the right answer can be written down, write the rule. It is cheaper, faster and easier to audit.
  • When a better form will do. If you control how information arrives, fix the input before you build something to read around it.
  • When the process is the problem. AI won't fix an approval that sits with someone who is travelling.
  • When the volume is too small. If a task happens a few times a month, building and looking after an AI system can cost more than it saves.
  • When a mistake costs too much to risk. AI can gather facts and draft, but some decisions need a person to own them.

Most real systems end up as a mix: plain rules for the fixed checks, better inputs where you control them, and AI for the steps that need judgement.

Where AI consulting pays off first

The work that pays off fastest is high volume and heavy on text or documents. Invoices and purchase orders. Supplier and customer emails. Contracts, claims and onboarding files. Internal requests.

If you are in finance, my guide to AI invoice processing covers how UAE e-invoicing changes the picture. If you are replacing old bots, see how we approach moving from RPA to AI agents. For contracts and requests, see contract workflows and the internal request desk.

Why we do this

I started Skcript in 2013, and we have been shipping software since. We run AI features in production in our own products, FeatureOS and SupportWire. For a global bank, we automated payroll for more than 10,000 people across more than 25 systems, and it went live in 3 months. Applied Labs takes that habit of shipping and points it at one problem: getting AI to work in your business. You own everything we build: the code, the tests and the numbers.

You can see how we work in AI consulting in the UAE, or across all regions on our AI consulting page. If one task is eating your team's week, start a chat with us on the site, or book a call through the Applied Labs page. Bring the task and a few real examples, and I'll tell you honestly whether ten days is enough to show it working.