Choosing ERP software is one of the highest-stakes technology decisions a growing business makes. The wrong choice costs years of re-work; the right choice compounds in value as the business scales. Most ERP evaluations go wrong not because companies choose a bad product, but because they evaluate products before they have clearly defined requirements, or they let vendor demos drive the selection instead of their own operational priorities. This guide provides a step-by-step framework for structuring an ERP evaluation so the selection is driven by business needs, not by which vendor presentation was most polished.

Step 1: Document Your Current-State Problems Before Looking at Software

The first step in any ERP evaluation is not to request vendor demos. It is to build a clear picture of what is broken or constrained in the current operating model. This means interviewing department heads, mapping the core processes that cross department boundaries, and identifying where data gets lost, re-entered, or manually reconciled. Common pain points that drive ERP adoption include: finance teams spending excessive time on month-end close because data is scattered across spreadsheets and disconnected systems; operations teams unable to get accurate inventory positions without manual counting; sales teams quoting from outdated pricelists because pricing is not connected to procurement; and leadership making decisions from reports that are days or weeks old.

Four professionals exchanging documents during a meeting in an office setting.

Document these problems in terms of business impact: hours per week, error rates, delayed decisions, and lost revenue opportunities. This problem inventory becomes the evaluation scorecard. Every ERP system will claim to solve all of these problems; the documentation allows you to test specific claims against specific scenarios during demonstrations.

Step 2: Define Functional Requirements by Department

Functional requirements are the specific capabilities each department needs the new system to perform. Gather these through structured interviews with department leads, not through open-ended wish lists. For each requirement, note whether it is a must-have (the business cannot operate without it) or a should-have (it would improve efficiency but can be worked around). Group requirements into modules that map to how ERP vendors structure their products.

Finance requirements to cover

Chart of accounts structure and multi-entity consolidation requirements; period-close workflow and audit trail standards; tax and compliance requirements specific to the jurisdictions where the business operates; integration needs with banking, payment processors, and payroll systems; reporting and consolidation requirements across subsidiaries or business units. Finance requirements often have the highest must-have density and should be weighted accordingly in scoring.

Operations and inventory requirements

Warehouse locations and bin management complexity; demand planning and reorder point logic; purchase order approval workflows; receiving and quality inspection steps; landed cost allocation; serial and lot tracking for traceability requirements. Operations requirements vary enormously by industry and should be mapped against the specific inventory model the business uses.

Sales and CRM requirements

Lead-to-cash process coverage; quote and proposal generation; customer-specific pricing and discount structures; order management and fulfilment visibility; commission calculation; customer portal or self-service requirements. If the business uses a dedicated CRM that is deeply embedded, consider whether ERP-native CRM can meet the same needs or whether integration is the better path.

Step 3: Build a Long List, Then Score It

Once requirements are documented, identify five to eight ERP systems that serve your industry and company size. Include the incumbents your industry peers use, the platforms your implementation partners recommend, and any systems already being evaluated by leadership. Do not eliminate options at this stage based on brand recognition or price assumptions; many ERP pricing decisions are more flexible than the published list price suggests. For mid-market companies weighing the two most common platforms in this segment, a detailed Zoho One versus NetSuite ERP comparison covers the capability and cost trade-offs at different revenue thresholds.

Team conducting a business presentation with technology in a modern office setting.

Score each system against your requirements list before requesting demos. Research capability coverage through documentation, community forums, and case studies from companies of similar size and complexity. This pre-demo scoring surfaces systems worth deeper investigation and allows you to enter demos with specific questions rather than leaving capability discovery to the vendor’s prepared script.

Step 4: Structure the Demo to Test Your Scenarios

The most common ERP evaluation mistake is allowing vendors to run their standard demonstration. Standard demos are optimised to show strengths, not to reveal gaps. Instead, provide each vendor with three to five specific scenarios derived from your documented pain points and ask them to demonstrate how the system handles each one. Examples of scenario-based demo requests:

Scenario-based demos reveal configuration complexity, workflow gaps, and the actual user experience in ways that scripted demos cannot. Record each demo session and share the recordings with department leads who were not present during the live demonstration.

Step 5: Evaluate Total Cost of Ownership, Not Just Licence Price

ERP pricing has three components that evaluation teams frequently underestimate: the initial implementation cost, the ongoing licensing and support cost, and the internal resource cost of operating the system post-go-live. Licence pricing is usually the smallest of the three over a five-year horizon.

Man presenting business data with graphs on a whiteboard in a meeting.
Cost CategoryWhat to Capture
Licence feesPer-user or revenue-based annual fees; module-level pricing for add-ons
ImplementationPartner fees for configuration, data migration, training, and go-live support
IntegrationConnectors or custom APIs for systems the ERP does not replace
Internal resource timeFinance, IT, and operations time spent on implementation and training
Ongoing supportPartner retainer, internal admin headcount, upgrade and patch management
CustomisationCustom development for requirements the standard product does not cover

Request itemised quotes from at least two implementation partners per platform, not just the vendor’s own services team. Partner rates and scope approaches vary significantly, and a lower-cost partner on a well-matched platform can be more economical than an enterprise vendor’s in-house team.

Step 6: Reference Check Against Companies of Similar Complexity

Vendor-provided references are always positive. To get useful signal, ask vendors for references from companies that match your profile in three dimensions: industry vertical, revenue or employee headcount, and number of entities or locations. Then ask those reference customers the questions vendors would not ask on their behalf: what took longer than expected during implementation, what the system still cannot do that you expected it to would, how the support model has worked post-go-live, and whether they would choose the same platform again given what they know now.

If the vendor cannot provide references that match your complexity profile, that is itself useful information. It may mean the platform is not commonly deployed at your scale, or that reference customers at that profile have not had positive enough experiences to agree to be referenced.

Step 7: Plan for Implementation, Not Just Selection

The ERP selection decision and the implementation approach decision should be made together. A platform that is technically the best fit can fail in deployment if the implementation partner does not have deep experience with your industry processes, or if the internal project team does not have the capacity to run a concurrent deployment alongside daily operations. Before finalising the selection, confirm which implementation partners are available for the platform, check their specific industry experience, and assess whether your internal team can staff a project manager and two to three subject-matter experts for the implementation period.

The NetSuite ERP implementation guide covers what the deployment process looks like in practice for mid-market companies. For organisations evaluating multiple platforms, understanding what the implementation process actually involves for each finalist is as important as the feature comparison. Businesses that engage experienced NetSuite implementation partners early in the evaluation often get more realistic scope and timeline estimates than those who rely solely on the vendor’s project templates.

Frequently Asked Questions

How long should an ERP evaluation typically take?

A thorough ERP evaluation for a mid-sized business typically takes eight to fourteen weeks from requirements documentation to signed contract. Compressed timelines increase the risk of selecting a system that does not fully match operational requirements. The highest-value time investment is in the requirements documentation phase; teams that rush this step often discover gaps during implementation rather than during evaluation.

Should we use a consultant or do the ERP selection ourselves?

An independent ERP selection consultant can accelerate the evaluation by bringing pre-built requirements templates, vendor relationships, and knowledge of common implementation pitfalls. The key word is independent: a consultant who also sells implementation services for specific platforms has an incentive to recommend those platforms. If using a consultant, structure their engagement to end at contract signature rather than extending into implementation, or use a different firm for implementation to maintain objectivity.

How many vendors should be in the final shortlist?

Two to three vendors in the final shortlist is the right range for most evaluations. Fewer than two creates insufficient competitive pressure on pricing and implementation terms. More than three extends the evaluation timeline significantly and makes the scoring process unwieldy when multiple stakeholders are involved in the decision.

What is the biggest mistake companies make in ERP selection?

The most common mistake is starting with demos before requirements are documented. When requirements are unclear, evaluation teams score vendors on presentation quality rather than functional fit. The second most common mistake is underestimating implementation complexity for the specific industry processes the business depends on, which leads to budget overruns and extended timelines when those processes require customisation the team did not anticipate.

How do we evaluate ERP systems for multi-entity or multi-currency operations?

Multi-entity and multi-currency requirements significantly narrow the field of viable ERP platforms and increase implementation complexity. In demo scenarios, require vendors to demonstrate intercompany transactions, consolidated financial reporting across entities, and currency revaluation workflows. Ask specifically how the chart of accounts is structured across entities and what the process is for period-end consolidation. These features vary significantly between platforms that market themselves as multi-entity capable.

Evaluating ERP platforms and want an independent perspective on how NetSuite or Zoho fits your requirements? Aaxonix helps growing businesses navigate the selection process with structured requirements workshops and scenario-based vendor evaluations.

Get an independent ERP assessment

A well-run ERP evaluation produces a documented requirement set, a structured vendor comparison, and a realistic implementation plan before any contract is signed. The companies that get the most value from their ERP investments are not necessarily those who chose the most sophisticated platform; they are the ones who matched the platform to their actual operational requirements, selected an implementation partner with specific experience in their industry, and staffed the project with the internal capacity to see it through to go-live.