Skip to content

Brief a product demo before choosing effects

A Motion guide for coding agents. Also covers product demo structure, product video brief, demo video script, hook reveal proof CTA, video archetypes, feature announcement video, and 1 more.

Show all 7 aliases

product demo structure, product video brief, demo video script, hook reveal proof CTA, video archetypes, feature announcement video, changelog video

Gather the content

Infer from the repository first. Ask only for material gaps. If the user cannot supply something, use a clear replace-me placeholder and never present it as final.

Required:

  • Product name and one-line value proposition
  • Hook: the viewer's problem or the promised outcome
  • Product surface: the real screen, component, screenshot, terminal or device to show
  • Two or three concrete feature moments, each written as an action and outcome

Optional:

  • Proof: a sourced metric, customer quote or integration result
  • CTA: one ask and one destination
  • Voiceover or supplied audio

Every proof number needs its source URL, exact source wording and the date checked. Do not invent a plausible number.

Product-demo beats

  1. Hook: state the problem or outcome in plain language
  2. Positioning: name what the product does; combine this with the reveal when time is short
  3. Product reveal: show the real product surface
  4. Feature moments: show two or three actions and their results, not a list of feature names
  5. Proof: land one credible result when proof exists
  6. CTA: make one request and show where to act

The hook and product reveal are the spine. Proof and CTA are optional. Read the scene titles alone; they must tell the argument without the animation.

Duration variants

  • Bumper, 4–5 seconds: positioning and logo lockup only
  • Short, about 18 seconds: hook, product interaction, payoff and CTA
  • Standard, 35–45 seconds: all beats with two or three feature moments
  • Long, 60 seconds or more: only when one narrative thread carries the whole film. Split a feature catalogue into separate clips

Give each scene enough time for one read and a still hold. Calculate reading time from the actual copy. Do not force all scenes to equal lengths.

Other archetypes

  • Feature announcement: change, before, interaction, outcome, CTA
  • Changelog: version, valuable changes, result, upgrade path
  • Tutorial: goal, steps, confirmation, next action
  • Social clip: hook, one interaction, payoff, CTA
  • Data story: question, evidence, change, meaning, source
  • Logo bumper: positioning, lockup

Use this guidance in your coding agent

Install the Better Design MCP once. Your agent then loads this page with one call.

get-motion-guide({ topic: "product-demo-brief" })
claude mcp add --scope user better-design --transport http https://better-design.com/api/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
Browse related design systems