The short answer
A partner who gives you a week count before reading your org is guessing. The date depends on how many systems Salesforce must talk to, the state of your data, the rules your regulator sets, and how fast your own people can sign things off. Industry matters because it changes those four things.
What we commit to instead: a free assessment, then a fixed first build week, and a written scope with a date at the end of that week. After that, one named process goes live first, and the next one follows when the first is quiet.
- Financial services usually runs longest. Core banking integration, data residency and audit evidence add the most time.
- Real estate is set by the number of portals and channels feeding leads, and by the sales launch you are building for.
- Healthcare is set by where patient data may be stored and by the clinical systems you must connect.
- Government is set by procurement, identity (UAE Pass) and Arabic-first service, more than by the build.
How the date gets set
The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.
In that first week we read the flows, permissions, integrations, licences and data, build the first piece, and write down the scope. The date is in that written scope, so you get it from people who have seen your org, not from a sales call.
From there the work follows the same path in every sector: design and build of the first process, a cutover, and hypercare until the first real week is quiet. If the process changes halfway, we stop and re-price in writing rather than let the date slide. The full path is on Salesforce implementation, and the prices are on what Salesforce and AI agents cost in the UAE.
What sets the date, by industry
Financial services and banking
The build is rarely the long part. The calendar goes on access to core banking and card systems, on data classification, and on the evidence your risk and compliance teams need before go-live. Firms in DIFC or ADGM work under those zones’ own data protection laws, and onshore banks under Central Bank rules, so the data flow map is part of the first week, not an afterthought. Plan for a sandbox with realistic masked data early; without it, testing waits. More on Salesforce for financial services.
Real estate
For a developer or a brokerage, the date is set by how many places leads arrive from (Property Finder, Bayut, your website, campaigns, WhatsApp) and whether the build has to be ready for a launch day. Inventory, reservations, payment plans and handover can follow once leads and the sales floor are working. Our real estate CRM pages set out each stage from lead to handover.
Healthcare
Health data in the UAE falls under its own federal law, which generally keeps it in the country, so hosting and the data flow are settled before anything is built. Connections to clinical and billing systems, and consent wording in Arabic and English, take more of the calendar than Salesforce configuration. More on Salesforce for healthcare.
Government and public services
Procurement and security review often take longer than the build. Sign-in through UAE Pass, Arabic-first forms and messages, and accessibility checks belong in the first week’s scope. More on AI and Salesforce in government.
AI agents: the timings we publish
An agent adds a shadow period: it runs on real work and writes nothing while your team compares its answers with their own. In our sample agent spec on what you get, that is two weeks before any write goes live behind an approval.
The only build times we publish are these, and they are our own delivery estimates, not benchmarks:
- A WhatsApp agent: paperwork starts the day scope is signed; answers and handoff from about week 1; integrations in weeks 3 to 4; bookings, payments and CRM writes in weeks 5 to 6. Most of that calendar is Meta’s business verification and access to your systems. See WhatsApp AI agents.
- A voice agent in Indian languages: we aim for one named process in one language pair in about 30 days, including the shadow period. See AI agents in India.
Whether the agent should be Agentforce or custom changes the build, not the shadow period. See Agentforce vs custom agents.
What slows every project
- Waiting for access to the org, the ERP or the core system. It is the most common delay, and it starts on day one.
- Data nobody owns: duplicates, missing owners, half-migrated history.
- Sign-off by committee. One named person per process who can say yes saves weeks.
- Five processes at once instead of one live and reviewed first.
- Arabic left until the end. Templates and tests in both languages belong in the first scope.
When a project has already slipped, read the failed project rescue guide.