The discovery question you miss while planning the next one

The buyer mentions a difficult handoff. The seller says “makes sense,” glances at the question list and asks about the budget. The useful detail disappears between two perfectly reasonable questions.

That opening is an illustrative scene. Its underlying problem appeared in a 2023 account executive’s Reddit post: worrying about the next question made it hard to listen, respond and explore the customer’s pain. The writer had prepared a script. Preparation alone had not solved the difficulty.

A discovery guide should help you return to the conversation when you lose your place. It should also give you permission to stay with an answer that matters.

Follow one incident

Suppose a fictional operations buyer says, “The handoff between our teams is messy.” You could ask for their whole process. You could also ask about the last time the handoff went wrong.

The second question gives both people something concrete to examine:

Can you walk me through the most recent example? Where did the work begin to stall?

Listen for what happened, who was involved and how the team dealt with it. If the buyer says a request sat in a shared inbox, the next question can follow that detail: how was someone supposed to take ownership?

You do not have to turn every answer into a new qualification category immediately.

Leave room for an answer you did not expect

The buyer might say the delay was harmless. Perhaps the team was waiting for an approval, and the process worked as intended. Perhaps the incident was rare and already fixed.

Those answers matter. A question designed only to confirm pain can lead the seller to overlook a perfectly adequate current approach.

Ask what happened next and whether the outcome was a problem for the buyer. Do not supply the severity yourself. If they describe a cost, clarify what it includes and whether it is measured, estimated or simply a concern.

“That must be costing a fortune” inserts a conclusion. “What did the delay change for the team?” leaves the buyer room to explain.

Stay with the inbox for another minute

In the fictional conversation, the buyer explains that two people thought the other person had picked up the request. Resist the urge to move straight to a feature that assigns owners. Ask what each person could see at the time.

Perhaps the inbox already had an owner field and nobody used it. Perhaps responsibility changed when a colleague was absent. Those answers lead to different problems and different next questions.

If the sequence is unclear, ask what happened immediately before the delay. If the buyer mentions a workaround, ask how it works today. Choose the follow-up that resolves the uncertainty in this answer. A fixed sequence of prompts can bring the checklist problem back.

It can help to note the buyer’s exact phrase privately, then pause long enough to understand it. Follow your organization’s established meeting-note and recording practices; a recording is not necessary for this exercise.

Check your interpretation out loud

Before moving on, summarize the connection you think you heard. For the fictional handoff example:

The request itself is clear, but nobody knows who has picked it up. Is ownership the main issue, or have I missed something?

A correction is useful progress. It is cheaper to discover a misunderstanding during the conversation than after building a proposal around it.

Avoid adding a business impact the buyer did not describe. Your summary should reflect the account you heard, including its uncertainty.

Return to the purpose of the meeting

Following an incident does not mean abandoning the agenda. Explain the meeting’s purpose at the start and leave time to identify what still needs discussion. If you have not covered decision ownership or constraints, say so and agree how to address them.

Afterward, review one moment where you moved past a potentially useful answer. Write the follow-up you could have asked. Use that observation to prepare the next conversation rather than grading yourself against an ideal performance.

RevQ describes preparing questions around business context and what buyers have said. A useful brief should make those questions easier to adapt in the room. The busy-day meeting brief keeps that preparation compact.

When you prepare the next call, leave a blank space beside each main question. Use it for the detail you hear, and the question that detail raises.

About this article: AI-assisted writing and editing, informed by the linked public discussion. Illustrative examples are labelled; they are not customer case studies. Read our editorial approach.

Updated October 3, 2026