The demo goes well. The buyer leans in, asks sharp questions, nods at the right moments, maybe even says something like "this is exactly what we've been trying to solve." The rep hangs up feeling good, logs a strong note in the CRM, and moves the deal to the next stage. Then nothing. A follow-up email gets a one-line reply. A second one gets nothing at all. Three weeks later the deal is quietly rotting in the pipeline, and nobody on the sales team can explain what happened, because as far as they could tell, everything happened.
This is one of the most common — and most misread — patterns in B2B sales. Teams treat it as a mystery. It isn't. A good demo measures how well the seller performed in the room. It does not measure whether the buyer has the intent, authority, or internal appetite to actually buy. Those are different questions, and the room is the worst possible place to answer the second one.
Engagement in the room is a demo skill. Follow-through afterward is a buying decision. Confusing the two is how forecasts get built on nothing.
Interest is cheap. Intent is expensive.
Nodding along costs a buyer nothing. Asking a good question costs nothing. Saying "this is exactly what we need" in the moment, with a helpful rep watching your reaction, costs nothing. What costs something is going to your VP and asking for budget that was earmarked for something else. What costs something is telling your own team you want to change a process they've tolerated for two years. What costs something is being the person who championed a new tool that turns out to be a hassle to roll out.
None of that shows up during the demo, because none of it is required yet. The buyer in the room is evaluating whether the thing looks good. The buyer after the call is the one who has to decide whether it's worth the internal cost of getting it. Those are two different people wearing the same face, and the second one only shows up once the seller has left the room.
Where the resistance actually moves
When a demo stalls afterward, the friction didn't appear out of nowhere — it moved. It was there all along, just invisible to a conversation focused on features and use cases. A few places it tends to resurface:
- Internal selling — the champion now has to repeat your pitch, badly, to people who weren't on the call and don't share their enthusiasm.
- Pricing the change — the buyer has to translate "this looks useful" into a number their finance process will accept, and that math often doesn't survive contact with a budget owner.
- Defending the decision — the champion has to be ready to answer "why this, why now, why not what we already do" from a skeptic on their own team.
- Quiet doubt that never got voiced — a concern the buyer didn't want to raise mid-demo because it felt impolite, or because they weren't sure yet whether it was disqualifying.
A rep who only pays attention to the call will miss all four, because all four happen after the rep has hung up. That's why "the demo went great" and "the deal is stalled" aren't contradictory — they describe two different phases of the same decision, and only one happened in the room.
Reading the silence instead of chasing it
Most reps respond to post-demo silence with more volume: another check-in, a slightly more urgent subject line, a "just floating this back to the top of your inbox." That treats silence as a scheduling problem. It usually isn't. Silence after a strong demo is data about where the buyer got stuck — and the shape of the silence tells you which kind of stuck.
A champion who goes dark immediately after being visibly excited is often stuck on internal selling — they liked it, and now they're realizing how much work it will take to bring their org along. A champion who engages briefly, asks about pricing detail, then disappears is often stuck on the number, waiting to see if it's defensible before they resurface. A champion who never quite commits to a next step, even while saying encouraging things, may be sitting on a doubt they never said out loud. The mistake is treating all three the same way — with a generic nudge — when each one calls for a different kind of follow-up.
Planting questions during the demo, not after
The fix starts earlier than the follow-up email. A demo that only shows the product and waits for objections is leaving the real resistance data on the table. A better approach plants a few questions mid-demo whose answers surface friction while it's still cheap to address:
- "Who else would need to be comfortable with this before it moves forward?" — surfaces the internal-selling problem before the call ends.
- "If this worked exactly as shown, what would you need to tell your team to get budget approved?" — forces pricing-the-change resistance into the open early.
- "What's the strongest reason someone on your team might push back on this?" — invites the buyer to voice a doubt they might otherwise sit on silently.
None of these questions are aggressive, and none require the rep to be a mind reader. They simply move the moment of truth earlier, into a conversation where the seller is still present to respond, instead of leaving it to happen alone in the buyer's inbox three weeks later.
What a useful follow-up actually looks like
Once the demo is over, the follow-up itself is either resistance-aware or it's noise. "Just checking in to see if you had any thoughts" asks the buyer to do the analytical work of naming their own resistance, unprompted, in writing — which is exactly the task most buyers will avoid. A better follow-up names the likely friction directly: "Wanted to check — is the open question more about getting the rest of your team aligned, or about making the internal case on cost? Happy to help with either." That does two things a generic nudge cannot. It gives the buyer permission to say the quiet part, and it shows them the seller already understands the shape of the decision they're facing, not just the shape of the product.
Deals that stall after a strong demo aren't unusually difficult deals. They're ordinary deals where the resistance simply moved to a room the seller wasn't in. The fix isn't a louder follow-up — it's noticing where the friction went, and following it there.