Before you ask “Which ERP should we buy?”, there’s a better first question:
“Are we actually ready to do this?”
ERP is not just buying software. It’s deciding to take your business apart a bit, clean up the messy parts, and put it back together in a more disciplined way. That can absolutely be worth it. It can also be miserable if you go in before you’re ready.
Here are the questions I’d ask myself as an owner before I green‑light an ERP project. Side note, if you read our article on Why ERP Projects Fail and How to Avoid it, you’ll notice a lot of commonalities here. Asking yourself these questions is the best and first step you can take to avoid failure on these projects.
1. Do I know what problems I’m trying to solve?
Not “Do I want ERP?” but “What exactly is broken today?”
Ask yourself:
- Where do we feel pain every single week?
- What are the three things we’re always apologizing to customers for?
- Which decisions are we making on gut because we don’t trust the numbers?
If all you have is “our systems are old” or “QuickBooks feels small,” you’re not ready. If you can say “we’re constantly running out of stock,” “our lead times keep slipping,” or “we’re closing the month on day 20,” now you’ve got something you can design a project around.
If you cannot write down 4–6 specific business outcomes you want (with verbs and numbers), press pause. ERP should be a tool to hit those outcomes, not the outcome itself.
2. Am I willing to change “the way we’ve always done it”?
ERP will not simply automate your current chaos. It will force choices.
Ask yourself:
- If the new system suggests a simpler way to do something, am I willing to kill my pet processes?
- Are there sacred cows in our workflows no one is allowed to question?
- Do I want the software to validate the way we work, or am I genuinely open to improvement?
If your internal stance is “the system must match exactly how we do it today,” you’re about to buy a very expensive typewriter. You might be better off tightening processes first, with the tools you already have, before layering in a platform.
3. Do I trust my team enough to put them in charge of parts of this?
ERP done well is not the owner and an IT person making decisions in a vacuum. It’s a cross‑section of the company designing how work will flow for the next decade.
Ask yourself:
- Who are my “truth tellers” in operations, finance, sales, and the warehouse?
- Am I prepared to give them real time away from their day job to work on this?
- Can I live with them telling me “your favorite report/process needs to change”?
If your honest answer is “I don’t really have people I trust to own pieces of this,” the first project is developing those people. A big system with no internal champions will just become something everyone blames.
4. Are we willing to clean up our data?
ERP does not magically turn dirty data into clean data. It just makes the dirt more visible.
Ask yourself:
- How messy are our customers, vendors, items, and BOMs right now?
- Are there duplicates, old junk, and mystery codes we keep “just in case”?
- Who will own the job of deciding what gets cleaned, what gets archived, and what gets left behind?
If the plan is “we’ll just migrate everything and clean it later,” you’re not ready. “Later” is when everyone is tired and just wants the project to be over. Data cleanup needs to be part of the plan from the start, not a side quest.
5. Do I have time to actually lead this?
You don’t need to run every meeting. You do need to be visibly engaged.
Ask yourself:
- Can I carve out steady time each week for steering‑level decisions and removing roadblocks?
- Am I prepared to say “no” to other initiatives while this is going on?
- Do people believe this is truly a priority for me, or just another “nice to have”?
If your calendar is already a game of Jenga, an ERP project will either stall or run wild without direction. Better to delay six months and clear the decks a bit than to “fit it in” around the edges.
6. Are we financially ready for the whole cost, not just the software?
The subscription number is the easy part. The real cost is people’s time and implementation work.
Ask yourself:
- Do I have a realistic budget in mind for implementation, not just licenses?
- Am I okay paying for configuration, training, and support, not just “turning it on”?
- Am I ready for key people to spend less time on their normal jobs for a while?
If the honest plan is “we’ll buy the software now and figure out the rest as cheaply as possible,” you’re likely to end up with an expensive half‑finished system and a team that hates it. You don’t need a giant enterprise budget, but you do need to be clear‑eyed about the investment.
7. Can we survive a few months of being slower before we get faster?
There is always a dip. People learn new screens, new codes, and new rules. It’s awkward. Mistakes are made. That doesn’t mean it was the wrong move; it means you’re in the messy middle.
Ask yourself:
- Can we tolerate some short‑term inefficiency without panicking?
- Are we willing to keep old and new systems in parallel for a short time, then actually pull the plug?
- Do I have the patience to work through the “why is this so clunky” stage?
If your tolerance for short‑term pain is zero, implementation decisions will skew toward “whatever is fastest today,” which is exactly how you end up recreating the old world in new software.
8. Do I know what “good” looks like 12–18 months after go‑live?
Go‑live is not the finish line. It’s the point where the tool moves from project to everyday life.
Ask yourself:
- A year after go‑live, how will I know this was worth it?
- What KPIs or reports should look different?
- What work should feel easier or faster for my team?
If you can’t picture the “after” in concrete terms, it’s very hard to steer the project in the right direction. You don’t need a 50‑page business case. You do need a short, specific story of the future that everyone can recognize when you get there.
If you walk through these questions and keep bumping into “no,” “not yet,” or “I don’t know,” that doesn’t mean you should never implement ERP. It means the work right now is getting yourself and your company ready so that when you do pull the trigger, it’s a controlled decision, not a desperate leap.