The honest answer is a range, and the range has reasons
Ask five vendors what an AI agent costs and you will get five numbers that span an order of magnitude. That is not because anyone is lying. It is because "an AI agent" can mean a chatbot that answers ten FAQs, or a system that runs your entire inbound sales process across WhatsApp, Telegram, and the web with a CRM, a calendar, and a human handoff behind it.
This guide explains what actually drives the price so you can compare quotes on the same basis, and it gives realistic ranges for the UAE market in 2026. Treat the numbers as orientation, not a price list. The right figure for your business depends on the answers to the questions below.
What drives the build cost
Scope of the job
The single biggest factor is what the agent is responsible for. Answering questions from a document is cheap. Qualifying leads, checking live inventory, booking appointments, and escalating to a human is a workflow, and workflows are where the engineering time goes.
Number of channels
WhatsApp alone is simpler than WhatsApp plus Telegram plus web chat plus voice. Each channel has its own message formats, media handling, and rate limits. Each one adds testing.
Integrations
Every system the agent has to read from or write to is an integration: your CRM, your calendar, your inventory or property database, your payment provider, your ticketing tool. Integrations with a clean API are quick. Integrations with an old system that has no API are not.
Languages and dialects
An agent that must handle Gulf Arabic and English in the same conversation, with correct right-to-left formatting and natural code-switching, needs more prompt work and far more testing than an English-only agent.
Guardrails, evaluation, and compliance
A production agent needs rules about what it may promise, a test suite that runs against real transcripts, and data handling that respects UAE privacy expectations. This is the part cheap quotes leave out, and it is the part that keeps you out of trouble.
Typical build cost ranges in the UAE
These are indicative ranges we see in the market for a properly built system, not a template chatbot.
| Tier | What it covers | Indicative build cost |
|---|---|---|
| Focused assistant | One channel, answers from your content, hands off to email or a human | AED 15,000 to 35,000 |
| Workflow agent | One or two channels, CRM and calendar integration, lead scoring, human handoff, Arabic and English | AED 40,000 to 90,000 |
| Multi-agent system | Several channels, several tools, multiple agents cooperating, custom evaluation and monitoring | AED 100,000 and up |
A real estate sales agent such as ResAI sits in the middle tier for a single brokerage and moves up as more portals, branches, and tools are connected.
What you pay every month
The build is one cost. Running the agent is another, and it has four parts.
Model usage. Every message the agent reads and writes is billed by the model provider per token. For a busy sales line handling a few thousand conversations a month, this is usually in the low hundreds of dirhams to low thousands, depending on conversation length and the model chosen. Smart routing, using a cheaper model for simple turns and a stronger one for reasoning, keeps this down.
Messaging fees. WhatsApp Business charges per conversation, with different rates for marketing, utility, and service messages. Budget for this separately from the model cost.
Hosting and infrastructure. The agent, its queue, its database, and its monitoring need somewhere to run. A well-architected deployment for an SME runs on a modest cloud footprint. Over-provisioned infrastructure is one of the commonest hidden costs, and we wrote about how to find it in our cloud bill audit guide.
Maintenance and improvement. Prompts need updating when your offering changes. Evaluations need reviewing. Integrations break when a vendor changes their API. A monthly retainer, or an internal owner, is part of the real cost.
A realistic all-in monthly figure for a workflow agent at SME scale is typically AED 1,500 to 6,000. The wide range is almost entirely message volume.
The hidden costs vendors skip
- Data cleanup. If your CRM has duplicates and your listings have stale prices, the agent inherits the mess. Budget time to fix the source data.
- Testing on real conversations. Reading a hundred of your actual WhatsApp threads and turning them into test cases is unglamorous and essential.
- Change management. Your salespeople need to trust the handoff. A short pilot with one team beats a company-wide launch.
- Vendor lock-in. If the agent only works on one model provider, a price change or an outage becomes your problem. Ask about fallback routing.
Working out whether it pays for itself
The return on an agent comes from three places, and you can estimate all three with numbers you already have.
- Leads that currently get no reply, or a slow one. Count them. Multiply by your average close rate and deal value. Even recovering a fraction of after-hours leads often covers the build cost within months for a sales-led business.
- Hours your team spends on repetitive first contact. Price those hours at what those people cost, then decide what they would do with the time instead.
- Consistency. Every lead gets the same qualified, compliant answer. This is hard to price, but it removes the bad day from your pipeline.
Run those three against the build plus twelve months of running cost. If the payback is under a year, the decision is straightforward. If it is over three years, the scope is probably wrong, and a smaller agent is the right first step.
Frequently asked questions
Is an off-the-shelf chatbot cheaper?
Usually yes to buy, and usually more expensive to live with. Template bots handle FAQs well and fall apart on anything that touches your data or your workflow. If your need is really a FAQ, buy the template. If it is a process, build the agent.
Can we start small?
You should. One channel, one workflow, one team, then extend. The architecture should be built to grow, but the first release should be narrow.
Who owns the prompts and the data?
You should. Make sure the contract says so, and that you can take the system to another provider if you need to.
How long does a build take?
A focused assistant can be live in a couple of weeks. A workflow agent is typically one to three months, with most of the time on integration and testing rather than on the model.
Want a number for your business rather than a range? Tell us about the workflow and we will scope it properly. See what we build for the full picture of agents, prompt systems, and the infrastructure behind them.