When a business evaluates an ERP, it compares proposals, and a proposal has a number on it: the cost of the implementation. That number gets scrutinised, negotiated, and approved. It is also, in our opinion, the least important number in the decision, because it is a fraction of what the system will actually cost, and the larger fraction never appears on any proposal at all.
What the proposal number covers
The implementation fee covers getting the system built and live: configuration, customization, data migration, training, the project to cutover. It is a real cost and a finite one. It has an end date. When the project is marked complete, that number stops growing. And then the part nobody quoted begins.
The cost that has no end date
Once the system is live, it has to be operated, and operating it costs continuously:
- Someone has to own it. A system needs an internal owner: someone who governs changes, runs the test environment, validates reports, decides what gets customized next. That is a real role and a real salary, whether or not anyone named it.
- It has to be kept current. Security updates, version upgrades, dependency maintenance. An ERP that is never upgraded does not save money; it accrues a debt that comes due all at once.
- It will change. The business will not stand still, so the system cannot either. Every year brings new requirements, new reports, new integrations. That is not a defect; it is the normal cost of a system that is actually used.
- It has to be hosted, backed up, and monitored. Infrastructure is a small line individually and a permanent one.
Add these up over the realistic life of an ERP, five years or ten, and the operating cost dwarfs the implementation fee. The number everyone negotiated was the small one.
Why this distorts the decision
When only the implementation fee is visible, the buying decision optimises for the wrong thing. A proposal that is cheaper to implement looks better, even if it produces a system that is more expensive to operate, harder to upgrade, and more dependent on a single vendor. The visible number wins the comparison; the invisible number is what the business actually lives with. A decision made on the implementation fee alone is a decision made on perhaps a fifth of the real cost.
The position, stated plainly
The right question is not "what does it cost to build this." It is "what does it cost to own this for the next ten years." That number is harder to produce, and it is the one that matters. A buyer who asks for it, and a vendor willing to estimate it honestly, are having the real conversation. Everyone else is negotiating the down payment and ignoring the mortgage.