1of 3
Make the discovery call valuable to the buyer
Bring an observation to the call worth discussing, ask questions that help the buyer think, and reflect what you hear before connecting it to your product.
Adapted by the EWOR Team from Sean Gallagher’s article (opens in a new tab)2 min read
Make it a conversation worth having
A discovery call can quickly turn into an interrogation or a product monologue. Neither gives the buyer much reason to engage. Sean Gallagher, a technology executive with 30 years of experience leading businesses across EMEA, advocates treating discovery as a value exchange: bring something useful to discuss, listen carefully and find out whether there is a commercial problem you can help solve.
Bring something the buyer can use
Prepare one relevant observation about the buyer's workflow or a challenge they may face. It could come from your own customer conversations, provided you have permission to share the information, or from a source you can substantiate.
Present it as a possibility, not a diagnosis of the buyer's business. Ask whether it reflects their experience and invite them to correct you.
If the observation doesn't fit, follow their correction rather than defending the insight you prepared. The goal is to understand their situation, not prove you were right.
Sequence questions, then listen
Start with a question the buyer can answer from their day-to-day work. Follow their response towards the consequences: which teams are affected, what happens when the process fails, and who decides whether it's worth changing?
More demanding questions are easier to answer once you've shown that you understand the initial response.
Pause to summarise what you've heard in plain language and check that you've understood correctly. Distinguish the buyer's stated concern from your interpretation of its cause. Let their answer shape your next question instead of simply waiting for your turn to pitch. Not every answer needs a feature attached to it.
Connect the product when the context is clear
Only after the context is clear should you explain which part of your offering might help. Keep the connection specific: identify the workflow discussed, the proposed change and the assumption that remains untested. Ask whether examining that assumption would be useful to the buyer. If not, the call has still produced valuable evidence about fit.
Finish with a next question or test that both sides understand. Don't manufacture urgency or steer the buyer towards an answer you've already decided on.


No comments yet.
Be the first to comment on this signal.