You are on a reference call and your existing customer starts telling the prospect the implementation was painful. What do you do, in the call and afterwards?

Do not interrupt

The instinct is to step in — to add context, to clarify that the delay was caused by their own data migration, to redirect towards the outcome. Every version of that instinct makes things worse, and it is worth being clear about why, because in the moment the intervention feels like helpfulness.

The prospect is on this call precisely because you are not controlling it. Its entire value is that a peer is speaking without a vendor filter. The moment you filter it, you have converted an independent reference into a managed one, and the prospect will discount everything said afterwards including the positive material. Worse, you have shown them how you behave when something inconvenient is said in front of a customer, which they will reasonably assume is how you will behave with them.

So you let your customer finish. You take notes. If the prospect looks at you, you acknowledge rather than rebut: "That is fair, and I would rather he told you than not." One sentence, then quiet. The reference call is not the venue for the defence.

Get the specifics while they are being offered

The one useful thing you can do in the call is make the complaint precise, and you can do that with genuine curiosity rather than with a counter-argument. Ask what the hardest part was, when it became apparent, and what he would want a company in the prospect's position to do differently. Those questions serve the prospect, which is the point, and they also surface the information you need.

They also frequently transform the call. A vague complaint about a painful implementation is damaging in a way a specific one is not. "The data migration took eleven weeks because our source system was undocumented and we underestimated it" is a story about a knowable risk with a knowable mitigation, and a prospect can act on it. Some references go from a liability to the most persuasive part of an evaluation in the space of five minutes for exactly this reason, because a customer who criticises you and is still a customer is more credible than one who does not.

What you must not do is lead the witness. Asking questions whose answers exonerate you is transparent, and both people on the call will see it.

Work out which of these it is

Afterwards, before you respond to anybody, separate the categories, because the honest follow-up depends entirely on which one applies.

What the complaint really is	How you would know	What the prospect needs to hear
A product limitation, since fixed	You can point at the release that changed it	The specific change, when it shipped, and how they can verify it
A product limitation, still present	It is on the roadmap or nowhere	That it exists, and what it will mean for them concretely
A delivery or resourcing failure	The account history explains it, not the product	What changed in how the work is staffed and run, without blaming a colleague publicly
Expectations set in the sale that delivery could not meet	The proposal says one thing, the outcome another	An unusually careful scoping conversation for their own deal
Their own organisation's contribution	Their dependencies slipped, and he half knows it	Nothing from you — let it be his account, and design their plan so the same dependency is visible

The fourth row is the uncomfortable one and the one interviewers are frequently probing for. If a customer was sold an outcome nobody could deliver, the reference call is telling you about your own commercial behaviour, and the useful response is to change how the deal in front of you is scoped rather than to improve how the reference is managed.

The last row needs care. It is often true, and saying it to the prospect sounds like blaming a customer, which lands badly whether or not it is accurate. The way it can be used legitimately is structural: build the customer-side dependencies into your proposal as named items with owners and dates, so the prospect sees the risk being managed rather than hearing it attributed.

The follow-up with the prospect

Same day, in writing, short. Thank them, restate the specific concern in their reference's own words rather than a softened version, say precisely what has changed since with something checkable attached, and offer whatever verification you can — another reference at a similar stage, a conversation with the delivery lead who would run their programme, a look at the actual implementation plan for a comparable customer.

Two things not to do. Do not offer a second reference to replace the first, because it reads as looking for a better answer; offer one to add a data point at a different stage or scale. And do not claim an improvement you cannot evidence. "We have improved our onboarding" is worth nothing. "The step that took him eleven weeks is now a migration tool with a fixed-price assessment, and here is the plan we ran with the last three customers" is worth something, and only one of those sentences can be checked.

The call was not the problem

The part that separates a senior answer is recognising that the sales incident is secondary. You have a customer, presumably paying and possibly renewing, who is unhappy enough to say so to a stranger. That is the finding.

So the account conversation happens next, and its opening cannot be about the reference call. If your first contact after he criticised you is a request to be less critical, you have confirmed that his experience matters to you only as it affects your pipeline, and you will lose both the advocacy and eventually the account. Go and ask what is still broken, take something away, fix it, and come back. A reference who has seen a complaint acted on becomes a strong advocate, and there is no faster route to one.

Then the internal question, which is how he ended up on the call. Reference programmes usually source names from the account team or from a customer-success list, and both can be out of date by a quarter. Somebody either did not check recent sentiment or checked with the wrong person. That is a fixable process failure — a quick pre-call conversation with the reference about what they intend to say, which is not coaching but courtesy, and which surfaces exactly this before a prospect hears it.

Finally, the complaint belongs where delivery and product can see it. A reference call is one of the few places you hear an unmediated account of what your implementation actually feels like, and if that only ever circulates as a note about a deal at risk, the organisation learns nothing from having heard it.

Let the reference finish, make the complaint specific rather than vague, and remember that the real problem is not the deal in front of you but the customer who was unhappy enough to say it. Fix that, and the reference programme repairs itself.