15 Questions to Ask an ERP Implementation Company Before Hiring

15 Questions to Ask an ERP Implementation Company Before Hiring

15 Questions to Ask an ERP Implementation Company Before Hiring

15 Questions to Ask an ERP Implementation Company Before Hiring

Quick Answer: What questions should I ask an ERP implementation company before hiring?

Ask about their track record on similar projects, their implementation method, how they handle scope changes, who actually does the work, and how they define “done.” Push for specifics on data migration, testing, training, go-live support, and what happens if the project runs late or over budget. The answers separate firms that manage ERP projects from firms that merely sell them.

You can apply these questions at any stage: a first discovery call, a formal request for proposal, or a final contract negotiation. Smaller boutique firms and large systems integrators answer them very differently, and that difference matters more than the price tag.

Before signing, compare fixed-fee versus time-and-materials pricing, named consultant CVs, reference clients you can actually call, acceptance criteria, payment milestones, exit clauses, and post-go-live support terms.

Why These Questions Decide Whether Your ERP Project Sinks or Floats

Why These Questions Decide Whether Your ERP Project Sinks or Floats

ERP projects have a reputation, and it is earned. Budget and timeline overruns are so common that they are closer to the norm than the exception, and surveys of ERP outcomes have consistently found that most projects run past their planned budget or schedule. One widely cited estimate from 2014 put average cost overruns around 30% above budget, with implementations taking roughly twice as long as planned. That figure is old, but the pattern has not disappeared.

The uncomfortable truth is that most of those overruns were visible in the sales process. They hid in vague scope documents, optimistic timelines, and contracts that never defined what “finished” meant. The questions below are designed to drag those risks into the open before money changes hands.

There is a second reason to ask hard questions early. The quality of your questions signals to the vendor how you will manage the project. Firms that know they are dealing with a prepared buyer tend to scope more honestly.

Questions About Track Record and References

1. How many projects have you delivered on this specific ERP platform?

General ERP experience is not the same as experience with your chosen system. Ask for a count of live implementations on that product, in your country, in your industry, and at roughly your company size. A firm with 200 SAP projects and three Microsoft Dynamics projects is not the right partner if you are buying Dynamics.

2. Can I speak to three reference clients whose projects look like mine?

Ask for references from projects that went live in the last 18 to 24 months, with a similar module mix and user count. Then ask the reference clients two questions the vendor cannot script: what went wrong, and how did the vendor respond? Every project has a rough patch. The response to it tells you more than the success story.

3. What happened on your last project that ran late?

This question makes weaker vendors uncomfortable, which is the point. Strong implementers can name a specific cause, describe what they changed, and explain how they would prevent a repeat. Vague answers about “client-side delays” without detail are a warning sign.

Questions About Methodology and Scope

4. Walk me through your implementation phases and what I sign off at each one.

You want a phase-by-phase map: discovery, design, configuration, data migration, testing, training, cutover, and hypercare. For each phase, ask what deliverable you receive and what acceptance looks like. If the answer is a single “implementation plan” document, keep asking.

5. How do you run requirements workshops, and who attends from your side?

Poor requirements gathering is one of the most consistently identified causes of ERP failure in academic and practitioner research, alongside scope creep and weak user involvement. Ask how many workshops are included, whether they are run by a business analyst or a junior consultant, and how the outputs are documented and approved.

6. What is your change control process, and what does a change typically cost?

Scope creep kills budgets quietly. Ask how changes are logged, who approves them, and what the hourly or fixed rate is for change requests. Get that rate in writing. A vendor that resists putting change rates in the contract is telling you something.

7. What is explicitly out of scope in this proposal?

Most proposals list what is included. Fewer list what is not. Push for the exclusions list: additional reports, integrations, data cleansing, extra training sessions, and post-go-live fixes. This single question prevents more disputes than any other on the list.

Questions About the Team Doing the Work

8. Who are the named consultants, and can I meet them before signing?

Sales teams and delivery teams are often different people. Ask for the CVs of the project manager, lead functional consultants, and technical lead, and request that key personnel be named in the contract with a replacement approval clause. If the A-team pitches and the C-team delivers, you want contractual protection.

9. How many projects will my project manager handle at once?

A project manager splitting attention across four implementations is a part-time project manager. Ask for the actual allocation percentage and confirm it in writing.

10. What percentage of the work is done offshore or by subcontractors?

This is not automatically a problem, but you should know. Ask where each workstream sits, what time-zone overlap exists, and who your single point of contact is. Distributed delivery can work well, but only with deliberate communication design.

Questions About Data, Testing, and Go-Live

11. Who is responsible for cleaning our data, and how is migration tested?

Data quality and migration problems are a recurring cause of go-live delays. Clarify the split: the vendor usually extracts, transforms, and loads, while your team owns data cleansing. Ask how many migration test cycles are included and whether a full cutover rehearsal happens before the real one. (Managed detection response checklist 12 questions ask before)

12. How many rounds of testing are included, and who writes the test scripts?

Ask about unit, integration, user acceptance, and performance testing separately. Confirm who writes the scripts, who executes them, and what defect severity levels trigger a delay to go-live.

13. What does hypercare look like, and how long does it last?

Post-go-live support is frequently under-specified. Ask how many weeks of on-site or dedicated support are included, what the escalation path is, and how knowledge transfer to your internal team happens. Four to six weeks is common; two days is not hypercare.

Questions About Money, Contracts, and Exit

14. What is the five-year total cost of ownership beyond the implementation fee?

Implementation is the visible cost. Ongoing support and maintenance typically run as a percentage of licence value each year, and upgrades, internal staff time, and training add more. Ask the vendor to model year one through year five, including their own support fees.

15. How are payments tied to milestones, and what are the acceptance criteria?

Milestone-based payment protects you. Ask what percentage is paid at contract signature, at design sign-off, at go-live, and after final acceptance. Then ask what happens if a milestone is missed. Public-sector IT guidance has long recommended clear acceptance criteria and exit clauses, and the same discipline applies to private buyers.

The Due-Diligence Questions Buyers Forget

Beyond the fifteen, a few practical checks separate prepared buyers from hopeful ones.

First, ask for the vendor’s own implementation checklist and compare it to what you have seen elsewhere. A firm with a genuine method will hand over a structured document without hesitation. If you are also evaluating software vendors directly, the same discipline applies to product due diligence, much like the scrutiny in this AI chatbot security 2027 checklist of nine questions to ask before buying, where vague answers about data handling and support are a red flag.

Second, ask whether the vendor has ever recommended that a client delay go-live. A firm that has never advised caution has either been lucky or is telling you what you want to hear.

Third, ask about their relationship with the software publisher. Are they a certified partner, what tier, and does that affect your licence pricing or support escalation path?

Finally, run the numbers on support and managed services separately. If you plan to outsource ongoing operations, treat it as its own buying decision, similar to working through a managed detection response checklist of 12 questions to ask before committing, because the questions about escalation, coverage, and reporting are just as relevant to ERP support as they are to security operations.

Common Mistakes Buyers Make

The most common mistake is treating the proposal as the scope. It is a sales document. The contract and the statement of work are the scope, and they are usually shorter and narrower than the proposal.

The second mistake is skipping reference calls because the vendor seems credible. Credibility in a meeting is a presentation skill. Credibility on a reference call is a track record.

The third mistake is underestimating internal effort. Your team will spend significant time on requirements, data cleansing, testing, and training. Budget that time explicitly, because a project that assumes zero internal cost is already over budget.

The fourth mistake is choosing on price alone. The cheapest proposal often has the thinnest scope, and the gap gets filled with change requests at premium rates. Compare total five-year cost and scope coverage, not the headline number.

How to Compare Vendors Side by Side

Build a simple scoring sheet before proposals arrive. Weight the criteria to match your priorities, then score each vendor on the same scale.

Criterion What to Check Weight
Relevant experience Live projects on your platform, industry, and size High
Named team CVs, allocation, replacement clause High
Scope clarity Exclusions list, change rates, acceptance criteria High
Data and testing Migration cycles, test ownership, cutover rehearsal Medium
Support model Hypercare length, escalation, knowledge transfer Medium
Total cost Five-year TCO including support and internal effort High
Contract terms Milestone payments, exit clause, IP ownership High

Score honestly. A vendor that wins on price but loses on scope clarity is not the cheaper option.

Conclusion

Hiring an ERP implementation company is a procurement decision, but it behaves like a risk management decision. The firms that deliver well are rarely the ones with the slickest pitch. They are the ones that answer uncomfortable questions with specifics, put named people and change rates in writing, and define acceptance before the project starts.

Ask all fifteen questions. Ask follow-ups when the answers get vague. Then check the references, read the exclusions list twice, and model the five-year cost before you sign anything. The hour you spend on due diligence is the cheapest hour of the entire project.

FAQ

How long should an ERP implementation take for a mid-sized company?

Most mid-market implementations run somewhere between six and eighteen months, depending on module count, customization, and data complexity. Be wary of timelines that look dramatically shorter than comparable projects, because compressed schedules usually push work into change requests later.

Should I choose a fixed-fee or time-and-materials contract?

Fixed-fee suits well-defined scope and gives budget certainty, but vendors price in risk and charge for changes. Time-and-materials offers flexibility but shifts cost risk to you. Many buyers use a hybrid: fixed fee for defined phases, time-and-materials for discovery and post-go-live support.

What is hypercare and how long should it last?

Hypercare is the intensive support period immediately after go-live, when users hit real problems and the vendor keeps a dedicated team close by. Four to six weeks is typical. Ask specifically whether it is on-site, how issues are prioritized, and when responsibility hands over to your internal team or a standard support desk.

Do I need to customize the ERP or change my processes?

Customization raises upgrade costs and slows future migrations, so the default should be process change first. Configure before you customize, and reserve code changes for genuine competitive differentiators. Ask the vendor to show you how each requirement is met through standard configuration before quoting custom work. (Ai chatbot security 2027 9 questions ask before buying)

How do I verify a vendor’s references are genuine?

Ask for references from the last two years with a similar scope, then contact them independently rather than through a single email introduction. Ask about budget performance, timeline slips, and how the vendor handled problems. A vendor confident in its delivery will not mind you choosing which reference to call.

What should the contract include beyond price and timeline?

Look for named key personnel with replacement approval, milestone-based payments tied to acceptance criteria, a defined change control process with rates, data protection and IP ownership terms, a warranty period after go-live, and an exit or transition clause covering handover if the relationship ends.

on this page