Guide · IT
Choosing Between Off-the-Shelf and Custom ERP
A decision framework covering true cost of ownership, implementation risk, and the process-fit question that decides most failures.
The real question
It is not build versus buy. It is whether your competitive advantage lives inside a process that standard software would flatten. If it does, customise there and buy everywhere else.
Total cost over five years
Off-the-shelf looks cheaper in year one and often is not by year three. Count licences per seat, mandatory upgrades, implementation partner fees and the customisation you will inevitably commission.
- Licence cost per user per year, escalated
- Implementation partner fees, typically 1–2x licence
- Customisation and integration work
- Internal time during rollout — the largest hidden cost
Why ERP projects fail
Rarely for technical reasons. They fail when scope covers everything at once, when the floor was never consulted, and when go-live happens without parallel running. Phased rollouts with one painful module first have a dramatically better record.
A workable rollout sequence
Start with the module tied to cash. Dispatch-to-invoice or purchase-to-payment produces measurable value in weeks, which buys organisational patience for the harder modules that follow.
FAQs
Questions this guide gets asked.
How long does an ERP rollout take?
Ten to twenty weeks for a phased custom rollout; large off-the-shelf implementations frequently run past a year.
Can we integrate with Tally?
Yes. Two-way Tally synchronisation is a standard requirement and should never be a reason to delay.
What about data migration?
Masters and opening balances should be in phase one. Full transaction history is rarely worth the cost.
More resources
Related guides and checklists.
Next step
Tell us the problem. We will tell you what it takes.
A 30-minute consultation with the practice lead who would actually run your mandate — no sales layer in between.