Most ERP selection processes start the same way. Someone at the executive team level, usually the CFO or COO, says out loud what everyone has been thinking: we've outgrown this. The next month is spent taking demos.
That sequence is backwards. By the time a company is watching demos, half the important decisions have already been made, most of them by accident.
This is a practical guide to running the process the right way. What to evaluate, what questions to ask, and when to bring in outside help.
Before evaluating any platform, answer one question honestly: is the current system actually the problem?
Sometimes it is:
The vendor is sunsetting the product.
The system can't support the current entity structure.
The integration architecture fights every new tool.
These are structural limits that no amount of configuration will fix.
More often, though, the signals point somewhere else. Modules that were paid for are not turned on. Processes run in spreadsheets alongside the system. Reporting is manual because the dashboards were never configured. In those cases, replacing the platform doesn't solve the problem. It transfers it to a new platform with a bigger implementation invoice.
A real ERP selection process starts by ruling this out. If nobody has asked whether the current system could do the job with better configuration, the selection process is starting with an assumption instead of an evaluation.
Once replacement is the right direction, resist the urge to make a vendor list. Define the problem first.
What specifically does the business need the system to do that it can't do today? Not "modernize finance" or "improve reporting." Concrete outcomes. Close the books in ten days. Consolidate three entities into one general ledger. Support a fourth reporting currency. Handle the acquisition that closes in Q3.
This list is what a good selection process is measured against. Without it, every vendor's demo will look impressive, because every vendor is showing what their product does well. The list is how a buyer separates "capable" from "fit."
Once a shortlist exists, the same four questions apply to every platform under consideration.
Does the platform support the business as it will look in three years, not just today? An ERP is a five-to-ten-year decision. Growth plans, acquisition activity, and reporting complexity all belong in the evaluation.
What does the total cost look like, honestly? Software license is often the smallest number. Implementation, integration, internal time, ongoing administration, and change management all belong in the comparison. A platform that costs less to license and more to run is not a cheaper platform.
What does a successful implementation actually require from us? Every vendor will say implementation is straightforward with the right partner. That's not useful. Useful is: what does the internal team need to commit, for how long, and what decisions will we have to make that we haven't made yet?
What happens after go-live? This is the question most selection processes never ask. Who owns the platform once the implementation partner leaves. Who configures the next report. Who decides when to turn on the modules that weren't in scope for phase one. If nobody has a clear answer, the platform will under deliver regardless of which one is selected.
An ERP decision is one of the largest technology investments a mid-market company will make in a decade. It is also one of the hardest to evaluate objectively from the inside, because most of the people who can help are selling something.
The value of an independent advisor in an ERP selection is not that they know the platforms better than the vendors do. The vendors know their own products best. The value is that an advisor can tell a company when the answer is "keep what you have and fix it," when the answer is "you need a new platform but not the one you're currently leaning toward," and when the answer is "the platform you're looking at is the right one." All three are possible outcomes. In a vendor-led process, only one of them is.
At Rotation Digital, this is what our Lighthouse platform is designed to support: giving executive teams a defensible, evidence-based recommendation rather than a shortlist shaped by whoever they talked to first.
The companies that get ERP selection right share a few habits. They rule out configuration issues before shopping for platforms. They define success in concrete terms before running demos. They evaluate total cost, not license cost. They have a plan for what happens after go-live.
None of this is complicated. It's just rarely how the process actually runs.