The honest answer to “how much does a custom ERP cost” is that it depends on what the system has to do. That sounds like dodging the question, but it isn’t. Two systems that are both called ERP can differ the way a family house differs from a warehouse. Both have walls and a roof, and the building costs have nothing to do with each other.
So you won’t find a price list or ranges here. Instead, this article explains what the price is made of, the things that actually move it, and how to prepare so that the quote you receive matches what you need.
What the price is made of
The cost of a custom system has two parts:
- the build, one-off, covering analysis, design, development, integrations, data migration and the switch-over
- a monthly subscription, covering hosting, backups, maintenance, support and further development after the switch
Most of what follows affects the build. The subscription is covered separately, further down.
What drives the build cost
Scope and number of processes
The biggest single factor is how many business processes the system covers and how tightly they are linked. A system that handles orders and delivery notes for one warehouse is one job. A system that follows the path from inquiry through costing and work orders to delivery and the delivery note is a very different one.
The number of modules says less than the number of rules inside them. Discounts by customer, by product group and by quantity, with exceptions for certain partners, mean more logic, more testing and more conversations than a single price list.
Exceptions and special cases
Most companies have a standard flow that covers the bulk of their work, and a set of exceptions around it: partial deliveries, returns, complaints, orders that change after confirmation, products made to a drawing.
Every exception the system has to support adds work. Some are worth it. Others can stay manual. That conversation belongs before the quote, not halfway through development.
Integrations with existing tools
Very few companies start from zero. There may be an older ERP, a webshop or a large customer’s B2B portal, while the invoicing software stays as it is. Every connection to an outside system has a cost, and that cost depends on how open the other system is.
If it has a documented API, the work is predictable. If data can only be pulled out through file exports or directly from its database, expect more work and more checking.
Direction matters too. Sending webshop orders one way into the system is simpler than keeping products and stock in sync between two systems that are both allowed to change the same data.
Data migration
Customers, products, price lists and open orders have to come from somewhere. If they sit in one tidy program, moving them is mostly a technical task. If they are spread across several spreadsheets, with the same customer entered three times and products under different codes, most of the work is cleaning rather than moving.
Companies tend to underestimate this part. Decide early what gets migrated: the full history, or only active customers, products and open items.
Users, roles and permissions
The number of users matters less than the number of distinct roles. Ten sales reps doing the same job are one role. A sales rep, a sales manager, a warehouse worker, purchasing, management and an outside partner with limited access are six roles, each with its own screens, permissions and approval steps.
For the subscription, the number of users doesn’t matter, because it isn’t limited.
Field work
If drivers, installers or service technicians work in the field, they need screens built for the phone, in the browser. That raises questions an office system never has to answer: photos, customer signatures on screen, barcode scanning and places with weak signal. All of it needs to be in the brief from day one.
Documents and reports
Every printout that goes to a customer or supplier, whether a quote, delivery note, work order or material certificate, has to look the way your partners expect. Management reports take time as well, especially when they combine data from several parts of the system.
What the monthly subscription covers
Building the system is not the only cost. It needs hosting, backups, updates and someone who knows it when things change: a new process, a new customer with special demands, a second warehouse.
That is what the monthly subscription covers:
- hosting and backups
- updates and maintenance
- user support
- further development when the business changes
The number of users in the subscription isn’t limited. When you hire a new sales rep or warehouse worker, they get access at no extra cost, so everyone who needs to work in the system can.
The data is yours. You can export it whenever you want.
How to prepare for a realistic quote
A quote is only as accurate as the description behind it. If the vendor has to guess, they will either build in a margin for the unknown or the unknown will show up later as extra work.
Before the first meeting, it helps to put together:
- the path of one typical order from inquiry to paid invoice, step by step, with the role that handles each step
- the tools you use today and what lives in each one
- real documents: a quote, a delivery note, a work order, the spreadsheet someone updates by hand every week
- the exceptions that come up regularly
- where you lose the most time today, or where most mistakes happen
- who makes the decision, and who will use the system every day
You don’t need a finished specification. An honest description of how work gets done today is enough, including the parts that don’t work the way they should.
How the rollout risk is reduced
The biggest risk with a custom system isn’t technical. It is building something that doesn’t fit how the people using it actually work, or switching to a system that isn’t ready.
That is why parts of the business aren’t put live one at a time. Inquiries, quotes, orders, delivery notes and the customer base depend on each other, so they are built and checked as a whole. The risk is reduced before the switch:
- process analysis and screen sketches show before the build whether the system fits the way you work
- the system is tested with your real customers, items and stock levels, not made-up examples
- people try out and learn their part of the work before day one
- on the agreed day you move to the new system, with the vendor alongside until everything runs
After the switch the system isn’t frozen. New needs and refinements go in through the subscription, so the system changes along with the company.
What to ask a vendor
When you compare quotes, the total at the bottom tells you little if you don’t know what’s in it. Ask:
- what exactly is included and what isn’t
- how changes during development are charged
- what the monthly amount covers after the switch: hosting, backups, support, further development
- whether the price depends on the number of users
- who owns the data and how you can export it
- how migration is handled and who cleans the data
If the answers differ, so do the quotes, even when the totals look similar.
Getting an estimate for your company
The best place to start is a description of your process. Tell us how an order moves through your company today, which tools you use and where things get stuck. From there we’ll suggest what the system would cover and send an individual quote for the build and the monthly subscription.