Most manufacturers start their ERP evaluation by looking at software. They Google “best ERP for manufacturing,” schedule demos with two or three vendors, and start comparing features. It feels productive. But it almost always leads to a decision you’re not confident in, because you skipped the foundational work that makes the comparison meaningful.
Before you look at a single vendor, answer these seven questions. They will sharpen your evaluation, speed up your timeline, and dramatically increase the odds that the system you choose actually delivers results.
1. What does this company need to look like in 24 months?
This is not a technology question. It’s a business strategy question. Are you trying to grow revenue from $40M to $60M? Improve margins? Expand into a new market? Retain institutional knowledge as senior employees retire? The answer to this question defines what your ERP investment needs to enable. Without it, you’re buying technology for the sake of technology.
2. What 2–3 measurable outcomes would make this investment worthwhile?
Get specific. “Better visibility” is not a measurable outcome. “Reduce quote turnaround from 5 days to 24 hours” is. “Improve on-time delivery from 72% to 93%” is. “Eliminate the 15 hours per week the finance team spends manually reconciling inventory” is. If you can’t define the outcomes, you can’t evaluate whether any vendor will help you achieve them.
3. What is the current state actually costing you?
Quantify the pain. How many quotes are you losing because your response time is too slow? What does each late shipment cost in expediting fees and customer goodwill? How much time does your team spend on manual workarounds that would disappear with the right system? These numbers build a business case that writes itself and create urgency that keeps the project moving.
4. What needs to change beyond the technology?
ERP implementations fail when organizations expect software to fix process problems. If your quoting is slow because you don’t have standard costing models, new software won’t fix that until you build the models. If your scheduling is chaotic because nobody owns the production schedule, new software will just automate the chaos. Be honest about what needs to change in your processes, roles, and accountability structures alongside the technology.
5. Who needs to own this decision?
ERP selection by committee produces committee-quality decisions. You need an executive sponsor with the authority to make the final call, the credibility to drive organizational change, and the time to stay engaged throughout the process. If your CEO or COO is too busy to be meaningfully involved, that tells you something about whether the organization is ready for this project.
6. What is your realistic budget for the total project?
Not just software licensing. The total project: software, implementation services, internal team time, training, change management, and a 20% contingency. For a midmarket manufacturer, this is typically 1 to 3 percent of annual revenue. A $60M company should be planning for a $600K to $1.8M total investment. If your budget is significantly below that range, you either need to reduce scope or adjust expectations about what the project will deliver.
7. Are you willing to change how you work?
This is the question nobody wants to answer honestly. An ERP implementation is an organizational change project with a technology component, not the other way around. If your team is expecting new software that works exactly the way the old software worked but with better screens, the project will disappoint. The manufacturers who get transformative results from ERP are the ones willing to rethink their processes, challenge their assumptions, and commit to doing things differently.
Start here, not with demos
If you can answer these seven questions clearly and honestly, you will walk into vendor conversations with a level of clarity that most manufacturers don’t have. Vendors will take you more seriously. Your evaluation will be faster and more focused. And the decision you make will be grounded in business outcomes rather than feature comparisons.
If you can’t answer them yet, that’s okay. That’s exactly what our Business Outcomes Discovery phase is designed to help with.
Need help answering these questions?
Our Outcomes Discovery Workshop is a standalone two-day engagement designed to produce your Business Outcomes Charter. Learn more →