ERP selection for Swiss mid-market: how to run it without wasting a year

Most ERP selections in the Swiss mid-market take nine to fifteen months and produce a decision that could have been made in eight weeks. The extra time is not spent learning about the products. It is spent building internal agreement, badly, through the medium of a requirements spreadsheet.

There is a faster method, and it produces a more defensible decision.

Why the requirements-matrix approach fails

The standard method asks every department to list its requirements, weights them, scores each vendor, and picks the highest total. It fails for three structural reasons.

Every modern ERP satisfies roughly 85% of any mid-market requirement list, so the scores cluster and the ranking is decided by noise. Departments inflate importance weightings strategically once they realise the weights drive the outcome. And the requirements that actually differentiate — the twenty things that are genuinely hard in your business — are buried among three hundred that any product handles.

The matrix produces a number. It does not produce confidence.

The differentiating-requirements method

Replace the matrix with a much shorter, much harder question: what are the ten things about our operation that break standard ERP?

Ten, not three hundred. They are usually some combination of: multi-entity and multi-currency consolidation with Swiss and EU entities, variant configuration in manufacturing, project-based revenue recognition, Swiss payroll and social insurance integration, QR-bill and ISO 20022 payment handling, industry-specific traceability, and whatever your business does that competitors do not.

Then run those ten against each shortlisted product as scripted scenarios, with your own data, in a sandbox. Not a demo — a demo shows you the happy path the vendor rehearsed.

What is the difference between SAP, Microsoft, Odoo and Abacus for a Swiss company?

Honestly summarised, and generalising more than any individual case deserves:

Abacus deserves a specific note for Swiss buyers: Swiss payroll, social insurance and tax handling that works natively removes an entire integration workstream that the international platforms treat as a localisation project.

The right answer depends far more on your ten differentiating requirements than on any general ranking, which is why general rankings are of limited use.

How long should ERP selection take?

Eight weeks, structured like this:

• Weeks 1–2. Write the ten differentiating requirements. This is the hard part and the part that creates the internal agreement everything else depends on.
• Week 3. Longlist to four. Public information is sufficient at this stage.
• Weeks 4–6. Scripted scenarios with your own data, run by your people, in a sandbox. Two days per vendor. Score only the ten.
• Week 7. Reference calls with companies of similar shape — and ask for one that went badly.
• Week 8. Decide, and write down why, including what would have changed the answer.

That last artefact matters more than it sounds. In month fourteen, when somebody asks why you did not pick the other one, the written rationale is what prevents the decision being reopened.

Should we customise or stay close to standard?

Stay close to standard unless the process is genuinely a source of competitive advantage. The test is commercial, not technical: if a customer would not notice or pay for the difference, the customisation is a maintenance liability you will carry through every upgrade for a decade.

The exceptions are real, though. If your variant configuration logic is why customers choose you, standardising it away to simplify an upgrade path is a strategy error dressed up as an IT decision.

The cost line nobody budgets

Data migration. It is consistently the most underestimated phase, and the reason is structural: you cannot scope it accurately until you have looked at the source data, and nobody looks at the source data during selection.

Profile your master data during week 4, not during month nine. Count the duplicate customers, the products with no unit of measure, the open items nobody can explain. That number changes your timeline more than the platform choice does — the pattern we documented in why ERP programmes stall.

After selection

Selection is the easy half. The programme that follows is where the value is won or lost, and the binding constraint is decision latency rather than technology. Our ERP consulting practice instruments that from week one, and our partnership models tie part of the fee to the go-live date you were promised.

Related reading

• Why ERP programmes stall in Swiss mid-market companies
• How to measure ROI on a digital transformation before you fund it
• How to choose a management consulting firm in Zurich