Mon – Sat: 9:00 AM – 7:00 PM IST
ERP Basics

How to choose an ERP system

A selection method that tests fit against your own processes rather than against a feature list.

In short

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.

Why It Matters

Why this matters in practice

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.

Scenarios expose fit; checklists do not
Distinguishes configuration from customisation before you commit
Surfaces the gaps that become change requests later
Lets the people who will use it form a view
How It Works

How it works in practice

1

Identify what is distinctive

Most of your processes are ordinary. Find the handful that are not — costing method, approval chain, statutory requirement — and focus there.

2

Write demonstration scenarios

Real cases end to end, with your data: a rush order on credit hold, a part-delivery, a month-end close.

3

Insist on standard product

Ask explicitly whether each scenario was shown in standard configuration or with development. The answer changes the cost.

4

Score consistently

Same scenarios, same scorers, same scale across vendors. Impressions fade between demonstrations weeks apart.

5

Check references in your sector

Speak to customers with similar complexity, and ask what went wrong rather than whether they are happy.

Worked example

A worked example: a scripted demo that changed the shortlist

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.

Key terms

The vocabulary, briefly

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.
What Goes Wrong

Common mistakes worth avoiding

Feature checklists as the primary tool

Every vendor answers yes. The matrix produces no discrimination and a false sense of rigour.

Demonstrations on vendor data

Vendor demo data is clean and designed to flatter. Use your own.

Excluding the eventual users

They will find the problems in month one. Better they find them during selection.

Deciding on licence cost

Licence is a fraction of total cost. Implementation, change and support dominate.

What to measure

Numbers worth tracking

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.
FAQ

Questions we are asked about this

Long enough to script scenarios, see them demonstrated and check references — commonly two to four months for a mid-sized business. Rushing it transfers the cost to implementation.
It can help where the team has not done this before, provided the consultant is genuinely independent of the vendors being considered. Ask directly about their commercial relationships.
Write down what matters, weighted, and keep it proportionate. A document listing 600 undifferentiated requirements produces vendor responses claiming to meet 580 of them, which tells you nothing. Thirty weighted requirements, with the genuinely essential ones marked, produces responses you can compare. The weighting is the valuable work, and it is also where internal disagreement surfaces usefully.
Frequently more important than the product. A capable partner will deliver a good outcome on a merely adequate product; a weak partner will deliver a poor outcome on an excellent one. Evaluate the partner with the same rigour as the software — named team, relevant sector experience, references you choose rather than ones you are given, and a clear statement of who owns the code afterwards.
It belongs on the list if per-user licensing is a material constraint or if you need deep adaptation. Be clear about what changes: the licence cost disappears, the implementation cost does not, and the absence of a vendor shifts risk onto your choice of implementer. That is a real trade with real advantages, and it should be evaluated on total cost and on partner quality rather than on the licence line alone.
Two to four months for a mid-market selection is reasonable — long enough for scripted demonstrations and reference checks, short enough that the team does not lose momentum and the requirements do not go stale. Selections running past six months usually indicate unresolved internal disagreement about scope or ownership, and that disagreement will follow you into implementation if it is not settled first.
Related

Where to read next

Cloud vs on-premise ERP

Read more

ERP total cost of ownership

Read more

What is ERP software?

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.