Custom ERP vs Off-the-Shelf: The Hidden Costs to Compare Over Five Years
Licences, customisation, workarounds and lock-in: the hidden costs that decide whether a custom or packaged ERP is better over five years.
Most ERP decisions are made by comparing the first-year proposal for a packaged system with the first-year proposal for a custom build. That comparison is understandable, but it is also the least useful one. The costs that decide whether an ERP was a good investment tend to appear in the years that follow, long after the contract is signed.
This guide walks through the hidden costs worth putting side by side over a five-year horizon. It explains when an off-the-shelf product such as Odoo, SAP Business One or Microsoft Dynamics 365 is clearly the better choice, and when a custom or hybrid system pays for itself.
1. Licences and seat growth
Packaged ERP products are usually licensed per user, per module or both, and the initial quote reflects the team you have today. As the business grows, every new employee who needs access, every new branch and every additional module adds to a recurring bill that never goes away.
To compare fairly, model your realistic headcount and module needs over five years rather than at launch. Check how the vendor treats read-only users, warehouse and field staff and external accountants, because licensing rules for these roles vary widely and can change at renewal.
A custom system has no per-seat licence, but it is not free to run either. Hosting, support and continued development are its recurring costs, and they deserve to be modelled with the same care.
2. Customisation and upgrade risk
Very few businesses run a packaged ERP exactly as it ships. Approval flows, pricing rules, reports and documents are adjusted to match how the company actually works, and each adjustment is reasonable on its own.
The hidden cost appears at upgrade time. Heavy customisation can make moving to a new version slow and risky, because every change has to be retested and sometimes rebuilt. Some companies end up stuck on an old version for years, missing improvements and security fixes they are still paying for. Ask any vendor or partner how your specific customisations will be handled in future upgrades, and get the answer in writing.
3. Implementation partners and your own team’s time
Packaged ERPs are rarely implemented by the software vendor directly. A certified partner configures the system, migrates data and trains staff, and that relationship continues for support and change requests long after go-live. The quality and continuity of that partner matter as much as the product itself.
Whichever route you choose, the largest unbudgeted cost is often internal: managers who spend weeks in workshops, staff who clean and migrate data, and a period of lower productivity while everyone learns the new system. Include this time in both scenarios; it is real, and it is similar in either case.
4. Workarounds and the spreadsheets that creep back
The clearest sign that an ERP does not fit is the return of spreadsheets. When a process cannot be handled in the system, people quietly export the data, manage it in Excel or on paper, and re-enter the result. Each workaround looks small, but together they bring back exactly the errors and delays the ERP was meant to remove.
Integration carries a similar hidden cost. Most businesses need the ERP to talk to e-commerce, POS, payroll, banking, logistics or a CRM such as Salesforce. Ready-made connectors cover common cases well; anything less common needs custom integration work that must be maintained whenever either system changes.
If you are weighing this decision for your own operation, a short scoping conversation that maps your real processes against a shortlist of products usually settles it quickly.
5. Data ownership, lock-in and switching costs
Your operational data is one of your most valuable assets. Check how easily you can export complete records, history and attachments from any system you are considering, and in what format. Some products make routine exports straightforward but make a full migration away from them difficult.
Switching costs are the final hidden cost. Leaving any ERP, packaged or custom, means migration, retraining and disruption, so the decision tends to last a long time. With a custom system you own the code and the database, which removes vendor lock-in but means you depend on good documentation and a capable team to maintain it. Make sure whichever option you choose leaves you in control.
When off-the-shelf wins, when custom wins, and the hybrid route
Off-the-shelf clearly wins when your processes are close to industry standard. Accounting, purchasing, standard inventory and payroll are solved problems, and a mature product brings years of refinement, compliance updates and a large support ecosystem. It is also the safer choice when you need to go live quickly or do not want to own a development roadmap.
Custom wins when the way you operate is itself a competitive advantage, when packaged products need so much customisation that you are effectively building on top of someone else’s platform, or when licence growth across a large or seasonal workforce becomes the dominant cost. It also suits businesses whose workflows span unusual steps that no single product covers well.
Many companies land on a hybrid: a standard product for finance and accounting, with custom modules or a custom operational layer for the processes that make them different, connected through clean integrations. This keeps the commodity parts standard and puts custom investment where it earns its keep.
How to run a fair five-year comparison
Build two simple models side by side. For each, list licences or hosting, implementation, customisation or development, integrations, internal time, training, support and expected changes over five years, using realistic growth assumptions rather than today’s headcount. Then add the cost of workarounds and of eventually switching away.
Test the result against your processes, not against feature lists. Walk through your most important daily workflows in each option and note every point where people would still need a spreadsheet. Waloshi Tech can help you map those processes and give you an impartial view of whether a packaged, custom or hybrid ERP fits your business best.
Frequently asked questions
Is a custom ERP more expensive than Odoo or SAP Business One?
Upfront, a custom build usually requires more investment than configuring a packaged product. Over several years the picture can change, depending on licence growth, customisation, upgrade effort and how many workarounds the packaged system leaves behind. The only reliable answer comes from comparing both options against your own processes and growth plans.
What are the hidden costs of an ERP system?
The most common are licence growth as you add users and modules, customisation that complicates upgrades, ongoing implementation partner fees, integration maintenance and the internal time your team spends on the project. Spreadsheet workarounds that reappear after go-live are another cost that rarely shows up in proposals.
When should a business build a custom ERP?
Custom makes sense when your core processes are genuinely different from industry standard and give you an advantage, when packaged products would need heavy customisation to fit, or when per-user licensing becomes a major long-term cost. If your processes are fairly standard, a packaged ERP is usually the better choice.
Can we combine an off-the-shelf ERP with custom software?
Yes, and it is often the most practical route. Many businesses use a packaged product for accounting and finance and build custom modules or apps for operations, field teams or customer-facing processes. The key is clean, well-documented integration between the two.
How long does an ERP implementation take?
It depends on the number of modules, the quality of your existing data, the integrations required and how available your team is for workshops and testing. Phased rollouts that start with one department or process usually reduce risk and deliver value sooner than a single big-bang launch.
