A Dubai agency will quote somewhere between AED 1,500 and AED 15,000 to put one process on autopilot, plus roughly AED 400 to AED 5,000 a month to keep it alive. That spread covers two very different products sold under the same label: a button menu an intern assembles in an afternoon, and an agent that reads your calendar, writes the deal into your CRM and sends a payment link inside the same chat. The buyer's problem is that almost nobody publishes either number, so you cannot tell which of those two products you are being quoted until the work has already started.
We run our own bookings on this stack before selling it to anyone, and our prices are on the site, so I will use ours as one reference point. The rest comes from what is publicly visible in this market, with a warning attached: published price lists for AI automation in Dubai are rare enough that any range you read, mine included, rests on a small sample.
An AI automation agency in Dubai builds and maintains the connections between the tools a business already runs, usually WhatsApp, a CRM, ads and a payment link, so that a repetitive process completes without anyone copying data by hand. Setup is priced per process or per workflow. A monthly fee covers running it, watching it and changing it when the business changes.
Why the price sits behind a form
Scope genuinely varies, and that part is legitimate: a clinic with three branches, two languages and an insurance question in every second chat is a different build from a single-location salon, and a rate card that ignores that will be wrong half the time.
Pricing also happens by appearance. The quote is written after a vendor has seen your website, your ad spend and your industry, so the same build gets a different number depending on who is asking. Anyone who has sat on both sides of that conversation knows it happens.
Sometimes the enquiry itself is the product: a form is a lead, and a price page lets you leave without becoming one.
Resellers add another wrinkle. If a vendor is putting a thin layer on top of a platform subscription that has its own published price, a public rate card invites you to do the subtraction.
None of that means a vendor hiding the price is a bad vendor. It means you should force the number out early. Ask two things in the first email: what is the smallest engagement you have delivered, and what did it cost. A vendor who has built ten of these can answer in one line. A vendor who cannot is either new or is waiting to hear your budget first.
What the setup fee actually buys
Setup buys the unglamorous work around the bot far more than it buys the bot itself.
- Mapping the process as it currently runs, including the exceptions nobody wrote down, like who gets the discount and who does not
- Writing the logic or the prompt, then feeding it your real prices, service list, opening hours and refusal rules
- Onboarding the number onto the WhatsApp Business Platform, business verification, display name approval, template writing and submission for Meta review
- Connecting the CRM so a chat becomes a deal with a source tag, rather than a note someone retypes later
- Testing against messages that were never planned for: voice notes, Arabic mixed with English, three questions in one line, a customer who sends a screenshot instead of typing
- Alerting, so a silent failure at 2am becomes a message to somebody rather than a gap you discover on Friday
- A handover document that tells the next person how the thing is wired
What is almost never inside setup: message fees, model usage, CRM seats, hosting, and any change you request after go-live. If the proposal has one number and no second line, that is the tell. The full arithmetic of a single workflow, including payback, is a separate calculation from what you are reading here, so I will not repeat it in this piece.
Three tiers, and what each one is honestly worth
Almost every quote you receive is one of these three, whatever the proposal calls it.
Tier one: the scripted bot
A decision tree with buttons. Press 1 for prices, press 2 for location. No language model anywhere. It deflects the ten questions you answer forty times a week, and it collapses the moment somebody types a sentence the tree did not anticipate.
Observed setup band: roughly AED 1,500 to AED 5,000. Monthly: roughly AED 400 to AED 1,200. Live in a few days. Worth buying if your enquiries really are that repetitive and your goal is to stop answering "what time do you close" by hand.
Tier two: the AI bot over your content
A language model answers freely using your price list, service descriptions and rules. It handles unexpected phrasing, quotes correctly, and holds a conversation. It does not touch your other systems. Somebody still reads the chat afterwards and moves the lead into wherever leads go.
Observed setup band: roughly AED 5,000 to AED 15,000. Monthly: roughly AED 1,000 to AED 3,000, plus model usage on top. Two to four weeks to build, and most of that time goes into extracting what your business actually says, not into engineering.
Tier three: the agent with integrations
This one does work rather than talk. It checks the calendar, holds a slot, writes the deal into the CRM with the ad source attached, issues a payment link, chases the quote that went quiet on day three, and escalates to a human on the conditions you set. When people say "leads get lost between the enquiry and the payment", this tier is the thing that closes the gap.
Observed setup band: from around AED 15,000 upward, sometimes well upward. Monthly: roughly AED 2,000 to AED 5,000 and beyond, depending on how many systems it touches. Four to eight weeks is realistic, and integration work is where the schedule slips.
Our own published numbers sit deliberately across the middle: one process on autopilot from AED 6,000 to build and from AED 1,200 a month to run and watch, and the WhatsApp sales agent from AED 8,000 standalone. The full list, including the setup and monthly for every role, is on the price page. Use it to sanity-check a quote you have received, whoever it came from.
The costs nobody puts in the proposal
Meta message fees
This is the one that surprises owners. WhatsApp automation runs on the WhatsApp Business Platform, and Meta bills for it separately from whatever your agency charges.
The model matters more than any single figure. Meta retired conversation-based pricing in favour of per-message pricing, and its own conversation-based pricing documentation is now marked deprecated. Messages fall into four categories: marketing, utility, authentication and service. Service messages, meaning your replies inside a customer-initiated conversation, were made free for all businesses on 1 November 2024, and utility templates sent inside an open customer service window carried the same free status from 1 July 2025. That changes again on 1 October 2026: Meta's own documentation moves both service messages and in-window utility templates to per-message billing from that date, priced by market like the other categories. Marketing templates, the ones you send to start a conversation, have always been the paid category, and the rate differs by country, so the UAE row on Meta's current rate card is the number to check before you budget. One thing is not moving: the free entry point window. When someone messages you from a click-to-WhatsApp ad or a Page call-to-action button, messages in the following 72 hours stay free.
If your automation is mostly answering people who wrote to you first, the free-service-message era kept a Meta bill small regardless of volume — from October 2026 that no longer holds, and every reply inside the service window carries a per-message cost, so ask a vendor to model that against your real chat volume rather than quoting the old free assumption. It is also worth asking who gets billed in the first place: the owner of the WhatsApp Business Account receives the invoice, and if your account sits inside the vendor's provider workspace, they get the bill and re-bill you, with the markup entirely at their discretion. A proposal that still quotes per-conversation pricing, or that assumes service messages stay free past September 2026, is working from a model Meta has already retired or is about to.
Model usage
Every reply an AI agent writes consumes tokens, and tokens are metered. A bloated system prompt that stuffs your entire catalogue into every single request costs multiples of a well-built one for identical output. Ask whose API key pays for it and what the expected monthly usage looks like at your message volume. If the vendor has never measured this on a live account, that is information.
Hosting, licences and middleware
A server, or a subscription to an automation platform, or CRM seats. Small money individually. It adds up, and it should be listed at cost with receipts rather than folded into a round number.
Change requests
Your prices change. You launch a service. Ramadan hours differ from the rest of the year. Every one of those is a change to the automation. Agree the change rate before you sign, not in month four when you need it done by Thursday.
Whose accounts, whose keys, whose logs
A glass-box build is one where every asset lives in something you own and the vendor is a guest with admin rights. A black-box build is one where the vendor owns the container and you own a monthly invoice. The two look identical while everything works.
Before you sign, get a written answer on each of these:
- The Meta Business Manager and the WhatsApp Business Account: created under yours, with the vendor added as a partner
- The phone number: registered to your business, not parked on a number they lend you
- The model API key: your account, your billing, your usage dashboard
- The CRM subscription and the automation platform workspace: your login, your payment method
- Conversation logs: exportable by you, in a format you can actually read
- The scenario, prompt and integration code: yours in writing, with a copy handed over at go-live rather than promised at exit
The portability test is a single sentence to put in the email: if we part ways next month, what exactly do I keep, how long does the handover take, and who performs it. A vendor running a glass box answers with a list. A vendor running a black box answers with reassurance about how unlikely that is.
Our own terms are published for the same reason: accounts stay in your name, and ad budget, message fees and licences are passed through at cost with receipts attached. That removes the argument that otherwise happens at the worst possible moment, a practical reason rather than a generous one.
Fixed scope or a monthly retainer
Fixed scope is the right shape when the process is stable, written down, and limited to one workflow, and when somebody on your side can make a small change without calling anyone. You pay once, you get the thing, you own it.
A retainer earns its place when your prices and offers move often, when the agent's answers have to track live ad campaigns, when several processes are wired together, or when nobody internally will notice a silent failure. Automations do not break loudly. A CRM field gets renamed, an API version is retired, a payment gateway changes a response format, and the system keeps reporting success while leads quietly stop arriving.
The question to ask about any retainer is what is actually inside it. Some monthly fees are pure insurance: the vendor will fix it if it breaks, and every change is billed separately. Others include a defined number of change hours and a response time. Both are defensible. Only one of them is what most owners think they are buying.
For a reference ratio, ours is public: AED 6,000 to build one process, AED 1,200 a month to run and monitor it. Treat that as one data point rather than a market rule.
How long it actually takes
"Live in one day" means a template bot with your logo on it. Here is the honest shape.
Meta's business verification and display name approval sit outside everybody's control. It can clear the same day. It can take over a week, especially if the trade licence name and the display name do not match. No vendor can compress that, and any vendor promising to is describing luck as a process.
A scripted bot goes live in days. An AI agent over your content takes two to four weeks, and the bottleneck is you: collecting the real prices, the real exceptions, the sentence your best salesperson uses when someone says the quote is too high. An agent that writes into a CRM and issues payment links takes four to eight weeks in practice.
Our published setup window for a full engine build is three to five weeks, and an audit runs one to two. Then add two weeks of supervised running after go-live, whoever builds it. The first fortnight of real traffic is where you find out what customers actually ask, and it is always different from what the team predicted in the kickoff meeting.
Eight questions to ask before you sign
- What is the setup price and what is the monthly fee, in writing, before a discovery call?
- Who owns the WhatsApp Business Account and the phone number, and whose Business Manager holds them?
- Whose API key pays for the model, and what monthly usage should I expect at my message volume?
- Are Meta message fees billed to me directly or re-billed by you, and at what markup?
- What exactly is inside the monthly fee: how many change hours, what response time, and who receives the failure alert, you or me?
- Can you show me a system running in production with its logs, rather than a recorded demo?
- On the day we stop working together, what do I keep, how long does the handover take, and who performs it?
- What has broken on a system you built, how did you find out, and how long did it take to fix?
The last one filters harder than the other seven combined. Anyone who has run automation in production has an outage story with a timeline attached. A vendor with no such story has either not shipped much or is not watching what they shipped.
Red flags worth walking away from
No price until a call, followed by a number that moves after they have seen your website. The WhatsApp Business Account sitting in their Business Manager with a friendly explanation of why that is better for you. Per-conversation Meta pricing quoted from a model that has been retired. A quote with a setup fee and no monthly line at all, which usually means the monthly conversation happens after you are dependent. A promised conversion lift stated as a percentage before anyone has looked at your data. A demo that only ever runs the happy path, and a polite deflection when you ask it something awkward. Refusal to name the platform underneath. Full payment up front.
Where we sit
Every price we charge is on the site, including the monthly. One process on autopilot starts at AED 6,000 to build and AED 1,200 a month to run. Accounts stay in your name, pass-through costs carry receipts and no markup, and payment for setups splits 50% to start and 50% on go-live.
The proof is our own operation rather than a case study written for a brochure. A lead from an ad or a chat lands in the CRM as a deal with its source attached, gets a payment link in the same thread, and gets chased if it goes quiet, with nobody copying anything by hand. It answers at 3am on Saturday the way it answers on Monday morning, which is the entire point of buying one of these.
If you want your own numbers before you commit to anyone, a Growth Audit at AED 3,000 takes one to two weeks and gives you a leak map with figures. Take it to whichever vendor you like, including a competitor.
