Product demo / UGC testimonial: structure, script and how to clone it

Product demo / UGC testimonial is a proven short-video structure. Here is why it holds attention, how its beats are timed, a script you can start from, and the command that clones it for your own subject.

Why this format works

A demo works when the viewer sees the outcome before the feature list. Show the result, then explain how it happened.

Structure breakdown

1. 1. Result first (0–3s)

   Show the finished output. No logo, no context.

2. 2. Problem (3–10s)

   Name the pain in the viewer's words, one sentence.

3. 3. Mechanism (10–35s)

   Screen or product shots with captions; one claim per shot.

4. 4. Proof (35–50s)

   A number, a before/after, or a third-party mention.

5. 5. Ask (last 3s)

   One call to action, matching the placement.

A script you can start from

Segments, takes and selection anchors — this is the part of the project that changes when you re-run the format:

<script>
<segment> id="demo">
  <take>This took || @nine-minutes nine minutes. || It used to take || @whole-day a day. || Here is the part || @the-trick nobody mentions.</take>
</segment>
<media-track>
  <item source=shot-1.png during={script.selection.result}/>
</media-track>

What you need

• — Screen recording or product shots
• — One measured outcome
• — Caption style that survives on mute

Run it

hypit run clone --reference ./reference/ugc-demo.mp4 --script ./demo.svs --variants 5

The reference video stays fixed. Change the script, re-run, and you get a new edit in the same format — that is the whole point of cloning instead of prompting.

Keep reading

• All clone formats
• Use cases
• Comparisons
• Quickstart
• Glossary

FAQ