Product story / origin format: structure, script and how to clone it
Product story / origin format 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
Origin stories work because they delay the pitch: the viewer stays for the narrative and arrives at the product already invested.
Structure breakdown
1. Situation (0–5s)
A concrete scene from before the product existed. One detail, not a summary.
2. Problem (5–15s)
What was actually broken, in the words you used at the time.
3. Turn (15–30s)
The moment something changed — a build, a conversation, a failed launch.
4. Product (30–45s)
Only now does the product appear, as the answer to that specific problem.
5. Invitation (last 5s)
One next step, 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="origin">
<take>We had || @seven-videos seven videos || and || @no-format no format. || Then we stopped || @the-fix writing scripts || and started || @the-habit cloning structure.</take>
</segment>What you need
- — One specific before-detail
- — A dated turning point
- — Product footage only at the end
Run it
hypit run clone --reference ./reference/product-story.mp4 --script ./story.svsThe 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
FAQ
How late should the product appear?
After the turn, usually around the thirty-second mark in a forty-five-second cut. Earlier and it reads as an advert.
Does this need founder footage?
No. Voice-over plus archival b-roll works; the specificity of the details is what makes it credible.
Can I re-run this for each release?
Yes, but keep one canonical origin story and reserve the format for milestones rather than weekly posts.