How to respond to “That sounds too good to be true”
Customers say “That sounds too good to be true” for a reason. Here is what usually sits behind it, how to respond and what to avoid.
What is really behind it
Experience has taught the customer that big benefits usually come with a catch, so they are protecting themselves. Often they have noticed the strongest claim in your pitch and doubt it. The remedy is rarely more enthusiasm: it is naming what the offer does not do, and showing where limits and conditions sit.
Typical in: Software and SaaS, Insurance and finance, Real estate, Telecom and energy, Professional services, Retail and e-commerce, Manufacturing and logistics, Contact centre and customer service
How to respond
Pick the framework that fits the customer. The wording is an example direction, not a script: say it in your own words.
Acknowledge, then ask
Show you heard it, then ask an open question before you respond.
“You are right to be careful. Let me be clear about what it does and what it does not. It will not fix everything, and some things depend on how you use it. Which part sounded most doubtful to you?” Then answer that part plainly.
Offer proof
Offer an example, a reference or a sample the customer can check. Never an invented figure.
“Instead of arguing, let me show you how it works in practice, including the limits. I can walk you through a real example, with the conditions written down, so you can check whether it fits your case. Would that be useful?”
Reframe around the outcome
Move from the objection to the result the customer said they want.
“I would be sceptical too if I only heard the headline. The useful question is which conditions apply to you. If I give you the full picture, including where it is weaker, would you be willing to judge it on that?”
The follow-up question
After your response, ask:
Which of the things I said would you most like me to prove or put in writing?
What not to say
Avoid: No, it’s absolutely real, there’s no catch at all.
A blanket denial sounds exactly like what a seller who is hiding something would say. Naming the limits is more convincing than insisting there are none.
Practise it out loud
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.
What does “That sounds too good to be true” really mean?
Experience has taught the customer that big benefits usually come with a catch, so they are protecting themselves. Often they have noticed the strongest claim in your pitch and doubt it. The remedy is rarely more enthusiasm: it is naming what the offer does not do, and showing where limits and conditions sit.
How do you respond to “That sounds too good to be true”?
Acknowledge, then ask: “You are right to be careful. Let me be clear about what it does and what it does not. It will not fix everything, and some things depend on how you use it. Which part sounded most doubtful to you?” Then answer that part plainly. Offer proof: “Instead of arguing, let me show you how it works in practice, including the limits. I can walk you through a real example, with the conditions written down, so you can check whether it fits your case. Would that be useful?” Reframe around the outcome: “I would be sceptical too if I only heard the headline. The useful question is which conditions apply to you. If I give you the full picture, including where it is weaker, would you be willing to judge it on that?”
What should you ask after “That sounds too good to be true”?
Which of the things I said would you most like me to prove or put in writing?
What should you not say when a customer says “That sounds too good to be true”?
Avoid “No, it’s absolutely real, there’s no catch at all.” A blanket denial sounds exactly like what a seller who is hiding something would say. Naming the limits is more convincing than insisting there are none.
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.