Consultative vs Solution Selling and When to Use Each

What separates consultative selling from solution selling?

They are different methods. The difference is timing. Consultative selling starts before the buyer has a clear problem, and the seller's first job is to help define it. The solution-selling method starts once the problem is defined, and the seller's job is to match a combination of products and services to it.

Both put the buyer's problem ahead of the product, which is why the two names get swapped so often.

The dividing rule is one question: how well does this buyer already understand their own problem? If they can name the problem, its cause and what it costs them, open as a solution seller. If they can only describe what hurts, open as a consultant. Both tables below apply that question row by row.

Consultative selling has a named origin. According to the publisher's description of his book, consultative selling was invented by Mack Hanan in 1970 (Google Books).

His consultative seller sells the customer an improvement in profit, with the product as the means to get there, and presents the price as an investment the customer makes in that gain. The sale goes to mid-level and top managers, inside a long relationship instead of one bid after another.

Solution selling is the more structured model. Harvard Business Review described it in 2012 as reps working out what a customer needs and then selling a complex mix of products and services that answers those needs (HBR, 2012). The rep still asks questions, but the conversation is aimed at a problem the buyer can already point to.

How do consultative and solution selling differ, point by point?

Rows one and two are the rule itself. The consultative seller works with a buyer who is still guessing at the cause, so the problem gets built in the room. The solution seller works with a buyer who walked in with a definition, so the seller tests it and moves on.

The middle rows follow from that starting point. When the problem is not agreed, the first meeting exists to agree on it, and open questions do that work. When it is agreed, the first meeting exists to confirm fit, and short confirming questions respect the buyer's time.

The last row is where deals die. Consultative selling used on a buyer who knows exactly what they need feels like an interrogation about things they already wrote in their email. Solution selling used on a buyer who only feels symptoms produces a clean demo of the right product for the wrong problem, and the deal stalls quietly after the meeting.

Which one should you use for your next deal?

Use the buyer's own words as the signal. The table gives a starting method for six common situations and the moment to switch.

Each row is an opening move. The last column tells you when to drop it.

The same buyer, handled both ways

This example is hypothetical, built only to show the rule. A software company sells project scheduling tools to construction contractors. The buyer is the operations director at a US general contractor with 40 active sites.

Version A: she knows the symptom. Her reply to an outreach message says: "Our projects keep slipping. Open to a chat." That is a symptom, so the rep runs a consultative meeting. Where do the slips start? What did the last three late projects have in common? What does a week of delay cost on a typical job?

Halfway through the meeting she names the cause herself: subcontractor date changes reach the team too late, so the site plan is wrong for days. Now there is a problem with a cause. The rep recommends the part of the product that pushes subcontractor changes into the site plan, plus a weekly update routine for site managers, and leaves the rest of the platform out of the first proposal.

Version B: she knows the problem. Same company, same director, a different reply: "We are replacing our spreadsheet schedules this quarter. Can you show how you handle 40 sites and subcontractor updates?" She has done the diagnosis already. The rep confirms the number of sites and users, the systems it must connect to, the deadline and who signs. Then he shows exactly the subcontractor workflow she asked about and sends a proposal against her criteria.

Now swap them. Run Version A as a solution sale, and the rep demos dashboards to a director who has not yet named her problem. She nods, thanks him and goes quiet. Run Version B consultatively, and the rep spends 40 minutes asking about things she already put in writing. She books her next call with the vendor who simply showed her the workflow.

Why does neither method work on its own anymore?

Buyers now do much of the defining before they talk to anyone, and both pure methods were built for a different buyer.

A 2012 HBR piece made the first half of that case. Its argument is that customers no longer need sellers the way they once did, because procurement teams and purchasing consultants with plenty of data now define solutions for themselves.

Solution selling worked when buyers understood their problems but not how to fix them. When the buyer arrives with the fix already written into a requirements sheet, a pure solution seller is left quoting against it. This is the authors' argument and no statistic backs it.

Numbers came with a 2017 HBR piece, "The New Sales Imperative". It drew on a CEB survey of over 600 business buyers. Responsive selling means the rep follows the buyer's lead. It cut purchase ease by 18%. Purchase ease is how easy buyers found it to complete the purchase. Prescriptive selling means the rep tells the buyer what to do next. It raised purchase ease by 86% (HBR, 2017).

The article never uses the words consultative or solution, so the mapping is my reading. Responsive selling is what pure consultative selling becomes when the seller keeps asking and never recommends.

The same article reports buying groups growing from an average of 5.4 people to 6.8 in two years. Every extra person brings their own version of the problem, so it pays to know how big B2B buying committees actually are before you pick a method.

The newest data points the same way, though it measures buying preference, not method. Gartner surveyed 646 B2B buyers in August and September 2025 and released the results in March 2026. Of those surveyed, 67% preferred a purchase with no sales rep involved, and a separate 45% had used AI during a recent purchase (Gartner).

Put those together and the buyer arrives half-defined. They have researched, often with AI, built a shortlist and formed a theory of their problem, and that theory may be wrong. Buyers want help on exactly that point. A 2025 Gartner survey of 632 B2B buyers found they prefer seller input when judging whether a product or service fits their company's needs.

A pure solution seller takes that theory on faith, and a pure consultant starts over as if it did not exist. The better move is to test it in a few questions, then recommend with conviction.

What does a hybrid of the two look like in practice?

Diagnose, then prescribe, then confirm. Each phase has a clear finish line.

1. Diagnose. Ask consultative questions until the buyer states the problem in their own words and agrees with the cause. The phase is done when you can write a one-sentence problem statement the buyer would sign.
2. Prescribe. Recommend one path and say why, including what you would leave out. This is the prescriptive move from the 2017 research: tell the buyer what to do next, in what order, and what tends to go wrong.
3. Confirm. Take the problem statement and the recommendation to every person in the buying group before the proposal goes out. A proposal built on one person's definition gets picked apart by the people who never agreed to it.

Signs it is time to stop asking and start recommending:

1. The buyer has repeated the problem back to you without prompting.
2. You can state the cause and the cost in one sentence each.
3. Your last two questions produced nothing new.
4. You know who else signs off, and how they decide.
5. The buyer asks some version of "so what would you do?"

There is also one sign to go back. A new person joins the call and describes a different problem. Return to diagnosis with that person before you defend the recommendation.

Booking a call and closing a deal are two different jobs. A rep who treats the meeting itself as the win runs the hybrid as one long friendly chat. The buyer enjoys it, the notes look full, and nothing gets signed. Conversations come first, but a conversation that never ends in a recommendation is still only a conversation.

What happens to the method before the meeting is booked?

My team's work ends where the meeting starts: we handle appointment setting through cold email and LinkedIn outreach, and the client's own sales team runs them and closes the deals. So I will not tell you how your rep should handle minute twelve of a call. What I can describe is what reaches the rep before minute one.

I treat the sale as something that starts online, long before the call: by the time a buyer joins, they have read your site, checked the person they are about to meet and decided how seriously to take you.

Nobody buys from an email. Their buying starts after they have examined you. The same message has gone out from two different companies in front of me. One got 2% replies. The other got 7.5%. Only the sender changed.

The reply is the first evidence of awareness. "Interesting, we have been struggling with late handovers" names a symptom. "We are reviewing vendors for this, can you send details?" names a defined problem.

The first thing a new campaign gives me is feedback: which angle earns replies and which titles answer. Read every reply for awareness too. Pass the reply wording to the rep along with the booking, so they walk in knowing which row of the decision table they are in.

The message itself decides who replies. Write for everyone and you reach no one. One client described what we do as translation: "You translate what we do into what people actually want to buy."

Pick one service and one audience, and the replies get easier to read. A broad message also books meetings with buyers at every level of awareness, and the rep finds out which kind they got only when the call starts. The method gets chosen by accident.

Write one message per awareness level instead. Here is a hypothetical opener for the symptom-aware buyer from the example above:

Subject: when a subcontractor moves a date

Hi Maria, a quick question about your sites. When a subcontractor changes a date, how long until the site plan and the client schedule show it? If that is worth comparing notes on, would a 20-minute call next week work?

It asks one diagnostic question and sells nothing, because the first message only has to earn a reply. A reply to this one is likely to describe a symptom, so the rep should prepare a consultative first meeting. For a buyer with a defined project, write the opposite message: name the project, name the criteria they are probably judging on, and offer to show exactly that.

Between the reply and the calendar sits qualification. When you qualify a lead before it goes on the calendar, ask two questions that tell the rep which method to open with: what are you trying to fix, and have you looked at other options yet?

When a company books plenty of calls and closes few, more calls will not fix it: they spread the same sales problem across more prospects and make it more expensive, because a booked call proves little before a deal closes.

This week, pull your last 10 booked meetings. Sort each one by the buyer's first reply into "named the problem" or "named a symptom", then check which method your rep actually ran. Every mismatch shows where the method and the buyer did not fit.

Unsure whether your buyers need a consultant or a solution seller? Talk it through on a call and describe your last three deals. We will work out which method fits.