How Many ERP Vendors Should You Consider During an ERP Software Selection?

Selecting ERP software requires a credible view of the market, but that does not mean every possible vendor should participate in the formal evaluation. Including too few vendors can limit perspective and create concern that stronger options were overlooked. Including too many can overwhelm the organization, dilute stakeholder attention, and make it difficult to evaluate each option consistently.

It is not recommended to assemble the largest possible list of ERP vendors. The goal is to identify a qualified group that can realistically support the company’s industry, operating model, complexity, growth plans, technical environment, and implementation expectations.

Why Companies Consider Too Many ERP Vendors

ERP is a significant investment, so it is understandable that executives do not want to overlook a strong option. That concern can lead companies to invite every recognizable vendor into the selection process. More vendors, however, do not automatically produce a better decision. Every additional vendor increases the number of introductory calls, confidentiality agreements, discovery sessions, questions, RFP responses, demonstrations, pricing packages, follow-ups, and internal evaluations the company must manage. Business process owners may be asked to attend repetitive meetings while also completing their regular responsibilities.

A large vendor field can also reduce the quality of the evaluation. Stakeholders become tired, scoring becomes inconsistent, and important differences begin to blur together. Vendors may receive less time to understand the business, while the internal team may spend more time administering the process than evaluating meaningful fit.

The selection should create enough competition and comparison to support a well-informed decision without exhausting the people whose participation is essential.

Start With a Broad Market View

Companies should begin with a broader view of the ERP market than the final list of vendors invited to the RFP. This early research helps the organization understand which platforms commonly support its industry, company size, operating model, geographic footprint, and expected level of complexity. It may also reveal vendors that are less recognizable but better aligned with the business. At this stage, the company is not conducting a full evaluation of every platform. It is identifying plausible candidates and establishing qualification criteria.

Those criteria may include:

• Industry and operational fit

• Company size and transaction complexity

• Manufacturing, distribution, service, or project requirements

• Multi-site, multi-entity, or global capabilities

• Regulatory and quality requirements

• Cloud, hosting, security, and technical expectations

• Integration and data requirements

• Availability of qualified implementation partners

• Expected implementation cost and ongoing ownership cost

• Vendor stability and product direction

Build a Qualified RFP Long-List Group

The vendors invited into the formal RFP should have already passed an initial qualification process. For many mid-market ERP software selections, inviting three to five qualified vendors to respond to the RFP provides a reasonable range of options. The appropriate number will depend on the industry, the availability of suitable platforms, the company’s complexity, and the amount of time the internal team can dedicate to the process.

Vendor evaluation should consider more than functional capability alone. The company should assess overall business fit, technical alignment, implementation approach, partner experience, cost, support model, and the risks associated with each option. Evaluating these factors together provides a more complete view of which vendors are best positioned to support both current operations and future needs.

Managing Extensive Vendor Communications

Vendor communication becomes one of the most demanding parts of an ERP software selection. Each vendor will have questions about requirements, scope, data, integrations, users, locations, timing, implementation expectations, and commercial terms. Vendors may also request separate meetings with executives, business process owners, IT leaders, or other stakeholders.

Without a defined communication process, the selection can quickly become inconsistent.

One vendor may receive additional operational detail that others do not. Another may gain early access to an executive sponsor and adjust its proposal around information that was never shared with the full group. Vendors may price different scopes, make different assumptions, or interpret the same requirement in conflicting ways.

The most persistent vendor should not gain an advantage simply because it requests more meetings or sends more follow-up messages. A well-managed selection establishes clear communication expectations from the beginning. Its recommended to have one primary contact for vendor communications with a defined channel so answers can be shared consistently when they affect the broader evaluation.

Control Vendor Access to Stakeholders

ERP vendors naturally want access to the people who influence the decision. That access can be valuable, but it should occur at the appropriate point in the process and with a clear purpose. Business process owners should not be expected to attend repeated vendor discovery sessions before the vendors have been qualified. Executive sponsors should not be pulled into sales conversations that could have been handled through the established selection team.

Early access should focus on understanding the business rather than allowing vendors to begin positioning solutions before requirements are complete. As the selection progresses, targeted access becomes more appropriate. Vendors advancing to demonstrations may need clarification on high-priority scenarios. Finalists may need discussions related to implementation approach, governance, technical architecture, risk, and executive alignment.

Separate the Software Vendor From the Implementation Partner

Many ERP evaluations involve both a software company and one or more implementation partners. Their roles should be clear throughout the selection. The software vendor is responsible for representing the product, licensing model, roadmap, and platform capabilities. The implementation partner is responsible for explaining how the system will be designed, configured, integrated, migrated, tested, deployed, and supported.

The software may support a requirement, but the implementation partner may not have relevant experience delivering it. The partner may propose a solution that depends on an integration or add-on that the software vendor has not validated. Each party may assume the other is responsible for an important part of the scope.

Vendor communications should require both parties to document their responsibilities, assumptions, dependencies, and exclusions. This becomes increasingly important as pricing and contracts are developed.

Narrow the Field Before Demonstrations

Not every vendor that receives the RFP should automatically advance to a demonstration.

The RFP response should be evaluated first. Vendors with significant functional gaps, unclear implementation approaches, misaligned pricing, or limited industry experience may not justify the time required for a full demonstration.

For many companies, advancing two or three vendors to the demonstration phase provides enough comparison while keeping the process manageable. This smaller group allows stakeholders to spend more time evaluating meaningful differences. It also enables the company to use detailed scenarios, ask deeper questions, and document follow-up items without requiring the organization to sit through an excessive number of sessions.

Give Every Vendor the Same Opportunity to Compete

A fair process does not require every interaction to be identical. It requires vendors to compete against the same business needs, decision criteria, and expectations. Each vendor should receive the same core requirements, demonstration scenarios, timeline, pricing instructions, and material scope updates. Scoring criteria should be established before demonstrations and applied consistently.

The goal is not to make the vendors look the same. It is to create enough structure that their differences can be evaluated accurately. Consistent information also improves proposal quality. When vendors understand the business context, operating complexity, expected outcomes, and evaluation process, they can provide more meaningful responses and fewer generic sales claims.

Choosing the Right Number of ERP Vendors

There is no universal number of ERP vendors that every company should consider. The right number depends on how many platforms credibly fit the company, how complex the evaluation is, and how much participation the organization can realistically support. A structed ERP selection approach protects stakeholder time while maintaining competition and market coverage. It also gives the company a clearer basis for explaining why vendors were included, why others were eliminated, and why the recommended solution represents the best overall fit.

John Hannan LLC serves as a vendor-neutral ERP advisor, helping companies identify qualified vendors, manage RFP communications, coordinate demonstrations, evaluate responses, normalize pricing, and develop a recommendation executives can support. John Hannan LLC's ERP selection methodology is based on more than 25 years of experience supporting companies through ERP decisions and implementations. We keep vendors accountable to the process while helping the client team focus on the operational, technical, financial, and delivery factors that matter most. If you are evaluating ERP software and need help identifying which ERP vendor belong in your selection, contact John Hannan LLC for our expert guidance.

Frequently Asked Questions about ERP Selections

How many ERP vendors should be included in an ERP software selection?

Many mid-market companies invite three to five qualified vendors to participate in the RFP and advance two or three to demonstrations. The appropriate number depends on the company’s complexity, industry, available ERP options, and the time stakeholders can dedicate to the evaluation.

How should a company evaluate ERP vendors?

ERP vendors should be evaluated across functional fit, business alignment, technical requirements, implementation approach, partner experience, cost, support, and overall risk. Considering these factors together provides a more complete view than evaluating software features alone.

Why is ERP vendor communication important during selection?

Consistent vendor communication helps ensure that participants receive the same requirements, scope updates, deadlines, and evaluation expectations. It also reduces the risk of vendors pricing different assumptions or gaining an advantage through informal access to stakeholders.

Should every ERP vendor that responds to an RFP receive a demonstration?

No. Companies should evaluate RFP responses first and invite only the strongest candidates to demonstrate. Limiting demonstrations to qualified vendors protects stakeholder time and allows for a deeper comparison of the most viable options.

What is the role of an independent ERP selection consultant?

An independent ERP selection consultant helps companies assess the market, qualify vendors, manage communications, coordinate the RFP and demonstration process, compare costs, and develop a vendor-neutral recommendation.