The Complete ERP Selection Guide

Last Updated: November 3, 2026

Share this article:

Selecting the right ERP software requires aligning technology decisions with business strategy. As ERP capabilities evolve through advances in AI, automation, and other enterprise technologies, organizations must evaluate how potential solutions support their future-state business processes, technology architecture, and long-term modernization goals. A strategically aligned digital transformation plan helps guide these decisions and ensures that ERP selection addresses both immediate priorities and future business needs.

From defining your future-state business requirements to evaluating ERP vendors and preparing for implementation, this guide outlines the key decisions, methodologies, and considerations involved in selecting right-fitting ERP and enterprise technology solutions.

Whatโ€™s Inside This ERP Selection Guide?

Part 1: Plan Your ERP-Driven Transformation

Part 2: Define ERP Requirements and Build the Business Case

Part 3: Select and Evaluate ERP Vendors

Part 4: Prepare for ERP Implementation

Part 1: Plan Your ERP-Driven Transformation

ERP selection should be part of a holistic transformation plan linked to business strategy. A piecemeal approach can overlook integration requirements, organizational readiness, and the long-term capabilities needed to realize the expected benefits.

Building a Solid Foundation for ERP-Driven Transformation

ERP-driven transformation starts with defining the future-state business model, processes, and capabilities that the technology must support. The benefits โ€“ actual business value โ€“ of ERP-driven transformation come from both improving legacy processes and enabling more fundamental changes to how the business operates. With respect to incremental business improvement, benefits can be generated by replacing outdated processes with integrated and automated processes, clean data, and timely analytics. Though valuable, these enhancements are not transformative.

Transformation-related value is driven by system capabilities that allow companies to enter new lines of business or make drastic changes to existing operations. Hereโ€™s an example to illustrate the difference.

Case Study: How a Furniture Manufacturer Transformed Its Order Fulfillment Process

A multinational furniture manufacturer approached us with declining business fortunes. It was struggling to keep up with customer demands for highly customized products on short lead times. Our client took seven weeks to fill orders while its competitors took four.

Optimizing our clientโ€™s current business processes with modern technologies was not going to work. It had already tried that approach when it implemented a then new ERP system. For that project, the company cloned the data structures and engineer-to-order business processes from its predecessor ERP system. Although the company had a new system that improved upon the old, it still struggled to keep up with its competitors.

As the company increased the size of its product catalogue, its operations struggled to keep pace. The company was forced to hire expensive design engineers and software developers to maintain sales levels. The excessive and variable indirect cost base was unsustainable.

It was clear that the labor-intensive engineer-to-order model of yesteryear was no longer a competitive business model. We needed to make fundamental changes that would enable our client to deliver customized products at scale. Our value-stream analysis showed that order entry and design engineering processes consumed three weeks of the order fulfillment cycle time. Remember that the companyโ€™s competitors were fulfilling orders in four weeks!

We recommended that our client ditch its legacy engineer-to-order model in favor of a configure-to-order model.

We showed them how to select ERP software that would support this new model and architected a solution that tightly integrated its customer-facing three-dimensional space planning software with configure-price-quote and ERP software. In effect, we made 75% of orders touchless from the time the customer customized its product orders to the point that those orders are scheduled for production. Together with changes to warehousing and production processes, our client shaved three and one-half weeks off its cycle times, launching it into the top quartile.

This companyโ€™s contrasting approaches to ERP illustrate the importance of viewing an ERP project in the context of digital transformation. Had our client again rushed into an ERP selection project, it might have acquired software incapable of delivering the transformational benefits associated with a new configure-to-order business model. The challenge is that a sound ERP decision is multifaceted; future business model needs are but one important dimension of analysis. A good decision needs to account for short-term improvements, end-user adoption, cost, and ease of systems administration. These areas are typically represented by multiple stakeholder groups.

ERP Project Governance: Teams, Roles, and Responsibilities

Effective ERP governance helps establish clear decision-making responsibilities, maintain executive oversight, and keep the transformation aligned with business objectives. Different stakeholder groups collectively represent a companyโ€™s varied digital transformation needs. It follows that each group should be asked to play a role in decision-making and execution. The starting point, therefore, is to identify, engage, and educate the relevant stakeholders.

The following graphic shows the relationship among typical key stakeholder groups. Boards of directors, executive committees, and steering committees establish strategic direction and oversee delivery. The project management and solutions architecture groups control the project and overall design. Meanwhile, the core team implements the solution, and the end-user community adopts the new solutions. Each group is impacted differently and has different interests.

ERP project team

If the plan and architecture fail to account for long-term strategic requirements, the company could find itself handcuffed. If end-users struggle to adopt the system, the value of its data store and processing automation capabilities will become limited.

It becomes critical to engage relevant stakeholders throughout the digital transformation program. Initially, during upfront design and planning, input is needed to map long term strategic needs and front-line business processing needs. During a subsequent ERP selection project:

  1. Business leaders need to assess which of the vendors would make strong long-term business partners
  2. Implicated core team and end-users should participate in scripted product demonstrations and associated feedback sessions. After all, they will be the ones called upon to implement and use the solutions

Once the ERP is implemented:

  1. Core team members should take on most of the workload under the guidance of consultants
  2. Steering and executive committees should meet periodically to govern

The following table provides a more detailed breakdown of the various stakeholder groups and their roles.

Stakeholder Group

Interest

Roles and Responsibilities on Digital Transformation

Board of Directors and its Technology Committee

To ensure that management acts in the shareholdersโ€™ best interests.

Leadership function that provides an oversight role to assure that technology supports business strategy execution, including:

  • Tech strategy & trends
  • Operational performance

Executive Leadership

To develop and execute operational plans that drive corporate strategy.

Leadership function that creates and executes an overall digital transformation plan that drives corporate strategy and value creation:

  • Approves overall mission and scope
  • Aligns key stakeholders to the missions
  • Funds the program
  • Dedicates people
  • Champions the program

Steering Committee

To develop and provide project-specific strategic direction and policy guidance.

Leadership function that is a decision-making body responsible to define and monitor project-specific:

  • Approves project charter and scope
  • Aligns and assuring commitment of key stakeholders
  • Monitors project finances and schedules
  • Assures dedication of key people
  • Assures benefits realization

Project Management

To develop and execute project management plans that deliver defined business objectives on-time and on-budget.

An execution function that:

  • Secures and coordinates internal and external personnel
  • Manages schedules and budgets
  • Reports to the Steering Committee
  • Assures timely deliverable production

Solutions Architecture

To assure that the technology solution is architected to align to enterprise architecture and to maximize business benefits.

An execution function that:

  • Guides functionality design and mapping decisions
  • Guides technical architecture

Core Team

To design and implement specific functional and technical functions.

An execution function that:

  • Designs, maps, and tests softwaresโ€™ functional and technical processes
  • Migrates data
  • Documents designs, test scripts, and user instructions
  • Trains end-users

Internal End-Users

To use the system as implemented.

An adoption function responsible to transact using new processes, reports, and systems.

External End-Users

To use the system as implemented.

An adoption function responsible to transact using new processes, reports, and systems.

The Four Pillars of Future State Architecture

With governance structures and teams established, the next step is to analyze the current state and design the future-state architecture that will guide ERP selection and the broader transformation program.

As described earlier, analysis should start with reviewing business strategies, objectives, and key performance indicators (KPIs). Charting actual and targeted performance helps to focus the programโ€™s scope on business value-driving initiatives. The following example is a modified version of the one we used for the furniture company described above.

KPI: ORDER FULFILLMENT CYCLE TIME

current KPI: 7 weeks

target KPI: 3 weeks

ย SALES PROCESSENGINEERINGMANUFACTURING
AND DISTRIBUTION
Current state and actual performance5 days to enter new order due to manual pricing and promise data checks4 weeks to design & engineer customer orders30% of orders miss customer promise dates because of unanticipated manufacturing scheduling & quality issues
Future StateAutomate order entry for all configured items for space planning software to ERPChange 70% of product structures to parametric configuration modelsAdoption of standard production data and processes for configured products will improve scheduling and minimize quality issues associated with engineered product
Target KPIs

Touchless order entry for 85% of order lines (5-day lead time benefit)

$150,000 benefit per year per site

Eliminate engineering lead times for 85% of order lines

$370,000 benefit per year per site

95% fill rates
90% promise date satisfaction$150,000 benefit per year per site

Once business strategies and models are defined, analysis should move down to a detailed architectural design. The end goal of this next exercise is to map the current state, the targeted future state, and any intermediate resting points along the way. Four deeply interconnected components โ€” the four pillars of future state architecture โ€” should be considered: organizational structures, data, business processes, and technologies.

Pillar #1: Organizational structures

As companies transform, the corporate and organizational structures that worked well in the past will probably need to be changed for the future. Companies evolving their business models will need to create different โ€” in many cases entirely new โ€” functions and roles.

As one common example, vertically integrated multinationals that grow through acquisition face common challenges. Target companies are converted onto the acquirerโ€™s legacy systems or allowed to retain their own systems. Limited process integration across companies means companies have mirrored functions:

  • Buyer at Company1/Inside sales at Company 2
  • AR at Company-1 / AP at Company-2
  • Planner at Company-1 / Planner at Company-2
  • and so on

The double-handling of data and transactions results in expensive inefficiencies. When the companies fully merge, they will need to create new global service functions that cross companies and, in many cases, borders.

The needs are oftentimes more extreme when companies pursue entirely new lines of business relating to Industry 4.0 and service-based revenue models.

Apart from meeting the technical requirements of role-based ERP systems, companies need to define and fill applicable roles before implementation starts. Preferably, the roles should be filled early so that key personnel can help define future state requirements and evaluate candidate technology solutions.

Pillar #2: Business processes

During the planning stage of digital transformation, business process mapping is crucial to:

  1. Define and quantify the value of gaps and issues associated with the current-state processes.
  2. Identify non-negotiable needs that represent your companyโ€™s competitive differentiators.
  3. Define future-state changes and best practices.

It is important to map both current-state and future-state processes. With respect to analyzing future benefit opportunities, the current state provides a critical anchor point. The business analysis should include a study of the manual tasks, the amount of processing time (cycle and takt), as well as the actors and systems needed to execute the process. The following annotated process map highlights issues with a current-state process. It also includes a quantification of process inefficiency together with an impact analysis on strategic drivers, which, in this case, relates to customer experience.

We also use process mapping to define idiosyncratic needs, which represent a companyโ€™s โ€œsecret sauceโ€. These requirements need to be preserved at all costs. During ERP selection, they should be used as a gatekeeper to screen prospective vendors. If these needs are non-standard, vendors must prove that they can adapt their systems accordingly (in todayโ€™s day and age, without code modification).

The current-state maps should be supported by future-state maps. These conceptualize and quantify planned improvements through efficiency gains and other forms of waste reduction. When the project progresses to ERP vendor selection, it becomes important to assess how the proposed technology solutions satisfy these future-state requirements. And, when gaps appear โ€” and there will be gaps โ€” it will be important to identify and quantify the impact of those gaps, because they may erode future-state business value.

Pillar #3: Data

To support operational business processing and management reporting requirements, data needs to be properly structured, accurate, and timely. The need for accurate and timely data is clear. Data structure concepts are more complicated, particularly for multinational and multisite companies.

Consider one example of a multinational automotive OEM that manufactures powertrains at a Canadian division for final assembly at a United States division. Both divisions need to use common data relating to that powertrain. Engineering specifications, for example, are key to the finally assembled vehicle in the United States and to how that powertrain is manufactured in Canada. And, to meet the just-in-time delivery needs, planning and scheduling need to be tightly coordinated across a supply chain network that includes the US division, transportation from Canada to the US, manufacturing in Canada, and the Canadian component suppliers.

Consider another example โ€” this one common to multinationals that sell to customers that cross divisions. Many want to centrally control credit to manage corporate financial risk. To do so, they need to have customer data structures that span the corporate hierarchy. For example, they may need to allocate a corporate credit limit to a customer family, then apportion that limit across its own entities as well as the customersโ€™.

There are many more examples. The point is that system data structures can either enable or impede efficient business processing, particularly when that processing crosses facilities and legal entities. It therefore becomes critical to define where data files should be controlled in relation to the corporate hierarchy. In many cases, the answer will be certain data elements should be at the corporate level and others at another level. In the above example, customer credit should be controlled at the corporate level, while customer shipping preferences and planning parameters at shipment facility level.

Here is a simple 3-step guide to properly identifying data structure requirements:

  1. Define your future-state corporate structure and hierarchy
  2. Define your future-state business processes for each entity at each level of the hierarchy and how they cross entities, including data elements
  3. For each data record type in a business process (e.g., customer/vendor, item, bills-of-material, costing, pricing, etc.), define the specific data requirements at each level of the hierarchy

Pillar #4: Technology

Once organizational structures, business processes, and data structures are designed, the next task is to architect the technologies that will support and enable the future-state.

Too often, companies focus on business application functionality to the exclusion of key technical components. Unfortunately, time and again, companies select ERP and other systems that are too difficult to integrate, too complicated to personalize, too unpredictable from a performance perspective, and incapable of meeting security needs. Further, as companies increasingly shift mission-critical application workloads to the cloud, it becomes critical that the underlying architecture be robust, highly available, and secure.

At this architectural stage of the process, it is important to consider:

  1. Middleware strategies
  2. Application development and extensibility
  3. Application upgrade management
  4. Security needs
  5. System availability and service levels
  6. Elasticity and scalability
  7. Latency and performance
  8. Data management and residency
  9. Storage capacity
  10. Disaster recovery

Part 2: Define ERP Requirements and Build the Business Case

Before evaluating ERP solutions, organizations need to translate their future-state business goals into clear requirements, implementation priorities, and a defensible business case. This helps ensure that ERP selection decisions are grounded in business needs, realistic project plans, and expected financial returns.

Defining Business and Technology Requirements

The various organizational, data, business process, and technology requirements are going to have different priorities, be needed at different times, and have differing levels of impact on your business


It is important for companies to have an easy place to catalogue, track, and report on the requirements. Business requirements are useful for the following purposes:

  1. To catalogue needs by functional and technical areas
  2. To prioritize needs relative to business drivers
  3. To time the need for implementation
  4. To identify value-driving best-practices that imply a change from the legacy ways
  5. โ€œFoundationalโ€ needs to help the company either a) get ready for implementation, or b) realize short-term value with low-hanging fruit
  6. To catalogue idiosyncratic needs that are competitively differentiating

As shown in the sample below, if requirements are well catalogued, they can be analytically sliced and diced to show implementation work effort, change management needs, and implementation readiness work effort.

Developing an Integrated ERP Transformation Roadmap

With the architecture design and requirements definition complete, the task shifts to planning. The various interdependent projects should be charted on a program roadmap: foundational and readiness projects, ERP and technology selection projects, implementation projects, and continuous improvement projects. A consolidated GANTT view of the projects on a timeline provides a clear view of the initiatives.

At a minimum, each of the charted projects should be distilled down into the teams, budgets, schedules, and specific plans.

The following table summarizes typical project types in ERP-centric digital transformations.

Project CategoryDescription
Foundational

Program management office (PMO): Companies with a big set of interdependent projects establish a PMO to a) leverage a consistent set of project management tools and frameworks, and b) to monitor and control the project portfolio.

Organizational structure and people: Oftentimes, new functions need to be created and new roles to be filled. Also, key employees slated for implementation work may need to be backfilled.

Business process cleanup: Business process optimization and processing disciplines may be recommended to establish a foundation for the future state and to minimize the extent of change during implementation.

Data re-architecture and cleanup: Where practical, companies should define future-state data structures and should clean inaccurate master data.

Technology SelectionERP and technology selection plans should include a listing of the vendors, the due diligence methods, and the decision-making methods.
ImplementationThe implementation plans should detail the rollout strategy across sites and phases, as well as the implementation methodologies.

ERP Budgets, Total Cost of Ownership, and ROI

Digital transformation and ERP implementation projects have notoriously high failure rates and sky-high costs. This combination does not make a compelling investment proposition. A business case for change will not pass executive or board of director scrutiny if it is unrealistic or incomplete. It needs to be comprehensive, detailed, and conservative.

The costs should be modeled according to an industry-standard 10-year total cost of ownership analysis (TCO).

Though some might be inclined to undersell the costs to get approval, this type of short-sighted approach will only damage credibility and imperil the project.

At this stage, before the systems have been selected, the objective should be to provide a realistic and comprehensive analysis of low-end and high-end cost scenarios. The costs should cover all technology-related acquisition, support, and implementation costs. The cost model should also account for internal costs, which may include project team member salaries, backfilling costs, and project-related facility lease, team-building events, and other such costs.

The benefit models should be tightly tied to the implementation scope and timing. Also, projections should account for a several month post-implementation stabilization period where business performance typically dips. Once a reasonable stabilization period, benefit projections should be slowly phased-in to mirror gradual adoption rates and efficiency gains.

Part 3: Select and Evaluate ERP Vendors

Selecting the right ERP software requires a structured approach to shortlisting and evaluating vendors against future-state business requirements, technology priorities, and long-term objectives. Evidence-based evaluations help organizations compare potential solutions and develop defensible recommendations for decision-makers.

ERP Software and Vendor Shortlisting

Historically, companies would build their lists by blasting out an RFP to any vendor that would respond to a 3,000 line feature-function questionnaire. This approach fell out of favor towards the early 2010 years when many vendors made it a common practice to reply โ€œyesโ€ to everything in the hopes of getting shortlisted.

At Pemeco, our ERP selection consulting approach starts with a deep internal vetting process before vendors are invited to participate. We present our clients with a detailed analytical report on the vendor landscape and hold workshops to handpick the vendors who have the highest probability of fit.

We present an initial vendor list curated from our database of 140+ technology solutions. The filters are customized based on our clientโ€™s specific needs and each vendorโ€™s probability of satisfying those needs. We then chart that list of vendors on a client-specific Right-Fit Quadrant to highlight strengths and weaknesses relative to areas that are important to our client. The objective is to handpick a select group of vendors that have the highest probability of meeting our clientโ€™s collection of needs.

The sample Right Fit Quadrant below focuses on cost and functionality. We have other clients that prioritize other dimensions, such as technology architecture and supportability.

erp selection quadrant

Evaluating ERP Vendors Using the Eight Dimensions of Vendor Fit

The 8 Dimensions of Vendor Fit is Pemeco Consulting’s framework for evaluating ERP vendors and their solutions against an organization’s business and technology requirements. It covers eight areas: vendor profile, functionality, technology, user experience, software development roadmap, total cost of ownership, implementation, and supportability (i.e. the talent ecosystem).

There is no universally correct way to evaluate vendors. The right approach is context specific. A company with heavy multi-company processing needs will spend more effort evaluating data structures and intercompany business processing. Meanwhile, a company with heavy integration requirements will spend its effort evaluating APIs and technology architecture.

The evaluations should be deeply rooted in its future-state architecture and requirements. Vendors, for example, should be asked to demonstrate their software according to tightly defined use case scenarios with actual data samples.

Meanwhile, demonstrations are but one due diligence method. Organizations can combine different evaluation methods, including scripted demonstrations, reference checks, and technical assessments, into a structured ERP selection plan.

From a decision-making perspective, clients almost invariably use a combination of qualitative and quantitative evaluation methods to assess vendors and their technologies against the eight dimensions.

Building an ERP Selection Scorecard

Before starting an ERP selection project, the evaluation committee should develop a balanced scorecard with weighted decision-making criteria organized around the 8 Dimensions of Vendor Fit.

It is very important to map the weighted scoring criteria back to the requirements defined in the transformation planning exercise. This will help make the recommendations defensible to the stakeholder groups that will be asked to approve the recommendations, notably the steering committee, executive committee, and board of directors.

The evaluation committee will make recommendations to some of those groups at certain strategic stages, notably long-listing, short-listing, and vendor-of-choice selection. It is important for the recommendations and the underlying analysis to be well-supported, organized, and defensible.

In our firmโ€™s experience, the actual scores are important, but do not in and of themselves justify a decision. Rather, they represent a launch-point to drill into the business implications of the candidatesโ€™ relative strengths and weaknesses.

When preparing recommendations, it is important to start with an executive summary of the recommendations and analysis. The recommendations report should include fingertip access to the underlying details, including vendor-by-vendor analysis of technology architecture maps, solvency analysis, implementation methodology gap analysis, and so on.

Part 4: Prepare for ERP Implementation

Selecting an ERP vendor is an important milestone, but organizations must also prepare for implementation. Before making contractual commitments, they need to define the implementation scope, assess delivery risks, and establish clear expectations with their technology partners. These steps help create a stronger foundation for implementation and long-term business value.

ERP Implementation Scoping and Contract Negotiations

Once a company has selected one or more vendors-of-choice, it should strongly consider going through an implementation scoping exercise before negotiating contracts. A โ€˜scope first, negotiate laterโ€™ approach brings three important benefits:

  1. It allows the vendors to precisely scope the software needs for contractual pricing purposes
  2. It provides a mechanism to scope the implementation work effort, which flows into the service agreements
  3. It gives companies an opportunity to assess the service teamโ€™s fit and capabilities before making any contractual commitments

Assuming a successful scoping exercise, contract negotiations are the only remaining hurdle to be cleared before implementation kickoff. Depending on the size, risk profile, and complexity of the deal, companies should expect contract negotiations to take between one and three months. For mission-critical technologies such as ERP, it is important that contracts be structured in a way that enables predictable scalability and accelerated ROI while mitigating risks and lowering total cost of ownership.

The Five Keys to ERP Success

We believe that companies should apply a disciplined approach to defining their paths to realize value-driving transformations. The best practices set-out in this article on how to select ERP software are methodical and proven to work.ย 

To summarize, a company should:

  1. First build a governance model that supports effective decision-making and high-performance teams
  2. Develop a sound future-state architecture that spans organizational structures, data structures, business processes, and technologies
  3. Build detailed plans and cost-benefit models
  4. Execute foundational projects to get the company ready for a transformative ERP implementation
  5. Perform well-rounded due diligence to select the right ERP software and technology partners

With these best practices carefully planned out and executed, companies will find themselves not just adapting to more efficient and effective ERP systems, but carving a path to a holistic digital transformation that is the catalyst for success.

Download The Ultimate ERP Selection Guide: Templates, Checklists & Scorecards

Whether your company is in the early stages of planning its digital transformation or is evaluating ERP vendors, you need to make sure youโ€™re making the right decisions at each stage.

The Ultimate ERP Selection Guide: Templates, Checklists & Scorecards has powered hundreds of companies to select the right software at each stage. These tools and templates will power your project with best-practices so you can make the right decisions for your ERP project teams, requirements, budgets and evaluation of vendors, as well as equip you with ERP demonstration script templates, selection scorecard template, analysis of best-practices, and digital transformation and ERP selection checklist.

Download The Ultimate ERP Selection Guide: Templates, Checklists & Scorecards

 ERP selection checklist

Frequently Asked Questions

ERP selection usually takes 3โ€“6 months. Smaller companies may finish faster, while global or complex organizations often take longer due to requirements gathering, vendor demos, and due diligence.ย 

Ask vendors to demonstrate how their software handles real business scenarios, including critical workflows, exceptions, and integration requirements. Use-case scripted demonstrations help companies assess how well each solution supports future-state processes, identify limitations, and compare vendors against consistent evaluation criteria.

The decision depends on whether your existing ERP can support future business needs. Consider functionality gaps, vendor support, scalability, integration requirements, and the total cost of ownership of upgrading versus replacing. Replacement may offer greater long-term value when upgrading cannot address critical limitations.

Use Pemeco’s ERP Upgrade vs. Replace Checklist to compare project risk, cost, and business fit.

Consider engaging an independent consultant when your organization lacks the expertise or resources to manage ERP selection, faces competing stakeholder priorities, or needs objective vendor evaluations. Early involvement can help establish requirements, structure the selection process, and identify risks before committing to a solution.

Pemeco Consulting guides organizations through ERP selection, from defining requirements to evaluating vendors and negotiating contracts. Its independent, client-side approach combines future-state planning, the 8 Dimensions of Vendor Fit, and structured due diligence to help companies select solutions aligned with their business needs.

Explore Pemeco’s ERP selection consulting services.

Share this article:

Guides & Tools

Agricultural technology

Agtech providers of precision agriculture and robotic solutions providers are transforming agriculture and farming operations.  Pemeco helps its agricultural technology clients implement standard, scalable business processes to drive their high-growth businesses.