The short answer
Discovery call questions are open questions a seller asks in a first meeting to understand the prospect's situation, their pain, the impact of that pain, how they buy and who decides. Good ones are specific to the account, open-ended and followed by probes such as 'Can you give me an example?' Pick two or three per category rather than asking all of them.
On this page
- How to Use This Discovery Question Bank
- Situation Discovery Call Questions
- Pain Discovery Call Questions
- Impact Questions That Show What the Pain Costs
- Process Discovery Call Questions
- Decision Discovery Call Questions
- Turning Generic Discovery Call Questions Into Account-Specific Ones
- Get discovery questions for any account in three steps
- FAQ
Key takeaways
Pick, don't recite: Choose two or three questions per category for each call. A 30-question interview feels like an audit.
Listen for specifics: Numbers, dates, names and recent examples signal real pain. Vague answers mean you need to probe.
Probe three deep: The first answer is the polite one. 'Tell me more' and 'For example?' get you to the real one.
Make them account-specific: Rewrite each question around something you know about the prospect. It proves preparation and gets better answers.
How to Use This Discovery Question Bank
Don't ask all 30. Pick two or three per category based on what you already know, and spend the time you save on probing. For the structure of the call itself, see the discovery call script.
| Category | What you learn | How many to ask |
|---|---|---|
| Situation | How things work today | 2 or 3, fewer if you researched well |
| Pain | Where it breaks and how often | 2 or 3 |
| Impact | What the problem costs, and who feels it | 2 |
| Process | How they'd go about fixing it | 1 or 2 |
| Decision | Who decides, with what money and timing | 2 or 3 |
Probe before you move on. Use this ladder after any answer that matters:
1. "Tell me more about that."
2. "Can you give me a recent example?"
3. "What happened next?" or "What did that cost?"
Situation Discovery Call Questions
Situation questions map the current state. Keep them short: if you could have answered one from their website, don't ask it.
| Question | Listen for | Probe |
|---|---|---|
| "Walk me through how [process] works today." | Steps, tools, handoffs, people | "Where does it slow down?" |
| "Who's involved, from start to finish?" | Names and roles for your account map | "Who owns it overall?" |
| "What tools hold it together?" | Tools you'd replace or integrate with | "What made you choose that?" |
| "How has that changed in the last year?" | Growth, new markets, new hires | "What drove the change?" |
| "What does a good week look like?" | Their definition of success | "How often do you get one?" |
| "What have you already tried?" | Past fixes and failed tools | "Why didn't that stick?" |
Pain Discovery Call Questions
Pain questions find the problem in the prospect's own words. Specific, recent stories mean real pain, while vague answers mean probe or move on.
| Question | Listen for | Probe |
|---|---|---|
| "Where does [process] break down?" | A specific step, not "everywhere" | "When did that last happen?" |
| "What's the most frustrating part of [task]?" | Emotion, repeated complaints | "How does the team feel about it?" |
| "What do you wish you could do that you can't?" | A gap your product fills | "What's stopping you today?" |
| "What workarounds have you built?" | Spreadsheets, manual steps, extra hires | "How much time goes into those?" |
| "What do customers complain about?" | External pain, often more urgent | "Has that cost you a customer?" |
| "If you could fix one thing tomorrow, what would it be?" | Their real priority | "Why that one?" |
Impact Questions That Show What the Pain Costs
Impact questions turn a problem into a business case. Without them you have a complaint, not a deal.
| Question | Listen for | Probe |
|---|---|---|
| "What does that cost you in time or money?" | A number, even a rough one | "How did you arrive at that?" |
| "Who else feels this problem?" | Other teams and stakeholders | "How does it affect them?" |
| "What happens if nothing changes this year?" | Real consequences, or indifference | "How would that affect your goals?" |
| "How does this affect [their stated goal]?" | A link to targets they own | "Is that goal at risk?" |
| "Has this come up with your leadership?" | Executive visibility | "What did they say?" |
| "What would it be worth to fix it?" | The value they'd attach | "What would you do with that time?" |
No number, no urgency. If they can't put even a rough cost on the problem, it may not be a priority yet. That's useful to know before you invest in a demo.
Process Discovery Call Questions
Process questions tell you how a change would actually happen here. Ask them on the first call, or you'll learn the answers when the deal stalls. Objections that surface here are easier to handle now than later; the objection handling script has replies ready.
| Question | Listen for | Probe |
|---|---|---|
| "If you decided to fix this, what would happen next?" | Steps, evaluations, approvals | "How long does that usually take?" |
| "Have you looked at other options?" | Competitors in play, or none | "What did you like about them?" |
| "How have you bought tools like this before?" | Procurement, security, legal steps | "What slowed that one down?" |
| "What would a trial or pilot need to prove?" | Success criteria | "Who would judge it?" |
| "What would make you decide not to change?" | Risks and objections, early | "How could we address that?" |
| "What needs to be true for this to go live?" | Integrations, training, timing | "Who owns that work?" |
Decision Discovery Call Questions
Decision questions map who signs, with what money and by when. Frameworks like BANT qualification cover the same ground in checklist form.
| Question | Listen for | Probe |
|---|---|---|
| "Who else would weigh in on a decision like this?" | Names, roles, committees | "What will they care about most?" |
| "Who signs off in the end?" | The economic buyer | "Have they been involved so far?" |
| "Is there budget set aside, or would it need approval?" | Budget owner and cycle | "When are budgets set?" |
| "Is there a date this needs to be solved by?" | Deadlines, events, renewals | "What happens if you miss it?" |
| "How does your team usually choose between options?" | Criteria: price, features, risk | "Which matters most?" |
| "What would you need from me to make the case internally?" | What your champion needs | "Who would you share it with?" |
Turning Generic Discovery Call Questions Into Account-Specific Ones
Generic questions get generic answers. Rewrite your top questions around one thing you know about the account, and the prospect hears preparation instead of a checklist.
| Generic | Specific (Halden Freight, hiring three pricing analysts) |
|---|---|
| "How do you handle quoting?" | "With three pricing analysts joining, how will quoting change?" |
| "What are your challenges?" | "Where do spot quotes get stuck when volume spikes?" |
| "Who's involved in decisions?" | "Will the new pricing lead own this, or does it stay with ops?" |
One specific question per category is enough. It changes the tone of the whole call. Prep it with a call prep template, and after the call, check fit against your lead qualification criteria.
Edithly writes account-specific discovery questions, each with what to listen for, from the prospect's website and your playbook. See how Edithly prepares discovery call questions.
How Edithly does it
Get discovery questions for any account in three steps
Edithly's cold call script includes discovery questions written around the prospect's business, each with what to listen for, plus objection replies for when the call pushes back.
- 1
Click the Cold Call Script tile
Open Home and pick Cold Call Script. Your pitch, proof points and positioning are already in your playbook, pulled from your website when you added your product.
- 2
Paste the prospect's website
Enter the company name and website, plus the contact's name and LinkedIn. Add context in Notes, like how the meeting was booked or what they asked about.
- 3
Click Generate cold call script
Copy the discovery questions and their listen-for notes into your call plan, and keep the objection replies nearby.
Website
Ready
- Opener
- Permission ask
- Discovery questions
- Objections
- Voicemail
- Gatekeeper
- By hand
- 15 to 25 minutes per account to research and tailor questions
- With Edithly
- A couple of minutes per account
Frequently asked questions
What are good discovery call questions?
Good discovery questions are open, specific and about the prospect, not your product. Examples: 'Walk me through how you handle [process] today', 'Where does that break down?', 'What does that cost you?' and 'Who else would weigh in on a change?' Follow each one with probes that ask for examples and specifics.
How many questions should you ask on a discovery call?
Plan around 8 to 12 questions for a 30-minute call, and expect to ask fewer, because good answers lead to follow-up probes. Two or three per category is plenty. If you get through every question on your list, you probably weren't probing deep enough on the answers that mattered.
What are the categories of discovery questions?
A practical set is situation (how things work today), pain (where it breaks), impact (what it costs), process (how they'd change it) and decision (who decides, with what budget and timing). Frameworks like SPIN and MEDDIC group them differently, but they cover the same ground: the problem, its cost and how buying happens.
What should you listen for on a discovery call?
Specifics: numbers, dates, names and recent examples. 'Last Tuesday we lost a customer because a quote took two days' signals real pain; 'it could be better' doesn't. Also listen for emotional words, mentions of other people and deadlines, which tell you about urgency and who else to bring in.
Can Edithly write discovery questions for a specific prospect?
Yes. When you generate a cold call script, Edithly reads the prospect's website and writes discovery questions around their business, each with what to listen for, along with objection replies. Add context in Notes, like how the meeting was booked, to steer it. It doesn't run or record the call.