Key takeaways
- 01Start from your processes and pain points, not from a feature list.
- 02Insist on industry fit: the software should already speak your trade’s language.
- 03Judge the implementation partner as carefully as the product.
- 04Ask how the system will grow with you — branches, users, companies and AI.
- 05Count the cost over five years, not the price on the quotation.
Every growing business reaches the same point. The spreadsheets that once worked now disagree with each other. Stock on the shelf does not match stock in the books. Month-end takes longer every month, and the owner learns how the business performed weeks after it was too late to act. That is usually when the search for an ERP begins.
The search itself is where many businesses go wrong. They watch three demos, compare prices and choose the system that looked best on the day. Five years later, they discover whether it fits. Having implemented ERP for textile mills, distributors, housing societies, schools, manufacturers, restaurants and hospitals since 2001, we have seen what separates systems that last two decades from those replaced in two years. This checklist is the distilled version.
1. Start with your processes, not with features
Before you speak to a single vendor, write down how your business actually runs. Not how it should run — how it runs today. Follow an order from the moment a customer asks for a price to the moment their payment is in the bank. Follow raw material from the supplier to the finished product. Note every place information is re-typed, every register kept by hand and every report someone builds in Excel.
This map does two things. It shows you where the real pain is, so you can prioritise. And it gives you a script: in every demo, ask the vendor to walk your process through their system, step by step, rather than presenting the features they prefer to show.
2. Insist on industry fit
A general-purpose ERP can record any transaction, but it does not understand any business. A spinning mill thinks in counts, blends and frames. A housing society thinks in plot files, instalments, balloting and utility cycles. A restaurant thinks in recipes, covers and kitchen tickets. A distributor thinks in credit limits, dispatches and returns. If the software does not already speak that language, your team will spend years translating — or the vendor will spend your budget customising.
Ask each vendor which businesses like yours already run on their system, and for how long. Ask to see the industry-specific screens, not the generic accounting ones. The best evidence of fit is a client in your trade who has stayed for many years.
The best evidence of industry fit is not a feature list. It is a client in your trade who has stayed for ten years or more.
3. One system, not a set of connected ones
Many businesses end up with a point-of-sale system from one vendor, accounts in another and inventory in a third, joined by exports and imports. Each piece may be good, but the joins are where errors live. Every figure your management sees has to be reconciled before it can be trusted.
A true ERP records each transaction once, at the point it happens, and lets every department read the same record. A sale reduces stock, raises a receivable and posts to the ledger in a single step. When you evaluate a system, ask what happens downstream of a single transaction — and whether anyone has to touch it again.
- Does a sales invoice update stock, receivables and the general ledger automatically?
- Does a goods receipt link to its purchase order and the supplier’s invoice?
- Can management see the same figures as the accounts team, at the same moment?
4. Check it handles local realities
Software built for another market often struggles with the way business is done here. Before you commit, test the situations your team handles every week:
- Sales tax and withholding tax on purchases and sales, with the reports your tax advisers need.
- Post-dated cheques, cheque printing and bank reconciliation across several banks.
- Credit customers with limits in both days and amounts, and aging that management actually reads.
- Multiple branches, warehouses or companies under one owner, with consolidated reporting.
- Multi-currency transactions for importers and exporters.
If a vendor’s answer to any of these is “we can customise that”, ask how many clients already use the customisation — and who maintains it when the product is upgraded.
5. Judge the partner as carefully as the product
An ERP is not a product you install; it is a relationship you enter. The quality of the implementation — how well your data is migrated, how thoroughly your team is trained, how quickly problems are solved in the first months — decides whether the project succeeds far more than any single feature.
- Who will implement our system, and will the same people support it afterwards?
- Listen forNamed people with experience in your industry, not a hand-off to a call centre.
- How long have your oldest clients been with you?
- Listen forRelationships measured in years, with references you can call.
- How do you migrate our existing data?
- Listen forA clear plan for opening balances, item masters and open documents, with reconciliation before go-live.
- What happens when we find a problem after go-live?
- Listen forDefined response times, a support channel your team can reach, and a local presence.
- How are upgrades delivered, and what do they cost?
- Listen forUpgrades on the same platform that keep your history and customisations intact.
6. Plan for the business you will be in five years
The system you choose today should still fit when you have twice the branches, three times the users or a second company. Ask how pricing changes as you grow, how new branches are added and whether the system can run in the cloud, on your own servers or both.
Increasingly, growth also means AI. Modern ERP should let a manager ask a question in plain language — which customers are overdue, which products are slow-moving — and get a table, a chart or a short written insight back. It should also automate routine work such as reconciliations, reminders and reorder suggestions. Ask to see these working on real data, not on a slide.
7. Count the cost over five years
The cheapest quotation is rarely the cheapest system. Build a simple five-year view for each option that includes licences or subscriptions, implementation, data migration, training, hardware, annual support and the internal time your team will spend. Then add the cost you are trying to remove: the hours lost to re-keying and reconciliation, the stock written off, the receivables collected late.
A sensible way to proceed
- 01
Map
Document your key processes and the five reports management needs most.
- 02
Shortlist
Choose two or three vendors with proven clients in your industry.
- 03
Script
Ask each to demonstrate your processes, using your examples, end to end.
- 04
Verify
Call references in your trade, and ask how long they have used the system.
- 05
Phase
Go live with the financial core first, then add departments on a trusted ledger.
Choosing an ERP is one of the few decisions that will shape how your business runs for a decade or more. It deserves more than a demo. Take the time to choose a system that understands your trade, and a partner who intends to be there for the long run.