B2B sales enablement workshop / 5 MIN READ
Run discovery without turning it into an interrogation
Use a shared agenda to understand the buyer’s work before prescribing a solution.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A discovery conversation should help both sides decide whether further evaluation is useful. It fails when qualification fields replace listening or when the seller hides a pitch behind questions.
What you will leave with: A discovery agenda that links current work, constraints and an agreed next step.
Use this when
- Sales conversations collect facts but reveal little about the actual task.
- A prospect wants an early conversation before a detailed demonstration.
This is not a script for manufacturing pain, extracting confidential information or forcing a buying timetable.
Agree what the conversation is for
Salesforce’s call guidance recommends setting expectations and aligning the agenda with the prospect’s needs. Begin by confirming what would make this particular conversation useful.
Offer a small number of topics and invite corrections. Explain whether you intend to discuss the current process, a specific difficulty or the suitability of a later demonstration. Do not insist on completing a qualification checklist before answering a reasonable question about what your service does. If the prospect’s purpose differs from your assumption, adjust the agenda openly instead of steering every answer back to a predetermined pitch.
Explore a recent episode
Ask for a concrete example of the task: what started it, who became involved, what information was needed and where work paused. Follow the sequence in the buyer’s language before translating it into your product categories. Distinguish a recurring operational constraint from an unusual event.
Ask what already works and what they have tried. This prevents the conversation from treating the existing process as worthless merely because your product is different. If the prospect cannot discuss confidential details, use a generalized scenario. You need enough context to assess fit, not a copy of their internal records or a list of colleagues’ private difficulties.
Check constraints and the cost of change
Explore required integrations, permissions, procurement steps, implementation effort and timing only as far as they affect the next decision. Ask who else would need to contribute to evaluation rather than treating the current contact as a route around their colleagues.
Separate a requirement from a preference and a known constraint from an assumption. A buyer may like a feature but be unable to change a workflow during a regulated reporting period. Reflect that constraint accurately. Do not convert every inconvenience into an invented financial loss or imply that the buyer has accepted your estimate of its importance.
Summarize before proposing the next step
State what you heard, what remains uncertain and why a particular next activity might help. Invite corrections. A useful next step could be a focused demonstration, a technical answer, an introduction requested by the buyer or an honest conclusion that the offer is not a fit.
Agree who will do what and when, without making an unrequested commitment on the buyer’s behalf. Send only the information that supports that step, subject to applicable communication permission. Keep discovery notes factual and relevant. Internal speculation about motives can become harmful when it is copied into account records as though the buyer said it.
Make the reasoning concrete.
A fictional equipment-monitoring vendor speaks with a plant manager who asks for a demonstration. The seller’s standard discovery form focuses on budget and executive authority.
Complete the qualification form first
Opening: Ask every commercial field before discussing the plant’s task.
Hypothesis: The CRM record will look complete.
Risk: The conversation may miss the equipment approval constraint that determines fit.
Agree a focused agenda
Opening: Explore a recent maintenance alert, explain the product briefly and identify the next useful demonstration.
Hypothesis: The buyer and seller can discover whether the use case fits.
Risk: Some commercial details will remain unknown until they become relevant.
The seller learns that installation must be reviewed by engineering. The agreed next step is a bounded technical demonstration, not a forecasted purchase date invented from enthusiasm.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Purpose
What would make this conversation useful to the buyer?
Episode
Which recent task will ground the discussion?
Constraint
What could make the offer unsuitable even if the feature is appealing?
Uncertainty
Which important statements are still assumptions?
Next step
What activity have both sides actually agreed to?
Watch for the wrong conclusion.
- Treating qualification fields as the conversation itself.
- Turning every frustration into a fabricated monetary loss.
- Recording interpretations of motive as buyer statements.
Your next action
Rewrite your next discovery agenda around one recent customer task and one decision both sides can reasonably make afterward.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Salesforce Trailhead: Make Successful Sales Calls →Primary vendor training guidance · Supports: Sales calls should align expectations, address needs and finish with clear next steps; the specific worksheet is original analysis.