How to Run Discovery When the Buyer Already Picked a Vendor in Their Head

You can hear it in the first ninety seconds. Closed questions, brisk pace, "just want to confirm a few things before we finish evaluating." Sometimes they'll even say the competitor's name out loud, unprompted, warmly. This is the courtesy call — discovery being run as a formality because the buyer already has a favourite, and both of you privately know it. Most reps handle this one of two ways, and both are wrong. They either play along and lose politely, or they challenge the pick directly — "what makes you say that?" in a tone that means "you're wrong" — and watch the buyer defend their choice harder than before the call started.

Why the direct challenge backfires

Once someone has said a preference out loud, especially to a colleague or in an internal email thread, they've made a small public commitment. Challenging that commitment doesn't create an opening — it creates a reason to defend it, because backing down now costs the buyer something socially that it didn't cost them before. You're not arguing against a vendor. You're arguing against a decision they've already announced to people whose opinion they care about. That's a fight you can't win by being more convincing. You win it by changing what the decision is being evaluated against, not by attacking the answer they already gave.

The sequence

1. Name the situation, without judgment. "Sounds like you've already got a strong direction in mind." Said flatly, as an observation, not a challenge. This does two things: it removes the pretence that the call is neutral discovery, which the buyer already knows anyway, and it takes the defensiveness out of the room because you haven't disagreed with anything yet.

1. Get the criteria that produced the pick — not the reasons they like it. "What did you evaluate on to get there?" is a different question from "why do you like them?" The second invites a justification. The first gets you the actual list of factors, which is the thing you can actually work with.

1. Find the gap category. Almost every informal evaluation is built on three or four criteria — price, a headline feature, a relationship, sometimes just familiarity. It's very rarely built on implementation risk, edge-case handling eighteen months in, integration cost that doesn't show up on a list price, or what support looks like once the sales team has moved on. That gap is your opening, and it exists in nearly every decided-buyer call, because informal evaluations are short by nature.

1. Introduce the gap as protection, not correction. "So you don't get blindsided by this six months in" reframes the new criterion as something that serves their existing decision rather than something that undermines it. You're not saying they're wrong. You're saying there's a question worth answering before they're the one accountable for the answer.

1. Ask for a diagnostic, not a pitch. Don't ask for thirty minutes to present. Ask for the smallest concrete thing that would actually surface the gap — a reference call with someone who's eighteen months in, a side-by-side on the specific edge case, a scoped technical walk-through. A diagnostic is something the buyer can agree to without feeling like they've reopened the whole decision.

1. Let them re-rank it themselves. Don't ask for the business at the end of this. If the gap is real, the buyer will do the re-ranking privately, in their own time, without needing you to ask them to admit it out loud.

What it sounds like

Buyer: "Honestly, we've pretty much decided on [competitor]. This call is really just due diligence." Rep: "Fair enough — sounds like you've got a clear direction. Can I ask what you evaluated on to get there?" Buyer: "Mostly price, and they've got the reporting feature we need." Rep: "Makes sense. One thing worth checking before it's locked in — how did they handle the account that's three seats over? A lot of tools that price well at your size get expensive fast past that threshold. Worth a five-minute reference call with someone who's past it?"

Nothing in that exchange contradicts the buyer. It adds a criterion they hadn't priced into their own decision, framed as something that protects them, not something that challenges their judgment.

When to walk instead

This only works when there's a real gap and the buyer is even slightly persuadable. Some "decided" calls are genuinely just procurement-mandated box-ticking — three quotes required by policy, with zero intention of switching from the incumbent. You'll know the difference by whether the buyer can name anything, even hypothetically, that would change their mind. If they can't, stop trying to reopen a decision that was never actually open, thank them for their time, and leave something useful behind for the next cycle. Pushing past a genuinely closed door doesn't read as persistence. It reads as not listening, which is the one thing that guarantees you don't get invited back next time.

For the specific phrasing of step four, the 'We're Happy With Our Current Vendor' Response Guide has variants of the protective reframe that hold up across different objections in the same family, and the Discovery Call Objection-Prevention Checklist is useful for catching a decided buyer earlier in the call, before you've spent fifteen minutes running discovery on a decision that was made before you dialled in.

The skill here isn't winning the argument. It's not having one.