top of page

Understanding ERP Selection Roles: Perspective, Expertise, and Where Bias Can Influence Decisions

  • Writer: John Hannan
    John Hannan
  • Nov 22, 2025
  • 4 min read

Updated: May 21


Selecting enterprise resource planning (ERP) software is one of the most important operational decision a growing business will make. ERP has become foundational to modern organizations, with ZipDo’s 2026 ERP industry statistics reporting that 94% of organizations use ERP systems and average productivity gains reach 20%. 


Yet implementation outcomes tell a more complicated story. Historically, only 23% of ERP implementations have finished on time and on budget, even though long-term adoption remains strong.


That contrast matters. ERP can deliver meaningful business value, but the path to getting there is often more complex than leadership expects. One reason is that ERP decisions involve multiple participants with different expertise, responsibilities, and perspectives. Vendors, implementation partners, consultants, and independent advisors can all play important roles. The challenge for leadership is understanding what each participant brings to the table, where perspectives may naturally differ, and how to structure the decision so the business remains at the center.


What Leadership is Really Asking 


They are asking practical questions that matter to their business and the outcome of the selection:


Who helps us define what we actually need?


Who understands the software market?


Who can validate whether a solution realistically supports our business?


Who is focused on implementation delivery?


Who is representing our business interests throughout the decision?


The strongest ERP selections typically involve multiple participants. Success comes from understanding how each role contributes and where perspective can influence recommendations.


The ERP selection ecosystem


Internal leadership team

Your executive team and business process owners (BPOs) remain central to the decision.


They understand:

  • Business priorities

  • Operational pain points

  • Growth strategy

  • Organizational constraints

  • Budget realities

  • Adoption risk


No outside partner can fully replace internal ownership of the decision, but many leadership teams have never selected ERP before, which creates a natural experience gap.


ERP advisor

Primary perspective: your business

An ERP advisor helps leadership structure and govern the selection process from the client side. Their focus is helping the organization make a disciplined, defensible decision aligned to business goals, operational realities, and long-term success.


Typical responsibilities may include:

  • Aligning stakeholders around business objectives

  • Organizing requirements and evaluation criteria

  • Structuring vendor comparisons

  • Maintaining decision discipline

  • Surfacing assumptions and risk

  • Helping leadership compare fit, cost, complexity, and readiness


Because this role is independent from software sales or implementation delivery, its value comes from objectivity and alignment to the client’s interests.


ERP consultant

Primary perspective: objective expertise aligned to business requirements

ERP consultants bring deeper operational, functional, or technical expertise to help evaluate whether business requirements can realistically be supported.


They may help:

  • Define business and technical requirements

  • Validate operational workflows

  • Assess functional fit

  • Pressure test proposed solution approaches

  • Identify technical or process complexity early


Unlike implementation partners focused on delivering a specific solution, independent ERP consultants can help leadership evaluate options through an objective lens. This role is especially valuable when internal teams need experienced guidance translating business needs into practical evaluation criteria.


Software vendor

Primary perspective: their product

Software vendors provide direct knowledge of their ERP platform.


They help organizations understand:

  • Core capabilities

  • Licensing models

  • Product roadmap

  • Deployment options

  • Ecosystem tools and extensions


This is an essential perspective because accurate product understanding matters. At the same time, vendors are naturally focused on positioning their own solution as the right fit.

That is expected. Leadership simply needs to recognize the perspective.


System integrator or implementation partner

Primary perspective: delivering the software successfully

System integrators help organizations implement ERP software by configuring the solution, designing workflows, managing technical execution, and supporting deployment.


Their expertise is critical in helping leadership understand:

  • Implementation effort

  • Timeline realism

  • Technical complexity

  • Integration requirements

  • Data migration challenges

  • Delivery methodology


Many implementation partners also maintain deeper expertise in selected ERP platforms or preferred software ecosystems. That experience creates implementation value, but it can also influence how solutions are positioned during selection. This is why implementation insight is valuable, while independent business-side guidance remains equally important.


How these roles work together


ERP selection is not about choosing one participant and excluding the others. The strongest decisions typically involve multiple perspectives.


A practical model often looks like this:

  • Leadership team defines business priorities, makes decisions, and owns outcomes.

  • ERP advisor provides decision structure, governance, and independent business alignment.

  • ERP consultant brings objective operational, functional, and technical expertise.

  • Software vendor provides direct product knowledge.

  • Implementation partner brings execution realism and delivery planning.


Each perspective matters. The key is understanding what each role is designed to do and ensuring leadership maintains balanced decision support.


Where confusion happens


Confusion usually happens when leadership assumes one participant can naturally fill every role. For example, a vendor may provide strong product guidance but will naturally emphasize their own platform. An SI may offer implementation insight but may frame recommendations around solutions they commonly deliver. A consultant may understand operations deeply but may not bring structured software evaluation discipline. An internal team may know the business well but still lack ERP market experience. None of these are flaws. They are simply differences in perspective.


When independent ERP guidance becomes more valuable

John Hannan kicking off an ERP software selection

Some organizations can manage ERP selection largely with internal leadership and vendor participation. Others benefit significantly from independent guidance. That tends to become more important when:

  • Multiple business functions are involved

  • Manufacturing or distribution complexity exists

  • Regulatory requirements matter

  • Integrations are significant

  • Data quality concerns exist

  • Internal bandwidth is constrained

  • Leadership has limited ERP selection experience

  • Competing vendors tell very different stories

  • Implementation risk is high


The more complex the environment, the more decision discipline matters.


A practical ERP selection journey


For most organizations, ERP software selection follows a progression like this:

  1. Define business objectives and future-state priorities

  2. Gather business and operational requirements

  3. Identify potential software candidates

  4. Review vendor responses and commercial assumptions

  5. Conduct structured product demonstrations

  6. Validate operational fit and implementation realism

  7. Compare total cost, risk, complexity, and readiness

  8. Select the software and implementation path


Different participants contribute at different stages. The key is ensuring someone is helping leadership connect the dots.


ERP selection is not simply a software buying exercise. It is a business transformation decision with operational, financial, and organizational consequences. Vendors, consultants, advisors, and system integrators all bring important perspectives. The goal is not choosing one role over the others. The goal is understanding how each contributes and ensuring leadership has the right structure to make a confident decision.


Over the last five years, mid-market companies have trusted John Hannan LLC to help them select a new ERP software. If you are looking to make a ERP software selection, contact John Hannan LLC for selection guidance.






CONTACT US

By submitting this form, you agree to our Privacy Policy.

Thanks for your submission.

(856) 952-2632

Lake Ariel, PA  |  Philadelphia, PA

  • twitter
  • linkedin

©2026 by John Hannan LLC

bottom of page