Calculator · 3 minutes
What an implementation is likely to cost
Seven answers about the shape of your business produce a range — never a single number — across licence, implementation, data migration and first-year support.
We do not print a licence price. There is no defensible public figure for what a vendor will charge you, so instead everything is expressed as a multiple of your own licence quote. The multipliers are our planning assumptions and they are all shown on the result.
Indicative first-year range
3.8–5.9×
one year of software licence, all in
Expressed as a multiple because we will not print a licence price we cannot defend. Add your own quote on the left to see it in AED.
This is a budgeting range, not a quotation. It is here so you can tell whether to plan for a number with five digits or six before you spend three months in vendor meetings. Only a written diagnosis — your processes, your data, your people — produces a figure anybody should sign.
Where the range comes from
Four lines. Every one of them is a multiple of your licence cost, because that is the only cost in an ERP programme with a number attached to it before the work starts.
Software licence (one year)
1.0–1.0× licence
The anchor, not an estimate. This is whatever your vendor quotes for the users and edition you need — the one number you can get in a single email, and the one we refuse to invent.
Implementation
2.4–4.2× licence
Design, configuration, the parts that have to be built because your process is genuinely yours, testing, training and the weeks after go-live when people still need someone in the room.
Data migration
0.1–0.2× licence
Extraction, cleaning, mapping and reconciliation. The spread is wide because it depends entirely on what the old data turns out to look like, and nobody knows that until they open it.
First-year support
0.3–0.5× licence
Hosting, upgrades, the changes you will want in month four, and someone to call. This is annual and recurring — it does not stop after the first year.
What made it that size
The implementation and support lines are scaled by a single effort weight. These are our planning assumptions, shown rather than hidden, so you can argue with any one of them.
- Baseline+1.0
- 26–50 users+0.3
- One legal entity0.0
- Trading & distribution+0.2
- 3 modules in scope0.0
- Arabic / bilingual+0.2
- E-invoicing in scope+0.2
- Effort weight1.7
What this range is, and is not
It is
- An order of magnitude, good enough to decide whether to start a budget conversation this year or next.
- A way to sanity-check a proposal that has already landed on your desk: if a quoted implementation is far under this range, ask what has been left out of the scope.
- Deliberately wide. A narrow range at this stage would be a fiction with a decimal point on it.
It is not
- A quotation, from us or anyone. Nobody can price work they have not scoped.
- A market survey. We have not looked up what anyone charges and we are not telling you what your peers paid.
- A prediction that the project will succeed. Most of what goes wrong is not in the price — it is in whether the business changed how it works.
Turn the range into a number
A written diagnosis looks at your processes, your data and who actually has to change, and comes back with a scope and a figure you can put in a board paper. Send us the shape you just described and we will tell you what we would look at first.
Want someone to read this with you?
Ten answers cannot see your data, your contracts, or the person who quietly refuses to use the system. Send them over and a consultant will come back with what they mean for a company your size, and what we would look at first. No newsletter, no sequence — one reply from a person.
ERP Cost Estimator
A range is a budget line, not a quote
Tell us what came out and we will tell you which of the assumptions behind it are wrong for a business like yours — before you take the number to a board.
Monday to Friday, 9:00 AM – 6:00 PM (GST)
Prefer we call you?
Leave your WhatsApp number and we will reach out.