Why Mid-Sized Businesses Need More Than a Tier 2 ERP Shortlist

Medium-sized businesses face a difficult ERP decision. They may have outgrown entry-level accounting software, spreadsheets, and disconnected applications, but that does not necessarily mean they need the cost, complexity, or global scale associated with the largest enterprise platforms.

This is where the term Tier 2 ERP often enters the conversation. Tier 2 ERP solutions are generally positioned for mid-sized and larger organizations that need meaningful operational depth without the full footprint of a global enterprise platform. These systems may offer strong capabilities for manufacturing, distribution, life sciences, project-based businesses, service organizations, or other specialized operating models.

However, identifying a group of Tier 2 ERP systems is only the beginning. The category includes platforms with very different capabilities, architectures, partner ecosystems, implementation approaches, and industry strengths. Choose an ERP solution based on the best fits for your requirements, operating model, growth plans, and ability to implement and support the system successfully.

ERP Tiers Are Only a Starting Point

ERP tier classifications can provide an initial way to organize the market, but they should not determine the final shortlist. Two companies with similar revenue or employee counts can require very different ERP solutions. A manufacturer with complex engineer-to-order production, outside processing, quality holds, and project costing may need more operational depth than a significantly larger company with a simpler business model. The same is true for a virtual life sciences company coordinating contract manufacturers and third-party logistics providers, or a distributor managing complex pricing, rebates, warehouse operations, and electronic data interchange.

Company size matters, but operational complexity often matters more.

An ERP selection should consider factors such as transaction volume, number of entities and locations, inventory complexity, manufacturing methods, regulatory requirements, integrations, reporting expectations, and the number and types of users who will rely on the system. These characteristics provide a much stronger foundation for identifying appropriate ERP vendors than a tier label alone.

Why Marketplace Knowledge Matters During ERP Selection

The ERP marketplace is broader and more specialized than many companies realize. Organizations often begin with a small group of familiar software names based on internet searches, peer recommendations, or prior experience. Those systems may be worth considering, but familiarity does not always indicate fit.

Some ERP platforms have particular strength in discrete manufacturing, process manufacturing, project-based operations, distribution, life sciences, financial management, or multi-entity organizations. Others may depend heavily on add-on applications, implementation partner intellectual property, or customization to support the same requirements.

ERP marketplace knowledge helps a company understand these differences before investing significant time in vendor conversations. It also helps the selection team evaluate more than the software product. Important considerations include

• The industries and operating models the platform supports well

• The maturity of its manufacturing, supply chain, finance, quality, and reporting capabilities

• The availability and quality of implementation partners

• The role of add-on applications and integrations

• Typical implementation scope and investment

• Product direction and cloud strategy

• Customer references with comparable operations

• The internal resources required to own and support the system

Without this perspective, companies may overlook viable solutions or spend months evaluating systems that were never likely to fit.

Start With the Business Rather Than the Vendor List

A well-informed ERP software selection begins with your business requirements.

This means understanding how work is performed today, where current systems create gaps, and what the organization will need in the future. Requirements should account for standard processes as well as the exceptions and edge cases that create operational risk.

For a manufacturer, this may include bills of material, routings, production scheduling, material availability, labor reporting, quality inspections, rework, outside processing, and job costing.

For a distributor, the requirements may focus on warehouse operations, inventory availability, customer-specific pricing, rebates, drop shipments, transportation, returns, and supplier performance.

For a life sciences company, considerations may include lot traceability, quality controls, validation, outsourced manufacturing, third-party logistics, financial controls, and integration with specialized regulatory or quality systems.

Documenting these needs creates the selection criteria used to evaluate the market. It allows you to identify vendors based on evidence rather than reputation, relationships, or marketing claims.

Build an Informed ERP Long List

A broad ERP long list should not include every product that could technically support your organization. It should include vendors with a reasonable chance of meeting your industry, functional, technical, geographic, and investment requirements.

This is where current ERP marketplace knowledge becomes especially valuable. An informed advisor can distinguish between systems that appear similar on the surface but serve different types of customers. They can also identify when a platform’s capabilities are native, delivered through an implementation partner, dependent on an add-on application, or likely to require customization.

John Hannan LLC maintains knowledge across more than 40 ERP vendors and their broader ecosystems. This allows our team to consider a wider range of potential solutions while narrowing the field based on practical fit.

Use the RFP to Establish Fit and Accountability

Once the long list has been established, John Hannan LLC asks vendors to respond to a structured request for proposal based on your requirements so you can compare functionality consistently. A well-developed RFP for a new ERP solution should require vendors to explain how each requirement will be delivered. The response should distinguish among functionality that is available within the standard product, requires configuration, depends on an add-on application, needs customization, or is not supported.

We also ask vendors to provide information about integrations, data migration, implementation methodology, proposed staffing, client responsibilities, training, support, pricing, and key assumptions. This level of detail gives the selection team a more realistic view of each proposed solution and helps identify hidden scope before the demonstration or contract stage.

Vendor's RFP response also creates accountability. Claims made during sales discussions can be compared with written responses, demonstrations, pricing, and the proposed statement of work.

Make Vendors Demonstrate the Real Business Need

ERP demonstrations can be polished and persuasive, particularly when vendors control the agenda and focus on ideal scenarios. A meaningful demonstration should instead be built around your actual processes, data, decisions, and exceptions.

Vendors should be asked to show how the system will handle the transactions that matter most to the business. This may include an order that changes after production begins, material that fails inspection, a customer-specific pricing exception, an inventory shortage, an outsourced manufacturing transaction, or a multi-step financial approval.

The selection team should score each demonstration against predefined criteria. This helps prevent a strong presenter, attractive interface, or isolated feature from outweighing broader business fit. Marketplace knowledge also helps during demonstrations by identifying areas that require additional pressure-testing. An experienced ERP advisor may know where a platform is likely to rely on workarounds, partner extensions, or future development and can ask vendors to prove those areas clearly.

Evaluate the Implementation Partner Alongside the Software

Selecting an ERP system also means selecting the organization and people responsible for implementing it. Many ERP vendors rely on partner ecosystems, and those partners can differ substantially in their industry experience, methodology, staffing model, solution knowledge, communication practices, and willingness to challenge weak assumptions.

A suitable ERP platform can still result in a difficult implementation when the partner lacks the right experience or underestimates the work required. Companies should evaluate whether the proposed team understands their industry, has completed comparable projects, and can explain how it will address data, integrations, testing, training, change management, and go-live readiness.

The software and implementation partner needs to be evaluated as a combined solution rather than as separate decisions.

Compare the Total ERP Investment

Software subscription costs represent only one part of the ERP investment. A complete comparison should also account for implementation services, data migration, integrations, add-on applications, internal resources, training, testing, infrastructure, support, and expected future phases.

Two vendors may present similar initial pricing while proposing very different scopes. One may include capabilities that another expects to deliver through an additional product or future phase. One partner may provide a more complete implementation estimate while another leaves important work as a client responsibility.

Normalizing these assumptions allows decision-makers to compare the options more accurately and understand the likely total cost of ownership. This comparison also helps you determine whether a proposed solution is right-sized for both its operational needs and its ability to absorb the implementation.

Selecting the Right ERP for a Mid-Sized Business

Tier 2 ERP solutions can offer mid-sized companies an effective balance of operational capability, scalability, flexibility, and investment. However, the Tier 2 label does not identify which system will work best for a particular organization.

That decision requires a structured ERP software selection process supported by clear requirements, current marketplace knowledge, objective vendor comparisons, realistic demonstrations, and a thorough evaluation of implementation partners and total cost.

John Hannan LLC serves as a vendor-neutral ERP software selection advisor for manufacturing, distribution, and life sciences companies. We help organizations understand the ERP marketplace, identify appropriate vendors, document requirements, manage the RFP and demonstration process, compare costs and risks, and select a solution that supports both current operations and future growth. Contact us and learn how we can help with your ERP selection.