Top 7 ERP Software Selection Mistakes (And How to Avoid Them

ERP

By Eric Kimberling, CEO of Third Stage Consulting


When it comes to ERP software, companies often think the biggest risk is choosing the wrong system. But in reality? The bigger danger is picking the right software — and then failing in how you select, implement, and integrate it.

After working with hundreds of organizations across industries, I’ve seen the same ERP selection mistakes repeat themselves time and time again. Whether you’re a mid-market manufacturer or a billion-dollar distributor, these patterns hold true.

In this blog, I’ll break down the seven most common ERP selection mistakes — and how you can avoid them by taking a more thoughtful, strategic, and independent approach to your transformation.


Mistake #1: Failing to Plan for Implementation Early

One of the most dangerous assumptions companies make is thinking ERP selection ends once you sign a contract.

Wrong.

ERP isn’t just a software purchase — it’s a business transformation. And that means your planning shouldn’t stop at which vendor you choose. In fact, the real work starts before the contract is signed.

What many organizations miss is this: the implementation approach should influence which system you select in the first place. For example, if you need a phased rollout due to resource constraints, some systems (and implementers) are better suited for that than others.

I always advise clients to develop a detailed implementation plan during the selection phase — one that includes:

  • Change management strategy
  • Data migration plan
  • Resourcing requirements (internal and external)
  • Integration architecture
  • Timeline and phasing approach
  • Training and user enablement

Don’t just ask what the software can do. Ask how you’re going to implement it successfully.


Mistake #2: Vague Requirements and Unstructured Demos

Let me be blunt here: vague requirements produce vague demos.

Too often, companies send out RFPs with high-level checklists, hoping to learn what a system could do. But without clearly defined business needs, those demos become generic sales presentations — not decision-making tools.

Instead, you need to take the time to define your business processes, pain points, and desired future state. Then structure vendor demos around those real-life scenarios.

We always coach clients to give vendors scripted demo scenarios:

  • “Show us how your system handles a multi-step BOM change for make-to-order.”
  • “Demonstrate how you would manage landed cost tracking across multiple warehouses.”
  • “Walk through a return-to-vendor workflow with inventory reconciliation.”

By making vendors show their system in your world, you’ll cut through the sales fluff and see what really fits.


Mistake #3: Evaluation Fatigue from Too Many Vendors

I’ve seen companies evaluate 10+ ERP vendors at once — and by the end, nobody remembers who did what. Everything starts to blur. Your team is burned out, disengaged, and just wants the process to be over.

That’s not how smart decisions are made.

Keep your shortlist short. I recommend evaluating 3–4 solid contenders based on your size, industry, and goals. Run initial mini-demos with a core evaluation team. Once you’ve narrowed it to 1–2 finalists, bring in broader stakeholders to vet specific concerns.

This helps avoid burnout and ensures you’re evaluating each system with fresh eyes and a focused mind.

Pro tip: Don’t over-democratize too early. Keep your process tight and strategic until you’re confident you’ve got real contenders.


Mistake #4: Ignoring the Implementation Team

You’re not just buying software — you’re buying a team of people to help you implement it.

And here’s what most companies miss: the quality of that implementation team is just as important — if not more important — than the software itself.

I’ve seen companies choose the right ERP and still fail because the implementer:

  • Didn’t understand their industry
  • Wasn’t available when needed
  • Had high turnover
  • Lacked experience in similar transformations

During selection, you should be evaluating the people behind the pitch — not just the tech. Ask:

  • Who will be on our project? Can we interview them?
  • Have they worked in our industry before?
  • What is their methodology and change management approach?

Choosing a great ERP system but partnering with the wrong implementation team is like buying a Ferrari and letting someone else drive it off a cliff.


Mistake #5: Underestimating Total Cost and Timeline

Every vendor pitch is optimistic. Timelines are tight. Budgets are “all inclusive.” But in reality? ERP projects almost always take longer and cost more than expected — not because of bad intentions, but because of hidden complexities.

Don’t just ask what the licensing fees are. Build a full Total Cost of Ownership (TCO) that includes:

  • Internal resource time
  • Data cleansing and migration
  • Integration development
  • Change management and training
  • Post-go-live support
  • Contingency buffer (trust me, you’ll need it)

When clients tell me their ERP project ran over budget, it’s almost always because they forgot to account for internal costs or third-party add-ons.

Rule of thumb: Whatever the vendor quotes, add 30–50% as contingency — especially if this is your first major ERP.


Mistake #6: Stretching Internal Resources Too Thin

ERP projects require your A-team. But here’s the problem — those people already have full-time jobs.

Trying to make your best employees juggle their day-to-day work while also leading a transformation is a recipe for burnout and failure.

I always recommend that companies backfill critical roles before ERP implementation begins. That could mean hiring temps, contractors, or reallocating duties so your core team can focus on the transformation.

Also: make sure your business users are empowered. Don’t let IT run the show alone. ERP success depends on strong cross-functional ownership, not just technical execution.


Bonus: Mistake #7 — Choosing Software Instead of Designing the Business

The final (and perhaps most important) mistake I see? Companies focus too much on the tool and not enough on the business design.

An ERP system can only enable what you’ve defined. If your processes are broken, automating them will just make bad things happen faster.

Before choosing software, step back and ask:

  • What are our core differentiators?
  • Which processes do we want to standardize vs. customize?
  • How do we want to run the business in 5 years?

Start with the operating model. Then choose the technology to support it.

That’s how you future-proof your ERP investment — and build a business that’s ready to scale.


Final Thoughts: Choose Strategy, Not Just Software

ERP selection is one of the most strategic decisions your organization will make. But it’s not about finding the flashiest system or the lowest price. It’s about choosing the right solution, implemented the right way, by the right people — all aligned to your business strategy.

At Third Stage Consulting, we help organizations navigate this process with vendor-agnostic, strategy-first guidance — ensuring you avoid costly missteps and make decisions that actually support your long-term growth.


Free Resource:
📘 Download the 2025 Digital Transformation Report — our annual guide featuring vendor comparisons, implementation benchmarks, and real-world best practices to help you plan smarter.


If you’re starting your ERP journey — or stuck midstream — let’s talk. We’ll help you get back on track, on budget, and aligned to the bigger picture.

YouTube player
Kimberling Eric Blue Backgroundv2
Eric Kimberling

Eric is known globally as a thought leader in the ERP consulting space. He has helped hundreds of high-profile enterprises worldwide with their technology initiatives, including Nucor Steel, Fisher and Paykel Healthcare, Kodak, Coors, Boeing, and Duke Energy. He has helped manage ERP implementations and reengineer global supply chains across the world.

Share:

More Posts

Subscribe for updates

We never share data. We respect your privacy

Additional Blog Categories

Artificial Intelligence 29
Business Intelligence 9
Business Process 22
Business Transformation 37
Cloud ERP Implementations 58
Cloud Solutions 1
Consulting 12
Coronavirus and Digital Transformation 13
CRM Implementations 27
Custom Development 1
Cyber Security 7
Data Management 7
Digital Strategy 301
Digital Stratosphere 11
Digital Transformation 417
Digital Transformation Case Studies 9
Digital Transformation News 9
E-Commerce 4
Emerging Technology 4
Enterprise Architecture 1
EPMO 1
ERP Architecture 3
ERP Consulting 30
ERP Expert Witness 3
ERP Failures 56
ERP Implementation Budget 2
ERP Implementations 386
ERP Project 18
ERP Software Selection 182
ERP Systems Integrators 16
ERP Thought Leadership 4
Executive Leadership in Digital Transformation 17
Future State 5
Global ERP Implementations 29
Government Transformation 1
HCM Implementations 72
Healthcare 1
IFS 4
Independent ERP 14
Independent ERP Consultants 29
Internet of Things 1
Legacy Systems 1
Manufacturing ERP Systems 7
Mergers and Acquisitions 2
Microsoft D365 10
Microsoft D365 Consultants 2
Microsoft Dynamics 365 Implementations 88
Microsoft Sure Step 1
NetSuite Implementations 42
OCM 9
Odoo 4
Oracle Cloud ERP Implementations 90
Oracle ERP Cloud Expert Witness 3
Oracle ERP Cloud Failures 7
Organizational Change Management 93
Project Management 12
Quality Assurance 3
Quickbooks 3
Remote ERP 1
Sage 100 3
SAP Activate 2
SAP Expert Witness 6
SAP Failures 23
SAP S/4HANA Implementations 123
SAP S/4HANA vs Oracle vs Microsoft Dynamics 365 9
SAP vs Oracle 6
SAP vs Oracle vs Microsoft Dynamics 7
Small Business ERP Implementations 18
Small Business ERP Systems 11
Small Businesses 3
Software Selection 36
Software Testing 5
Software Vendors 15
SuccessFactors Implementations 50
Supply Chain Management 33
System Architecture 5
Systems Integrators 8
Tech Trends 2
Tech Trends 1
Technology Consultant 3
Top ERP Software 35
Top OCM 0
Warehouse Management Systems 6
Workday Implementations 52