The ERP market has dozens of credible vendors. When you first start researching, you can easily end up with a list of fifteen or twenty names — each one claiming to be the best fit for your industry. Working through that many demos, proposals, and discovery calls would take months and exhaust your team before you ever signed a contract.

Building a focused shortlist is not about being hasty. It is about applying the right filters early so the vendors you spend real time with are genuinely worth your attention. This guide walks you through how to get from a sprawling long list down to three to five vendors who actually deserve a live demo.

Why the Long List Problem Is So Common

ERP selection starts with internet research, analyst lists, peer recommendations, and vendor outreach that finds you before you find them. Within a few weeks, your inbox fills up, and your evaluation spreadsheet grows to a size that feels unmanageable.

The core issue is that most ERP vendors are capable of handling a wide range of businesses. Their marketing is broad by design. Until you apply specific filters, the field does not narrow on its own.

Your job in the shortlisting phase is to act as the filter — replacing vendor marketing with structured criteria that reflect your actual situation.

Step One: Define Your Non-Negotiable Criteria

Before you look at a single vendor in depth, write down the criteria that are absolute requirements. These are the conditions where if a vendor does not meet them, there is no point continuing.

Common non-negotiable criteria include:

• Deployment model. If your IT policy requires a cloud-hosted system, on-premise-only vendors are off the list regardless of their other features.
• Industry fit. If you are a food manufacturer with traceability and lot tracking requirements, a vendor with no food and beverage experience is a poor match no matter how good their general financials module is.
• Company size range. Some ERP products are built for teams of five to fifty. Others are engineered for organizations running hundreds of users across multiple entities. Trying to put enterprise software into a small business creates implementation debt and wasted licensing cost.
• Integration requirements. If your business depends on a specific piece of equipment, a proprietary e-commerce platform, or a third-party logistics system, check early whether the ERP has a proven integration path.
• Budget ceiling. You do not need precise numbers yet, but if a vendor’s base licensing starts above your total budget, they should come off the list.

Apply these criteria to your long list immediately. You will often eliminate a third to a half of the names without any vendor conversations.

Step Two: Use a Weighted Scoring Framework

For the vendors that survive your non-negotiable filter, move to a weighted evaluation. Assign weights to categories that matter to your business, then score each vendor against those categories based on public information and initial outreach.

Evaluation Category	Example Weight
Industry fit and reference customers	25%
Total cost of ownership (license + services)	20%
Deployment model and infrastructure	15%
Core module coverage for your operations	20%
Vendor stability and support model	10%
Implementation partner ecosystem	10%

The weights in this table are illustrative. Your team should debate and set the weights that match your priorities. A manufacturing company might weight industry fit higher. A company replacing a system for the second time in five years might weight vendor stability more heavily.

Score each vendor from one to five in each category and multiply by the weight. This gives you a ranked list that surfaces vendors worth a deeper look.

Step Three: Research Without Relying on Demos

One of the biggest time traps in ERP evaluation is requesting demos too early. Demos are time-intensive for your team, and they are controlled environments designed to show strengths, not weaknesses. Before you request a single demo, do your homework from sources the vendor does not control.

Analyst Reports

Analyst firms that cover the ERP market publish reports that evaluate vendors across categories like functionality, customer satisfaction, and implementation experience. These reports are useful for understanding where a vendor sits in the broader market. The limitation is that analyst coverage tends to focus on larger vendors and mid-market platforms. Smaller or niche vendors may not appear even when they would be a strong fit for your specific situation.

Peer Review Platforms

User review platforms aggregate feedback from actual customers. The quality of information varies — reviews are self-selected and often written by customers who had an unusually positive or negative experience. That said, patterns in reviews are informative. If you see repeated mentions of the same implementation challenge or the same support failure across dozens of reviews, that pattern is worth weighing.

Look specifically for reviews from companies that share your industry, your size, and your operational model. A review from a five-person accounting firm is not meaningful signal for a manufacturing company running forty-person shifts.

Customer Reference Calls

The most valuable information before demos comes from talking to reference customers. Ask vendors early in the process whether they can provide references from companies similar to yours — same industry, similar revenue, similar operational complexity. A vendor who cannot produce relevant references is showing you something important.

When you speak to references, ask about the implementation timeline, the actual versus estimated cost, the quality of ongoing support, and what they would do differently if they started again.

Step Four: Run a Structured RFI

A Request for Information (RFI) is a written questionnaire you send to vendors asking specific questions about their product, their implementation approach, and their company. An RFI is faster than a demo and puts vendors on record with answers you can compare.

A useful ERP RFI covers:

• Company background and financial stability
• Number of live customers in your industry segment
• Module coverage and whether specific features are native or require third-party add-ons
• Implementation methodology and average timeline for companies at your scale
• Pricing structure and what is included in the base license versus what triggers additional cost
• Upgrade model and how major version upgrades are handled

Vendors who respond to an RFI with vague or incomplete answers are telling you something about how they will communicate throughout an implementation. A vendor who responds thoroughly and provides supporting documentation is easier to work with.

When to Cut a Vendor from Your List

As you gather information, you will encounter reasons to remove vendors. Here are common signals that a vendor should leave your list:

Inflexibility on reference calls. If a vendor cannot provide a reference from your industry or deflects the request entirely, that is a red flag. Either they lack relevant customers or those customers are not willing to recommend them.

Pricing opacity. Vendors who refuse to provide even ballpark figures in early conversations are typically either not a good budget fit or are using information asymmetry to maximize their negotiating position. Neither is a good start.

Poor RFI response quality. A vague, template-heavy RFI response that does not engage with your specific questions is a preview of how this vendor handles communication when the relationship gets difficult.

No implementation partner in your region. Many ERP systems are delivered through implementation partners rather than directly by the software vendor. If no qualified partner operates in your geography or your industry, the vendor’s software may technically be capable, but the delivery path is broken.

Misalignment on company size. If a vendor’s case studies cluster around companies five times your size or a fraction of your size, the fit is likely poor regardless of what their sales team claims.

Building the Final Shortlist

After applying your non-negotiable filters, running weighted scoring, conducting independent research, and reviewing RFI responses, your list should be manageable. The goal is to reach three to five vendors who have:

• Met all non-negotiable criteria
• Scored well on your weighted framework
• Provided credible reference customers in your segment
• Given transparent, substantive responses to your RFI

This is the group you invite to a structured demo process. Each demo should follow a script of scenarios you define based on your actual workflows — not a general product tour.

Frequently Asked Questions

How many vendors should be on a final shortlist before demos? Three to five vendors is the standard range. Fewer than three risks missing a strong option you did not fully evaluate. More than five creates demo fatigue and slows decision-making without proportional benefit.

Is it worth considering a vendor outside my industry if their features are strong? General functionality can be excellent, but industry-specific configuration, pre-built integrations, and reference customers matter significantly during and after implementation. A vendor with a strong general platform but no track record in your industry puts implementation risk on your team.

How long does the shortlisting phase typically take? For most mid-market companies, the shortlisting phase from initial research to a confirmed demo list takes four to eight weeks when conducted rigorously. Rushing it tends to bring weaker vendors into the demo phase, wasting more time overall.

Should we involve a consultant to help with shortlisting? An ERP selection consultant can accelerate shortlisting significantly, particularly if your team has limited time or limited prior ERP experience. The key is to choose a consultant who does not earn referral fees from vendors, which creates a conflict of interest that undermines the independence of their advice.