Solution Selling: Start With the Problem, Not the Product

Most enterprise sellers have lived through this one. The demo went well, the champion was enthusiastic, and then the deal went quiet, because nobody upstairs could say why the company needed it. The buyer didn't have a problem, or at least not one they were prepared to spend money on. Solution Selling exists to prevent that moment. It refuses to talk about the product until the problem is on the table and the buyer has said it out loud.

The premise is simple to state and hard to practice: people don't buy products, they buy solutions to problems they recognize as theirs. So the seller's job is to help the buyer recognize and articulate the problem, build a picture of what solving it looks like, and only then show that the offering fits the picture. Product comes last.

Where it came from

Michael Bosworth developed the method at Xerox in the late 1970s and early 1980s and founded Solution Selling Inc. in 1983 to teach it. His 1994 book Solution Selling: Creating Buyers in Difficult Selling Markets codified the approach, and it became one of the most widely adopted sales training programs of the 1990s, especially in enterprise software. Keith Eades later acquired the methodology, founded Sales Performance International, and updated it in The New Solution Selling (2003).

The context matters. Enterprise software in the 1990s was expensive, poorly understood, and sold to organizations that had never bought anything like it. Feature-led selling failed because buyers couldn't map features onto their business, and Solution Selling gave sellers a repeatable way to do the translation for them. The word "solutions" became so popular that it ended up in nearly every vendor's vocabulary, which is part of why the 2012 Harvard Business Review piece The End of Solution Sales argued the method had been hollowed out. Buyers, the argument went, now do their own diagnosis before they ever talk to a rep.

Where it fits

Solution Selling was built for enterprise SaaS and similar products. It works best when the offering is configurable or modular, so the same product solves different problems for different buyers; when the buyer is early in their understanding of the problem and needs help framing it; when cycles are long enough to run structured discovery; and when a demo without context tends to confuse more than persuade.

It's weaker when buyers show up with a well-defined requirement and a shortlist. The vision is already built at that point, and the job is differentiation. Challenger or Command of the Message usually do better there.

How it works

Solution Selling defines a process with its own vocabulary. The core stages:

1. Identify the pain

Every opportunity starts with a pain: a business problem the buyer admits to. The seller uses research and a pain chain, a map of how one person's problem creates problems for others in the organization, to find the pain that matters most. A missed forecast is the VP of Sales's pain. It becomes the CFO's pain when guidance is missed, and the CEO's when the board asks why.

2. Diagnose with the 9-Box Vision Processing Model

This is the signature tool. The seller works through a three-by-three grid of question types:

	Open	Control	Confirm
Diagnose reasons	"Tell me about..."	"Is it because...?"	"So the reason is...?"
Explore impact	"Who else is affected?"	"Does this also affect...?"	"So this impacts...?"
Visualize capabilities	"What would it take?"	"What if you could...?"	"So if you could..., would that help?"

Rows move the buyer from admitting the problem, to seeing its impact across the organization, to imagining a capability that would fix it. Columns move from open exploration, to gentle steering toward the seller's strengths, to confirming agreement. Done well, the buyer ends up describing the vision of the solution in their own words. Done mechanically, it sounds like an interrogation, which is the most common way the method goes wrong.

3. Create or re-engineer the vision

If the seller gets to the buyer before a competitor does, they help create the vision from scratch. If the buyer already has a vision shaped by someone else, the seller has to re-engineer it: surface the capabilities the current vision is missing and reframe what a good solution needs. The method is blunt about this. Arriving second means re-engineering, and a deal where you can't re-engineer the vision is usually one you should walk away from.

4. Qualify and get to power

The seller has to identify the power sponsor, the person who can actually approve the purchase, and get access to them through the champion. After key meetings, a sponsor letter (a written summary of the agreed pain, vision, and next steps) goes back to the buyer. It confirms alignment and, just as usefully, exposes the gaps when the buyer quietly disagrees with something in it.

5. Control the buying process

Solution Selling introduces the evaluation plan: a jointly agreed sequence of steps from where the deal is now to signature, with dates and owners. It's an early ancestor of the mutual action plan that's standard in enterprise sales today. The seller uses it to keep momentum and to notice when a deal has started drifting.

6. Close

The close follows from the evaluation plan. Pain, vision, power, and process are already established, so the negotiation is about terms rather than about whether to buy at all.

A worked example

A seller of expense management software targets a fast-growing services firm. Research turns up a plausible pain: finance closes the books ten days late every month. Discovery confirms it, and the pain chain shows that the late close delays investor reporting, which the CFO cares about a great deal.

Working through the vision model, the seller learns the delay comes from employees submitting expenses late and from manual reconciliation. "What if expenses were captured at the point of purchase and reconciled automatically?" The controller says that would take a week off the close. That's the vision, in the buyer's words. The seller confirms it in a sponsor letter, gets introduced to the CFO, and agrees an evaluation plan that ends with a decision before the next quarterly close.

Strengths and limitations

The method gives a sales team a shared language and a disciplined path from problem to purchase. Its weaknesses are real, though. Run mechanically it feels scripted, and it assumes the buyer needs help building a vision, which is less true now that most buyers have done a lot of research before they take a call. Most teams we see combine its discovery structure with a qualification framework like MEDDIC and borrow a teaching posture from Challenger.

Key takeaways

• Solution Selling starts with a pain the buyer admits to, and holds the product back until then.
• Bosworth built it out of Xerox sales training in the late 1970s and codified it in 1994.
• The 9-Box model walks the buyer from reason to impact to capability, in their own words, and it's the part that goes wrong when run like a script.
• If you arrive second, you re-engineer the vision or you walk.
• The evaluation plan is where today's mutual action plan came from.

The evaluation plan only works if someone is watching it. When a step slips, a revenue orchestration platform can flag it as a revenue signal and put the next action in front of the rep before the deal turns into the slippage every forecast dreads.