A selection method that tests fit against your own processes rather than against a feature list.
Choosing an ERP means establishing which of your processes are genuinely distinctive, scripting demonstration scenarios from them, and scoring vendors on how the standard product handles those scenarios. Feature checklists favour whoever has the longest list; scenario demonstrations favour whoever actually fits.
Most selections are decided by a requirements matrix with hundreds of rows, each answered yes by every vendor. That process cannot distinguish between products, so the decision ends up resting on price or rapport. Scripted scenarios using your own data produce visible differences, because awkward cases are where products genuinely diverge.
Most of your processes are ordinary. Find the handful that are not — costing method, approval chain, statutory requirement — and focus there.
Real cases end to end, with your data: a rush order on credit hold, a part-delivery, a month-end close.
Ask explicitly whether each scenario was shown in standard configuration or with development. The answer changes the cost.
Same scenarios, same scorers, same scale across vendors. Impressions fade between demonstrations weeks apart.
Speak to customers with similar complexity, and ask what went wrong rather than whether they are happy.
Three vendors reach the shortlist. All demonstrate impressively, all claim to handle the business's requirements, and the evaluation team finds them hard to separate.
The team then issues the same scripted scenario to each: take this actual customer order with its mixed tax treatment, a part delivery, a price override requiring approval, and a credit note against a partly paid invoice — and show it end to end with our data. One vendor does it cleanly. One does it with two workarounds, explained candidly. One cannot complete it without custom development, which had not come up in the standard demo at all.
The scripted scenario took a day to write and resolved a decision that had been stuck for weeks. The general principle is that vendor demonstrations are optimised to show strength, and the only reliable way to see weakness is to choose the scenario yourself — specifically the awkward one that your team argues about internally.
| Term | What it means |
|---|---|
| Fit-gap | Comparing your requirements against a system's standard capability. |
| Requirements weighting | Separating what is essential from what is desirable, before seeing any demonstration. |
| Scripted demonstration | A demo following your scenarios and your data rather than the vendor's. |
| Reference visit | Speaking to an existing customer, ideally one of similar size and sector. |
| Total cost of ownership | Licence, implementation, infrastructure and support over several years. |
Every vendor answers yes. The matrix produces no discrimination and a false sense of rigour.
Vendor demo data is clean and designed to flatter. Use your own.
They will find the problems in month one. Better they find them during selection.
Licence is a fraction of total cost. Implementation, change and support dominate.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Requirements met in standard | The proportion needing no customisation. The single best predictor of cost. | |
| Total cost of ownership over five years | Not year one, where licence and implementation distort the comparison. | |
| Reference satisfaction | What existing customers of similar size and sector actually report. | |
| Implementation partner capability | Often a larger determinant of success than the product chosen. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.