Illustrative examples are fictional.
Follow the problem before the demo
A discovery call is not a race to demonstrate everything a product can do. Its purpose is to understand a meaningful decision and the evidence the buyer will need. A useful question invites a specific example; a follow-up tests the consequence and the next decision.
Fictional exchange
Buyer: “We need better reporting.”
Seller: “Which decision is difficult to make with today’s reports?”
Buyer: “Our regional leads cannot tell which accounts are at risk.”
Seller: “Can you walk me through the last account where that mattered? What signal did you miss, and who needed it?”
Buyer: “The usage drop was visible, but no one agreed who should contact the customer.”
The conversation has moved from a broad feature request to a workflow and an ownership problem. The seller still needs to test whether the issue is frequent, material and within the product’s actual scope. They should not announce a solution from one answer.
Four questions worth practising
- What triggered the search now, and what happens if the current process continues?
- Where does the handoff fail in the last real example?
- Who else sees the problem differently, and what would they need to trust a change?
- What evidence would let your team choose a next step?
In a five-minute practice, one person plays the buyer, one asks questions and one observes. Score whether the seller explored the consequence, checked assumptions and agreed a buyer-owned next step. Debrief the evidence, then replay the same moment with one changed question. See how NewSkilz approaches sales enablement.