Every manufacturer we meet has already tried at least one ERP. Some run Tally with a dozen spreadsheets around it; some have a packaged ERP that the production team quietly ignores; a few have a legacy SAP environment that locks up during peak shifts. The question is rarely whether to have an ERP. It is whether the next one should be bought or built.
There is no universal answer, but there is a reliable way to reach one. It starts with an honest look at your processes rather than at vendor feature lists.
Start with the processes that make you money
List the five processes that most distinguish your plant: perhaps multi-stage job work with subcontractors, heat-number traceability, piece-rate payroll, distributor schemes or make-to-order configuration. These are the processes a packaged ERP is least likely to model well, because they are specific to your sector and your history.
If those processes are standard for your industry and a vertical ERP already models them, buying is usually right. If they are the reason customers choose you, bending them to fit a generic product will cost you the advantage.
Count the integrations, not the modules
Module counts are marketing. Integrations are engineering. Machines on the floor, weighbridges, biometric attendance, GST portals, courier APIs, WhatsApp and your bank all need to talk to the ERP. Packaged products often integrate with the popular ones and leave the rest to a partner, at partner rates.
A custom build treats integrations as first-class. In our ERP engagements, machine connectivity, GST e-invoicing and payroll rules are part of the data model from the start rather than add-ons purchased later.
- Which machines expose OPC UA, Modbus or vendor APIs?
- Which statutory filings must be generated from live data?
- Which external systems must stay (Tally, SAP finance, a bank portal)?
Consider the hybrid path
Most of our ERP work is not a big-bang replacement. We often keep the finance system a client trusts and build the modules that the existing system handles badly: shop-floor routing, job cards, machine monitoring, stores with barcode scanning. Clean integration layers let the two coexist.
This reduces risk, delivers value in the first quarter and gives leadership real data before deciding whether to go further.
Total cost over five years
Packaged ERPs cost less in year one and more in years three to five: per-user licences, customisation at partner rates and upgrade projects that break customisations. Custom ERPs cost more up front and then behave like an asset you own, with maintenance under an AMC you control.
Run the comparison over five years, including the cost of the processes you would have to change. That number, not the licence quote, is the real decision.