by Carly Caines on May 21, 2026
You’re thinking about ERP, and naturally, you want to see the software.
You want to understand what it looks like, how it works and whether it can solve your problems. So, when someone suggests starting with ERP discovery, it can feel like a delay. Maybe even unnecessary.
Some providers might even tell you to skip it and go straight to a demo.
But that shortcut can lead to unclear expectations and a higher risk of choosing a system that doesn’t fully fit your business.
After working with over 200 small and mid-sized businesses on ERP projects, we’ve seen firsthand how discovery conversations uncover hidden process issues, misaligned expectations and gaps that would have otherwise surfaced much later—during demos, implementation or even after go-live.
In this article, you’ll learn what ERP discovery is, why it plays such a critical role and how to tell if it’s being done the right way. By the end, you’ll know what to expect and how to get real value from this step in the ERP buying process.
What is ERP discovery? (and why it matters)
At a high level, ERP discovery is a structured conversation between you and your ERP partner. If it’s done well, it’s much more than just going through a checklist of questions.
It’s where you define your business needs and challenges, what’s happening behind them and what a better future state could look like.
Just as importantly, this process isn’t only for the partner. You’re also building a deeper understanding of your own challenges and how ERP can solve them.
When you start your ERP journey, you likely have a general idea of what you want—better reporting, tighter inventory control or a way to move away from spreadsheets. Those goals are usually driven by underlying issues like manual reporting, inaccurate inventory or a heavy reliance on Excel.
The challenge is that those underlying issues aren’t always fully understood at the start.
Through ERP discovery, you might find that what you thought was a system issue is actually a process issue. Or that the problem is bigger (or smaller) than you expected. In some cases, it may even become clear that ERP isn’t the right solution for what you’re trying to solve.
Think of ERP discovery like planning a major home renovation
Imagine you’re doing a major home renovation. You’re stripping the house down to the studs and reworking the entire layout. Would you want your contractor to show up with a fully formed plan in the first meeting? Probably not. Because they don’t understand your needs yet.
To design a home that actually works for you, they need to understand what isn’t working today, how you use the space and what you want your future to look like. Only then can they design something that fits.
ERP discovery works the same way. It’s how you move from a general idea of what you want to understanding your challenges and what a better future state looks like.
What happens when you skip ERP discovery
It’s tempting to skip discovery and go straight to an ERP demo. You may just want to see the software and see how it works.
But without proper discovery, the demo you see will be based on assumptions, which may turn out to be inaccurate.
Instead of seeing a demo which speaks to your business process, you’ll get a generic walkthrough. You’ll see plenty of features, but they might not apply to your specific challenges or how your team would use them day-to-day.
You’re left trying to figure out whether the system fits your processes and solves the problems you’re dealing with. That’s not easy to do—especially if it’s your first time evaluating ERP. And when the demo isn’t relatable to your business, it becomes much harder to confidently choose the right system.
ERP projects don’t always go as planned. In some industries, that failure rate is significant. One study from Godlan Consulting found that 73% of discrete manufacturing ERP projects failed to meet their objectives, often with major cost overruns.
While every project is different, outcomes like this often come back to a mix of process, data and implementation challenges.
This is often where early discovery plays a role—helping you identify those requirements upfront so you can make a more informed system selection and avoid surprises later in the form of added tools, scope changes or workarounds.
For example, some businesses structure their ERP evaluation around an RFP (request for proposal) process, where they create a long list of requirements and send it to multiple ERP partners to compare solutions. On the surface, that can seem like a good approach because it appears to give each partner everything they need to propose a solution.
The challenge is that those requirement lists are often disconnected from the business context behind them.
We’ve seen many cases where, once the underlying processes, pain points and goals are explored through discovery, some requirements turn out to be misunderstood, outdated or no longer as important as they first appeared. Without that deeper understanding, ERP partners are left designing and pricing solutions based on assumptions. That can lead to unnecessary complexity, misaligned implementations and higher long-term costs.
Skipping ERP discovery increases the risk of choosing the wrong solution and creates issues that are more costly and harder to fix later in the process.
What a good (and bad) ERP discovery looks like
A strong discovery process will give you clarity and confidence as you move through your ERP journey, while a weak discovery pushes you forward without either.
Your ERP partner should be trying to understand your challenges in context and put themselves in your shoes. That means looking beyond surface-level requirements and taking the time to understand how your business operates.
Signs of a strong ERP discovery process
You’ll know the discovery process is being handled well when your ERP partner:
- Asks about the business problems behind your requirements, not just the features you want
- Explores whether the issue is a system problem, a process problem or both
- Digs into the impact of those problems, such as inefficiencies, extra costs, reporting delays or limits on growth
- Challenges assumptions in a helpful way, especially if there may be a better way to solve the problem
- Connects the conversation back to what you need to see in the ERP demo and proposal
- Focuses more on asking questions and understanding your business than talking about software features or solution approaches
A strong ERP discovery process should help you answer a few key questions: What challenges are you facing, how are you handling them today and what should be a better future state look like?
Signs of a weak or superficial ERP discovery process
A weak discovery process usually feels rushed or overly scripted.
You may still answer a lot of questions, but the conversation doesn’t go deep enough to understand your business. It becomes more about collecting requirements than understanding what’s driving them.
Common red flags include:
- The conversation feels like a checklist, with little room for discussion
- Your ERP partner asks what you need, but not why you need it
- The sales team talks more than they listen
- Everything is framed as a good fit without much explanation
- The goal seems to be getting to the demo as quickly as possible
Your partner should be trying to understand your business well enough to give you meaningful guidance, not just move you to the next stage in the ERP sales process.
How to prepare for ERP discovery (so you get real value from it)
You don’t need to have everything figured out going in, but a bit of preparation can make the conversation much more productive.
What to come prepared with
Your ERP partner isn’t looking for perfect answers, but you should have a clear sense of where things aren’t working in your business.
That might include:
- The biggest challenges your team is dealing with today
- Processes that feel manual, slow or error-prone
- Areas where you lack visibility or trust in your data
- Bottlenecks that are limiting growth or efficiency
Be open about what’s not working. Share real examples. If something is frustrating your team, that’s worth talking about.
Who should be involved
It’s important to have the right people in the room.
That usually includes individuals who understand how the business runs day to day and where the real challenges come from. This often means involving people from finance, operations and other key functional areas.
If only leadership is involved, you may miss important details. If too many people are involved, it can be hard to stay focused or aligned as a group.
The goal is to bring in people who can speak to how things actually work today—not just how they’re supposed to work.
Questions you should ask during discovery
ERP discovery is also a good opportunity to evaluate how the partner works and whether they’re a good fit for your business.
Some good questions to ask include:
- How does what we’ve described translate into what we’ll see in the demo?
- How have you seen other businesses solve similar challenges?
- What might we be overlooking at this stage?
The answers you get will tell you a lot about how well they understand your business and how they approach ERP projects.
How ERP discovery sets you up for success
Skipping discovery can feel like a way to move faster. You get to the demo sooner and that feels like progress.
But as you’ve seen, that shortcut often creates more uncertainty, not less. You’re left trying to evaluate a system without enough context and that can lead to decisions that don’t fully align with your business.
After working with hundreds of ERP projects, one thing is consistent:
ERP discovery is what turns a generic demo into a decision-ready evaluation. When it’s done well, it brings clarity to your requirements, uncovers root issues early and reduces the risk of choosing the wrong system or underestimating scope, cost and the timeline of your ERP project.
The next step is to work with a partner who can guide you through that process—asking the right questions, challenging assumptions and helping you get a complete picture of what your business actually needs.
Have questions about ERP? We’ve got answers.
Book a quick call with our team to gain clarity and take the next step of your ERP journey with confidence. There’s no pressure, no obligation—just honest advice to help you make the right decision for your business.
