Sell the Solution, Not the Product: Five Discovery Questions

A customer asks for a quote on a specific product. The sales team prepares a careful proposal with specifications, prices and timelines. Weeks later the answer comes back: another supplier was chosen, or the project was postponed. The product was rarely what failed. More often, nobody had understood what problem the customer wanted to solve.

Behind almost every request sits a need that does not always match what was asked for. A good discovery conversation is how that need gets found before anything is offered.

Why ask before proposing

In complex sales, the customer usually knows the problem better than the solution. But pressure to move forward pushes both sides to discuss specifications too soon. The result is a proposal that answers what was requested, not what is needed.

Consultative selling reverses the order: understand first, propose second. The approach is associated, among other works, with SPIN Selling by Neil Rackham, which studied how questions shape long-cycle sales. What follows does not reproduce that method. These are five questions in our own words, useful in a first conversation.

Question one: what happens if nothing is done this year?

This question tests real urgency. If the answer is "nothing serious," the project probably competes with many other priorities. If it describes losses, risks or pressure from outside, the tone of the conversation shifts.

It also reveals what the customer fears. Often the reason that surfaces is not the one written in the original request.

Question two: who else has to agree for this to move forward?

In a business purchase, one person rarely decides alone. Asking who takes part in the decision is not prying. It is understanding the real path to approval.

It works best when asked calmly and with respect, as a way of preparing a better proposal. The answer often brings in teams that were absent from the conversation, such as finance, legal, operations or security, each with its own concern.

Question three: how do you measure today whether this works?

A project with no way to judge its result is hard to defend in front of leadership. This question helps the customer put expectations into words and helps the seller align the proposal with a criterion that can be checked.

If the customer has no answer, that is valuable too. It may be a chance to help define the measure, which tends to strengthen the relationship.

Question four: what has been tried before, and what was missing?

Almost no business problem is new. Someone has already tried to solve it with another supplier, an in-house build or a partial fix. Knowing that history avoids repeated mistakes and shows what the customer hopes will be different this time.

The question should come from curiosity, not criticism. The goal is to learn, not to point at what others did wrong.

Question five: what would have to be true a year from now for this to have been worth it?

This is a question about the future that forces a description of success. The answers are often more concrete and more human than expected: fewer incidents, a calmer team, a report that finally arrives on time.

That description becomes the thread of the proposal. Instead of listing features, the proposal explains how to get to that outcome.

An example

What follows is an invented example to show the kind of conversation. It does not describe a real case.

A customer asks for a quote to renew an internal platform. Instead of sending prices, the sales team asks what would happen if the platform were not renewed this year. The answer mentions that the operations group loses a lot of time on manual tasks at every month end. Asked how that is measured today, they find that nobody measures it. The final proposal centers on cutting that manual work and on how to track it, with the platform renewal as a means to reach it.

The requested product did not change. What changed was the reason the customer would choose it.

Common mistakes

• Turning the questions into an interrogation. The five questions are not asked back to back. They are spread across the conversation, with real listening in between.
• Asking what could have been learned beforehand. Doing the homework before the meeting shows respect for the customer's time.
• Answering too soon. If every answer is met with a product feature, the talk slides back into specifications.
• Not taking notes. The customer's answers are raw material for the proposal, best returned in the customer's own words.

Recording what was learned

A simple page with the five questions and the customer's answers, in the customer's own words, becomes the base for the proposal and for the next conversation. It also helps anyone who joins the sales team later to see what was discussed and why the proposal has the shape it has.

Closing thought

Nobody buys a tool for the tool. They buy the peace of mind, the result or the improvement they believe it will bring. Whoever helps uncover and express that need becomes more valuable than a supplier of specifications.

What question would you add to this list to better understand a new customer?