How Long Does ERP Selection Take for a Mid-Sized Business?

For most mid-sized businesses, defined as $10M to $1B in revenue, an ERP selection should take about 16 weeks.

That is usually enough time to understand the business requirements, involve the right stakeholders, evaluate qualified ERP vendors, run meaningful demonstrations, compare pricing and services, and make a confident executive decision.

An accelerated ERP software selection timeline may be possible, but it comes with tradeoffs. The goal should not be to rush executives, business process owners, or other ERP participants through decisions they need time to understand. Instead, a mid-sized business can shorten certain ERP selection phases by preparing early, limiting the vendor field, aligning decision makers, and keeping requirements, vendor demonstrations, pricing, and evaluation steps tightly managed.

At John Hannan LLC, we lead ERP software selection from a vendor-neutral, client-side position. The timeline and methodology outlined here are based on 25+ years of ERP selection, implementation, rescue, and advisory experience across mid-sized businesses and larger enterprise environments. Our role is to help companies make a practical, informed ERP decision based on how the business operates today, what it needs in their future state, and help them develop a plan through implementation and go-live.

Why ERP selection takes time

ERP selection takes time because it is not just a software decision. It is a business decision that affects finance, operations, supply chain, inventory, manufacturing, warehousing, purchasing, sales, reporting, compliance, customer service, and executive visibility. Mid-sized businesses often reach the ERP selection stage because they have outgrown disconnected systems, spreadsheets, legacy software, QuickBooks, or an ERP system that no longer supports the way the business operates.

By the time a company is ready to evaluate new ERP software, there are usually several business issues to resolve. Processes may vary by department or location. Reporting may depend on manual work. Inventory may not be trusted. Finance may need better controls. Operations may need stronger planning, scheduling, quality, or warehouse visibility. A good ERP selection process takes these realities into account before vendors are asked to present software.

A realistic ERP selection timeline for mid-sized businesses

John Hannan LLC recommends to mid-sized companies a 16-week ERP selection timeline. This does not mean every week is full time for every participant. It means the process needs enough calendar time for business process discovery and requirements gathering, vendor engagement, demos, evaluation, pricing review, and executive decision making. A realistic timeline also gives business process owners time to review information without creating unnecessary disruption to daily operations.

Weeks 1-2: Executive alignment and project planning

The ERP selection process begins with executive alignment. Before vendors are engaged, leadership needs to agree on why the company is selecting ERP software, what business outcomes matter most, what the major pain points are, and how the final decision will be made.

This is also where the selection team defines scope. A mid-sized business may need to decide whether it is selecting a full ERP replacement, evaluating whether to expand the current system, or reviewing ERP along with related systems such as CRM, EDI, warehouse management, quality management, transportation management, or manufacturing execution software. Clear scope protects the timeline. Without it, ERP selection can expand quickly and become difficult to manage.

Weeks 3-5: Business process discovery and requirements gathering

Business process discovery is one of the most important parts of ERP software selection and a foundation to the selection. This is where the company identifies what is working today, what is not working, what needs to change, and what future-state capabilities the ERP system must support.

For a mid-sized business, this usually means interviewing leaders and business process owners across finance, operations, supply chain, manufacturing, distribution, purchasing, sales, customer service, IT, and executive leadership. The goal is to understand the business to create clear ERP requirements that reflect current needs, future needs, gaps, risks, and cross-functional handoffs.

Strong requirements help vendors respond accurately. Weak requirements lead to vague responses, generic demos, and decisions based on sales presentations instead of business fit.

Weeks 6: ERP RFP and vendor long list

Once requirements are developed, the company can prepare the ERP RFP and vendor long list. For mid-sized businesses, the vendor list is focused. Too many vendors can slow the process and make comparison difficult. Too few vendors can limit the company’s understanding of available options. The right participant list depends on the company’s industry, size, complexity, budget, implementation needs, and future growth plans.

The RFP gives ERP vendors enough context to respond with meaningful information. This usually includes company background, business drivers, requirements, implementation expectations, integration needs, reporting needs, data considerations, timeline assumptions, and pricing structure. A strong RFP makes the selection more objective. It also helps the company compare vendors on the same basis.

Weeks 7-9: RFP responses and vendor evaluation

After the ERP RFP is issued, vendors need time to respond with enough detail for the company to evaluate fit, cost, implementation approach, and risk. For the RFP participants, this is also the point where they may ask the company follow-up questions, clarify assumptions, normalize pricing, and identify any gaps to deliver their proposal.

For the company, this stage focuses on a structured review of RFP responses comparing how each ERP vendor addresses the requirements, industry needs, integration expectations, reporting priorities, implementation assumptions, pricing structure, and known business risks. For a mid-sized business, the goal is not to bring every RFP respondent into demonstrations. The RFP response review helps narrow the field to the vendors that appear to be the strongest fit for the company’s needs, budget, industry, and implementation expectations.

Weeks 10-13: Vendor shortlist and ERP demonstrations

Once the RFP responses are reviewed, the company can confirm a shortlist of qualified ERP vendors for demonstrations. ERP demonstrations should be based on the company’s workflows, not a vendor’s standard software tour. This matters because the wrong demo structure can hide important gaps. Vendors may show what their software does well, but not how it handles the specific scenarios that matter to the business.

Our recommendation is to provide shortlisted vendors with demo scenarios tied to real business processes. This may include order to cash, procure to pay, plan to produce, inventory management, warehouse operations, quality, finance close, reporting, project accounting, service management, or regulatory workflows.

Internal participants should use scorecards to evaluate each vendor consistently. The scorecard reflect business fit, usability, process support, reporting, implementation confidence, risk, and the vendor’s ability to support the company through go-live and beyond.

At the end of this phase, the company should have a clearer view of which ERP vendors are viable, which gaps need to be addressed, and which option is best positioned for final pricing, services review, and executive recommendation.

Weeks 14-16: Final pricing, services review, and executive decision

By this point in the ERP selection process, most of the information needed to make a decision should be in place. The company has reviewed requirements, evaluated RFP responses, narrowed the vendor field, completed demonstrations, gathered participant feedback, and identified the strongest ERP options.

This phase brings that information together for the executive sponsor team where they confirm final pricing, implementation services, assumptions, risks, contract considerations, and total cost of ownership. This includes software licensing, implementation services, integrations, data migration, reporting, training, support, internal staffing, partner responsibilities, and future costs.

For a mid-sized business, this step is important because the preferred ERP software is only part of the decision. The implementation partner, project approach, staffing model, industry experience, and go-live support can have a significant impact on the outcome. The executive sponsor team uses this phase to compare the final options, resolve open questions, review business and implementation risks, and confirm which ERP vendor and partner are the best fit for the company. Its important for the company to consider business fit, implementation confidence, vendor and partner alignment, long-term scalability, total cost, and readiness for change.

A strong ERP selection process gives executives confidence that the company is not just buying software. It is choosing a business platform and an implementation path that can support the business through go-live and long-term growth.

What can make ERP selection take longer

ERP selection may take longer than 16 weeks when the company has multiple locations, multiple business units, international operations, complex manufacturing, regulated processes, private equity oversight, or significant disagreement about future-state needs.

The process may also extend when the company is not ready to make decisions, business process owners are not available, vendor responses are incomplete, pricing is difficult to compare, or leadership has not agreed on the selection criteria.

Some extra time can be valuable when it improves decision quality.

Why ERP selection should not be rushed

ERP software affects how a company runs. A rushed selection can create problems that do not show up until implementation. Common issues include missed requirements, underestimated implementation effort, unclear integrations, poor data planning, weak user adoption, incomplete pricing, and unrealistic timelines.

For a mid-sized business, these problems can be expensive. The company may not have unlimited internal resources to absorb rework, delays, or a poorly matched implementation partner. A disciplined ERP selection process helps reduce those risks before contracts are signed.

How to keep ERP selection moving without rushing it

A good ERP selection process is structured and not overbuilt. The process moves faster when there is a clear executive sponsor, defined scope, access to the right business process owners, a focused vendor shortlist, practical requirements, structured demonstrations, and a clear decision framework.

Delay may be experienced if any phase is rushed and not completely thoroughly. It may feel efficient at first, but it often creates confusion later. A good ERP selection comes from structure. When the process is organized, the company can make better decisions with less rework.

The best ERP selection timeline for a mid-sized business

For most mid-sized businesses, John Hannan LLC recommends a 16-week ERP selection timeline as a practical planning range. That timeline gives the company enough room to understand business needs, involve stakeholders, develop ERP requirements, engage vendors, run meaningful demos, compare costs, evaluate implementation partners, and make an executive decision.

ERP selection should not be rushed, but be led with discipline. John Hannan LLC helps mid-sized businesses lead ERP software selection from a vendor-neutral, client-side position. We help companies define requirements, manage vendor engagement, structure demonstrations, compare options, and make ERP decisions that support the business through implementation, go-live, and long-term growth. Contact John Hannan LLC for a Selection Consultation.