Discovery call questions: when to follow up and when not to

01

The test: important, and left under-developed

Follow up when an important point needs more detail. Six signals show it: vague language that should be made concrete, a problem named without its causes, a business impact implied but not stated, time pressure hinted at but not grounded, a decision whose context is unclear, and a point where numbers would materially improve understanding.

The six are the working list of the listening prompt (prompts/live_listener_v1.txt) in an AI sales coach Jacob Top Møller built, and its rules open with restraint: "Most conversation moments need NO intervention." Small talk, specific statements and questions already asked get no follow-up.

A buyer who says four people spend the first five days of every month matching invoices by hand has already given you the numbers. There is no need to ask how many people or how long it takes again. Write those details down and listen for what the buyer adds.

The Sales Engineering training page names the gap the test points at: "Discovery finds requirements while the business consequence remains vague." Huthwaite International, the firm that pioneered SPIN Selling, draws the same line from the buyer's side. A dissatisfaction such as "our reporting is a mess" is an implied need, a wish for a solution is an explicit need, and Huthwaite writes that in major sales "the former implied needs have no relationship with success." So the follow-up asks the buyer to name the consequence in their own words.

02

Ask in the buyer's words, one step at a time

Use the buyer's words and ask about one thing at a time. Write one to three candidate questions, each open, neutral and grounded in what the buyer said, as the coach's question prompt (question_coach_v1.txt) does. Choose one, ask it and listen before deciding whether to ask another.

For a vague word: "When you say a bit of a mess, what happens at month end?" For an implied impact: "What happens when it slips?" For an unclear decision: "How will you choose between the options?"

Each of these asks about one thing. "What happens at month end, who is affected and what does it cost?" asks for three steps at once and lets the buyer answer the easiest.

The questions you did not ask can wait. PostHog's sales handbook says it plainly: "We don't need to cram every question into the first call."

03

Four questions to strike before you ask them

Check each question for assumptions, product pitches and framework jargon before you ask it. The coach's question prompt rules out these four kinds of question.

The first is "why now?" before the buyer has signalled urgency. "We are looking at a few options this year" is not such a signal. "We have to show a fix before the September audit" is. Listen for a deadline, milestone or outside force that the buyer says creates urgency and determines when a decision must be made. Winning by Design's SPICED calls this a Critical Event. Without that signal, the question can push the buyer towards a deadline they have not mentioned.

The second assumes a budget, a decision maker or a deadline before the buyer has raised one. "Which budget will pay for this?" assumes there is a budget. Ask how the choice will be made, and let the buyer say who is involved.

The third brings in your product. "Our platform automates invoice matching, would that help?" turns the conversation from the buyer's problem to a pitch. GitLab's handbook calls the urge "Happy Ears" and tells its sellers to hold back until they understand the challenges, their implications, how big the problem is and how urgent it is.

The fourth uses a framework term. "Who is your economic buyer?" uses the seller's framework. "Who will weigh in on this?" asks about the decision without assuming someone else is involved.

04

Worked example: an invented month-end call

Run the test line by line. In this first call, a head of finance operations speaks with an account executive and a Sales Engineer.

Four of the six lines get a question. The question about timing waits until the buyer names the audit, and then it uses the buyer's own deadline.

05

Use the test on the recording

Review the call for important points that needed a follow-up. If you have a transcript, go through it line by line; otherwise listen to the recording. Mark missed opportunities, repeated questions and questions that introduced the product, used framework terms or asked "why now?" before the buyer signalled urgency.

Turn the missed points into candidate questions using the buyer's words. Choose what still matters for the next conversation and put it in the pre-call plan, so both of you know who will ask what. Discovery should leave you with the business problem in the customer's words and a possible champion, as what the demo needs from discovery sets out. For exercises that build the listening itself, see ten resources for practising enterprise discovery.