Structure a product demo video

Structure a product demo video.

Build it around **one** problem:
1. The problem, shown not stated. What does the viewer see that makes them recognize it? *Opening with a claim about the problem is weaker than showing it.*
2. The moment it becomes annoying — the specific friction.
3. The product entering, at the point of friction, not before.
4. The resolution, with the outcome visible on screen.
5. One line on what else it does. **One.** A feature list here undoes the whole structure.

Per shot:
- What to screen-record versus what to generate versus what to shoot. *Anything showing the actual product must be recorded — generated UI that does not match the product is a false claim.*
- Duration.
- What text or callout is needed, added in editing.

Then:
- What to cut if the length runs over. Usually the setup.
- The frame to use as a thumbnail — typically the resolution moment, not the problem.
- Where viewers will drop: almost always during setup that goes on too long.

Rules:
- Do not show a feature the problem did not require.
- No fabricated metrics or results on screen.
- If the product does not actually solve the stated problem cleanly, say so — that is a product finding and a demo cannot hide it.