Discovery call questions
Questions are the whole job on discovery. The right ones turn a nice-to-have into a must-fix and reveal how a yes actually happens.
Choose the highest-signal questions for the buyer in front of you.
Short answer
Great discovery uncovers the problem, its business impact, who decides, and the timeline. The question bank below is organized into those four buckets so you can run a structured call and leave knowing exactly why and how this prospect will buy. Pick 10 to 15, do not machine-gun all 30.
Key takeaways
- Pick 10 to 15 questions; a 30-question interrogation kills rapport.
- Always quantify the pain in dollars or hours before moving on.
- Never leave discovery without knowing the decision process and timeline.
- Log answers as structured fields so the deal record shows why they will buy.
Problem and current-state questions
Understand how it works and where it hurts.
- "Walk me through how you handle {process} today."
- "Where does that break down or slow you down?"
- "How long has that been a problem, and what have you tried?"
- "If you did nothing, what happens over the next six months?"
Impact and metrics questions
Quantify the cost of the problem.
- "How much time or money does that cost per week or month?"
- "How does it affect your team's numbers, or your own goals?"
- "Who else feels this pain, and how loudly?"
- "What would solving it be worth to you?"
Decision and timeline questions
Learn how a yes happens.
- "How does a decision like this usually get made here?"
- "Besides you, who needs to weigh in or sign off?"
- "What is your timeline to solve this, and what is driving that date?"
- "What could get in the way between now and then?"
Generate and send this with Ardovo
You do not have to start from a blank page. Tell Rook, Ardovo's AI operator, what you need (for example, "discovery call questions") and it drafts a version grounded in your real pipeline data, personalizes it for the specific contact or deal, and can send it or attach it to the record in one step. Every template lives in one shared library, so your whole team stays on message and nothing gets rewritten from scratch.
Frequently asked questions
How many questions should I ask on a discovery call?
Ten to fifteen well-chosen open questions across problem, impact, decision, and timeline. Quality beats quantity; a 30-question checklist turns the call into an interrogation and breaks rapport.
What are the most important discovery questions?
The ones that quantify impact ("what does this cost you?") and map the decision ("who signs off, and by when?"). Those two threads turn interest into a qualified, forecastable deal.
Should I use a framework like MEDDIC for discovery?
A framework keeps you honest about what you still need to learn. MEDDIC, BANT, or SPICED all work; the point is to leave discovery knowing metrics, decision process, and timeline.