ERP Reference Check Questions You Must Ask Before Buying

The reference call is your last truth test

A reference call is your final chance to hear the unvarnished story before signing. Vendors will connect you only to satisfied customers, and those customers have agreed to take the call — but that does not mean they will recite the sales script. Your job is to ask the questions that reveal the gaps between the demo and the lived experience. Reference calls are the cheapest insurance in the entire selection, because the cost of hearing the truth is one phone call and the cost of missing it is the whole implementation, paid for in budget, schedule, and credibility with your team.

Open with the honest question

Start with: "If you were buying again, what would you do differently?" The pause before the answer tells you more than the answer itself. A confident reference answers quickly and specifically; a hesitant one reveals a wound — a module that never worked, a cost that blew up, a go-live that slipped by months. Let the silence sit. The most valuable reference insights are the ones the customer was not explicitly coached to share, and the open-ended question is what gives them permission to be honest without feeling disloyal to the vendor who introduced you.

Drill into timeline and budget

The two numbers that matter most are time and money, and both are where implementations diverge from plan. Ask directly about slippage and overruns; a reference who says "on time and on budget" with no qualification is either unusually lucky or lightly loaded, so probe what they scoped out of the first phase. The pattern across many references is more informative than any single glowing quote, because one happy customer can be an outlier, but five references with the same caveat is a trend you cannot ignore in good conscience.

• Did you go live on time? If not, what specifically caused the delay?
• Final cost versus initial quote — what changed, and by how much?
• How many of your original must-haves actually made it to go-live?

Ask about the support reality

Demos show features; references show what happens at 2 a.m. when something breaks. Support quality is the dimension buyers most regret underestimating, because a slow or costly support model turns every small issue into a project. Ask for the real response time on a severe issue, whether a third-party partner was needed, and whether they would recommend the vendor to a competitor — the last question is the cleanest yes-or-no you will get, and a hedged answer there is worth more than three enthusiastic sentences about the user interface.

• What is your real response time for a severe, system-down issue?
• Did you need a third-party implementation partner? Which one, and why?
• Would you recommend this vendor to a competitor? Why or why not?

Read between the lines

Listen for hedging: "overall it's fine" often means "specific parts are not." A reference who praises the sales experience but goes quiet on support is telling you where the weakness is. Note the ratio of enthusiasm to qualification; a credible reference is enthusiastic about specifics, not the brand, and the specifics are what you will be living with long after the brand's marketing has faded from memory.

How many references and which ones

Talk to at least two references per finalist, and insist on at least one in your industry and size, because a system that fits a $2B manufacturer may be a poor match for a $20M distributor. A vendor unable to provide an in-industry reference is a red flag worth more than any feature score. If you can, ask to speak with a customer who went live roughly when you plan to, so the lessons are fresh and relevant to your scale rather than polished by years of distance from the hard early days.

What to do if a reference hesitates

If every reference is suspiciously perfect, that is its own signal — vendors curate, but real customers have real scars, and a wall of flawless praise suggests the honest ones were filtered out. Press gently for the hardest moment of the project; a reference who can describe a genuine difficulty and how it was resolved is more reassuring than one who claims a flawless journey, because difficulty handled well is what you are actually buying when you choose a vendor for the long term.

Feed the answers back into your scorecard

Record each reference answer against the same criteria you used in the demo scoring — implementation risk, support, and fit. A vendor that dazzled in the demo but produces references full of caveats should drop in the ranking, and the documented call notes give your steering committee the evidence to act on that drop rather than ignore it, which is how a disciplined selection protects itself from the pull of a impressive presentation.