Free private planning tool
Free product demo script and shot-list builder
Turn one product outcome into a recordable script rather than a feature tour. This free builder creates a timed narration draft, a six-beat shot list and an honest word budget entirely in your browser.
In short: Choose one audience, one painful starting state, two visible actions, one verifiable proof point and one next step. The builder turns those answers into a 30-, 60- or 90-second storyboard without uploading or saving the form values. Download the free four-page PDF workbook for a printable version.
Build a product demo script and timed shot list
Fill in concrete language you would be comfortable showing to a customer. The builder does not call an AI model, create an account, persist the answers or send the field values to Cadre. It assembles the draft locally with fixed, inspectable rules.
Your timing and word budget
| Beat | Time | What to show | What to say |
|---|
Narration draft
The six-beat product demo structure
- Hook: name the audience and the problem in language they already use. Do not open with your company history.
- Problem: show the old state for long enough to be recognized, but not long enough to become a tour of everything that is wrong.
- Promise: state one outcome. A short demo cannot carry three audiences and seven value propositions.
- Walkthrough: record two visible actions that connect the problem to the outcome. Narrate consequences, not every click.
- Proof: show a result the viewer can inspect: a changed timeline, a completed state, a before/after, a source-linked number or a clearly attributed customer statement.
- Next step: ask for one action. “Start a project” is clearer than a list of five links and three subscription choices.
The framework is deliberately narrower than a live sales-demo agenda. It is designed for a short recorded product demonstration that must make sense without a presenter answering questions in real time.
Use a word budget that leaves room for the interface
Spoken narration around 130–150 words per minute is usually understandable. A product demo needs extra air because the viewer is reading the interface while listening. The builder uses 140 words per minute as a maximum, not a target.
| Length | Maximum draft | Good for | What to remove |
|---|---|---|---|
| 30 seconds | About 70 words | One social proof, launch teaser or single feature outcome | Setup, secondary actions and most adjectives |
| 60 seconds | About 140 words | One complete problem-to-result workflow | Feature catalogues and implementation detail |
| 90 seconds | About 210 words | Two connected actions plus a careful proof section | Unrelated use cases and multiple calls to action |
Read the draft aloud while playing the intended screen sequence. If the voice reaches a result before the interface does, shorten the sentence or slow the capture; do not hide the mismatch with faster playback by default.
Make every narration line recordable
A useful script pairs every spoken claim with a visible shot. “Save time” is not a shot. “The three manual corrections appear as ordinary timeline blocks, then undo restores the prior state” is recordable and reviewable.
- Prepare synthetic demo data and close private notifications before recording.
- Reset the product to a known state so the same actions can be recorded again.
- Keep the pointer still while the viewer reads, then move once with purpose.
- Let the result remain on screen after the narration line ends.
- Record a clean wide take before adding zooms, captions or decorative framing.
- Review the final artifact at the size and aspect ratio where the audience will see it.
Use the separate product-demo recording playbook for environment preparation, narration, privacy review and export checks.
A good proof point is specific and falsifiable
The builder leaves proof optional because an empty field is safer than a fabricated number. Choose one of four evidence types:
- Visible state: show the completed export, saved project, changed record or delivered message.
- Measured before/after: publish the original input, exact edit, duration or output and the limits of the comparison.
- Source-linked fact: put the primary source next to the number and record the date it was checked.
- Attributed customer evidence: use a real, permissioned statement without changing its meaning or implying a universal result.
Use only proof that can be inspected directly in the finished project or supported by a primary source. Avoid invented numbers and unsupported comparisons.
Privacy, method and reuse
The builder is deterministic JavaScript served with this page. It performs no fetch, upload, account creation or local-storage write. The generated wording is a planning draft, not an AI output or claim that the suggested sentences are correct for a particular product.
You may copy, modify and use the generated shot list in commercial work. Cadre does not claim ownership over answers entered into the form or the draft assembled from them. Review every product claim, customer reference, metric and call to action before recording.
This free tool is published by Cadre, a product-demo recorder and editor, and naturally links to Cadre workflows. It is not an affiliate comparison and no email gate is used. Corrections or accessibility feedback can be sent to jack@cadre.cam.
Turn the recording into the finished story
Cadre records your Mac and gives you an editable cinematic timeline—automatic zooms, local captions, cuts, styling and an AI agent that can follow your direction.
Record, edit and preview free · Cadre Pro required to export · Apple Silicon · macOS 13+
Frequently asked questions
How long should a product demo script be?
For a short recorded demo, use roughly 70 words for 30 seconds, 140 for 60 seconds or 210 for 90 seconds as a ceiling. Leave extra pauses while the viewer reads the interface.
Does this product demo script builder use AI?
No. It combines your answers with a fixed six-beat template in the browser. It does not call an AI model, invent product facts or send the form values to Cadre.
Are my product details uploaded or saved?
No field values are uploaded, stored in local storage or attached to an account by this builder. If ordinary site analytics are enabled, they can record a page visit but not the builder answers.
Can I use the generated script commercially?
Yes. Copy, change and use the generated planning draft in commercial work. You are responsible for verifying claims, permissions, customer references and metrics before publishing.
What should I show as proof in a product demo?
Prefer a visible completed state, a reproducible before/after, a source-linked fact or an attributed customer statement used with permission. Leave proof blank rather than inventing a metric.