When a manufacturing owner evaluates an ERP, the question that comes first is almost always "what does it cost", and the number they reach for is the licence price. That instinct leads to poor decisions, because it focuses on the least important number and ignores the ones that matter. This piece is about what manufacturing owners get wrong about ERP cost.
Mistake one: thinking the licence is the cost
The licence price, what you pay the software vendor, is the most visible part of ERP cost and one of the smallest. The real cost of an ERP is dominated by the implementation: configuring the system, preparing and migrating data, customising where genuinely needed, training the team, and the effort the business itself puts in. An owner who compares two systems on licence price alone is comparing the tips of two icebergs. A cheaper licence on a system that is expensive and difficult to implement is not cheaper. The first correction is to stop thinking "ERP cost" means "licence price".
Mistake two: ignoring the cost of your own people's time
A real ERP implementation requires significant time from the manufacturer's own people, the people who know how the business works have to help shape how the system will run it. That time is a genuine cost, and owners routinely leave it out of the sum entirely, then feel ambushed when the project pulls key people away from their day jobs. It is not a hidden cost; it is a predictable one. Budget for it honestly, in time and in attention, and the project does not derail when it arrives.
Mistake three: treating the status quo as free
This is the most consequential mistake. When an owner weighs the cost of an ERP, they weigh it against zero, as if doing nothing costs nothing. Doing nothing is not free. The current way of running the business, the spreadsheets, the disconnected tools, the workarounds, has a real and continuous cost: money tied up in wrong stock, work quoted at a loss because true cost is unknown, skilled hours spent on reconciliation and data entry, decisions made on stale numbers, the operation depending on a few people's heads. That cost is paid every month, and it is invisible only because it is not on an invoice. The honest comparison is not "ERP cost versus zero". It is "ERP cost versus the cost of continuing as you are".
Mistake four: seeing only cost, not return
An ERP is an expense, but it is bought to produce a return: fewer stock-outs, accurate costing that fixes pricing, faster month-end, less time lost to reconciliation, an operation that can grow without strain. An owner who looks only at the cost side of the page, and never estimates the return side, cannot actually judge the decision. The question is not "how much does it cost" but "what does it cost, and what does it give back, against what the status quo is costing me".
Mistake five: underbuying or overbuying on price
Owners who fixate on price err in both directions. Some underbuy, choosing the cheapest option, and get a system too thin for the operation, so the manufacturing problems persist. Others, frightened into it, overbuy a heavyweight system far larger than the business needs, and drown in the implementation cost and complexity. Neither is a cost decision well made. The right system is the one sized to the operation, and price is one input to that, not the whole of it.
How to think about ERP cost properly
An owner should do four things. Cost the whole thing: licence, implementation, data, training, and the business's own time, first-year and ongoing. Cost the status quo honestly: what the current way of running the business is losing every month. Estimate the return: what genuinely changes when the operation runs on a connected system. And size the system to the operation, not to the lowest price or the biggest brand. Done that way, the ERP decision is a real investment judgement rather than a flinch at a licence figure.
The takeaway
Manufacturing owners get ERP cost wrong by treating the licence as the cost, ignoring their own people's time, treating the status quo as free, looking at cost without return, and letting price drive them to underbuy or overbuy. The honest view costs the whole thing, costs the status quo, weighs the return, and sizes the system to the operation. For how we approach this, see our ERP practice.