This page does not produce a number. Any tool that asks you for a user count and a module list and then returns a figure is guessing, and the figure it returns is a sales qualification device rather than a budget. We would rather give you the thing a guess cannot: the complete list of lines an ERP budget contains, what moves each one, and which of them are routinely left out until they arrive as a variance.
Take this to your own vendors and make them fill it in. A vendor who will put a number against every line below is a vendor you can hold to something.
Software subscription or licence. Usually priced per user per month, with users split into tiers that are not equivalent. Ask which roles need a full seat and which need a limited one, because the ratio between them moves this line more than the headline rate does.
Implementation services. Configuration, testing, cutover and the project management around them. Almost always the largest line in year one, and the one with the widest spread between vendors.
Data migration. Extracting, cleaning, mapping and reconciling what you already hold. Priced on the state of your current data, which nobody can assess from a requirements document.
Integration. Every system that must exchange data with the new one. Costed per interface, and the count is usually higher than the first list suggests.
Customisation and extension. Anything the platform does not do as configured. This line carries a second cost nobody quotes: it is the line that makes future upgrades expensive.
Training and change. Not a launch-week event. The organisations that underspend here pay it back in the first close.
Ongoing support and internal effort. Vendor support, plus the time your own people spend running the system - which is real cost even though it never appears on an invoice.
Process variance first: how far your way of working sits from what the platform assumes. Then entity and currency complexity. Then the integration count. Then data condition. The user count - the input every online calculator leads with - sits well below all of these, which is precisely why a calculator built on it cannot be accurate.
Every line, with its unit and where the value comes from. The values are deliberately blank: they are yours to obtain, and a number we invented here would be worth less than the empty cell.
Replacing a system that works. Your costs concentrate in migration and change, because the process is known and the risk is in moving.
Replacing spreadsheets. Costs concentrate in configuration and training, because the process has never been written down.
Consolidating several systems. Costs concentrate in integration and data reconciliation, and this is the shape most likely to be underestimated at the outset.
Counting only named users and not occasional ones. Pricing integration per system rather than per interface. Treating data migration as a task rather than a workstream. Omitting internal effort entirely. Assuming training ends at go-live. And pricing year one without pricing years two and three, where the subscription and support lines continue while the implementation line does not.
It cannot tell you what your implementation will cost, and no page can. The spread between two quotes for the same requirement is routinely wide enough that any single published figure would mislead more readers than it helped. What it can do is make sure that when the quotes arrive, you can compare them line for line and see which one has left something out.
Why is there no calculator here? Because the rate model a calculator needs is not something we publish, and a figure produced from invented inputs would be a worse answer than no figure.
Will you give me a number if I ask? We will give you a structured range once we understand your entity structure, integration count and data condition - the three things that actually move it.
Do you resell any of these platforms? No. We hold no reseller arrangement that pays us to prefer one, which is why the worksheet above is platform-neutral.
We start from the worksheet above, fill it against your actual estate, and challenge the lines vendors have left blank. The output is a budget you can take to a board with the assumptions attached, rather than a single figure whose derivation nobody can reconstruct. See ERP selection consulting for how that engagement runs, and how we evaluate impartially for why we have no stake in the answer.
If you are still choosing between platforms rather than budgeting for one, start with Best ERP for Saudi companies. If you have a shortlist and need the budget to survive scrutiny, ask us and we will work through the worksheet with you.