Skip to content

ERP & CRM

One system of record instead of nine spreadsheets.

Odoo, Microsoft Dynamics, Zoho and Salesforce implementations configured to how you actually trade, integrated with your bank and your VAT filing, and adopted because the training was real.

Book a discovery callBuild your plan
  • Dubai head office, GCC-wide delivery
  • Arabic and English throughout
  • Written scope and fixed timeline before you commit

You walk away with

  • Fit-gap analysis
  • Implementation
  • Data migration
  • FTA-ready VAT

Typical timeline

10–24 weeks

Typical engagements start around

AED 35,000 per project

What good looks like

rehearsal migrations before any cutover date
2+rehearsal migrations before any cutover date
VAT configured to FTA invoice requirements
5%VAT configured to FTA invoice requirements
system of record instead of nine spreadsheets
1system of record instead of nine spreadsheets

The problem this solves

Sales lives in one spreadsheet, inventory in another, and finance reconciles both by hand at month end. Someone sold an ERP licence eighteen months ago and the system now runs alongside the spreadsheets rather than replacing them. The software was never the problem — the implementation was, and so was the training that never happened.

Where this usually hurts

  • The system runs alongside the spreadsheets

    A licence was bought, a consultant configured it, and the team kept their spreadsheets because the system does not match how they actually work.

  • Month end is a reconciliation exercise

    Sales, inventory and finance hold different numbers, and closing the month means someone manually agreeing them by hand.

  • Customisation has become a cage

    Every upgrade breaks bespoke code written by someone who has left, so the platform sits three versions behind and cannot be patched.

  • Nobody was trained properly

    Two hours of screen-sharing at go-live, no role-based material, no one available in the moment of confusion — so adoption quietly failed.

We implement Odoo, Microsoft Dynamics 365, Zoho and Salesforce for businesses trading in the UAE and the wider Gulf. The work is only partly technical: most of it is deciding, with the people who do the job, which of your current processes are genuine requirements and which are habits worth abandoning before they get encoded into software for a decade.

Fit-gap before licences

We map your processes against what the platform does natively, then classify each gap: configure, extend, integrate, or change the process. The last option is the cheapest and the least popular, so we make the cost of each customisation explicit — every one is code somebody maintains and something that complicates every future upgrade.

  • Process map built with the people doing the work, not only the department heads
  • Every gap costed as configure / extend / integrate / change the process
  • Customisation counted as a long-term liability, because that is what it is
  • Licence sizing after the fit-gap, so you buy what you will use

Built for the way business runs here

UAE trade has requirements a generic template does not carry: VAT at five per cent with FTA-compliant tax invoices and the audit file the authority can request, e-invoicing readiness as the mandate phases in, multi-currency with AED as functional currency, WPS-compatible payroll, free-zone versus mainland entity structures, and Arabic on customer-facing documents. These are configuration decisions made at the start, not patches applied after the first filing goes wrong.

Data migration is the risk

Most implementations that slip, slip here. Legacy data is duplicated, half-formatted, and full of records nobody will admit to owning. We profile it early, agree what is actually migrating versus what is archived, and run at least two full rehearsal migrations into a sandbox your team reconciles against the old system before anyone commits to a cutover date.

2+

full rehearsal migrations before any cutover date is fixed

Adoption decides whether this worked

A system that is technically live and practically ignored has failed, and it fails quietly for months. We train by role rather than by module, run a hypercare period where someone is available in the moment of confusion, and track adoption — logins, records created, processes completed in the system rather than beside it — as the actual measure of success.

What is included

  • Fit-gap analysis

    Process mapping against native platform capability, with every gap costed and classified.

  • Configuration & build

    Modules configured, workflows and approvals set up, and extensions built only where justified.

  • Data migration

    Profiling, cleansing, mapping and at least two rehearsal runs reconciled by your team.

  • Integrations

    Banking, payment gateways, e-commerce, logistics and the existing systems you are keeping.

  • VAT & compliance setup

    Five per cent VAT, FTA-compliant tax invoices, audit file readiness and Arabic document templates.

  • Training & hypercare

    Role-based training, written and recorded, plus intensive support for the first month after go-live.

What we build with

  • Platforms

    • Odoo
    • Microsoft Dynamics 365
    • Zoho One
    • Salesforce

  • Integration

    • REST APIs
    • Middleware
    • Bank connectors
    • E-commerce sync

  • Reporting

    • Power BI
    • Odoo Studio
    • Financial reporting packs

How engagements are sized

Three sizes, so the scope matches the problem rather than the budget matching a template. Every tier is a starting point — the number moves with what we find in discovery, and you see the revised figure before anything is signed.

  • Essential

    One clear problem, scoped tightly and shipped.

    From

    AED 35,000

    per project

    CRM or a single ERP module for one entity, configured and adopted.

    • One entity
    • Up to 3 modules
    • Role-based training
    Get a firm number

  • Growth

    The full engagement, with measurement and iteration built in.

    From

    AED 110,000

    per project

    Full ERP across finance, sales, inventory and operations, with integrations.

    • Multi-module ERP
    • Banking and gateway integration
    • Data migration and hypercare
    Get a firm number

  • Enterprise

    Multi-entity, regulated, or integrated across several systems.

    From

    AED 280,000

    per project

    Multi-entity, multi-currency, free-zone and mainland structures, manufacturing.

    • Multi-entity consolidation
    • Manufacturing or projects
    • Compliance and audit reporting
    Get a firm number

Prices are in AED excluding 5% VAT. Other currencies on the pricing page.

How delivery actually runs

The phases below are what a typical engagement moves through, with the durations we plan against. You always know which phase you are in and what leaves it.

See the full process
  1. 1

    Fit-gap

    2–4 weeks

    Process mapping with the people who do the work, every gap classified as configure, extend, integrate or change the process, and each one costed.

  2. 2

    Configure and build

    4–10 weeks

    Modules configured, approvals and workflows set up, VAT and document templates done properly, extensions built only where justified.

  3. 3

    Migrate and rehearse

    3–6 weeks

    Legacy data profiled and cleansed, then at least two full rehearsal migrations your team reconciles against the old system.

  4. 4

    Train, launch, hypercare

    4–6 weeks

    Role-based training before go-live, then a month of intensive support with someone reachable in the moment something is confusing.

  • Fit-gap · You get

    • Process map
    • Costed gap analysis
    • Licence sizing

  • Configure and build · You get

    • Configured environment
    • FTA-ready VAT setup
    • Justified extensions only

  • Migrate and rehearse · You get

    • Cleansed data set
    • Two rehearsal runs
    • Signed reconciliation

  • Train, launch, hypercare · You get

    • Role-based training
    • Go-live
    • 30 days hypercare

Built for the UAE

What working with a Dubai partner actually changes

Most of what follows is invisible until it goes wrong — a supplier who cannot keep data in-country, an invoice the FTA rejects, a support rota that is asleep for half of your working day. These are the questions we answer before they become findings.

A generic ERP template does not know about five per cent VAT with FTA-compliant tax invoices, the audit file the authority can request, WPS payroll files, free-zone versus mainland entity structures, or the need for Arabic on customer-facing documents. These are configured at the start, not patched after the first filing is rejected.

  • Data residency, decided up front

    AWS me-central-1, Azure UAE North and OCI Dubai are all in scope. We map the whole data path — backups, logs, metrics and support access — rather than the primary database alone, and put the result in writing.

  • PDPL, and the free zones

    Federal Decree-Law No. 45 of 2021 governs most of the mainland; DIFC and ADGM entities fall under their own data protection laws instead. We establish which applies to your entity before we design anything that touches personal data.

  • VAT and e-invoicing that pass

    Five per cent VAT, FTA-compliant tax invoices, the audit file the authority can request, and readiness for e-invoicing as the mandate phases in. Configured in the build, not patched after the first filing is rejected.

  • Your hours, your languages

    Delivery runs on Gulf hours with real overlap with your team, in Arabic and English. Customer-facing interfaces, documents and training are produced in both where you need them, with RTL treated as a design requirement rather than a translation step.

Sectors we do this in most

Not the only sectors we work in — the ones where we have shipped this service enough times to know the regulatory edges and the usual traps.

  • E-commerce & Retail

    Fast storefronts and checkouts engineered to lift AOV.

  • Real Estate

    Listing and portal experiences that turn browsers into leads.

  • Travel & Hospitality

    Booking flows that reduce drop-off and drive direct revenue.

In-house, generalist agency, or us

An honest comparison, including where the other two options are the better call.

Hiring in-houseWorking with us
Time to first outputThree to five months to source, notice-period and onboard, in a market where senior specialists are scarce and expensive.Two to three weeks from signature, with people who have shipped this before.
Cost shapeFixed monthly cost plus visa, insurance, end-of-service and equipment, whether or not there is a full workload.Scoped to the work. Costs stop when the work does.
Breadth of skillOne or two specialisms per hire. Anything outside them gets improvised or outsourced anyway.Design, engineering, security and growth from the same team, without a handoff between vendors.
Institutional knowledgeStays in the building — which is the real advantage, and the reason to hire eventually.Documented and handed over. We write runbooks so you can take it back in-house.
When it is the wrong choiceRarely, once the workload is genuinely full-time and permanent.If you need someone in your standups every day for years, hire. We will say so.

Related work

Questions people ask before starting

It depends on your size, sector and appetite for customisation. Odoo suits SMEs wanting broad coverage at a lower licence cost; Dynamics 365 suits organisations already committed to Microsoft; Salesforce leads where the CRM side dominates; Zoho is strong on value for lean teams. We make a recommendation during discovery and explain the trade-offs rather than defaulting to whichever we resell.

Services that pair with this

Most engagements use two or three together.

Ready to talk about ERP & CRM?

Tell us what you are building and where it is stuck. We will come back with a scope, a timeline and a number — usually within two working days.

Step 1 of 3 · What you need

Which services are you interested in?