There is a common pattern in early-career technology sales. A prospect agrees to a meeting, the seller opens the slide deck or the product, and spends forty minutes showing features. The prospect nods, says it looks interesting, and the deal quietly goes nowhere. The missing step is discovery: understanding the buyer’s situation well enough that anything you show afterwards is about their problem rather than your product.
What discovery is for
Discovery is the structured conversation where a seller learns how the buyer works today, what is going wrong, what that costs, who cares about it, and what would have to be true for them to change. It has three jobs:
- Qualify: decide honestly whether this is a real opportunity worth both sides’ time.
- Diagnose: find the specific problem and its business impact, not a general interest in “digital transformation”.
- Shape: gather what you need to tailor the demo, the proposal and the business case.
Questions that move from surface to substance
Good discovery tends to move through layers. Using an illustrative example of a company that sells helpdesk software to mid-sized Indian firms:
- Current state: “Walk me through what happens today when an employee raises an IT issue.” This gets the buyer describing their reality in their own words.
- Problem: “Where does that process break down?” Perhaps tickets arrive by email, WhatsApp and phone, and nobody knows what is open.
- Impact: “What does that cost you?” Maybe new joiners wait three days for laptop access, and the finance team has complained to the CFO.
- Priority and timing: “Why look at this now rather than next year?” An upcoming audit or an expansion plan often sits behind the answer.
- Decision process: “Who else would be involved in choosing a tool like this, and how have purchases like this been made before?”
The impact question is the one most often skipped. Without it, the seller has a problem but no reason for the buyer to spend money on solving it. A problem with no measurable cost tends to stay on the “nice to have” list indefinitely.
Qualification frameworks are discovery checklists
Sales teams use frameworks to make sure discovery covers the essentials. BANT (budget, authority, need, timeline) is the oldest and simplest. MEDDIC and its variant MEDDPICC are common in enterprise software and ask for more: metrics the buyer will use to judge success, the economic buyer who controls the money, decision criteria, the decision process, the specific pain, and a champion inside the account who will push for you. The extra letters in MEDDPICC add the paper process (legal and procurement steps) and the competition.
None of these should be read out like a form. They are a checklist for the seller’s own notes after the call: which boxes are filled, which are assumptions, and which are completely unknown. The unknowns become the agenda for the next conversation.
How discovery changes the demo
After good discovery, a demo stops being a tour. In the helpdesk example, the seller would open with the exact scenario the buyer described: an employee raises a request on WhatsApp, it becomes a ticket automatically, the right engineer is assigned, and the IT head sees a dashboard of overdue items. Features that do not relate to their pain can be left out entirely. Buyers remember a demo of their own problem being solved far better than a list of capabilities.
Listening is the actual skill
The mechanics are easy to learn. The hard part is staying quiet long enough for the buyer to finish, following up on what they said rather than the next question on your list, and summarising back accurately: “So if I’ve understood, the real issue is not the tool, it’s that nobody owns the queue after 7 pm. Is that fair?” A buyer who hears their situation described back clearly is far more likely to trust the person who described it.
Discovery also gives a seller permission to walk away. If there is no real pain, no budget and no one who can decide, the most professional thing to do is say so and spend time elsewhere.
Written by the RP Strativa Team. The company and scenario in this article are illustrative.
Leave a Reply