◆
Why ERP Selection Requires Independent Expertise
A software demonstration shows a vendor’s preferred story. I help your team evaluate the process you will actually operate, including exceptions and integration needs. My hands-on ERP background is strongest in Odoo, and I founded ERPixel, an Odoo business. We make the advisory scope and any delivery involvement explicit before evaluation begins.
◆
Business Requirements Discovery
I interview management and the people handling daily work, then identify requirements for each business process. We distinguish essential controls from preferences and record the reason behind each requirement. This prevents the shortlist from being driven by whichever department produces the longest feature list.
◆
Current Process and System Assessment
I review the systems, spreadsheets and workarounds currently supporting the business. We identify what should be retained, redesigned or retired, including data that must move and integrations that must remain. You receive a baseline for comparing the full change required by each option.
◆
ERP Selection Criteria
I build evaluation criteria around process fit, reporting, integration, permissions, local requirements and the delivery model. We agree on mandatory conditions before assigning scores. A low price or attractive feature should not compensate for a missing process the company cannot operate without.
◆
ERP Vendor and Product Research
I investigate options against the agreed requirements and ask vendors to explain material gaps. The review covers the relevant product edition, hosting approach, integration capabilities and support arrangements. Product claims are recorded as questions to verify rather than accepted as proof of a usable solution.
◆
ERP System Shortlisting
I reduce the long list to options worth testing in detail. Each shortlist decision includes the reason for inclusion or rejection and any unresolved assumptions. The aim is a manageable comparison, with enough information to avoid spending weeks on demonstrations of unsuitable systems.
◆
ERP Demonstration Scenarios
I prepare scenarios using your transactions: for example a partial receipt, an intercompany sale or a returned order. Vendors demonstrate the complete flow, including reports and exceptions. Users can then evaluate how the proposed system handles their work instead of relying on slides.
◆
ERP RFP Preparation
I prepare a request for proposal that explains processes, volumes, integrations, data, rollout expectations and responsibilities. A common response structure makes proposals easier to compare. Vendors identify what is standard, configured, customised or supplied by a third party, with assumptions attached to estimates.
◆
ERP Vendor Evaluation and Scoring
I facilitate scoring and maintain an evidence record for each important requirement. We separate demonstrated capability from statements that still need validation. Scores support discussion; unresolved mandatory gaps, delivery risks and business constraints remain explicit in the final decision.
◆
ERP Implementation Partner Selection
I evaluate who will do the work, their relevant process experience and the availability of the proposed team. We review discovery, testing, migration, training and support responsibilities. A suitable ERP product still needs a delivery partner capable of implementing your particular operating model.
◆
Final ERP Selection Recommendation
You receive a recommendation explaining the preferred system and partner, remaining gaps, cost assumptions and implementation risks. I also set out the conditions that need to be resolved before commitment. The selection output becomes the starting point for implementation planning.