Insight
What a custom ERP actually costs
Custom ERP pricing is quoted per module, not as one number. Here is what drives the figure, and when an off-the-shelf product is the cheaper answer.
The honest answer to "what does a custom ERP cost" is that nobody can tell you over email, and anyone who does is quoting a number they intend to revise later. But that is not a useful answer either, so here is what actually drives it.
It is priced per module, not as a system
A custom ERP is not one purchase. It is a sequence of them. You start with the part of the business causing the most pain — usually stock, orders, or job scheduling — and that first module is priced like a focused internal tool, because that is what it is. Each later module is quoted when you decide to build it.
This matters for cash flow as much as for risk. You are never writing one large cheque against a system you have not seen.
What actually moves the number
How unusual your process is. If your operation looks like every other operation in your sector, you are paying us to rebuild something you could have configured. If the thing that makes you competitive is also the thing your current tools handle worst, that is where custom earns its cost.
How many systems it has to talk to. Integration is usually cheaper than replacement, but every integration is real work — and the older the system on the other side, the more of it there is.
How much of your data needs moving, and what state it is in. Migration is planned in discovery rather than discovered in month three, and messy data is a cost whether or not you address it.
When you should not do this
If a configurable product covers you, buy the product. We will tell you that in discovery, and it is the cheapest conversation you will have with us. Custom software is worth it when the alternative is running your real process in a spreadsheet next to the ERP you already pay for.