The discovery call, run properly
A 30-minute agenda, 24 questions by category, the six qualification checks and the recap email that follows. This is the structure our own reps run inside SalesCollab Sales Companion — use it as-is.
What a discovery call is for
A discovery call is the first structured conversation with a prospect. Its job is to establish whether there is a real problem worth solving, what it costs them, and how a decision would get made. It is not a demo and it is not a pitch — if you spend the call presenting, you leave without the information you need to win the deal.
The single biggest difference between reps is not charm; it is whether they run the same structure every time. Below is that structure.
The 30-minute agenda
Frame the call
State how long you'll take, what you want to understand, and what happens at the end. Ask permission to take notes.
Their context
Who they are, what the team does, how the current process works today — before you mention your product.
The problem
Dig into the pain: when it happens, who it hurts, what it costs, and what they've already tried.
Impact and priority
Quantify it. Then find out where fixing it sits against everything else on their list this quarter.
Decision and process
Who else is affected, who signs, what budget exists, and what has to be true before they can buy.
Summarise and set the next step
Play back what you heard, confirm you got it right, and book the next meeting in the calendar on the call.
24 discovery call questions
Pick two or three per category rather than reading all of them. Follow every answer with "what does that cost you?" until you get a number.
Context
- Walk me through how your team handles this today, step by step.
- Who touches the process, and where does it usually get stuck?
- What tools are involved right now?
- What made you take this call?
Problem
- When did you first notice this becoming a problem?
- How often does it happen — weekly, monthly, every deal?
- What have you already tried, and what happened?
- Who feels it most: the reps, the customer, or the finance side?
Impact
- What does this cost you in hours per week?
- What does one lost deal look like in revenue terms?
- If nothing changes in twelve months, what does that look like?
- What becomes possible for the team if this is solved?
Priority
- Where does this sit against your other priorities this quarter?
- Is there a date or event that makes this urgent?
- What's the cost of waiting another six months?
- Has anyone above you asked for this to be fixed?
Decision process
- Besides yourself, who needs to be comfortable with this?
- How were similar purchases approved here before?
- Is there budget allocated, or would this need to be motivated?
- What would make this a 'no' internally?
Next step
- If I sent a short written summary, who else should receive it?
- What would you want to see in a demo that's specific to you?
- What's a realistic date for a decision?
- Is there any reason we shouldn't put the next session in the diary now?
Did the call qualify?
Six checks. Three or more missing means you need a second discovery conversation, not a demo.
Problem
They described a specific, repeating problem in their own words.
Impact
You have at least one number: hours, rands, deals or headcount.
Priority
It is on this quarter's list, not 'someday'.
Power
You know who signs and whether you've met them.
Process
You know the steps and rough timeline to a decision.
Next step
A dated meeting exists in both calendars.
Five mistakes that cost deals
Pitching in the first five minutes.
Earn the pitch — ask about their process first.
Accepting the first answer.
Follow every pain with 'what does that cost you?'
Talking to one person only.
Map everyone the problem touches before you demo.
Ending with 'I'll follow up.'
Book the next meeting while you're still on the call.
Writing the recap two days later.
Send a written summary the same day, while it's accurate.
The recap email template
Send it the same day. Short, factual, and easy for your contact to forward internally.
Subject: Recap — [their company] and [your company], [date] Hi [name], Thanks for the time today. Capturing what I heard so you can correct me: Where you are now - [current process, in their words] What's not working - [problem 1] - [problem 2] What it's costing - [hours / rands / deals per month] What we agreed - [action, owner, date] - [action, owner, date] Next step - [meeting type] on [date, time], with [attendees]. If I've misheard anything, reply and I'll correct it. [Your name]
Discovery call FAQs
What is a discovery call?
A discovery call is the first structured sales conversation with a prospect. Its purpose is to understand their situation, problem, impact and buying process — not to pitch. A good discovery call ends with a qualified decision to continue or stop, plus a booked next step.
How long should a discovery call be?
Thirty minutes is the working standard for a first call. Book 45 minutes for enterprise deals with several stakeholders. Anything longer usually means the call has turned into an unplanned demo.
How many questions should I ask?
Aim for roughly ten to fifteen real questions with follow-ups, and keep the prospect talking about 70% of the time. Working from a set list per category is more reliable than improvising.
What should happen after a discovery call?
Send a written recap the same day covering what you heard, what it costs them, what you agreed and the next step with a date. Then log the answers against the account so the next person on the deal is not starting cold.
How do I know if the call was good?
Test it against six criteria: a specific problem, a quantified impact, a stated priority, a known decision-maker, a known buying process, and a booked next meeting. Missing three or more means you need a second discovery conversation, not a demo.
Stop hoping every rep runs this
SalesCollab Sales Companion walks each rep through the discovery questions for your business, tests them before they may engage a customer, and drafts the recap email afterwards — filed against the account.