According to the latest Trovarit study, a medium-sized company spends 8-15 months selecting new ERP software. The methods used for ERP selection often differ, just like the software itself.
Must have" and "nice to have" in the ERP selection
Over the course of decades of ERP history, a number of principles have developed that inevitably belong in the "toolbox" of ERP selection. However, it is perhaps time to take a closer look at one or two paradigms and check whether they are in line with the state of development of today's software tools.
For a medium-sized company, there is often a specific problem or a triggering moment that leads to looking for a new ERP Software to see. However, with the introduction of the new Business software then optimise all processes as far as possible. In the subsequent creation of a specification sheet, the original objectives often fade more and more into the background. The "must-haves" and "nice-to-haves" then stand side by side on an equal footing.
Overloaded specifications
From the Specifications This results in a catalogue of requirements that is often overloaded and tends to stand in the way of system comparability. It should come as no surprise to either of them that many ERP providers only see a specification as an initial hurdle that needs to be overcome before serious discussions can begin.
On the other hand, when such "catalogues of duties" are discussed seriously, a lot of time and effort is put into checking features and processes that are then hardly relevant in "real life" because the monetary benefit falls by the wayside due to a lack of frequency or potential savings in automation.
The goals are more important
Perhaps it would sometimes be smarter to ask the providers before creating a Specifications talk about the goals. The real goals that are being pursued with the introduction of new ERP software. This initially helps the consulting company to understand what the problem is and whether and how it can help. At the same time, the entrepreneur looking for a new ERP system is not deprived of the opportunity to get to know new approaches without blinkers. But above all, the goal remains in focus, not features and technology.
In any case, all those involved in the process should always aim for a ERP introduction deal with. Otherwise it could happen that everyone only talks about ERP functions and ultimately the providers determine the discussion.
More on ERP selection:
NIS-2, medical technology & ERP
Generative AI in ERP: How LLMs are changing the role of ERP systems
Preparing the ERP future with APIs and microservices
Data quality & AI : AI can only be as good as your data
AI-ERP transformation basics and AI governance
