You're Growing. You Think You Need an ERP. Read This First.
Published: April 5, 2026
Your company is growing. Purchases are increasing. More people need to buy things. More assets to track. The accountant is overwhelmed. Someone — maybe a consultant, maybe a vendor, maybe a well-meaning friend — suggests the obvious solution: "You need an ERP."
Before you sign that contract, consider what the data says about companies that went down this path before you.
1. The Numbers Nobody Shares During the Sales Demo
ERP vendors show you a polished demo with every module working perfectly. What they don't show you is what happens after you buy:
| What happens | How often |
|---|---|
| Implementation exceeds the original budget | 3 to 4 times the initial estimate is typical |
| Implementation takes longer than planned | 30% beyond the original schedule on average |
| The system fails to meet original business goals | More than 70% of implementations |
| Employees actively use the system | Only 26% of the workforce |
| Purchased modules that sit unused | 60 out of 100 in a typical installation |
| Additional technology needed that nobody planned for | Half of all ERP projects |
These are not outlier stories. These are averages from industry research covering thousands of implementations globally.
2. The Shelfware Trap
A company purchases an ERP with 100 modules because the package deal seemed like good value. Two years later, the company uses 40 of them. Accounting works. Basic inventory works. Maybe payroll.
The other 60 modules — procurement approvals, asset management, compliance reporting, vendor management, advanced analytics — were never configured. The team that was supposed to set them up got pulled into other priorities. The consultant's engagement ended. The modules sit there. Unused. Untouched.
But the invoice keeps coming. ERP vendors typically charge 18 to 22 percent of the license cost as annual maintenance. This is charged on all 100 modules, not just the 40 you use. There is no natural expiration for unused licenses — you continue paying until you proactively cancel them. Most companies never do, because nobody audits which modules are actually in use.
This is called shelfware. It is one of the largest hidden costs in enterprise software.
3. The Indian SME Version of This Story
The global statistics are bad enough. In India, the pattern has its own flavour.
Indian SMEs frequently select ERP vendors based primarily on cost, which often leads to software that does not fulfil actual operational requirements. The cheapest option wins the purchase decision, but the cheapest option is rarely the one that fits.
Implementation drags on because the vendor's standard configuration doesn't match how the organisation actually works. Customisation requests pile up — each one costing more and taking longer than expected. Staff training is underestimated. The team that was supposed to champion the system is too busy with their regular work to learn a new one.
The result: the company ends up using the ERP for basic accounting — something Tally already does well — and everything else continues in Excel and WhatsApp. The lakhs spent on the ERP could have been invested in the business itself.
4. What You Actually Need (And What You Don't)
When a growing company says "we need an ERP," what they usually mean is: "We need to stop the chaos in how we buy things, track what we own, and report to management."
That's not 100 modules. That's five things:
- Purchase approvals. When someone needs to buy something, the request goes to the right person — based on the amount, the department, the type of purchase. Not through WhatsApp. Not verbally. Through a defined process that keeps a record.
- Purchase order management. The approved request becomes a formal order. The vendor knows exactly what was authorised. The finance team knows what's committed before the money leaves.
- Delivery verification. When goods arrive, someone confirms: did we receive what we ordered? Was the quantity correct? Does the invoice match? Discrepancies are flagged before payment, not discovered during the annual audit.
- Asset register. Everything the company owns — where it is, who has it, what it cost, what it's worth now. Built automatically from the purchases that were received. Not maintained in a separate spreadsheet that nobody updates.
- Accounting integration. The entries flow into your existing accounting system. No re-entering the same transaction in two places. The governance layer — approvals, purchase orders, delivery verification, asset register — works for any jurisdiction. The accounting integration is modular and adapts to your local system.
That's it. Five capabilities. Not a hundred modules. Not a 12-month implementation. Not a team of consultants. And you're not replacing your accounting software — it stays exactly where it is. You're adding the governance layer that sits in front of it, so that by the time a transaction reaches your books, it's already been requested, approved, verified, and recorded.
This approach — using focused, specialised tools alongside your core accounting system instead of one monolithic suite — is now the dominant trend in enterprise technology. Organisations increasingly keep their accounting where it works and add purpose-built systems for areas like procurement, HR, or asset management. The reasoning is straightforward: a tool built to do one thing well will always outperform a module that was bolted onto a platform designed for something else.
5. The Cost You Don't See
The license fee is the number everyone negotiates. But the real cost of an ERP is everything around it:
- Implementation consulting. The vendor's standard package never fits exactly. Someone has to configure it to your approval structure, your asset categories, your GST treatment, your depreciation policy. This is where the 3-4x budget overrun happens.
- Staff time. Your people spend months learning a new system instead of doing their jobs. 40% of companies underestimate this cost.
- Ongoing maintenance. 18-22% of the license cost, every year. On all modules. Whether you use them or not.
- Opportunity cost. The ₹30-50 lakhs you spent on an ERP could have been working capital, a new hire, a market expansion, or inventory. Instead, it's paying for 60 modules that nobody configured.
- Switching cost. Once you're in, you're locked. Your data is in their format. Your team learned their interface. Moving to something else means starting over. This is why shelfware persists — it's easier to keep paying than to migrate.
6. The Alternative: Start With What You Need
The smartest thing a growing company can do is resist the urge to buy everything at once.
This isn't about replacing one ERP with another. It's about starting with a governed process for the one thing that's costing you money right now — uncontrolled procurement — and adding capabilities only when your operations demand them.
Start with purchase approvals. Just that. When someone in your organisation wants to buy something, they raise a request. It goes to the right person. They approve or reject. There's a record. That alone — just structured purchase approvals — eliminates the chaos that prompted the "we need an ERP" conversation in the first place.
Then add delivery verification. Then the asset register builds itself from what was received. Then connect it to Tally when you're ready.
Each step takes days, not months. Each step builds on the previous one. And at no point are you paying for modules you haven't configured yet.
The question isn't "which ERP should we buy?" The question is: "what do we actually need governed right now?" Start there. The system grows as your organisation grows. Every rupee you don't spend on unused modules is a rupee invested back in your business.