A demo is an argument

Most product demos are organised around the product's structure: here is the dashboard, here is the settings page, here is the reporting module. That is a tour, and tours are what you give someone who has already decided to visit.

A demo is given to someone who has not decided anything. It needs to make a case. Every case has the same three parts: a situation the viewer recognises as their own, a moment where the situation changes, and enough evidence that the change is real.

The recognisable situation

Open on something your viewer does today, shown concretely. Not “managing shipments is complex” — show the spreadsheet with forty tabs, or the eleven-step process, or the screen where they currently do this badly.

The test is whether someone in your audience would watch the first eight seconds and think “that is my Tuesday.” If they would think “that is a generic stock scenario,” start again.

The moment it changes

There is one moment in every good demo where the viewer's posture changes. It is usually a single interaction — the click after which the painful thing is simply done. Find it before you record, and build everything around it.

The evidence

After the turn, the viewer's question changes from “what is this” to “is this real.” That is where you show the edge case, the volume, the integration, the thing that proves it is not a prototype. Put it after the turn, never before.