What to take into the project
Use the same business scenarios and response structure for each vendor. Record what was demonstrated and what remains an assumption.
Define ERP Selection Goals
Define what the investment should change and which constraints are fixed. Growth across entities, unreliable inventory or slow financial reporting lead to different evaluation priorities. Agree the essential outcomes with management before research begins, along with the people who can make the final decision.
Document Business Requirements
Gather requirements from the teams that create, process and use business information. Explain the reason for each important requirement and define the expected result. Include exceptions and approval rules. A requirement should be specific enough that a vendor can demonstrate it and the business can judge the outcome.
Assess Current Business Processes
Map the current process and identify what should change before it enters a new system. Separate a necessary control from a workaround caused by existing software. This reduces the risk of choosing an ERP primarily for its ability to reproduce practices the business already wants to improve.
Create ERP Selection Criteria
Create criteria covering process fit, integration, data, reporting, permissions, delivery and cost. Distinguish mandatory conditions from weighted preferences. Agree how evidence will be recorded and who evaluates each area. A weighted score should not hide a critical gap that prevents normal operation.
Research ERP Vendors
Research products that plausibly fit the operating model and constraints. Ask vendors to identify relevant limitations, third-party dependencies and the edition required. Confirm important claims through documentation and demonstrations. Keep research focused on the agreed criteria rather than expanding the list whenever a new feature appears.
Build an ERP Shortlist
Shortlist options that justify detailed evaluation. Record why each candidate remains and what still needs to be verified. The shortlist should be small enough for meaningful process demonstrations and reference discussions. An unexplained long list shifts work to stakeholders without improving the quality of the decision.
Prepare ERP Demonstration Scenarios
Prepare scenarios drawn from your own work, with sample inputs and expected outputs. Include a normal transaction and a difficult exception. For example, test a partial receipt through invoicing and stock reporting. Ask vendors to show where configuration, custom work or external tools are required.
Evaluate ERP Systems
Score the demonstrated process and capture evidence beside the result. Allow users to explain usability concerns and unresolved questions. Compare standard functionality with the effort needed to implement the complete solution. A polished demonstration should not receive credit for work that remains unproven.
Compare Implementation Partners
Meet the proposed delivery team and review its relevant process experience, capacity and method of acceptance. Ask how discovery, migration, testing and training are divided between parties. Product selection and partner selection are connected decisions, but a strong product does not automatically guarantee a suitable delivery team.
Review Costs and Risks
Compare costs over the same scope and operating period. Include internal effort, integrations, migration, support and unresolved gaps. Review the assumptions most likely to change the estimate. This makes the decision more useful than a comparison of licence prices or headline implementation fees.
Make the Final ERP Selection
Document the preferred option, alternatives, material gaps and conditions that must be resolved before commitment. Assign owners to open questions and carry the evaluation evidence into implementation planning. A good selection record explains both why the option was chosen and what the business still needs to deliver.