The honest answer is that no single figure fits everyone, and anyone who gives you one without seeing how your company works is guessing. What can be explained clearly is what moves the price, so that when a quote lands on your desk you know how to read it and where the money is going.
What weighs the most: how many processes it covers
An ERP is not one thing. It is a set of modules, and every module is work. A system that handles sales and inventory does not cost the same as one that also covers purchasing, imports, dispatch, production and finance.
The most common building blocks are these:
- Sales: CRM, quotes, orders and e-invoicing.
- Purchasing and inventory: suppliers, warehouses and a stock ledger per product.
- Operations: dispatch, delivery, service orders or manufacturing orders.
- Management: dashboard, reports and consolidation across companies.
The first question that defines the price is not "which technology?" but "which processes does it have to solve on day one?"
Integrations
Every external system the ERP has to talk to adds work: e-invoicing, a payment gateway, a shipping carrier, an online store, or a legacy system that cannot be switched off yet. Connecting them is what stops people typing the same data twice, but each connection has to be built and tested.
The data you already have
Almost no company starts from zero. There are years of customers, products and transactions sitting in spreadsheets or in a previous system. Cleaning that data and loading it into the new system is part of the project, and it weighs more the more scattered it is.
Who is going to use it
A system for five people in one department is not the same as one where sales, warehouse, administration and management each log in to do their own thing. The more departments, the more permissions have to be defined: who sees what, who approves what. The same applies if the system has to serve several companies in the same group.
What should not move the price
Once the scope is agreed, the price should not drift on its own. It is reasonable to ask for two things before signing:
- A fixed price on a defined scope, in writing.
- That any change outside that scope is quoted separately and only goes ahead with your approval.
If a proposal does not say what it includes, it cannot say what it costs either.
How you get to a number
The sensible route is a diagnosis before a price. At xPlain that is a 30-minute conversation, free of charge, and you leave it with a quote that details modules, timeline and a fixed investment. Payment goes by milestones: you receive deliveries you can already use, and you sign off each one before moving on to the next.
How to spend less without cutting what matters
You do not have to build everything at once. What works best is starting with the modules that hurt the most today, which is almost always where time or sales are being lost, and expanding in phases without redoing what is already there. A system that solves three processes well is worth more than one that half-solves ten.
If you want to know what yours would cost, the next step is telling us what you need: you can see what a custom ERP includes or request your quote.