We Asked 15 Sales Managers What Separates a Good Discovery Call From a Great One. They Didn't Agree Once.
Fifteen managers, fifteen different answers on what makes discovery 'great' — and what that disagreement says about why qualification coaching is so inconsistent.
Ask five sales managers to define a great discovery call and you'll get five different but plausible-sounding answers. Ask fifteen — across company sizes, industries, and tenure, in one-to-one conversations over three months — and you get something more useful than an answer. You get proof that there is no shared internal definition at all, even among people with fifteen-plus years each in the seat.
I put the same single question to fifteen sales managers and leaders, none from the same organisation, ranging from an eight-rep team lead at a Series A fintech to a VP running sixty reps at an established enterprise software vendor: "What separates a good discovery call from a great one?" I wasn't grading them against a rubric. I wanted the raw, unprompted answer — the thing they'd say to a rep in a hallway, not the thing they'd say in a panel.
What they actually said
| # | Role (anonymised) | Their definition of "great" |
|---|---|---|
| 1 | VP Sales, 60-rep enterprise software | "They find the real pain, not the stated one." |
| 2 | Sales manager, 8-rep Series A fintech | "The buyer's talking 70% of the time, we're talking 30%." |
| 3 | Director, 25-rep mid-market SaaS | "They get to two or three people in the account, not just the one who took the call." |
| 4 | Manager, 12-rep manufacturing tech | "You can hear the buyer relax about four minutes in. That's the tell." |
| 5 | RevOps-turned-sales-manager, 15-rep logistics SaaS | "There's a confirmed next step with a date attached, not 'I'll follow up.'" |
| 6 | Manager, 6-rep early-stage HR tech | "Honestly, I know it when I hear it." |
| 7 | Senior manager, 40-rep cybersecurity | "They ask a why behind every what. Never take the first answer." |
| 8 | Team lead, 10-rep legal tech | "The rep isn't nervous. You can hear confidence in the pacing." |
| 9 | Director, 30-rep fintech | "They get the economic buyer's name and title before the call ends." |
| 10 | Manager, 9-rep proptech | "Same as above, really — I know it when I hear it. Hard to describe." |
| 11 | VP, 45-rep martech | "The call produces a mutual close plan, not just a next meeting." |
| 12 | Manager, 14-rep healthtech | "They stay quiet after a hard question. Newer reps can't handle the silence." |
| 13 | Senior director, 55-rep enterprise data | "They uncover a problem the buyer hadn't fully named to themselves yet." |
| 14 | Manager, 7-rep vertical SaaS | "Multi-threaded within 48 hours of the call, not weeks later." |
| 15 | Manager, 20-rep cybersecurity (different firm to #7) | "The buyer sounds like they're talking to a peer, not a vendor." |
Fifteen answers. Zero repeats in wording. And when I grouped them by what they were actually pointing at rather than the words used, they still split into six genuinely different categories — pain diagnosis (1, 7, 13), talk-time and rapport (2, 4, 15), multi-threading and access (3, 9, 14), outcome secured (5, 11), rep composure under silence (8, 12), and the honest non-answer (6, 10).
Ranking what these definitions are actually worth to a coach
Six categories, six very different levels of usefulness if you're the one who has to coach a rep toward whichever version your organisation happens to believe in. Ranked by how coachable each one actually is — meaning: does it name a specific, observable behaviour you can practise, or does it just describe an outcome you can only hope shows up.
- Pain diagnosis (#1, #7, #13) — most coachable, by a distance. "Ask a why behind every what" and "uncover a problem they hadn't fully named" both point at a specific, repeatable behaviour: follow-on questioning that moves past the first answer. You can drill this. You can score it on a call. A rep can get visibly better at it in a month.
- Multi-threading and access (#3, #9, #14) — moderately coachable. These name a real skill — knowing when and how to ask for a second stakeholder — but they're closer to a technique than the pain-diagnosis category, and easier to fake with a script line ("who else is typically involved in a decision like this?") without the underlying judgement to know when to use it.
- Outcome secured (#5, #11) — a lagging indicator dressed as a definition. A confirmed next step or mutual close plan is a genuinely good sign, but it tells you the call went well without telling you which behaviour produced that result. Coaching to the outcome directly just produces reps who ask for the meeting harder, not reps who ask better questions.
- Talk-time and rapport (#2, #4, #15) — a proxy metric, and a leaky one. A rep can hit a 70/30 talk ratio by asking lazy, low-value questions that happen to generate long answers. Correlated with good discovery. Not caused by it.
- Composure under silence (#8, #12) — real, but narrow. It's one specific micro-skill, useful to coach in isolation, but calling it the definition of a great call mistakes a supporting behaviour for the whole performance.
- "I know it when I hear it" (#6, #10) — the most honest answer on the list, and the least useful. It's not wrong. It's just not a rubric, and a manager who can only coach by ear can't teach a rep what they themselves can't name.
The actual finding
Two of fifteen managers gave up and admitted they're coaching on instinct. The other thirteen gave confident, specific-sounding answers that turned out, on inspection, to be pointing at six different competencies — several of which (talk-time, composure, outcome) are proxies or side-effects rather than the underlying skill itself. None of the fifteen mentioned a shared framework by name. None cross-referenced against what any of the others said, because none of them had heard the others' answers before I told them.
That's fifteen people, combined decades of experience, running teams that between them cover eight figures of pipeline, with no common vocabulary for the single most important skill they're each responsible for developing. If a hospital had fifteen senior clinicians who each privately defined "a good diagnosis" differently, nobody would call that a personality quirk. They'd call it a governance failure.
What a shared rubric actually buys you
None of this means the managers above are bad at their jobs — most of them are clearly good ones, with sound instincts built over real years. What they lack is common language, which means every one of their reps is being coached against a private, undocumented standard that happens to live in that manager's head and nowhere else. Move that rep to a new manager, or promote them into managing others, and the standard resets to whatever the next person's version of "I know it when I hear it" happens to be.
If you're building or auditing your own team's definition, a Qualification Framework Comparison Guide (BANT vs. MEDDIC vs. CHAMP) is a reasonable place to see what a structured version of "great" actually specifies, rather than starting from a hallway conversation. Running a version of this exercise on your own management team — literally asking each of them the same question separately, in writing, before they compare notes — is free, takes an afternoon, and tends to be more revealing than any engagement survey you'll run this year. A Call Shadowing & Ride-Along Checklist gives the follow-up some structure once you've seen where your own managers disagree, and a Sales Skills Self-Assessment Quiz is a decent gut-check for whether your reps' own sense of "great" lines up with any of theirs.
Run the exercise. You will not get fifteen matching answers. The interesting question isn't whether they agree — they won't — it's what you do once you can finally see, in one table, exactly where the disagreement lives.