The situation
The skeptical buyer is not hostile. They took the meeting, they are listening, and they will answer your questions. What they will not do is take your word for anything. Every claim gets a follow-up question. Every number gets a "compared to what." Every "our customers see" gets met with a flat "which customers, and how do you measure that."
This is a different problem than an objection. An objection is a specific reason not to move forward, budget, timing, an existing vendor, that you can address and resolve. Skepticism is a standing posture toward everything you say, usually built from a past vendor who overpromised and underdelivered. The buyer has learned that confident claims from a salesperson are a weak signal, so they discount them by default and wait to see if you can back them up. Reps who have not run into this before mistake the questioning for resistance to the idea itself, when it is really a demand for evidence before the idea gets taken seriously.
Why reps lose here
Answering skepticism with more enthusiasm. When a buyer pushes back on a claim, the instinctive response is to restate it more emphatically, "no really, this genuinely does work that well." Emphasis is not evidence. To a buyer who already discounts confident claims, a more confident version of the same unsupported claim reads as more of the thing they are skeptical of, not less.
Getting defensive instead of curious about the skepticism. A rep who treats "how do you know that" as an attack tends to either over-explain or shut down. Both signal that the question landed somewhere uncomfortable. A buyer watching for signs that a vendor cannot back up its claims reads defensiveness as confirmation.
Not asking what burned them before. Skepticism this specific usually has an origin, a past tool that promised results and did not deliver, a vendor who buried the real limitations until after the contract was signed. A rep who never asks about that history keeps re-triggering the same wound with every claim, without ever finding out what "proof" would actually mean to this particular buyer.
What the buyer is actually thinking
They are pattern-matching you against someone who burned them. Somewhere in this buyer's history is a purchase that did not hold up. They are not evaluating your product in isolation, they are checking whether you sound like that previous vendor did before things went wrong. The tell they are watching for is a claim with no evidence attached.
They want to be shown, not told. A skeptical buyer usually still wants the outcome you are describing to be real. What they are asking for is a way to verify it before they commit, a reference, a specific number with its methodology, a trial with a defined success measure, rather than a story about other customers.
They are testing whether you can handle being doubted. How a rep responds to pushback tells a skeptical buyer more than the answer itself. A rep who stays calm, specific, and willing to name limitations reads as someone who is not hiding anything. A rep who gets rattled or repeats the same pitch louder reads as someone who has not been tested this hard before, which is itself a bad sign.
The dialogue
The rep sells a workflow automation platform for customer support teams. Derek is the Director of Customer Support at Torchwood Apparel, an online retailer that switched away from an AI ticketing tool eighteen months ago after it under-delivered on its promised deflection rate.
Weak handling:
Derek: You're telling me this cuts resolution time by forty percent. I've heard a number like that before and it didn't hold up.
Rep: I understand the concern, but our platform is genuinely different, we've built it specifically to avoid the issues other tools have. Customers really do see results like that.
Derek: Which customers. What were they measuring.
Rep: We have a lot of happy customers across retail and e-commerce, I can send you some case studies.
Derek: Send them over. I'll take a look when I get a chance.
The rep answered a specific, sourced skepticism with a general reassurance, "genuinely different," "results like that," neither of which is a fact Derek can check. Asked directly which customers and what they measured, the rep retreated to "I can send you case studies" instead of answering in the room. Derek's closing line is the sound of a meeting ending without anything actually being resolved.
Strong handling:
Derek: You're telling me this cuts resolution time by forty percent. I've heard a number like that before and it didn't hold up.
Rep: That's fair, and I'd rather you doubt it than take my word for it. Can I ask what happened with the last tool, what the gap was between what you were told and what you actually saw?
Derek: They promised a deflection rate on tickets and it never got close. Turned out their number came from a pilot with a much simpler ticket mix than ours.
Rep: That's a useful detail, thank you. Our forty percent is a median across support teams handling apparel returns and sizing questions specifically, not a blended number across every industry we serve, and it's measured on resolution time, not deflection, so it's a different claim than what you were burned by. I'd rather show you than argue the number: could we run it against thirty days of your actual tickets in a limited pilot with a defined measure you pick, before any commitment?
Derek: What would you need from us to set that up?
Rep: A ticket export and one person on your team to sign off on the success measure before we start, so there's no argument afterward about whether it worked.
The rep did not fight the skepticism, it invited it, and asked what specifically went wrong last time instead of assuming the objection was about the number itself. That question surfaced the real gap, a mismatched ticket mix, which let the rep draw a precise distinction between this claim and the one that failed before, instead of a blanket "we're different." Offering a pilot measured against a standard Derek chooses himself, agreed before the pilot starts, turns the claim from something to be believed into something that will simply be checked. Derek's final question is engagement with a process, not a promise.
How to run this live
Set up a discovery or demo call against a skeptical buyer persona and treat every pushback as a request for evidence, not a challenge to overcome with tone. Goals for the practice run:
- When a claim gets questioned, resist the instinct to restate it more emphatically. Answer with a specific source, a methodology, or an offer to verify.
- Ask what happened with a previous vendor before defending your own claim. The real objection is usually buried in that history, not in the number itself.
- Stay specific under pressure. A buyer who is testing you will keep pushing past the first answer, and vague language gets easier to spot the second and third time.
- Offer a way to verify instead of a reason to believe. A pilot with a measure the buyer chooses is worth more than any case study you can send afterward.
Run it once against a buyer who softens once you name the right proof, and once against one who keeps pushing no matter what you offer. Knowing the difference between skepticism you can resolve in the room and skepticism that only a real pilot will settle is what this drill is for.
