Blog — 2026-08-07
By Emad Yahya — web developer & IT systems engineer, Dubai
Almost certainly not — not as a first move. ERP means one integrated system running finance, inventory, purchasing, sales, HR and payroll off a shared database. It works, for companies with the volume, headcount and process discipline to justify it. Most UAE small businesses asking for "a custom ERP" are describing something much smaller and far more specific: one workflow that hurts, every week, and a hope that software will make it stop.
Let me put my own position on the table first, because it shapes everything below. I'm Emad Yahya, a web developer and IT systems engineer in Dubai. I have not shipped an ERP. I am not selling one. What I ship is focused systems — a brokerage CRM, an HR platform, a pharmacy POS, an online booking platform, an IT asset manager — the kind that solve one workflow properly and then get out of the way. So read this as a guide to whether you need something I do not build, from someone with no incentive to talk you into it.
Enterprise Resource Planning is an integrated suite where modules share a single database, so a transaction flows through the business without being re-keyed. A sales order reserves stock, triggers a purchase when stock runs low, posts to the ledger, and comes out the other end as an invoice — one record, touched by several departments, with no spreadsheet in between. That integration is the entire product. Everything else is modules.
The market is well served: large platforms, mid-market suites and open-source options sit at various points on the complexity curve, and most can typically be configured for UAE requirements by an implementation partner. If you genuinely need ERP, the answer is usually to buy a proven platform and hire people who implement it for a living — not to commission one.
But in Dubai business conversations, "ERP" often does not mean any of that. It usually means "a system that runs my business", said by an owner who is tired of chasing information. That is a completely reasonable request. It is just a different request, and answering it with a full ERP programme is a common way for a small company to lose a year.
Because integration is the expensive part, and a small business does not have enough moving pieces to pay for it. The value of ERP comes from eliminating handoffs between departments. If you have three departments and they sit in the same office, the handoffs cost you a conversation, not a consultant.
The failure mode is common enough to describe in advance. A long configuration project, a partner who understands the software but not your business, a system that goes live half-configured because everyone is exhausted, and a team that quietly keeps running the real work in Excel and WhatsApp because the official system does not match how the job is actually done. The company now pays for both.
One thing not to improvise on: your accounting and tax records. UAE VAT and invoicing requirements continue to evolve, so whatever operational system you build, your accounting system of record should be one your accountant is comfortable signing off on, and current obligations should be confirmed with them rather than with a software vendor.
In practice it decodes to one of a handful of specific pains. Most enquiries that open with the word ERP resolve to a line on this list:
Pick the one workflow costing you the most time or money right now. Build only that. Ship it, use it for a month, and let it prove itself before you commit to anything else. Then connect the next one.
Three reasons this beats a big-bang programme for an SME. Cash flow: you spend in stages, and each stage returns something usable. Adoption: staff learn one new system at a time, which is roughly the maximum any team absorbs while still doing their jobs. And learning: you find out what you actually need by using software, not by specifying it in a requirements document written before anyone has seen a screen.
The timelines make the argument on their own. A focused internal tool is typically a 2–4 week build. A full platform — CRM, HR, POS or booking — runs 4–8 weeks depending on features. A CRM's lead-and-pipeline core lands in 3–5 weeks, with the fuller build including commissions, approvals and reporting at 6–10 weeks. Those are real delivery times from systems now in production in Dubai. An ERP programme, by contrast, is typically a much longer commitment before anyone sees value.
Silos happen when the same fact lives in two places and nobody decides which one is true.
The fix is boring and effective. Agree a single owner for each core entity — the customer lives in the CRM, the employee lives in the HR system, the product lives in the POS — and make every other system read from that owner rather than keep its own copy. Design the exports and APIs at the start, when it costs nothing, instead of bolting them on later. Nominate one accounting system of record that everything reports into. Then use one test to judge the result: is anyone typing the same information into two systems? If yes, you have a silo. If no, you have modules.
Most SMEs need two or three connections, not a mesh — your booking system probably needs your calendar and your accounts, not your asset register. Resisting unnecessary integration is most of what keeps a modular setup cheap.
There is a genuine threshold, and pretending otherwise would be the same dishonesty in the opposite direction. Buy a proper ERP platform when several of these are true: multiple legal entities or branches whose accounts must consolidate; manufacturing or assembly with bills of materials; multi-warehouse inventory with transfers and real supply-chain complexity; a finance team rather than a finance person; and enough transaction volume that manual handoffs are measurably costing you.
At that point the right move is a proven platform and an implementation partner who does that work full time. That is not me, and I will say so on the call rather than after the contract. My work sits earlier on the curve — turning operations that run on spreadsheets and WhatsApp into one system with logins, permissions, history and reports.
If you are unsure which side of the line you are on, the build-vs-buy framework in my off-the-shelf guide settles most cases in an afternoon. Or describe your business and the workflow that hurts most, and you will get a straight recommendation — including "you need an ERP partner, not me" if that is the truth. If a focused build is the right call, you get a fixed written quote within 24 hours.
ERP is an integrated suite covering finance, inventory, purchasing, sales and HR off one shared database, usually bought as a platform and configured by an implementation partner. Custom software is built to solve a specific workflow the way your business actually does it. ERP buys you integration across departments; custom buys you fit within one. Small businesses almost always need fit first.
No — and I would rather be clear about that than take the project. I have not shipped an ERP, and building one from scratch for an SME is rarely the right call anyway. What I build is focused systems: CRMs, HR platforms, POS, booking systems and internal tools, several of which are running inside Dubai businesses today. If you genuinely need ERP, you need a platform and an implementation partner.
That question usually can't be answered as asked, because "ERP" covers everything from a single operational tool to a multi-module programme. What I can tell you is that scope drives everything, and that a focused system solving one workflow costs a fraction of an integrated suite. Describe the workflow that hurts most and you get a fixed written quote within 24 hours — and an honest answer if the right move is buying a platform instead.
They can be, and both are commonly used here — but test them against your real workflow before committing, not against a feature list. Run one full month of your actual process through a trial, including the awkward cases: a returned order, a mid-month leaver, a partial payment. Platforms that handle the awkward cases are worth configuring; platforms your team works around will end up as another system nobody uses.
Yes, if you plan for it rather than assume it. Give each core entity one owning system — customer in the CRM, employee in the HR platform, product in the POS — and design the exports and APIs at the start when they cost almost nothing. Most SMEs need two or three connections, not everything wired to everything.
With the single workflow that costs the most time or money right now, not with a master plan. Build that one properly, use it for a month, then decide what comes next based on what you learned rather than what you guessed. A focused internal tool is typically 2–4 weeks; a full platform runs 4–8 weeks.
Custom Software Development in Dubai · Custom Software vs Off-the-Shelf for UAE SMEs — the build-vs-buy framework · CRM Development in Dubai · HR System Development in Dubai · POS System Development in Dubai