A custom CRM for groups with several companies.

Yes, and it is the main reason to build rather than configure. The entity becomes an object on the record, so every account, deal and quote names the company it belongs to and a deal cannot reach Won without one. That matters because the licence decides who may sell to whom, and the entity that closes decides the VAT treatment and the corporate tax position. From 2027 it stops being an internal convention: a UAE business invoice is issued as PINT AE structured data through a provider accredited under Ministerial Decision No. 64 of 2025, and the issuing entity is a field inside it. The rest of that calendar sits on the Dubai page.

Buy the packaged CRM unless one of three things is true. The group sells through more than one licensed entity and the record has to know which. The data cannot sit wherever the vendor happens to operate. Or the seat count has already passed the point where a licence costs more each year than a build costs once. Everything else is a configuration job, and Webzenia says so rather than proposing a build, which is why the first deliverable is a written verdict and not a quote.

It sits wherever you decide in discovery, and yes it matters. The federal instrument is the Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, in force since 2 January 2022, and it reaches anyone processing the data of people in the UAE regardless of where the processing happens. A packaged CRM answers this for you by defaulting to the regions its vendor operates in, which is a decision you did not take. A built one puts the records in an account and a region you chose, with retention and access rules written down. Both are stated in the scope document before the first field is drawn.

Yes. DIFC and ADGM each run their own data protection regimes, separate from the federal PDPL, so a DIFC-registered advisory and a Business Bay brokerage are not answering the same question about the same customer record. It changes the lawful basis you rely on, the transfer rules and who has to be notified, and it is expensive to retrofit through a finished system. Where a group holds entities on both sides, the CRM carries the regime alongside the entity rather than picking one and hoping. That is settled at the data-model stage, not at go-live.

Both are built in, because most of the evidence on a deal here is in a thread and a call rather than an inbox. Enquiries arriving on the WhatsApp Business API become records with a source, deduplicated against contacts you already hold. Calls are dialled from the record through Twilio, so the number, the duration and the recording attach themselves. In a packaged CRM these are usually connectors priced per user, which is fine until the person who set them up leaves and the history goes with the handset. The rule we build to is that the conversation belongs to the deal, not to the rep.

You own all of it, and there is no per-seat fee. The repository, the database and the hosting account are opened in your entity’s name, and the assignment is written into the agreement rather than implied by it. Adding the fiftieth rep costs an account rather than a licence, which is the whole commercial argument for building one. Support and new modules run on a retainer you can end, and ending it does not stop the CRM. Who Webzenia is and who sits on the account is a fair thing to check before signing any of that.

The first working pipeline is weeks rather than months, and what it costs afterwards is hosting plus whatever support you choose. Three things move the build figure more than anything else: how many entities and licences the record has to model, how many systems it has to write to, and whether the history from your current system has to come across with it. Running cost scales with records rather than with people, which is the opposite shape to a subscription and the reason the two curves cross. We price the first phase after the data model is agreed, never before it. The wider automation programme is scoped the same way.