In short
- An explanation break is not disinterest. The prospect is often still engaged, but the explanation has gone further than they can follow, or the person carrying it forward has lost the thread.
- Choice confusion, competitive doubt, and workflow questions are three different breaks, and each wants a different drawing.
- A decision tree settles which option fits. A matrix settles why you over the alternative. A sequence settles how it slots into what they already do.
- Test any model on a champion who was not in the room. If they cannot use it without you, it is not finished.
- A complex sale usually needs more than one drawing, not one drawing trying to do everything.
What is a B2B explanation break, and why does it stall a deal?
An explanation break is the moment a prospect stops following the argument, and it is worth separating from a lack of interest because the fix is completely different.
But the prospect can be genuinely engaged and still lose the thread. Maybe the explanation went further than they can restate. Maybe the person carrying it into the next room, a champion rather than you, never had the full picture to begin with. Either way, the break has a shape, and the shape tells you what to draw.
A few common ones. Somebody understands the feature list but not how it solves their specific bottleneck. A champion believes in the approach but cannot say why it wins against a named competitor. A technical buyer can see that it works but not how it fits what they already run. Three different breaks, and reaching for the same slide deck for all three is why the deck stops working the third time.
When does choice confusion call for a decision tree?
When the question is which one, not whether. "Is this for a company like ours?" "Do we need the bigger tier or the standard one?" Those are routing questions, and a paragraph answers them badly.
So a decision tree is a sequence of yes-or-no questions that ends at a recommendation, and its real value is that it takes you out of the room. A champion can walk a stakeholder through it asynchronously or in a committee meeting neither of you attends, and the stakeholder reaches your recommendation on their own steam. The criteria that decide it, a budget line, a scale threshold, a compliance requirement, sit right there on the page instead of living in your head.
But it does not do everything. If the buyer already knows which product fits and is asking why you over a named alternative, a tree adds nothing, because that is a different break entirely.
When does a competitor objection call for a matrix?
A matrix plots you and the alternatives against two things the buyer actually weighs, ease of setup against depth of customisation, say, or total cost against how well it plugs into what they run.
So this is the drawing for "doesn't competitor X do the same thing" and "why not the cheaper one." It turns an argument into a pointing exercise. Instead of contesting the claim, your champion shows where each option sits and lets the buyer decide which dimension matters more to them.
And it also does something for the champion personally. Reciting a feature comparison from memory sounds like a script. Pointing at a drawing and saying "we're strong on these two, and those are the two that matter here" sounds like judgement, and it does not depend on your champion remembering your talk track.
When does a workflow question call for a sequence?
A sequence is the step-by-step: first this, then this, then this. It is the right drawing when somebody understands what your product does on its own but cannot see how it connects to what they already do.
Picture a data platform explained as five steps: bring the data in, clean it, run the analysis, hand back the result, act on it. Label each step with who owns it, how long it takes, what comes out the other end. The prospect now sees not just the product but where in their own week it lands, and which of their current steps it quietly replaces.
And a sequence keeps paying after the deal closes, too. The same drawing that explained the rollout during the sale can walk the customer's own team through setup and training once they are through the door.
Where does a canvas fit, and should you trust the fourth box?
Worth being honest here. A canvas, a multi-panel view like the well-known nine-block Business Model Canvas, shows how several parts of a system depend on each other at once: customers, what you offer them, how the money moves, what it costs to deliver.
It is useful when a prospect who thinks your product only touches one team needs to see that it also changes finance's forecasting, or procurement's supplier list, or an executive's view of cost. A feature list will not show that kind of knock-on effect. A canvas can.
Scroll the table sideways to see every column.
| Drawing | Answers | Runs out when |
|---|---|---|
| Decision tree | Which option fits | The buyer already knows which one, and is asking something else |
| Matrix | Why you over the alternative | The question was never about a competitor |
| Sequence | How it fits what we already do | The buyer already understands the workflow fit |
| Canvas | What else in the business does this touch | The product only ever touches one team |
Treat that fourth row as the least tested of the four. The other three show up across most of the explaining we do. A canvas is the right shape for a genuinely multi-team knock-on effect, and it is worth building one the day you actually have that shape of problem, not by default.
Test it before a prospect ever sees it.Hand the drawing to a champion who was not in the room and ask them to walk a colleague through it. If they cannot, without calling you, the drawing is not finished yet. That is a cheaper place to find the gap than the deal where it actually mattered.
At Strategem this is the work. We do it for a champion who has to explain it internally, for a buying group that takes too long to agree, and for a product that takes too long to explain.
Why do visual models loosen founder dependency?
Because a founder can improvise their way through a break that a champion cannot, and every deal that needs the founder in the room is a deal that waits on the founder's calendar.
The founder holds the full context and can adapt on the fly. Nobody else on the team can reproduce that on demand, which is exactly why the same explanation keeps landing on the founder's desk in a new outfit each time. Give a champion a drawing instead, and the explanation stops living in one person's head. They point, they ask a clarifying question, the drawing does the carrying.
And that changes the shape of a quarter, not just one meeting. Deals stop queuing behind one calendar. Several conversations move at once. An internal stakeholder review can happen on a Tuesday the founder never hears about, because the argument travels without them.