How to choose the right ERP system – without regretting it later
What makes the difference between a successful and a frustrating ERP implementation? Not just the software you choose, but above all how you prepare that choice and guide the process.
Eight steps from analysis to go-live
Internal analysis
Requirements map
Market exploration
RFI / Longlist
Demo & Shortlist
Business case
Contract phase
Go-live
Start with yourself, not with the software
Many companies start an ERP selection with a list of vendors. That is the first wrong decision and, unfortunately, a pretty fatal one. You are better off starting internally: what are your core processes, where do your processes chafe today, what needs to be different five years from now?
What to look at: process flows per department, integration points, data flows, organisational pain points, compliance requirements and growth ambitions.
Important: involve all stakeholders, from finance to warehouse.
Translate your needs into requirements
Everything you gathered in step one, you structure in a requirements document. Functional and non-functional. With priorities: must-have, should-have, nice-to-have. That document is your compass throughout the entire process.
Pitfall: requirements that are too vague cause comparison problems later on. Every requirement must be measurable or testable. So beware of descriptions such as ‘user-friendly’ and ‘flexible’.
Explore the market without being seduced
Only now do you look at what the market has to offer. Not to go shopping, but to understand which solutions are suitable for your sector, scale and maturity. Salespeople are masters at telling you what you want to hear. You need facts.
Sources: analyst reports (Gartner, Forrester), sector-specific benchmarks, reference calls with comparable companies and independent market analyses.
RFI and longlist: structure brings clarity
Send a Request for Information (RFI) to a selection of vendors – typically six to ten. Don't ask for prices, but for insight: how does their solution work, how do they deal with your sector, what references do they have? With those answers you filter down to a longlist.
Scoring framework: use your requirements document as the basis for an objective score matrix. Compare apples with apples, not with pears.
Demos and shortlist: look beyond the slide deck
From the longlist, you select three or four candidates for a structured demo based on your own processes and data. That way you see how the system responds to your reality, not to the vendor's.
Tip: dig deeper on workarounds and configuration limitations. Also let key users take part in the demos and evaluate immediately afterwards. Don't let the impressions fade.
Watch out: after a convincing demo, it can feel as if the choice is obvious. That feeling is dangerous. In fact, it is only just beginning: references, total cost of ownership, contract details and implementation approach. Anyone who skims over these now risks unpleasant surprises after signing.
Business case and TCO: calculating with the right numbers
Request a detailed quote from two or three shortlisted candidates. Calculate the Total Cost of Ownership over at least five years: licences, implementation costs, customisation, training, maintenance and scalability. Weigh these against the expected benefits.
Underestimated costs: internal man-hours during implementation, change management, data migration complexity and future upgrades. A cheap licence is rarely a cheap solution.
Contract and implementation phase: detail is protection
Don't negotiate on price alone. Negotiate on SLAs, exit clauses, liability in case of delays, ownership of data and customisations, and the implementation methodology. A good contract protects you when things get difficult.
Implementation: insist on a phased approach with clear milestones, go/no-go moments and a strong project governance model on both sides.
Go-live is a beginning, not an endpoint
Going live is the moment when the system is truly tested, by real users, under real pressure. Plan hypercare support for the first few weeks, make sure you have well-trained key users as the first line of contact and measure your KPIs from day one.
After go-live: plan a formal evaluation at three and six months. Processes evolve, and the system has to evolve with them. An ERP implementation is only successful when the organisation is effectively better off because of it.
A walk in the park?
On paper, this process looks straightforward. In practice, it is far less so. Every step involves decisions with long-term consequences. The required objectivity is sometimes hard to safeguard internally: people have preferences, agendas, blind spots. The technical knowledge to truly assess vendors is often lacking. And the time to do everything thoroughly is often simply not there – because the day-to-day work still has to get done.
While for a company such a process is an exercise that only has to be done once every few years, for us it is our daily business. We have guided numerous ERP implementations for clients who understood from the start that it is better not to do this alone.
Are you taking your ERP implementation seriously too?
Contact us for an initial introduction. We'd be happy to take a critical look together with you.
Contact Evolynx
Contact Evolynx