Questions that uncover what the buyer actually needs, not asks for

4 days ago
3 min read

Introduction

Buyers rarely describe a problem. They describe a solution they have already selected, frequently the wrong one, arrived at from a search, a neighbour's experience or an assumption about what their situation requires. Quoting for exactly what was asked is therefore a reliable way to deliver something that does not solve anything.

The alternative is not to second-guess people. It is to ask a small number of questions that get behind the request to the situation that produced it. Where the request turns out to be right, you have lost five minutes. Where it does not, you have avoided a job that would have disappointed and won one on better terms.

1. Questions that uncover what the buyer actually needs start behind the request

The reframing.

Somebody asking for a specific thing has already made a diagnosis. Asking what led to it is not doubting them; it is checking the diagnosis before acting on it. Framed as curiosity rather than correction, buyers welcome it.

2. Ask what is happening rather than what they want

The opening move.

"What is the situation you are dealing with?" produces a description of the problem. "What would you like?" produces a description of a solution they may have chosen badly. The first question also produces information you can use in the quote.

3. Ask what prompted it now

The trigger question.

Something changed. Whatever it was frequently defines the real requirement, and it is invisible if you accept the request at face value. It also tells you how urgent this genuinely is.

4. Ask what happens if nothing is done

The severity question.

The answer tells you the size of the problem, the urgency and the budget it can justify. It also tells you whether the buyer is actually going to act. A buyer who cannot answer it is frequently not going to proceed.

5. Ask what they have already tried

The history.

Previous attempts, previous suppliers, temporary fixes. This prevents you proposing something that failed before and it explains any wariness in the conversation. A bad previous experience shapes everything that follows and is rarely volunteered.

6. Ask what a good result looks like

The definition.

In their words. Two buyers requesting the same work frequently want different outcomes, and quoting to the wrong one produces a technically correct job that disappoints. Write the answer down and use their phrasing in the proposal.

7. Ask what would make this a poor experience

The negative version.

It surfaces the concerns nobody volunteers: disruption, mess, timing, uncertainty. These frequently matter more to the buyer than the specification does. Addressing them in the quote is what wins against a cheaper competitor.

8. Repeat back what you heard

The verification.

A summary that they correct. This is where a misunderstanding is caught cheaply, rather than during the work where it is expensive. It also demonstrates that you listened, which is part of what they are assessing.

9. Say if the request is not the right answer

The difficult part.

Where the diagnosis is wrong, explaining why is more valuable than complying. Some buyers will proceed elsewhere, and the ones who stay are better customers.

Be careful about appearing to know their business better than they do. The questions work when they are genuinely curious and they irritate when they read as correcting somebody, so the tone matters as much as the content.

Conclusion

Ask about the situation rather than accepting the request.

Open with what is happening rather than what they want, establish what prompted it now, ask what happens if nothing is done to gauge severity and urgency, find out what has already been tried, get a definition of a good result in their own words, ask what would make it a poor experience, summarise what you heard so they can correct it, and say plainly when the thing they requested is not the right answer.