We are looking at an ERP. When is a custom platform the better answer?

When the fit is the expensive part. A licensed ERP is the right buy where the process is generic, the entity structure is simple and the connectors you need already exist, and in that case a good implementation partner will serve you better than we will. It stops being the right buy when the configuration bill starts to look like a build, when the per-seat licence grows faster than the value, or when the data question has an answer the vendor tenant cannot give. Most of the organisations that reach us have already discovered one of the three.

Our entity is registered in DIFC. Does that change how our data has to be handled?

Yes, and it is the first thing we establish. DIFC entities are governed by DIFC Law No. 5 of 2020 rather than the federal PDPL, ADGM entities by the ADGM Data Protection Regulations 2021, and a mainland entity by the federal PDPL, each with its own regulator. The consequence for a build is that a group operating across zones is under more than one framework at the same time, so the platform has to hold that boundary in the data model rather than describe it in a policy. Where a record sits and which of your companies may see it is settled at custom CRM development for a sales system; here it is settled for the whole estate.

Can the platform integrate with the systems we cannot replace?

That is the starting point rather than a later phase. We ask which system is immovable on the first call, because everything else is arranged around it: the finance system a parent company mandates, something installed years ago that nobody will touch, or a system a client or a regulator requires you to use. The integration is built so that system does not change, reading and writing against it while the record stays where it already lives. A proposal that quietly assumes a migration is a proposal that has not asked the question.

Will it produce what the FTA expects for VAT and for e-invoicing?

That is a build requirement with a date on it, not a compliance checkbox. Structured e-invoicing runs through an Accredited Service Provider under Ministerial Decision No. 64 of 2025, on the Peppol-based PINT AE standard, and businesses at or above AED 50 million in annual revenue appoint a provider by 30 October 2026 and comply from 1 January 2027. What that means architecturally is that the finance layer has to emit structured data to a third party on a schedule, which is an integration with a deadline. When each obligation falls due, and how the dates interact, is argued at AI automation in Dubai.

Does our data have to stay in the UAE?

Sometimes, and where it does the answer has a shape rather than a checkbox. There has been an AWS region in the country since 29 August 2022 across three availability zones, and Azure UAE North sits in Dubai. Azure has a second UAE region in Abu Dhabi, but access to it is restricted and granted for defined scenarios such as disaster recovery, so an architecture drawn against it may not be one you can actually use. We settle the region during architecture and write it into the scope, because discovering a residency requirement after the platform exists is a migration rather than a setting.

How long does an enterprise build take, and what do we see first?

You see something usable well before the platform is finished, and that is the point of phasing it. Each phase ends in something a department can actually work in, so the first group is live while the second is still being scoped, and the architecture is available to disagree with in week three rather than month nine. We commit to a scope and a price per phase rather than one number for the whole programme, because an enterprise estimate given as a single figure is a figure nobody can defend once the first integration turns out to be harder than the demo. Where a group bids for government-linked work, the entity structure is worth settling early too, and that is argued at Abu Dhabi.

Who owns the code, and what happens at the end of the engagement?

You own it throughout, not at the end. The repository is in your organisation from the first commit, the cloud accounts are in your name, and the runbooks are written as the work happens rather than assembled at handover. That means the end of the engagement is a transfer of operation rather than of ownership, and you could put the platform in front of another supplier without asking us for anything. How this sits inside the wider automation programme is argued at AI and automation in the UAE.

Enterprise software development · UAE

Enterprise software built around the systems you keep.

At this scale the architecture is decided by the regime your entity sits under and the systems nobody may replace. Webzenia scopes against both, before the module list opens.

Tell us what the platform has to survive

Where the packaged answer stops

Enterprise software beyond packaged ERP.

A suite is quick to buy and slow to fit, and the fitting is where the cost moves. Three things decide whether it fits at all, and none of them is on a module list.

Built to the process

A suite asks the organisation to work the way the product does. At one department that is a reasonable trade and at five it is a reorganisation, paid for in change requests nobody scoped.

Wired into what exists

The systems of record are not moving, whatever the proposal implies. The architecture starts from the one nobody is allowed to replace, and everything else is arranged around it.

Governed against the regime

A mainland entity is under the federal PDPL, a DIFC entity under DIFC Law No. 5 of 2020, an ADGM entity under the ADGM Data Protection Regulations 2021. The entity decides the law before the build decides anything.

What gets built

The platforms we build.

Six shapes an enterprise brief arrives in. Which one you are in is usually decided by what already exists rather than by what is wanted.

Core business platforms

The system the organisation actually runs on, built to the process rather than to a product roadmap

Output

one platform several departments work inside instead of four that email each other

Multi-departmentOne system

System integration

The layer that connects what you already run without asking permission to replace any of it

Output

the immovable system still in place, and no longer an island

Systems of recordNo rip-out

Legacy modernisation

Replacing what genuinely has to go, in an order that keeps the business trading while it happens

Output

a migration with a rollback rather than a launch date

PhasedReversible

Approvals that survive an audit

Every step with a named owner, an authority limit and a clock, recorded so a reviewer can reconstruct who approved what and under what delegation

Output

an audit trail, not a log file

Named ownerAuthority

Dashboards and MIS

One set of numbers a board can act on, assembled from the systems rather than from a spreadsheet somebody maintains

Output

a figure with a lineage behind it

One versionTraceable

Customer and partner portals

External access scoped so a partner sees their own data and nothing adjacent to it, which is an access-model question before it is a design one

Output

a door with a lock specified

Scoped accessExternal

Three ways it gets done

Three ways to build a platform.

A Business Bay contracting group with five licensed entities is quoted all three, usually inside the same month, and the papers are not comparable.

	Build it in-houseHire the team, own the risk	Licence a suiteConfigure the product to fit	Build against the regimeScoped to the entity and the estate
Fit to the process	Exact, until the two people who understood it leave.	Good where the process is generic, and expensive where it is not.	Built to the process you have, including the parts nobody documented.
The cost model	Salaries, and a bus factor nobody prices.	Licence per user, per year, rising with headcount.	Capex per phase, and an asset on your side of the balance sheet.
The immovable system	Integrated eventually, by whoever is still there.	Integrated if a connector exists, rebuilt if not.	The starting point of the architecture, not a later phase.
Who holds the data	You do, on infrastructure somebody has to keep patched.	The vendor tenant, in whichever region the contract names.	You do, in a region chosen against the regime the entity is in.
At a questionnaire	Answerable, once somebody writes the answers down.	Answered by the vendor, about the vendor.	Answered from the scope, because the regime is named in it.

When a licence is right.

Where the process is generic and the entity structure is simple, a licensed suite configured by a good partner is the correct purchase and we will say so. It stops being right at two points: when the fit is bought back in change requests, and when the data question has an answer the licence cannot give. If you need one process rebuilt rather than a platform, that is automate business workflows, and where the brief is one system rather than an estate, custom software development.

The UAE context

What decides the architecture here.

Webzenia has worked with Gulf clients since 2018. Four things shape an enterprise platform in this market, and none of them appears on a module list.

01of 04
A group is under two at onceNot one regime
Groups face multiple data laws.
A DIFC-registered asset manager running a mainland service company alongside it is under DIFC Law No. 5 of 2020 and the federal PDPL simultaneously, each with its own regulator. That is a data-model decision rather than a policy one: the platform has to hold the boundary, not document it.
Our methodThe regimes in scope are named before the schema is drawn.
02of 04
One system cannot moveThe architecture starts there
One system never gets replaced.
A Sharjah SAIF Zone manufacturer running finance on something installed in 2011 is not going to migrate it because a proposal assumed so. Competitors sell rip-and-replace by omission. We ask which system is fixed on the first call, because everything downstream is arranged around the answer.
Our methodThe immovable system is identified before any architecture is proposed.
03of 04
In-country has a shapeNot a checkbox
UAE residency has a shape.
AWS has run an in-country region here since 29 August 2022 across three availability zones, and Azure UAE North sits in Dubai. Azure Abu Dhabi is access-restricted and granted for defined scenarios such as disaster recovery, so residency belongs in the architecture rather than in a questionnaire six months later.
Our methodThe residency decision is taken in the architecture phase, in writing.
04of 04
ICV is scored per entityAnd the licence caps it
ICV is scored per entity.
A supplier on anything other than an Industrial Licence is scored as a Service Provider, and a free-zone Service Provider is counted as outside the UAE in the formula. An ADGM fintech bidding into Abu Dhabi work discovers that the achievable score was capped at incorporation.
Our methodWhich entity bids is treated as an architecture input, not an afterthought.

What the engagement contains

The engagement in six phases.

Six pieces of work, and the fifth is the one competitors leave to a procurement questionnaire six months after signature.

Discovery and architecture

The estate mapped, the immovable systems named and the entity structure written down, before a schema exists

Output

an architecture somebody can disagree with in week three rather than month nine

The estateThe entities

Platform build

Built in phases that each end in something usable, so the first department is working while the second is being scoped

Output

value before the whole thing is finished

PhasedUsable early

Connecting systems

The connections into the systems of record, built so the record stays where it is and the platform reads and writes against it

Output

one truth, in the place it already lived

Read and writeIn place

Data migration

Moved in a rehearsed sequence with a reconciliation at each step, because a migration nobody can reverse is a launch nobody can stop

Output

numbers that tie out before cutover

RehearsedReconciled

Regime and residency review

Which law each entity is under, where the data may sit, and the access model written as a matrix rather than described

Output

the answers a questionnaire asks, ready before it arrives

The regimeResidency

Handover and support

The repository, the runbooks and the accounts in your name, with support scoped as a term rather than assumed

Output

a platform you could hand to somebody else

In your nameRunbooks

Our stack

The tools behind the boundary.

The kit behind a platform that answers a questionnaire from its own architecture. Select one to see why it earns its place, and what we do with it that most do not.

AWS

Why AWS

Residency stopped being a constraint here and became a decision. There has been an in-country region since 29 August 2022, across three availability zones, which means "the data stays in the UAE" has an architecture behind it rather than a promise.

How we excel

We decide the region in the architecture phase and write it into the scope, so the answer exists before a procurement questionnaire asks for it. Discovering the residency requirement after the platform is built is a migration, not a setting.

In-country regionAvailability zonesSince

AWS2022

AzureDubai

An offshore regionElsewhere

A vendor tenantTheir choice

How the work runs

Built under audit for every department.

The order is set by what has to be provable at the end. A platform that cannot show who did what is a platform that fails its first review.

01Before buildScoped

Map the estate and the regime.

We establish which entities are in scope and which law each sits under, which systems are immovable, and where the data may be held. Those three answers are written into the scope before an architecture is drawn, because each of them changes the schema rather than the configuration.

The entitiesand the law each is under
The estateimmovable systems named
Residencydecided, not deferred

02Under auditBuilt

Build and migrate under audit.

The platform is built in phases that each end in something a department can use, integrated against the systems of record rather than around them, and migrated in rehearsed steps that reconcile. The audit trail is not a later feature; it is on from the first record written.

Each phaseends in something usable
Migrationrehearsed and reconciled
The trailon from the first record

03By departmentRunning

Roll out department by department.

Each department goes live against an access matrix somebody has approved in writing, rather than a permissions set assembled during training. The repository, the runbooks and the accounts are in your name throughout, so the last phase is a handover of operation rather than of ownership.

Accessa signed matrix, per department
Runbookswritten as you go
Ownershipyours from the first commit

The regime the build was designed against is written into the scope, with the repository in your name.

Governed from the first record

The regimeAudit trailPhased

Our commitment

Yours from day one.

Enterprise engagements fail at the regime, at the immovable system and at the point somebody asks who owns it. These four are about that.

Ownership starts on day one
The repository sits in your organisation from day one rather than transferring at the end, and the cloud accounts are in your name. An enterprise platform you cannot hand to another supplier is not an asset, it is a dependency.
The regime is named upfront
Which law each entity is under, and where its data may sit, is written down before the architecture rather than answered in a questionnaire later. Where a group spans zones we name every regime in scope, not the convenient one.
Price is fixed per phase
Each phase is quoted and scoped on its own, so a change in phase three is a decision rather than a renegotiation of everything. An enterprise build priced as one number is a number nobody can defend by month six.
Sometimes a licence is better
If the process is generic and the entity structure is simple, a configured suite from a good partner will serve you better and cost less to run. Saying so is the least commercial line here and the reason the rest is worth reading.

Common questions

Your ERP and software questions answered.

When the fit is the expensive part. A licensed ERP is the right buy where the process is generic, the entity structure is simple and the connectors you need already exist, and in that case a good implementation partner will serve you better than we will. It stops being the right buy when the configuration bill starts to look like a build, when the per-seat licence grows faster than the value, or when the data question has an answer the vendor tenant cannot give. Most of the organisations that reach us have already discovered one of the three.
FAQ · 01
Yes, and it is the first thing we establish. DIFC entities are governed by DIFC Law No. 5 of 2020 rather than the federal PDPL, ADGM entities by the ADGM Data Protection Regulations 2021, and a mainland entity by the federal PDPL, each with its own regulator. The consequence for a build is that a group operating across zones is under more than one framework at the same time, so the platform has to hold that boundary in the data model rather than describe it in a policy. Where a record sits and which of your companies may see it is settled at custom CRM development for a sales system; here it is settled for the whole estate.
FAQ · 02
That is the starting point rather than a later phase. We ask which system is immovable on the first call, because everything else is arranged around it: the finance system a parent company mandates, something installed years ago that nobody will touch, or a system a client or a regulator requires you to use. The integration is built so that system does not change, reading and writing against it while the record stays where it already lives. A proposal that quietly assumes a migration is a proposal that has not asked the question.
FAQ · 03
That is a build requirement with a date on it, not a compliance checkbox. Structured e-invoicing runs through an Accredited Service Provider under Ministerial Decision No. 64 of 2025, on the Peppol-based PINT AE standard, and businesses at or above AED 50 million in annual revenue appoint a provider by 30 October 2026 and comply from 1 January 2027. What that means architecturally is that the finance layer has to emit structured data to a third party on a schedule, which is an integration with a deadline. When each obligation falls due, and how the dates interact, is argued at AI automation in Dubai.
FAQ · 04
Sometimes, and where it does the answer has a shape rather than a checkbox. There has been an AWS region in the country since 29 August 2022 across three availability zones, and Azure UAE North sits in Dubai. Azure has a second UAE region in Abu Dhabi, but access to it is restricted and granted for defined scenarios such as disaster recovery, so an architecture drawn against it may not be one you can actually use. We settle the region during architecture and write it into the scope, because discovering a residency requirement after the platform exists is a migration rather than a setting.
FAQ · 05
You see something usable well before the platform is finished, and that is the point of phasing it. Each phase ends in something a department can actually work in, so the first group is live while the second is still being scoped, and the architecture is available to disagree with in week three rather than month nine. We commit to a scope and a price per phase rather than one number for the whole programme, because an enterprise estimate given as a single figure is a figure nobody can defend once the first integration turns out to be harder than the demo. Where a group bids for government-linked work, the entity structure is worth settling early too, and that is argued at Abu Dhabi.
FAQ · 06
You own it throughout, not at the end. The repository is in your organisation from the first commit, the cloud accounts are in your name, and the runbooks are written as the work happens rather than assembled at handover. That means the end of the engagement is a transfer of operation rather than of ownership, and you could put the platform in front of another supplier without asking us for anything. How this sits inside the wider automation programme is argued at AI and automation in the UAE.
FAQ · 07

Keep exploring

Explore AI and Automation Services

Part ofAI and Automation Services

AI Consulting

What your licence and data regime allow, ranked and costed.

Custom AI Development

Built where your own data beats a hosted model.

AI Chatbot Development

Answers from your documents, in the Arabic customers write.

AI Voice Agents

Agents that answer your published line, in Arabic and English.

AI Dialers

Outbound calling built inside the telemarketing rules.

WhatsApp Automation

Threads that finish in writing, in Arabic and English.

Business Process Automation

Rewrite the process for this market, then automate it.

Workflow Automation

Wire the two systems either side of the hand-off.

CRM Development

A CRM that knows which of your companies is selling.

Next step

Scope it against what cannot move.

Tell us which systems are fixed and which entity the platform runs under. We will come back with the phases, in order.

Tell us what you need.

Enterprise software beyond packaged ERP.

Built to the process

Wired into what exists

Governed against the regime

The platforms we build.

Core business platforms

System integration

Legacy modernisation

Approvals that survive an audit

Dashboards and MIS

Customer and partner portals

Three ways to build a platform.

What decides the architecture here.

Groups face multiple data laws.

One system never gets replaced.

UAE residency has a shape.

ICV is scored per entity.

The engagement in six phases.

Discovery and architecture

Platform build

Connecting systems

Data migration

Regime and residency review

Handover and support

The tools behind the boundary.

Built under audit for every department.

Map the estate and the regime.

Build and migrate under audit.

Roll out department by department.

Yours from day one.

Your ERP and software questions answered.

Explore AI and Automation Services

AI Consulting

Custom AI Development

AI Chatbot Development

AI Voice Agents

AI Dialers

WhatsApp Automation

Business Process Automation

Workflow Automation

CRM Development

Scope it against what cannot move.