Stop Selling Solutions, Start Solving Problems
- Claas
- Jun 12
- 3 min read
My former strategy professor once used the metaphor of a "haircutting machine" in one of his books. The customer puts their head into an opening, selects hair length and style on a dial, presses a button and within seconds, the haircut is done. The patent attorney raised an objection: "But people have different shaped heads." The inventor’s response? "Only beforehand."
Of course, the story is exaggerated, but it remains alarmingly relevant in the consulting world. Too often, we design solutions, or even full proposals, that only work if reality reshapes itself to fit. But consulting shouldn't be about building machines for uniform outcomes. It should be about understanding real problems and creating tailored solutions.
The trap of the prepackaged solution
Even at the proposal stage consultancies often go to clients with ready-made offerings: methods, templates, and solution packages. They look sharp, they’re structured, and they work great in PowerPoint. But they’re quickly mistaken for the solution itself. The impression arises: surely the problem fits this solution.
This doesn’t just happen in project delivery. It starts as early as the proposal phase. Jumping to a solution without fully understanding the problem risks misalignment, and in many cases, losing the deal altogether. Clients can sense when an answer comes before their question is even fully heard.
There’s also a subtler risk: when we pitch a solution too early, we stop listening. We guide the conversation toward our product or framework rather than staying open to what’s actually needed. Over time, this narrows our relevance and erodes our credibility.
Reuse is valuable. Good frameworks save time. But a toolbox doesn’t replace a diagnosis. If you always turn the same screw, you’ll miss when the problem is actually a nail. Repetition without reflection turns experience into rigidity.
When the answer comes too soon
I’ve seen projects where a solution was selected before the actual issue was understood. Sometimes the client asked for “X,” but what they truly needed was “Y.” We came in with all the right slides - but missed the mark.
These projects often lose momentum early. The impact is minimal. The team ends up executing a plan instead of solving a problem. The same applies to proposals that look impressive but lack real insight into the client’s situation.
Worse, once the direction is set - especially in a formal proposal - it’s difficult to challenge later without undermining confidence. The room for course correction narrows. And when the results don’t materialize, no one feels empowered to say, "We misunderstood the problem."
Real help starts with understanding the problem
What matters most is listening. Asking good questions. Thinking critically. Not rushing to provide the fastest answer, but identifying the right question. That means resisting the urge to sell first - and instead seeking to understand.

Comments