KinnowKinnow
Sign in
← All articles

How to choose an ERP for an Indian SME

Buying guide05 October 20267 min read

Ashish Chawla, Co-founder · Sales & Go-to-Market · LinkedIn

Choosing an ERP is one of the most consequential decisions an Indian SME makes. The wrong choice wastes money and months; the right one gives the business software it can grow into for a decade. This guide is a practical checklist - the questions to ask, the traps to avoid and the must-haves for a business that operates in India.

Start with what hurts

Do not start with a long feature list. Start with the three problems that cost you the most time or money today. For most Indian SMEs, those problems fall into a short list: the month-end close takes too long, GST filings are manual and error-prone, receivables are hard to track, inventory numbers do not match the physical count, or the promoter cannot see the real financial position without asking three people.

Write those three problems down. Every ERP you evaluate should solve at least two of them in the first month, not after a six-month implementation.

The checklist

1. Indian compliance built in

GST with IRN e-invoicing and e-Way bills, GSTR-1 and GSTR-3B prepared from the books, GSTR-2B matching for input tax credit, TDS, and payroll with PF, ESI and professional tax. These are not optional extras. If the ERP treats Indian compliance as an add-on or a partner-built extension, walk away. The compliance rules should be part of the main product, updated when the law changes, and tested by the vendor.

2. No per-user pricing

Per-user pricing punishes growth. A business with 20 people today and 80 next year should not face a four-times increase in software cost for the same ledger and the same routines. Look for pricing where every employee gets access without a per-seat charge. If the vendor charges per user, ask what happens when the warehouse team, the field staff and the project managers all need access - because they will.

3. Useful within four weeks

An ERP that takes six months to implement is an ERP that starts paying for itself seven months after you sign. For an SME, that is too long. The right ERP should be live - with real data, real transactions, real filings - within two to four weeks. Ask the vendor: what does week one look like? What does the business do on day fifteen? If the answer involves a long discovery phase, a blueprint document and months of running both systems side by side, the product is not built for an SME.

4. Several companies from day one

Indian businesses often run more than one company: a trading company, a manufacturing unit, a holding company, a partnership. The ERP should handle several companies as a matter of course - separate books, shared customer and item lists, combined reports - without buying a second licence or running a second copy. If you run one company today and might have three in two years, this matters.

5. Works without a dedicated IT team

Most Indian SMEs between 10 and 500 people do not have an IT department. The ERP should run in the cloud, update itself, back itself up and need no server room. If the vendor talks about installing on your own servers, looking after databases or applying patches, the product is designed for a different kind of buyer.

6. The CA can see the books

In India, the chartered accountant is often the most important external stakeholder. The ERP should give the CA read access - or better, a review portal - so they can check the trial balance, the tax workings and the filings without asking the team to export a spreadsheet. A CA who can see the books in real time catches problems before they become statutory notices.

7. AI that does work, not just dashboards

Dashboards are useful. But an ERP that also has agents - software that reads the records and does defined work like reconciling bank statements, chasing overdue invoices or preparing the GST return - saves hours every week. Ask the vendor: what does the AI actually do? Can you show me a bank reconciliation it performed? Can you show me a journal entry it drafted? If the answer is limited to charts and questions typed in plain language, the AI only reports; it does not do the work.

8. Moving your data, with a safety net

Every ERP switch means moving your data: opening balances, customer and supplier records, item masters, outstanding invoices. The right vendor brings the data across as the first step, not the last. And the system should let you see your financial statements in the old format - the layout your team checks against - so the switch does not feel like starting from scratch.

What to skip

Do not evaluate based on the number of applications. A vendor that lists 200 applications is not necessarily better than one with 49. What matters is whether the applications you need work together without extra connection work, and whether the ones you do not need today are available when you do - without buying an upgrade.

Do not decide on a demo alone. A demo is a rehearsed performance. Ask for a trial with your own data, or ask to speak to a customer in your industry who went live in the last six months.

The decision

The right ERP for an Indian SME is one that solves the three problems you wrote down, goes live in weeks, handles Indian compliance natively, does not penalise you for adding users, and gives your CA a window into the books. Everything else is a feature. Features matter, but they matter less than getting the fundamentals right.

Frequently asked questions

How long should an ERP implementation take for an Indian SME?

Two to four weeks for a business running 10 to 500 people. Data comes across first, the team starts using the software within the first fortnight, and refinements happen after go-live.

Should an SME choose a cloud ERP or an on-premise ERP?

Cloud. An SME without a dedicated IT team should not look after servers, backups or patches. A cloud ERP updates itself and works from any device.

Which Indian compliance features are must-haves?

GST with IRN e-invoicing and e-Way bills, GSTR-1, GSTR-3B, GSTR-2B matching for input tax credit, TDS, and payroll with PF, ESI and professional tax. These should be part of the main product, not add-ons.

Is per-user pricing a problem?

For a growing SME, yes. Per-user pricing means every new employee increases the software cost. Look for pricing where all users are included and the cost follows usage or value delivered, not headcount.

Tell Kinnow what slows you down.

Tell us in a sentence. Kinnow drafts a starting plan and a person follows up.