Discovery calls: probe a buyer's firm opinions without sounding adversarial
Summary
Salesforce's November 5 Ask Slackbot column, answered by a forward deployed engineer's Slackbot from their real Slack history, tackles discovery calls with customers who arrive with firm opinions. Its advice: ask what happened that makes their solution look obvious, frame questions around what a feature unlocks, show the numbers instead of disagreeing, and say what still needs validating. The column ends with a prompt for drafting curious discovery questions.
TopCloserR Perspective
The takeaway
A buyer's firm request is a compressed story about a pain. The rep who asks what's behind it, without arguing, finds the real problem and avoids building the wrong deal.
Who gets the most from this
- In the role
- You are expected to be both the expert and the listener, and the column says you don't have to pick one.
- Aspiring
- Technical reps and implementation staff moving into presales. — Practice 'what does that unlock' questions. They are the difference between taking orders and shaping the solution.
- In the role
- Customers with a fixed solution in mind often haven't shown you the whole picture, and the first ask can change mid-deal.
- Aspiring
- SDRs and BDRs moving into full-cycle discovery. — Questioning a buyer without interrogating them is the core discovery skill. Start building it now.
Put it to work
- Swap 'why' questions for 'what does it unlock' questionsAccount Executive
Rewrite your top three discovery questions so they ask what a feature lets the team do, not why they want it.
- Bring the customer's own numbers to the callSales Engineer
Describe their current setup in concrete figures before you propose anything, so they reach the conclusion themselves.
- Mine past deals for the moment the ask changedAccount Executive
For your last five deals, note what the customer first asked for, what they ended up needing and the question that would have surfaced it sooner.
Recommendations
More Sales Enablement & Training news