Independent ERP and system selection
What questions should you ask ERP vendors before you sign?
Before you sign, ask the vendor who will actually do the work, what the quote leaves out, how many hours a week your own team must give, who owns data migration, how change orders are priced, and how you leave if it goes badly. Get every answer in writing. The checklist below groups the questions so you can print it and take it into the room.
An ERP contract is one of the largest technology commitments a company makes. It is also one where the person selling and the person delivering are rarely the same. These questions exist to close that gap. They are part of a larger process we describe on our independent ERP selection page and in how to choose an ERP.
Why do the questions matter more than the demo?
A demo shows what the software can do on its best day. The contract decides what you get on an ordinary day, after the sales team has moved on. Most expensive surprises in ERP projects were visible before signing, in what the quote did not say. Questions turn silence into a written answer.
Vendor-led selection has a built-in conflict. The vendor's team works for the vendor. That does not make them dishonest. It means nobody in the vendor's room is paid to protect you from the scope you did not know to ask about. You have to ask, or hire someone to ask.
Who on your side does the work, and can I meet them?
This is the first question and the most revealing. Ask for the names, roles and expected hours of the project manager, the lead consultant and the technical lead. Ask to meet them before you sign.
- Will the people I meet in the sales process be the people on my project?
- What happens if a named consultant leaves or is reassigned mid-project?
- Are any parts of the work done by subcontractors or offshore teams, and can I speak to them?
- Can I approve a replacement for any key role?
If the answer is "we staff once the contract is signed," treat that as a pricing risk. You are agreeing to a price for people you have not met.
What is not in this quote?
Ask this exact question, then ask for the answer as a written list of exclusions. A quote is a statement of what is included. The exclusions are where the second invoice lives. Our companion article on what an ERP really costs beyond the quote lists the usual suspects: data cleanup, integrations, training, reporting, a second phase and support.
- Which modules, users, entities and locations does this price cover?
- What is priced per user, per module, per transaction or per environment?
- Are test and training environments included?
- What happens to the price if we add a location or a legal entity next year?
How many hours a week do you need from my team?
Every ERP project runs on your people's time. Ask for a weekly hours estimate by role: finance, operations, sales, warehouse, IT. Then ask what the vendor has seen go wrong when customers cannot supply those hours.
The honest answer is often larger than the owner hopes. Your best people are also the ones running the business today. Decide in advance who covers their day jobs, because a project that depends on "we will find the time" tends to slip on exactly the weeks that matter.
Which references should I ask for?
Ask for references that match your size, industry and complexity, and ask for at least one that is more than a year past go-live. Go-live references tell you the project finished. Year-later references tell you whether the system works.
- Which of your customers have a similar number of locations, entities or order channels?
- Can I speak to one that had a difficult project, and what changed?
- Can I speak to one that left you, if any have?
When you call, ask about the project, not the product: what slipped, what cost more than planned, and what they would do differently.
Who owns data migration?
Data migration is where many projects lose weeks. Ask who cleans the data, who maps it, who loads it, who validates it and how many trial loads are included. "Customer is responsible for data" is a common line in a statement of work. It may be fair, but you need to know how big that job is before you accept it.
- How many test migrations are in scope before the final cutover?
- What counts as acceptable data quality, and who signs off?
- How much history comes across, and what stays in the old system?
Not sure how your current systems would hold up in a selection? Start with a free look at where they stand.
Take the Systems CheckHow are change orders handled?
Change orders are normal. What matters is the rules. Ask for the hourly rates now, the approval process, and how long the vendor has to price a change. Ask what counts as a change versus a defect versus a misunderstanding of the original scope.
The cleanest protection is a scope written in your language, not the vendor's. We saw this on a project for a multi-brand auto parts distributor owned by a private equity firm. The team wrote 240 requirements and ran a gap analysis of the storefront agency's proposal that forced a re-scope and a rewritten statement of work before signature. The requirements gave the company something concrete to point to when a line item did not match what the business needed.
What are the exit terms?
Nobody likes asking how to leave while they are still deciding to buy. Ask anyway. The exit terms tell you how the vendor behaves when the relationship is not going well.
- If we end the contract, in what format do we get our data back, and at what cost?
- What is the minimum term, and what are the renewal and price-increase terms?
- Can we stop after a phase if the first phase fails its acceptance tests?
- What happens to our data and access if the vendor is acquired or changes the product?
- Are there termination fees, and how are they calculated?
What should be in an ERP RFP?
An ERP RFP is the written request you send to shortlisted vendors so every answer can be compared. It should hold your company profile (size, entities, locations, industry), the business requirements ranked as must have, should have and nice to have, the scenarios you want shown in a scripted demo, and the systems the ERP must connect to. Add the questions on this page, a request for named team members and hours by role, and a pricing format that makes every vendor list exclusions.
The requirements are the heart of it, so write them first. Our ERP requirements checklist shows what to capture. Keep the document short enough that vendors answer the questions instead of pasting in marketing. Send the same RFP to everyone and score the answers on one sheet.
Which contract terms matter: renewal caps, minimum users and integration fees?
Three terms cause most of the later surprises. Renewal caps limit how much the subscription can rise each year, and set the notice you must give to leave or renegotiate. Without a cap, the second term can cost much more than the first. Minimum users and minimum spend decide whether you pay for a floor of users or modules even if you use fewer, and whether you can reduce them at renewal. Integration fees decide whether connectors to your other systems are included, priced separately or custom work, and who maintains them when either side updates.
Also read the data-return terms, the change-order rates and what happens if the vendor is acquired. Put every answer in the statement of work, and have counsel review it. The exit questions earlier on this page cover the rest.
The printable checklist
Print this page or copy the table. Mark each question answered, partly answered or avoided, and keep the written answers with the contract.
| Group | Question | Answer in writing? |
|---|---|---|
| People | Who does the work, what are their roles and hours, and can I meet them? | ☐ |
| People | What happens if a named consultant leaves, and do I approve replacements? | ☐ |
| Price | What is not in this quote, as a written list of exclusions? | ☐ |
| Price | What is priced per user, module, entity or location, and what happens when we grow? | ☐ |
| Your team | How many hours a week do you need from each of my departments? | ☐ |
| Proof | References from companies our size, including one more than a year live? | ☐ |
| Data | Who owns cleanup, mapping, loading and validation, and how many test loads are included? | ☐ |
| Change | What are the change-order rates, approval steps and pricing turnaround? | ☐ |
| Exit | How do we get our data back, what is the minimum term, and can we stop after a phase? | ☐ |
What should you do with the answers?
Compare them across vendors, not in isolation. A vendor who says "it depends" on four of nine questions has told you something. Put the important answers into the statement of work. A promise made in a meeting is only as good as the memory of the person who made it.
The questions are one step in a longer process. If you are earlier than this, read our step-by-step guide on how to choose an ERP, or see how we approach independent ERP and system selection.
Common questions
When in the process should you ask these questions?
Ask them before you pick a finalist, and again in writing before you sign. A vendor who answers vaguely in a sales meeting will answer the same way in a dispute, so get the answers into the contract or an attached document.
Who should be in the room when you ask?
The executive who owns the outcome, usually the CEO or CFO, plus the person who will run the system day to day. Questions about cost and exit belong to the owner. Questions about hours and data belong to the people who will carry the load.
What is the biggest red flag in a vendor's answers?
Vagueness about who does the work. If the vendor cannot name the people, their roles and their hours, you are buying the sales team and getting someone else.
Do you need an independent advisor to ask these questions?
You can ask them yourself. An advisor helps because the vendor's own team works for the vendor, and someone on your side of the table has seen what a quote leaves out.
Not sure where to start?
Take a free three-minute score. If a conversation makes sense, it will offer one.