You pull up the funnel report. MQLs are fine. SQLs took a hit. Somebody asks why, and the honest answer is: nobody actually knows. The stage tells you where the deal stalled. It has nothing to say about what stopped it there.
That’s the problem with running a funnel as your model of the buyer. A funnel measures motion. It was never built to explain why motion stops. If you want to fix a stalled pipeline instead of just reporting on it, you need a different question: not “where are they,” but “what’s in their way.” Here’s how to build a friction map instead of a funnel report, and why that shift changes what your team spends time fixing.
The funnel answers “where.” It can’t answer “why.”
A funnel is a reporting structure dressed up as a strategy. It tells you a prospect moved from MQL to SQL, or didn’t. It can’t tell you whether they stalled because the pricing page confused them, because sales took four days to respond, or because the buyer looped back to re-pitch their own CFO and got stuck doing someone else’s job for them. Three completely different problems produce the exact same funnel chart: a flat line between stages.
Real buyers don’t move in a straight line anyway. They loop, they stall, they ghost for six weeks and come back with a different champion. A funnel assumes a buyer who walks a hallway from one room to the next. Most B2B buyers are doing something closer to shopping with four other browser tabs open and a Slack channel full of skeptical colleagues. The stage-based view isn’t wrong exactly. It’s just incomplete in the one place that matters: the “why.”
Friction has three different sources, and they need three different fixes
Friction over Funnels, one of the core principles behind the adaptive GTM model, starts from a simple reframe: funnels describe motion, friction explains why buyers stop. Once you start looking for friction instead of stage, three categories tend to show up.
Buyer friction is the most visible kind. It’s confusion about what the product actually does, a pricing page that raises more questions than it answers, a demo that doesn’t match the buyer’s actual use case. This is the friction most teams already hunt for, because it’s the easiest to see on a recording or hear on a call.
Operational friction lives inside your own house. It’s the lead that sits in a queue for four days because routing rules weren’t built for this segment. It’s sales and marketing arguing about lead quality when the real issue is a handoff that nobody owns. Operational friction rarely shows up in a funnel chart at all, because the funnel only tracks the buyer’s movement, not your team’s.
Learning friction is the quiet one, and it’s usually the most expensive. It’s paying to relearn the same lesson every quarter because nobody captured it the first time. The rep who figured out the exact objection that kills deals in this segment leaves the company, and six months later a different rep hits the same wall and has to work it out from scratch. A funnel can’t catch this at all. It has no memory built in.
Mapping friction stage by stage instead of just counting conversions
The practical move is to take whatever stages you already track and, instead of only asking “how many converted,” ask “what had to be true for someone to move forward, and what got in the way for the ones who didn’t.” That’s a different kind of audit, and it needs different inputs than a conversion report.
Two sources matter here, and most teams only use one of them. Quantitative data, the stuff your funnel already shows you, tells you where the drop happened. It’s reliable, but it lags; by the time the numbers confirm a problem, you’ve usually been living with it for a quarter. Qualitative signal, the actual language buyers use on calls, in support tickets, in sales notes, tends to show up earlier. It’s messier to collect, but it leads. Most teams flip this pyramid and over-index on the lagging numbers because they’re easier to put in a slide.
The qualitative layer is also where you find what’s called a micro-narrative: the specific line a buyer keeps saying, almost word for word, across unrelated calls. “We already tried something like this and it didn’t stick.” “I need to show this to our ops lead before I can move.” That one sentence, repeated by five different prospects, is worth more than a funnel stage, because it tells you exactly what friction you’re dealing with and who owns the fix.
A friction audit you can run this week
You don’t need a new platform to start this. You need an hour, a handful of recent deals, and a willingness to ask a different question than “where did they drop off.”
- Pull ten deals that stalled in the last 60 days, a mix of ones that eventually closed and ones that went quiet.
- For each one, listen to or read the last three touchpoints before the stall, and write down, in the prospect’s own words if you can, what they said was holding them up.
- Sort those notes into the three friction types: buyer, operational, learning. Most teams find the split isn’t even close to what they assumed.
- Pick the single most repeated line across all ten deals. That’s your micro-narrative. It’s probably not what’s on your competitive battlecard.
- Assign the fix to whoever actually owns that type of friction. A confusing pricing page is marketing’s. A four-day response lag is sales ops’. A lesson nobody captured is a process problem, not a messaging one.
That’s a diagnostic, not a campaign. It’s meant to tell you where to point real effort, not to replace your funnel reporting. Keep the funnel. It still tells you where things happened. Just stop asking it to explain why, because that was never its job.
The one thing to remember
A funnel shows you where a buyer stopped. It can’t tell you why, and chasing conversion rate by stage without understanding friction type just means you keep fixing the wrong thing faster. Separate buyer friction from operational friction from learning friction, and you’ll find the fix usually belongs to a different person than the one currently getting blamed for the drop.
Pull five stalled deals this week and run the audit above. You’ll probably find the real blocker isn’t where your funnel said it was.