Tag: pipeline

Most discovery calls lose the deal before anyone mentions price. The rep arrives with a script, works through it dutifully, and finishes feeling like that went well, while the prospect is already half-switched-off and composing a polite “we’ll be in touch” email. The call was technically complete. It just wasn’t a conversation.

The checklist problem

The single most common failure is treating discovery like a form to fill in. Reps move from question to question without really processing what they’ve heard, because they’re already thinking about what comes next, and the prospect who came hoping to feel understood ends up feeling processed instead. The questions get answered, the boxes get ticked, and nothing of substance is learned by either side.

The fix is genuinely simple, if a little uncomfortable: ask a question, actually listen to the answer, then ask a follow-up based on what you just heard before moving on. It sounds obvious, but it’s rarer than it should be, and prospects notice immediately when it happens.

Pitching before you’ve earned it

A rep does their research, gets excited about the fit, and can barely contain the urge to show off what the product does. So before the prospect has finished articulating what they actually need, the rep is already talking about features. Engagement quietly evaporates.

A practical guardrail: commit to asking at least three open-ended questions before you mention a single product feature. Not because three is a magic number, but because it forces a pause long enough to actually learn something. If you catch yourself pivoting to pitch mode, stop and ask another question instead.

Asking things you should already know

Asking a prospect how many employees they have, or what tools they currently use, when that information is sitting on their website or LinkedIn, signals clearly that you didn’t prepare. Most buyers have done substantial research before agreeing to a discovery call at all, so arriving with questions about public information reads as lazy at best.

A twenty-minute look at LinkedIn, Companies House, Crunchbase, and any recent press releases changes the entire tone of the conversation. You can ask about things that actually matter rather than things that are already written down somewhere.

Not going deep enough when something interesting surfaces

The prospect mentions something significant, something that might be the real reason they’re looking for a solution, and the rep nods and moves on to the next prepared question. The seed of the real problem gets passed over in favour of completing the script.

When something interesting comes up, stay with it. “Tell me more about that” isn’t a sophisticated technique, but it works because it gives the prospect permission to keep talking. The causes, costs, and knock-on effects of a problem are almost always more revealing than the problem itself, and that’s where you find out whether you’re genuinely useful to them or not.

Ending without a real next step

Vague sign-offs are where qualified deals quietly go cold. “I’ll follow up with some information” isn’t a next step, it’s a postponement. A discovery call should end with a specific, calendar-confirmed action, whether that’s a demo, a proposal call, or a clear decision on whether to proceed at all. Without that, you’re both starting from scratch the next time you speak, assuming there is a next time.

Summarise what you heard, check your understanding is correct, and propose a concrete next step before the call ends. That summary also shows the prospect you were actually listening, which, given how infrequently it happens, tends to leave a surprisingly strong impression.

Frequently Asked Questions