Sales

You Asked the Questions. Did You Change the Proposal?

Why consultative selling shows in the recommendation, not just the questions.

Bogdan Vizitiu at a café

Imagine two sales meetings. In the first, a salesperson presents a solution after asking a few questions about the customer's needs. In the second, the salesperson explores the situation, identifies problems, discusses goals and checks priorities. Both end up sending the same standard proposal.

Which one practised consultative selling? A proposal does not have to change after every conversation. Sometimes the original solution is exactly right. What matters is being able to explain why.

To me, this is where the difference becomes visible between following the stages of a sales process and using them to make better decisions.

From listening to value

In the previous article on perceived listening, we explored how feeling heard is more strongly associated with relationship quality than with performance. A good conversation and a good recommendation are not automatically the same thing.

Alnakhli, Inyang and Itani analysed data from 201 B2B salespeople in industrial goods, combining questionnaires with objective sales performance indicators. Their study in the Journal of Business-to-Business Marketing found positive associations involving listening, communication, adaptive selling and value co-creation, as well as between value co-creation and sales performance.

Value co-creation also played a mediating role in their model. These findings do not prove that changing a proposal causes sales to increase. They do invite us to examine not only whether the salesperson listens, but what the salesperson and customer build from the information exchanged.

The client asks for negotiation training. What problem are they trying to solve?

A sales director requests negotiation training for the team. The immediate response might be a course brochure with modules, duration, methods and price. But why negotiation? Where does the team struggle? At which points are opportunities lost?

The conversation might reveal that the team knows negotiation techniques but starts discussing price too early. They do not explore customer needs deeply enough and offer discounts before establishing value.

A programme focused exclusively on negotiation might miss the real problem. A more relevant recommendation could include needs discovery, decision criteria, value articulation and only then negotiation. We have not simply rearranged modules. We have changed the diagnosis and therefore the recommendation.

Adaptation is not telling every customer what they want to hear

Adaptive selling is sometimes reduced to communication style: be direct with one customer and provide more detail to another. Yet adaptation can go beyond tone.

Two customers request the same software. One wants to reduce time spent on repetitive work; the other cares most about operational control and error risk. We could show both the same features in a different order. Or we could offer different recommendations: automation and time-saved measures for the first, traceability, checks and controlled implementation for the second.

The product may remain unchanged while the demonstration, configuration and evaluation criteria differ. Adaptation does not necessarily mean changing the product. It means changing the recommendation for a defensible reason. If the product cannot meet an essential need, additional promises are not the answer.

The customer's criteria are not necessarily ours

Experience helps salespeople recognise familiar situations quickly. It can also encourage them to assume they know what matters to a customer.

Szymanski and Churchill compared the cues salespeople use to evaluate prospective customers. They found differences in how particular cues were weighted and in the standards used for evaluation. The study did not directly examine proposal customisation, but it shows how the same information can be interpreted differently.

A customer may say that price, quality, implementation speed and support all matter. The decisive question is what happens when trade-offs are necessary. Would they pay more for faster implementation? Prefer fewer features with stronger support? Without ranking these criteria, we risk designing a proposal around our own priorities.

What does 'too expensive' actually mean?

A price objection shows how easily we can respond to an interpretation rather than the underlying problem. 'Too expensive' might mean an insufficient budget, a cheaper competing offer, unclear benefits or difficulty justifying the investment internally.

Each situation calls for a different response. Sometimes the configuration needs reviewing; sometimes the customer needs evidence, evaluation criteria or a meaningful comparison.

Before arguing, one question can redirect the discussion: 'When you say it is too expensive, what are you comparing it with?' The value lies not in the question itself, but in using the answer to decide what to do next.

What remains after training?

For a sales manager, the challenge does not end with teaching people to ask questions. It also matters which behaviours managers observe and discuss afterwards.

In an exploratory study involving 420 non-retail salespeople, Pelham and Kravitz examined relationships between training content, salesperson evaluation and consultative behaviours. Evaluation against consultative criteria was more strongly associated with the behaviours examined than training content.

This does not prove that evaluation automatically changes behaviour or that training is ineffective. It does raise a practical question: if we measure only meetings and closed revenue, how do we observe the quality of the sales diagnosis? We can also discuss whether a salesperson checked priorities, corrected an assumption and justified the recommendation.

Value is not built only during the presentation

Needs discovery is not a ritual before the product presentation. It is how we determine what deserves to be recommended, and why.

A standard proposal may be exactly right. A customised proposal may be wrong. The difference is not the number of changes but the connection between the identified problem and the proposed solution.

After a sales meeting, the useful question is not only 'Did I ask the right questions?' but 'What did I learn from the customer, and how did it influence my recommendation?' If we can answer specifically, we have a solid starting point for consultative selling. If not, perhaps we heard the answers without allowing them to change anything.

The decisive question is not how many questions we asked, but what we did with the answers.

Turn sales conversations into relevant recommendations

Explore Sales Lab

Sources and context

Editorial article drawing on research into value co-creation, customer evaluation and consultative behaviours. Examples are illustrative, not documented personal experiences.

Back to insights