Analysing a demo call: what to take from it

A demo is almost always judged on feel. The prospect smiled, asked questions, said it was exactly what they were looking for. Three weeks later the follow-up goes unanswered.

The problem is not that the demo went badly. It is that a demo which goes well and a demo which closes look very much alike in the moment, and almost nothing that separates them is ever kept.

A demo is not judged like a discovery call

A discovery call looks for a situation, a pain and what it costs. A demo plays on different ground: the person has already admitted the problem and is now assessing whether your answer fits without breaking what they already run.

That shift changes what you listen for. In discovery, the material is what the prospect tells you. In a demo, the material is how they react: what they cut short, what they come back to, what they ask about twice.

In discovery you listen to what the person says. In a demo you watch what they do with what you show them.

The four things to take from a demo

• The questions left unanswered. The ones where you said you would check, or that you talked around. Those are the ones that come back in the committee, without you there to answer them.
• The technical objections. The missing integration, the data that has to stay somewhere, the security constraint. They are not negotiated, they are either handled or they block.
• The moment attention dropped. The part of the demo where the person stopped reacting. It is nearly always the part you show out of habit and that they do not need.
• What they asked to see again. A second request on the same screen is the most reliable signal of the whole call. That is where their real question sits.

None of these four survive a write-up done afterwards, because all four are about moments you do not notice while living them.

What gets written down, and what should be

The left column is a feeling, and feelings do not compare from one demo to the next. The right column is made of verifiable items, and that is what lets you see, after ten demos, that the same question comes up every time.

The recurring question is your real roadmap

An objection heard once is an anecdote. The same objection across eight demos in a row is a defect, either in your product, in your demo, or in who you invite to it.

Moving from anecdote to pattern is what no memory does on its own. You remember the last demo, never the last ten, so you correct for the most recent prospect rather than for what keeps coming back.

Recording is not enough, it has to be consolidated

Plenty of tools transcribe a demo and summarise it. That helps you find a detail again, and it stops there: you get one summary per call, so as many documents as demos, and the recurring question stays invisible.

What changes things is consolidation: a single view gathering the objections, the questions and the words used across all your demos, ranked by how often they appear.

Where to start

• Record your demos, with the participants' consent, and keep them in one place.
• After each demo, write down only the four points above. Five minutes is enough.
• After ten demos, read the set and look for what appears at least three times.
• Fix what comes back most often first, not what the last prospect said.

The gain is not in the demo you just ran, it is in the twentieth. A demo you review improves the next one; a demo you forget gets replayed identically, with the same blind spots.