Three Systems, No Diagnosis: An ERP Selection Story

A business owner called us with what sounded like a simple request.

They had narrowed their search for a new system down to three options. The demos had happened. They wanted us to evaluate the three systems and tell them which one to choose.

We asked one question first: evaluate them against what?

There was no written list of what the business needed. No agreed priorities. No clear picture of how work moved through the company today, or how it needed to move tomorrow. There were three systems on the table and nothing to measure them against.

So we told them what we would tell anyone in that position.

You can't bring three different medications to a doctor and ask which one to take.

A good doctor will not pick one off the counter. They examine you first. They ask questions, order blood work, and find out what is actually wrong. Only then does the choice of medication mean anything. Without the diagnosis, any of the three could be the right one, and any of them could do harm.

Choosing a business system works the same way. Without a diagnosis, comparing three systems is really comparing three sales presentations.

Why the first demos missed

Looking back at the first round of demos, the problem was easy to see. Each software company showed what its system does best. The screens were polished and the features were impressive. But very little of what the team saw was about their business.

That is not the software company's fault. When a buyer has not said what it needs, the demo fills the gap with the product's strengths. The team watched three good presentations, came away with three good impressions, and had no way to tell which system would actually fit. The same gap shows up later in the paperwork: what a proposal sounds like and what it commits to are often two different things.

Three months of groundwork

Instead of scoring the three systems, we started with the examination.

We spent three months working with the client's team. We sat with the people who do the work and looked at how things actually run today, including the workarounds nobody had written down. We found where the real friction was and what the business needed a new system to fix. We put those needs in writing and agreed the priorities with the team: what the business cannot run without, and what would simply be nice to have. Then we turned the most important needs into real situations from the client's own work, for each software company to walk through.

This is the part that sounds slow from the outside. It is also the part that makes everything after it faster. It is what we call Phase 0: finding the problem before buying the solution.

The second round of demos

Then the client invited the software companies back.

The difference showed from the first meeting. This time the team was not sitting through presentations. They were leading them. Their questions were about their own work: show us how your system handles this situation, step by step, the way it happens here. The conversations went deeper, and the gaps between the three options became easy to see.

The team noticed the change themselves. The first demos had shown them three products. The second round showed them which product fit their business.

Choosing with confidence

In the end, the client chose the right system for them, and they chose it with confidence. Not because a consultant told them which one to pick, but because they could see for themselves how each option handled the work that mattered most.

That confidence is the real outcome of the groundwork. The decision was theirs, and they knew why they made it.

Before your first demo

If you are about to compare systems, ask yourself a few questions first:

• Can you describe, in writing, what the new system needs to do for your business?
• Has your team agreed which needs are essential and which are nice to have?
• Do you know how work moves through the business today, including the workarounds?
• Could you give every software company the same situations to demonstrate?

If the answer to any of these is no, the demos can wait. Do the examination first. Our ERP selection work starts exactly there, and the free readiness checklist is a quick way to see where you stand today.