Customers say “Do you have references” for a reason. Here is what usually sits behind it, how to respond and what to avoid.
This is usually a reasonable request for proof, from someone close to a decision who wants cover if it goes wrong. Occasionally it is a polite delay. The honest approach is to say what you are able to share, not to invent or stretch examples. Ask what they want to confirm: results, service, reliability or similarity to their own situation.
Typical in: Software and SaaS, Professional services, Manufacturing and logistics
Pick the framework that fits the customer. The wording is an example direction, not a script: say it in your own words.
Ask what sits behind the objection, so you answer the real concern.
“Yes, that is a sensible thing to ask for. So I can offer the right kind of proof, what would you most like to confirm: how the service runs day to day, how we handle problems, or whether it fits a business like yours?”
Offer an example, a reference or a sample the customer can check. Never an invented figure.
“I can share what we are able to share. That may be a description of how a similar customer uses it, or a contact who has agreed to speak, if our rules allow. I will not give you a name without their consent. Which would help more?”
Shrink the decision to something low-risk that moves things forward.
“Another way to check us is a short trial of one piece of the work, so you see the real thing rather than rely on someone else’s word. Shall I outline what a small start would look like?”
After your response, ask:
Who else in your team needs to be comfortable with this, and what would they want to see?
Avoid: Our customers are happy, I can tell you that, so you don’t need to check.
It asks them to trust the very claim they want to verify. A request for proof answered with a promise sounds evasive.
Reading is not the same as saying it. Talk to an AI customer who raises this kind of objection and see in the report which sentence helped.
Practise this objectionThis is usually a reasonable request for proof, from someone close to a decision who wants cover if it goes wrong. Occasionally it is a polite delay. The honest approach is to say what you are able to share, not to invent or stretch examples. Ask what they want to confirm: results, service, reliability or similarity to their own situation.
Clarify before you answer: “Yes, that is a sensible thing to ask for. So I can offer the right kind of proof, what would you most like to confirm: how the service runs day to day, how we handle problems, or whether it fits a business like yours?” Offer proof: “I can share what we are able to share. That may be a description of how a similar customer uses it, or a contact who has agreed to speak, if our rules allow. I will not give you a name without their consent. Which would help more?” Propose a smaller step: “Another way to check us is a short trial of one piece of the work, so you see the real thing rather than rely on someone else’s word. Shall I outline what a small start would look like?”
Who else in your team needs to be comfortable with this, and what would they want to see?
Avoid “Our customers are happy, I can tell you that, so you don’t need to check.” It asks them to trust the very claim they want to verify. A request for proof answered with a promise sounds evasive.
Educational conversation training. It is not legal or financial advice and it promises no results. Always follow your company’s rules, the terms of the product and a customer’s clear no.