Custom ERP vs. Off-the-Shelf: The Honest 5-Year Cost Comparison
Per-seat licences look cheap in year one and expensive in year five. Custom builds look expensive in year one and boring in year five. Here is how to actually compare them.
The comparison most vendors won't show you
Ask an ERP vendor what their system costs and you will get the licence price. Ask a development company what a custom ERP costs and you will get the build price. Neither number is the one that matters. The number that matters is the total you will have spent five years from now — licences, implementation, customization, integrations, training, and the cost of the workarounds your team invents for everything the system doesn't do.
We build custom ERP systems for a living, so you should read this with that in mind. But we also tell roughly a third of the businesses that approach us to buy an off-the-shelf package instead — because for them it is genuinely the right answer, and a client who discovers that in year two becomes an expensive lesson in reputation. Here is the framework we use in those conversations.
When off-the-shelf ERP wins
If a standard package covers 90% or more of your processes out of the box, buy it. A trading business with conventional purchase-sell-stock flows, standard GST invoicing, and no unusual approval chains will get live on Zoho or Odoo in weeks for a few lakhs a year. No custom build can compete with that economics, and we will say so in the first call.
Off-the-shelf also wins when your team is small and stable (per-seat pricing stays proportionate), when you have no in-house appetite for owning software decisions, and when your processes are honestly nothing special — which is more common than most founders like to admit.
Where the off-the-shelf math quietly breaks
The break usually happens in one of three places. First, seats: at 10 users, ₹1,500 per user per month is pocket change; at 80 users across three locations it is ₹14+ lakhs a year, forever, rising with every hire. Second, customization: the moment your processes diverge from the package's assumptions — export documentation, multi-firm structures, job-work flows, dealer-specific pricing — you are paying implementation partners ₹2,000–₹4,000 an hour to bend software that resists bending, and every upgrade risks breaking what they bent. Third, the workaround tax: the 20% the package doesn't cover moves back into spreadsheets and WhatsApp, which is exactly where you started, except now you are also paying licences.
A useful signal: if your implementation-partner quotes for customizing SAP Business One or Odoo are approaching the quote for building the system you actually described, the package is no longer saving you money — it is charging you rent on a compromise.
The 5-year arithmetic, side by side
Off-the-shelf, 40-user mid-size manufacturer, realistic numbers: licences ₹7–10 lakhs/year, implementation and training ₹8–15 lakhs once, customization and annual-maintenance contracts ₹3–6 lakhs/year, upgrade-related rework every few years. Five-year total: roughly ₹60–90 lakhs — and you own nothing at the end.
Custom build, same business: first phase (the two or three modules causing the most pain) ₹16–35 lakhs, remaining phases over years two and three ₹15–40 lakhs depending on scope, then maintenance at ₹1.5–3 lakhs/year. Five-year total: roughly ₹50–90 lakhs — a similar band. The difference is the shape and the endpoint: custom is front-loaded, has no per-seat meter running, fits your processes exactly, and at year five you own an asset instead of renewing a subscription. Growth is the tiebreaker: every new hire, location, and firm makes the off-the-shelf line steeper and the custom line flatter.
The decision rule we actually use
Buy off-the-shelf if a package covers ≥90% of your processes, your team is under ~20 users, and your workflows are standard for your industry. Build custom if two or more of these are true: your processes are a competitive advantage you refuse to flatten; per-seat costs across your real headcount exceed roughly ₹8–10 lakhs a year; customization quotes rival build quotes; or you have already outgrown one package and are being quoted a 'migration' that is really a re-implementation.
And in either case, insist on the five-year number in writing — from the vendor, from the implementation partner, and from whoever quotes your custom build. Anyone unwilling to put a five-year total in front of you is telling you something about which number they would rather you not see.
In Short
Key Takeaways
- Compare 5-year totals, never year-one prices — licences plus customization plus the workaround tax
- Off-the-shelf wins at ≥90% process fit and small, stable teams — and we say so when it does
- The math breaks at scale: seats, divergent processes, and upgrade-fragile customizations
- Custom is front-loaded but flat: no per-seat meter, exact process fit, and you own the asset
- Get every five-year number in writing before deciding
Go Deeper
More Guides
Your situation is specific
Talk it through with an engineer
Book a free 30-minute discovery call. We'll apply this to your business and tell you honestly what we would do.
