Teardown: The 'Great' Discovery Call That Was Actually a Vendor-Confirmation Call in Disguise
Line by line, a call that scored well on every discovery checklist — and still lost, because the buyer was never actually discovering anything.
A manager I know grades every recorded discovery call against a sixteen-point scorecard: rapport, pain, budget, authority, timeline, next steps. Last month a call came through that hit fourteen of sixteen. She flagged it as a training exemplar and queued it for the next call-review session. Three weeks later the deal died in procurement, to an incumbent nobody on the call had ever mentioned. The scorecard hadn't missed a topic. It had missed a tense.
What follows is a composite — stitched together from patterns that show up often enough across call libraries to count as a category, not a single unlucky rep. The company is fictional. The failure mode isn't.
The call that graded perfectly
Thirty-four minutes. A supply-chain visibility vendor, call them Bramwell Analytics, selling into a mid-market food manufacturer, call them Halden Foods — 340 staff, three disconnected systems across finance, ops and the warehouse floor. The buyer is Priya, VP of Supply Chain. The rep runs a clean, structured call: rapport, pain, budget, timeline, in that order, each one dutifully ticked.
The transcript
Rapport, 02:10 — Priya: "I looked at your case study with the beverage client — that's basically our exact problem." Rep: "Good, so this has been on your radar a while?" Priya: "Definitely."
Pain, 09:40 — Rep: "What's the actual cost of the visibility gap right now?" Priya: "Honestly it's mostly a reporting headache — when we roll this out we'll finally get one number for on-time-in-full instead of three conflicting ones."
Budget, 18:05 — Rep: "Do you have budget allocated for this?" Priya: "It's already in next year's ops-systems line, yeah."
Timeline, 26:50 — Rep: "If we moved forward, what's realistic for a start date?" Priya: "First week of the new fiscal year — we've already blocked out the change-management comms internally for it."
Every box, ticked cleanly. The manager's 14/16 wasn't wrong on the checklist. It was wrong on what the checklist was capable of seeing.
What each box actually proved
| Checklist box | What was said | What the manager assumed it proved | What it actually proved |
|---|---|---|---|
| Rapport | Priya had already read a specific case study before being offered one | Genuine interest, built organically | She'd already done vendor research — this is evaluation-stage behaviour, not first-contact curiosity |
| Pain | "when we roll this out," not "if" | Pain confirmed, buyer bought into the future state | Future tense used as certainty — a decision may already exist, not be forming on this call |
| Budget | "already in next year's line" | Budget qualified | Budget existed before this call — someone already built a business case, and the rep never found out whose vendor it was built around |
| Timeline | "we've already blocked out change-management comms" | Timeline aligned | The org has already committed to a change; the open question is which vendor, and the rep never asked |
The tell a checklist can't catch: tense
Genuine discovery lives in conditional, exploratory language — "if," "could," "we're trying to figure out," "what would that even look like." A pre-formed decision lives in confirmatory language — "when," "already," "we've blocked out," "that's basically our exact problem" said about a case study she went and found herself. Priya used confirmatory language in all four boxes. Not once did she use a conditional. The rep asked good questions, in the right order, and recorded accurate answers to all of them — and still missed that he was several steps behind a process that had already been decided, quite possibly around a different vendor, with this call serving only to complete a comparison for procurement.
The two questions that would have caught it
- "Who else is in this conversation with you — vendors, or just people internally?" Asked early, directly, before rapport makes you reluctant to break the mood.
- "What happens if you do nothing at all this year?" A genuinely open pain surfaces something specific and costly on the spot. A closed, pre-decided process produces a vague, rehearsed non-answer, because the real cost-of-inaction maths was already done for a different conversation months ago.
Run the Champion Identification Checklist here — not to find a champion for your deal, but to establish plainly whether the person opposite you is championing a decision that already has a direction.
What to coach instead of scoring topics
Tell managers reviewing calls to stop scoring whether a topic got raised and start scoring whether the buyer's language in each of those four boxes was exploratory or confirmatory. Add a fifth column to the Discovery Call Scorecard for Managers — tense — and mark every future-tense, presumptive sentence the buyer uses. One or two on a call is normal enthusiasm. Six or seven, like this one, isn't discovery. It's a buyer being polite while she finishes her paperwork.
The rep here wasn't bad at his job. He asked structured questions in a sensible order and wrote down honest answers. What he'd never been taught to hear is that a buyer can answer every discovery question truthfully and still be several steps ahead of the call, filling in boxes for a decision that has nothing left to decide.