Product demos practice, out loud, against someone who pushes back
A demo is not a tour. Practise showing the three things this specific buyer cares about, checking whether it landed, and resisting the pull to show the thing you are proudest of.
Built for sales engineers and solutions teams. Every call is spoken in real time — not a chat transcript — and ends with a scored debrief you can replay.
What you are scored on
These are the four axes the debrief grades, written out in full rather than summarised. Knowing them before the call is not cheating — it is the difference between practice and a test.
Relevance
Was what they showed tied to a problem this buyer had actually stated, or a tour of what the product does?
Checking in
Did they stop and find out whether it landed — and change course when it did not — or present uninterrupted?
Handling gaps honestly
When the product could not do something, did they say so plainly and move to what it does do, or deflect and over-promise?
Result
Did the buyer leave able to describe what this would change for them, and was a next step agreed?
How the call can end
The counterpart is not scripted to agree. Each of these is a real outcome the scenario can reach, ordered best to worst.
Bought in, next step agreed
winThe buyer can articulate the change and agreed what happens next.
Impressed but unclear
partialThey liked it and cannot say what it would do for them.
Overwhelmed
partialToo much shown, nothing retained.
Lost interest
lossThe demo never connected to anything the buyer cared about.
The scenarios
The demo with the wrong person in the room
Realistic · 20 minYou prepared for the ops lead. Her CFO joined at the last minute and he has one question, which he will not ask directly.
You are: A solutions consultant at an expense-management vendor, running a 30-minute demo. Your goal: Demo to the two stated problems, find out what the CFO actually came for, and leave with a next step both of them own.
Teaches: Demoing narrowly to stated problems and engaging the person who did not speak.
The approver who skipped every check-in
Veteran · 20 minYou built the readout the ops lead asked for. The VP who has to sign it off skipped every check-in, has not opened the deck, and has twenty minutes.
You are: A solutions engineer at a data-analytics platform, presenting a four-week pilot readout. Your goal: Find out what Raj actually needs from this readout, show only what answers that, and leave with a security review scheduled — not a feature tour.
Teaches: Running a readout for the person who can say no, not the person who ran the pilot.
Other things to practise
Sales discovery
Qualify without interrogating.
Objection handling
Price, timing, competitor, status quo.
Customer success
Renewals, QBRs and expansion.
Support de-escalation
Take the heat out before solving it.
Manager feedback
The conversation managers avoid for months.
Leadership
Set direction and hold the room.
Negotiation
Salary, contract and scope.
Take a product demos call
Demo to the problem, not the feature list. A real voice on the other end, a counterpart who does not simply agree, and a scored debrief against the four axes above. The first call is free.