There’s something seductive about dividing consultants into two neat camps.
On the one hand, you have those who sell what they know: frameworks, playbooks, checklists, best practices. They close the knowledge gap between “we don’t know how to do this” and “now we do.” On the other hand, you have those who are drawn to hard, messy problems: people who want to sit in the fog with you, think with you, and help you see what’s really going on.
The first type essentially sells answers. The second type sells thinking.
I think that distinction points at something real.
If you strip it down, you can recognise these two archetypes everywhere:
The knowledge‑seller has a known solution and looks for situations where it fits. They specialise in codifying what works and delivering it efficiently. They get better by seeing the same pattern again and again, and shaving friction off implementation.
The problem‑solver is more interested in the shape of the problem than in the comfort of a familiar solution. They get energy from constraints, ambiguity, and “this doesn’t quite behave like the last ten I saw.” They get better by expanding their pattern library and refining their judgement.
If you’re rolling out a known CRM or setting up a standard analytics stack, you probably want a knowledge‑seller. If you’re trying to figure out why growth has stalled, why teams keep building features nobody uses or how to turn a legacy backend into a usable platform, you probably want a problem‑solver.
The knowledge‑seller learns primarily from repetition:
Each engagement is a chance to polish the same core offering.
They learn which slides land, which objections come up, where clients get stuck.
Over time, the offering gets smoother, clearer, more “productised”.
There’s a risk hidden in that learning loop: it’s mostly confirmatory. You get rewarded for getting better at selling and delivering what you already know, not for questioning whether the thing itself is still the right answer. You can end up as the world’s most efficient implementer of something the world no longer particularly needs.
The problem‑solver’s learning loop is messier and wider:
They learn from peers and other experts, yes – but also from adjacent domains, from odd constraints, from the ways organisations behave under pressure.
They pay attention to how problems show up, not just which solution ultimately worked.
They’re constantly building a private library of “I’ve seen something like this before, but never quite like this.”
Their risk is different: it’s easy to drift into abstraction, or to underestimate how much clients value clarity and repeatability. Not every situation needs a bespoke theory of change.
As with most tidy dichotomies, this one starts to fray the moment you look closely.
Most good consultants are hybrids. They may start as knowledge‑sellers and slowly earn the right to do deeper diagnostic work. Or they start as problem‑solvers and, over time, crystallise some of their thinking into reusable patterns. The work swings between these modes inside a single engagement.
Both are selling more than they think. The knowledge‑seller isn’t really selling a PDF or a framework; they’re selling reduced risk and borrowed confidence. The problem‑solver isn’t just selling thinking; they’re selling the courage to look at the real problem and act on it.
There’s a missing third leg: execution. Increasingly, there’s a category of consultant whose main value isn’t a framework or a diagnosis, but the ability to get things over the line in ugly, political, constrained environments. They’re paid not for ideas, but for making decisions and absorbing friction.
In other words: “what you know” and “how you think” are important axes, but they’re not the whole map.
Even if it’s imperfect, the distinction is still useful, especially for consultants themselves.
If you see yourself primarily as a knowledge‑seller, the strategic questions are:
Is what I know becoming more common or more scarce?
Am I investing in depth, or just in packaging?
How do I keep my offer from turning into something an AI or a template can do?
If you see yourself primarily as a problem‑solver, the questions change:
How do I make my thinking legible and valuable to clients who don’t live in my head?
Where do I build enough structure that clients feel safe, without pretending every situation is the same?
How do I keep one foot in the messy reality of shipping, not just in the comfort of diagnosis?
For clients, the distinction is a reminder to ask not just “who has done this before?” but also “what kind of help do we actually need here – an answer, a partner in thinking, or someone who will drag this over the finish line?”
For people who recognise themselves more in the second type, there’s both good and bad news.
The bad news: “I like hard problems” is not a proposition. It’s a personality trait.
The good news: done well, problem‑solving scales better than knowledge that can be easily copied. But only if you translate your way of thinking into:
problems you are the first person they call for
outcomes that are obvious and concrete
stories that make your invisible work visibleThat’s where this neat little two‑type sketch stops being a taxonomy and starts being a mirror. It’s less about sorting consultants into boxes, more about asking: what exactly am I selling, how do I get better at it, and is that still the thing the world will happily pay for?