How to choose an ERP consulting firm: process, criteria, questions
Choosing an ERP consulting firm is the decision by which a company picks the firm that will run its ERP project, comparing candidates on scope, method, team, pricing model and references. A sound choice starts from a written scope, not from a software demo: firms are assessed against the same needs, the same scenarios and the same criteria, and proposals are compared on the same line items.
Last updated: · MindDX
01Selection process
Choosing an ERP consulting firm, step by step
Each step uses the output of the one before. Skipping steps usually ends in proposals that cannot be compared and a scope that grows later.
Clarify the need and the scope
Write down which processes will change, which systems need a connection, the state of your data and the local regulatory flows. Proposals requested before the scope is written are prepared on each firm’s own assumptions.
Build a long list
List the firms that have worked in your sector and production type, implement the software you are considering and can offer a team close to you. At this stage the aim is not to eliminate but to see who could meet the scope.
Send a request for proposal (RFP)
Send every firm on the long list the same scope, the same questions and the same proposal structure: company profile, processes, current systems, data migration, localisation, expected timeline and evaluation criteria.
Narrow it to a shortlist
Read the answers with the evaluation table below. The firms that understand the scope without rewriting it, state their assumptions openly and answer the questions stay on the shortlist.
Hold demos and reference calls
Ask the shortlisted firms for a demo built on your own scenarios instead of a prepared presentation — for example, an order’s journey from quotation to production, shipping and invoice. Then talk directly to one of the firm’s customers in a similar situation.
Compare the proposals
Read the proposals on total cost of ownership and on the same line items, not on the day rate: licence, consulting, data migration, integration, training, support and the time your own team will give.
Sign the contract
Write the scope, the acceptance criteria, the roles, change management and post-go-live support into the contract. Everything said in the proposal and the demo should also be in the contract.
02Evaluation criteria
Which criteria should you assess a consulting firm on?
Fill in the same table for every candidate. The «How to test it» column makes sure the answer comes from evidence, not from a presentation.
| Criterion | Why it matters | How to test it |
|---|---|---|
| Sector experience | A firm that has worked with similar processes knows the critical points of your business from the start and asks the right questions. | Ask for completed projects in your sector and production type, together with their scope. |
| Method | If the scope is not validated before the implementation commitment, the real scope surfaces during the project and causes rework. | Ask how the scope is validated before the commitment, and in which written deliverable. |
| Team and local presence | Training, testing and go-live need a team that speaks your language, knows local regulation and is at your side when needed. | Ask for the people who will work on the project by name, with their roles and experience; ask whether the sales team stays on the project. |
| Data migration and integration | Projects struggle most with cleaning the data that comes from the old system and with the connections to other systems. | Ask who is responsible for data migration and integration, and how both are rehearsed before go-live. |
| Localisation and e-documents | In Türkiye, the e-invoice, e-archive, e-dispatch and e-ledger flows, the chart of accounts and taxes are a precondition of go-live. | Ask to be shown how the e-document flow is set up, who maintains it and how it is tried with real documents. |
| Pricing model | If the price is tied to the days spent (man-days), the budget grows with the scope; if it is tied to a written scope, a change is discussed separately. | Ask in writing which scope assumption the proposal rests on and how a request outside the scope is priced. |
| Post-go-live support | Go-live is not the end; questions, corrections and new needs pile up in the first weeks. | Ask about the scope, channel and language of post-go-live support, and how version upgrades are planned. |
| References you can call | The first-hand account of a similar customer shows far more than a prepared presentation. | Ask for at least one customer you can talk to, and ask them yourself how the project went. |
If you want to add a weight column to the table, you set the weights: your scope tells you which criterion matters more to you. This page proposes no ready-made weight or score.
03Questions to ask
Ten questions to ask a consulting firm
Ask these questions in the same way in the request for proposal and in the demo meeting, and ask for the answers in writing.
- How do you validate the scope, and which scope assumption does your proposal rest on?
- Which projects have you run in our sector and production type, and can we talk to one of those customers?
- Who will work on the project, and will the team named in the proposal stay the same throughout?
- Is your price tied to the days spent or to a written scope, and how is a request outside the scope priced?
- Who carries out the data migration, who is responsible for cleaning the data, and how is the transfer rehearsed?
- Which systems will you integrate with, and who will maintain those connections?
- How do you set up the e-invoice, e-archive, e-dispatch and e-ledger flow, and how do you test it before go-live?
- How do you decide between standard features, configuration and custom development, and how do you plan version upgrades?
- Whom on our team do you expect to give time, and to which work?
- How is support delivered after go-live, and where and in which language are questions raised?
04Warning signs
Warning signs: when to be careful
None of these signs rules a firm out on its own, but each one calls for a written answer before the contract.
A firm price and timeline before the scope is clear
A price and a date given before your processes and data have been reviewed are an assumption; when the assumption proves wrong, the difference comes back to you.
A prepared demo instead of your scenario
If only a prepared presentation is shown and nothing can be tried with your own order, bill of materials or invoice, the fit has not really been tested.
No reference you can talk to
If only a list of logos is offered and no conversation with a customer can be arranged, the claim of experience cannot be checked.
An unclear team
If the role of the people from the sales meetings on the project is not written down, the team may change once the project starts.
Line items missing from the proposal
If data migration, integration, training or post-go-live support do not appear as separate items, that work is either out of scope or will be priced later.
Custom development for every need
If code is proposed for every need without questioning the standard features, a burden builds up that has to be carried over at every version upgrade.
Promised results that were never measured
Promises of efficiency or savings made without a baseline measurement are not a result but an estimate.
05Manufacturing companies
Extra points for manufacturing companies
In a manufacturing company, the consulting firm must be able to show the production processes with your own data. In demos and reference calls, test these points in particular:
Bill of materials (BOM)
How multi-level bills of materials with variants and revisions will be migrated, and who will maintain them.
Routings and work centres
How operation sequences, work-centre capacities and subcontracted operations will be reflected in the system.
Material requirements planning (MRP)
How material planning will be set up for your production type, make-to-stock or make-to-order.
Lot and serial tracking
At which points traceability from raw material to shipment is recorded, and how it is queried backwards.
Quality
How incoming, in-process and final inspections, non-conformance records and corrective actions will be tracked.
In the glossary: Bill of materials (BOM) · Routing · MRP (Material Requirements Planning) · Lot and serial tracking
06The MindDX approach
The MindDX approach
At MindDX, consulting starts from evidence, not from software. Assess comes first: Checkup measures maturity independently of software; Discover Scope is added for a new system, Audit for an installed Odoo, Zoho or abas ERP system, and the output is the validated scope. Then Implement, at a fixed price based on the validated scope.
07Questions
Frequently asked questions about choosing an ERP consulting firm.
Write the scope first, then test the firms against the same scope and your own production scenarios. In the demo, see how your bills of materials, routings, material planning, lot and serial tracking and quality inspections would work in the system; talk to a customer with a similar production type; and ask in writing who handles data migration and integration, what the price depends on and how post-go-live support works.
The scope comes before both. Consulting firms often implement particular software, so in most projects the software and the firm are assessed together. When the scope is written independently of software, both the software candidates and the firms can be compared against the same needs.
What decides is not the number but comparability. Keep as many firms on the shortlist as you can really assess with the same scope and the same scenario; ask each the same questions and read the answers in the same table.
Firms often price different things: the scope assumptions, the pricing model (days spent or a written scope) and the items included differ. Data migration, integration, training and support may be in one proposal and not in another. Reading proposals on the same scope and on total cost of ownership shows where the difference comes from.
Ask whether the project finished within the planned scope, what happened when the scope changed, whether the team stayed the same throughout, how data migration and go-live went and how post-go-live support works. If possible, talk to a customer whose processes are similar to yours.
Start the selection from the scope
X-ray first, then diagnosis: choosing a consulting firm before the scope is clear is writing a prescription before the diagnosis. Let’s set the starting point together in a meeting.