Most failed first AI projects fail the same way: they were too big, had no baseline, and had no defined point at which anyone was allowed to call them off. The fix is a time-boxed 90-day pilot with a written kill-or-scale gate at the end. Here is the playbook, worked through in dirhams with realistic cost bands.
If you search for advice on how to scope a first AI project as a small business, most of what you find splits into two unhelpful camps: vendor content promising transformation in a fortnight, or enterprise frameworks that assume you have a PMO and a data science team. Neither answers the question an owner or COO is actually asking: how do I spend a small, capped amount of money and get a defensible yes or no?
The answer is a fixed, time-boxed 90-day pilot with one process, one measurable success criterion, and a written kill-or-scale decision at day 90. This is not a readiness diagnostic. This is the execution of the test, after you have decided that something is worth testing. The method below is adapted from a 90-day roadmap published for UAE SMEs (baseline in days 1–14, off-the-shelf pilot in days 15–45, measurement in days 46–75, decision in days 76–90), combined with process-documentation guidance from CIT Solutions and realistic UAE cost bands from implementation guides for Dubai SMEs. All the numbers are third-party ranges or worked examples, not our own client results.
Why the big first project fails
The most common first-project failure is not technical. It is scoping. CIT Solutions, in their guide for leaders choosing a first AI project, puts it plainly: large multi-department initiatives become "shiny objects" that get bogged down in studies and stakeholder meetings and never leave the pilot phase. Their recommendation is a focused project deliverable inside a single quarter, with a clear, justifiable ROI.
The pattern we see over and over: a business buys into a broad "AI transformation" covering sales, service and operations simultaneously. Ninety days later nobody can say what changed, because nobody recorded what things cost before. There is a strong argument that a kill-or-scale gate is the single most protective thing a small business can do with AI spend: it caps your downside at roughly three months of subscription fees and some senior attention, instead of an open-ended commitment that quietly becomes a sunk cost nobody wants to admit to.
The pilot exists to produce one of two outcomes, both valuable: a dirham number proving the use case works, or a cheap, documented reason to try a different one. Everything in the plan below serves one of those outcomes.
How to scope a first AI project for a small business
Three rules govern the whole 90 days, and they all get decided in week one:
Pick exactly one process. Not one per department. One. A published UAE SME roadmap is blunt about this: piloting more than one process at a time is the most common reason SME AI projects produce no measurable result. Use these selection criteria for the candidate process:
- Repetitive and high volume: it happens 20 or more times per week.
- Documentable in an afternoon: if nobody can write the steps down, no tool can follow them.
- Low data sensitivity: your first pilot should not involve Emirates ID copies, salary data or medical records. UAE's Federal Decree-Law No. 45 of 2021 (the PDPL, in force since 2 January 2022) applies to personal data you feed into any third-party tool, and your first experiment should not double as a compliance project.
- Bilingual-tolerant: if the process involves Arabic, test the candidate tool in Arabic during selection, not after purchase. Tools that demo beautifully in English can degrade badly in Arabic.
- Disliked by the people doing it: CIT's litmus test is the overlap between high time consumption and low job satisfaction. That overlap is where you will get adoption without having to force it.
Document the current workflow first. CIT is emphatic on this point and it matches what we see: you cannot improve a process you have not written down. Record a video of someone doing the task, note every step, every handoff and every system involved. Only then can you tell whether you need AI, simple automation, or both. Most "processes" turn out to be three processes stapled together, and this is the moment you find out.
Define one measurable success criterion and one business outcome, up front. The criterion is a number ("hours spent on quotation drafting fall from 40 to under 16 per month"). The outcome is what the business gets ("we respond to enquiries within 15 minutes during working hours without hiring"). Vague goals like "improve customer service" produce vague results; CIT reports that implementations driven by specific objectives achieve materially higher returns than those driven by general technology enthusiasm.
Write the kill criteria now, before any subscription is purchased: one sentence, signed by the owner, of the form "we kill this pilot on day 90 if measured savings are below X." A common default for X is two times the monthly tool cost. Deciding this after the pilot invites sunk-cost bias. Deciding it before day 15 is what separates a pilot from a hobby.
Days 1–14: baseline the cost of the process
You cannot claim savings against a number you never recorded. For two weeks, before touching any AI tool, log actual data:
- Hours spent on the process, per person, per week. Timesheet data, not estimates.
- The loaded hourly cost of each person: salary plus housing allowance plus visa costs plus gratuity accrual plus medical insurance, divided by working hours. A useful UAE reference point: an employee on AED 8,000 per month typically costs AED 11,000–12,000 loaded, which is roughly AED 63–69 per working hour.
- Error and delay costs where they are measurable: enquiries answered after four hours, quotes sent out with mistakes.
Multiply hours by loaded cost. That number is your baseline, and every claim the pilot makes later gets tested against it.
Worked example. A 12-person facilities maintenance firm in Sharjah picks WhatsApp enquiry triage as its one process. Two coordinators handle inbound enquiries: pricing questions, service-area checks, booking requests. During weeks one and two the timesheets show a combined 60 hours per month on triage and first response. Both are on AED 6,500 per month; loaded, that is about AED 9,700 each, or AED 65 per working hour.
Baseline = 60 hours × AED 65 = AED 3,900 per month spent on enquiry triage. The signed kill criterion: "If the pilot does not show at least AED 1,600 per month in measured net savings by day 75, we kill it at day 90." (AED 1,600 is two times the expected AED 800 monthly tool cost.)
Days 15–45: run the pilot off-the-shelf, under a cap
No custom development. No API integrations. Off-the-shelf tools only, under a hard monthly cap. A UAE SME roadmap uses AED 2,000 per month as the cap, which is deliberately generous for a first pilot. Typical tool categories and their monthly costs:
| Process | Tool category | Typical monthly cost (AED) |
|---|---|---|
| WhatsApp enquiry handling | WhatsApp Business API platform with AI replies | 200–1,100 |
| Quotation / proposal drafting | LLM subscription (ChatGPT Team, Claude, Copilot) | 90–110 per seat |
| Meeting notes and follow-ups | AI transcription tool | 40–120 per seat |
| Invoice data entry | OCR / document AI inside your accounting tool | 0–400 |
| Arabic-English content | LLM subscription with human review | 90–110 per seat |
For context on the broader market: Dubai implementation guides put basic customer-facing automation at roughly AED 15,000–25,000 for a full one-time setup with integrations, and comprehensive operational AI at AED 45,000–75,000. Those are the budgets you are testing your way into, not starting with. The whole point of the pilot is to spend a few hundred to a few thousand dirhams before you commit tens of thousands.
Three regional rules during the pilot phase:
- WhatsApp first, if your customers use WhatsApp. In the UAE they overwhelmingly do. Do not pilot an email automation and call it customer service AI. Use the official WhatsApp Business API through a proper platform; unofficial automation tools risk your business number being banned.
- Ask every vendor one question on day one: where is our data stored, and can we delete it? The PDPL covers personal data processed inside or outside the country, requires consent and purpose limitation, and obliges controllers to report personal data breaches to the regulator. The UAE government's official summary of the law and its cross-border transfer rules is worth ten minutes of reading. A vendor with a vague answer on data location is a vendor you do not pilot with. This is your cheapest compliance insurance.
- One owner, five hours a week. Someone senior owns the pilot and spends five hours weekly on it: setup, prompt and workflow tuning, and weekly logging. Unowned pilots die by week three.
Spend days 15–25 on setup and tuning, then days 26–45 on real usage at full volume. Log usage weekly; a shared spreadsheet with hours saved per person is enough.
Days 46–75: measure honestly against the baseline
This is the phase everyone skips. The formula is deliberately boring:
Monthly saving = (baseline hours − current hours) × loaded hourly cost − tool cost − new costs
Rules that keep the number honest:
- Use actual hours from weeks 6–10, not the vendor's claimed "70% time saved."
- Count redeployed time only if it went somewhere billable or measurable. Time that evaporates into longer coffee breaks is not a saving.
- Count the new costs: the subscription, the owner's five hours a week, and any rework caused by AI errors.
- Track quality alongside speed: response time on WhatsApp, error rate on quotes, customer complaints.
A tiny script keeps the arithmetic consistent and mechanical, which is the point: when the day-90 decision comes, nobody should be arguing about the maths.
LOADED_HOURLY_COST = 65 # AED: salary + allowances + visa + gratuity + insurance / hours
BASELINE_HOURS = 60 # hours per month, from weeks 1-14 timesheets
TOOL_COST = 800 # AED per month, subscriptions
KILL_THRESHOLD = 2 * TOOL_COST # signed in week two, before any purchase
def monthly_saving(current_hours: float) -> float:
saved_hours = BASELINE_HOURS - current_hours
return saved_hours * LOADED_HOURLY_COST - TOOL_COST
# weeks 6-10 timesheets: triage now takes 20-24 hours/month
for h in (24, 22, 20, 23, 21):
print(h, round(monthly_saving(h)), "AED")
# decision at day 76, applied mechanically
print("Decision:", "scale" if monthly_saving(22) >= KILL_THRESHOLD else "kill")
Worked example, continued. At day 75, the timesheets for weeks 6–10 show triage running at 20–24 hours per month, call it 22 on average. The saving is (60 − 22) × AED 65 = AED 2,470 gross, minus AED 800 in tool costs, minus an honest allowance of AED 400 for the owner's five hours a week: AED 1,270 net per month, sustained for six consecutive weeks. That clears the AED 1,600 gross-threshold test against tool cost (AED 2,470 vs AED 1,600) and the team kept using the tool without being reminded. Response time on enquiries fell from an average of four hours to under 15 minutes during working hours.
Had the timesheets shown triage at 50 hours a month, the saving would have been (60 − 50) × 65 = AED 650 gross, below the AED 1,600 threshold, and the correct decision at day 90 would be to kill it. That is not a failure: it is a result, bought for roughly three months of subscription fees, and it redirects the budget to a better candidate process.
Days 76–90: the kill-or-scale gate
Pull out the criteria you signed in week two and apply them mechanically. No negotiation, no "give it one more quarter."
| Signal at day 75 | Decision | Action |
|---|---|---|
| Measured savings above the pre-agreed threshold for 6+ consecutive weeks | Scale | Extend volume, add seats, then consider integration |
| Savings below the threshold | Kill | Cancel subscriptions, document why, pick a different process |
| Team routed around the tool and reverted to the old way | Kill | Adoption failed; the saving was never real |
| Quality dropped in a way customers noticed | Kill | Speed gains that cost you customers are negative ROI |
| Savings near threshold, quality up, adoption voluntary | Extend once | One 30-day extension with a revised, stricter threshold |
Killing a pilot on day 90 with AED 5,000 total spent is a cheap education. Killing it on day 400 with AED 60,000 spent is the outcome this whole structure exists to prevent.
If you scale, do it in order of cost: extend the same tool to more volume first, add seats for more people second, and only then consider custom integration. The sequencing matters because the expensive options are the ones you should reach for with evidence in hand. The staged pathway recommended for UAE SMEs is the same shape: start with customer-facing automation, progress to operational AI, and only then move to predictive work. When you do get to the integration stage, that is when the shape of the work changes: you are connecting a proven tool to your systems, on your infrastructure, with your developers involved. That is the point at which it is worth bringing in outside engineering help, and it is a different engagement from the pilot.
The whole plan on one screen
| Phase | Days | Output |
|---|---|---|
| Scope and baseline | 1–14 | One process, written workflow, dirham baseline, signed kill criteria |
| Pilot | 15–45 | Off-the-shelf tool live at full volume, under a fixed monthly cap |
| Measure | 46–75 | Actual hours saved × loaded cost, net of tool and owner time, in AED/month |
| Decide | 76–90 | Kill or scale, mechanically, per the written criteria |
What to do next
- This week: run a time audit. Ask each team two questions: where do you spend the most time, and what do you like the least? Take the overlap as your shortlist.
- Pick one process against the five criteria above and write the workflow down, step by step, in an afternoon.
- Log real hours for two weeks and compute the baseline in dirhams, using loaded cost rather than salary.
- Write and sign the kill criterion before purchasing anything.
- On day 90, hold the gate. Celebrate the kill as loudly as the scale: a documented "no" frees budget for the process where AI will actually pay.
If you want help with the upstream question, which is knowing where AI will pay off in your business and what to pilot first, that is exactly what our AI strategy and readiness work covers: we look at how your business runs, from processes and systems to data, and tell you plainly where AI will pay off, what it takes, and what to do first. And when a cleared pilot graduates to real integration with your systems, that is AI engineering territory, done on your infrastructure with your developers equipped to build with it safely.
The ninety days will pass either way. The difference is whether you end them with a number and a decision, or with another subscription nobody remembers buying.
Sources: the 90-day UAE SME AI roadmap, dizzdev's UAE AI implementation guide for SMEs, CIT Solutions on choosing your first AI project, and the UAE government's official summary of the data protection laws.
Originally published on Azrty.
Top comments (0)