Become an SDR/BDR · Intermediate · ~7 hours
Sales Discovery & Qualification
Plan discovery conversations and make thoughtful qualification decisions based on customer needs and evidence.
Status: Catalogue ready. This lesson version is available in review mode while subject-matter, accessibility and assessment checks are completed.
Buyer-centred discovery
Prepare and open a discovery conversation
By the end of this lesson
- Set a clear, buyer-centred purpose for a discovery conversation.
- Use an agenda that creates room for the buyer's priorities and corrections.
- Open with context and curiosity without turning discovery into a hidden pitch.
Discovery begins with a decision about the conversation
Discovery is not a script that extracts a list of pain points. It is a structured conversation that helps both sides decide whether there is a problem worth exploring and whether the seller can contribute useful evidence. Preparation matters because the buyer should not have to repeat information already shared, but preparation must remain provisional. Research can suggest questions; it cannot replace listening. Before the call, write a working hypothesis, the information already known, the most important unknowns and the decision the conversation should support. The decision might be whether to involve a technical colleague, whether to review the current process in more detail or whether there is enough fit to plan a demonstration. Avoid preparing a fixed conclusion. A good discovery call allows the buyer to say the issue is smaller, larger, different or not current. An agenda gives the conversation shape. It can include introductions, the buyer's priorities, current process, desired outcome, constraints and a decision about next steps. Offer the agenda rather than imposing it: “I have a few areas I would like to understand, and I would like to leave time for your questions. Is there anything you want to make sure we cover?” That question establishes collaboration before the detailed questions begin.
Create enough safety for useful answers
People give better information when they understand why a question is being asked and do not feel that every answer will be used to pressure them. Explain the reason behind sensitive or detailed questions. If asking about workflow, say that the purpose is to understand where effort or risk appears today, not to judge the team. If a question is not relevant, let the buyer decline it. The opening should make it easy to correct the seller's assumptions. A useful structure is: acknowledge previous context, state the purpose of the call, share the working hypothesis as tentative and invite the buyer's view. For example: “You mentioned that reporting is reconciled manually. I would like to understand how that affects the team and what a better process would need to protect. I may have the context wrong, so please correct me.” This is more credible than claiming to know the buyer's business. Good discovery is also inclusive. Use plain language, avoid unnecessary acronyms and check whether the pace works for the people on the call. If different stakeholders have different priorities, make that visible rather than forcing a single story. A finance concern, an operations concern and a technical constraint can all be real at the same time.
Close the opening with a shared question
The first question should open the buyer's experience, not steer them toward a feature. Broad questions such as “What prompted you to look at this now?” can reveal the trigger, but they should be followed by focused questions about the process, consequences and desired change. Silence is useful; do not fill every pause with a new question or an explanation of the product. Listen for the buyer's language. Repeat the important part in neutral terms and ask whether you understood it correctly. This can sound like: “So the main issue is not that the data is unavailable; it is that teams spend time reconciling definitions before the meeting. Have I got that right?” The buyer can confirm or amend the summary. That correction is valuable evidence. An opening is complete when both sides know what the call is for and the buyer has had a real opportunity to set priorities. Do not rush into a demonstration because the agenda is finished. The next part of discovery should follow the evidence that emerged, and the call should leave enough time to decide whether more investigation is worthwhile.
Workplace example
A fictional buyer at Elmbridge Services agreed to discuss inconsistent operational reports. The learner opens by confirming the context, shares a tentative hypothesis about reconciliation work and asks what prompted the conversation. The buyer explains that the bigger issue is a lack of ownership for data definitions. The learner updates the agenda instead of continuing with prepared questions about dashboards.
Try this walkthrough
- 1.Write the decision the discovery call should support and three unknowns that matter to that decision.
- 2.Draft a four-part agenda that leaves room for the buyer's priorities and questions.
- 3.Create an opening that states a tentative hypothesis and invites correction.
- 4.Practise reflecting one buyer statement in neutral language and asking whether you understood it correctly.
Watch for these traps
- Treating research as a conclusion instead of a source of provisional questions.
- Opening with a product tour before understanding the buyer's situation.
- Using an agenda as a script that prevents the buyer from changing the priority.
- Asking a long chain of questions without summarising or checking understanding.
Knowledge check
Choose the response you think is strongest. These checks are practice until the course version has passed subject-matter review; graded attempts will be handled server-side.
For the reviewed pilot, answers are checked on the server. This draft result is not yet added to your official learning record.
Practice studio
Make a decision. Test a response. Leave evidence.
Use the case from this lesson to practise judgement without creating a score or changing your course record.
Scenario decision
A fictional buyer at Elmbridge Services agreed to discuss inconsistent operational reports. The learner opens by confirming the context, shares a tentative hypothesis about reco…
Choose a response
Branching roleplay
A colleague asks you to move this situation forward. What do you say next?
Evidence workspace
Draft a short known / assumed / next note from the fictional case. Use fictional details only.
This is a session-only practice draft. It is not saved, graded or added to your learning record. Never enter real personal or confidential information.
Practical assignment
Prepare a discovery plan for the Elmbridge Services scenario. Include the decision to support, five open questions grouped by purpose, a buyer-centred agenda and a 90-second opening that clearly marks assumptions as tentative.
Pass this lesson's knowledge check before recording it as complete.
Portfolio evidence
Practical portfolio project
Complete a discovery worksheet and qualified opportunity handover from a fictional customer conversation.
Turn the practical project into a bounded evidence record. Save a draft while you work, then submit it for human review when it is ready.
Sign in to save practical evidence. Sign in