The template
Introduce a product update or launch with a clear problem, feature reveal, and next step.
Use this scene sequence as an editable outline. Replace sample wording with verified details; the sequence is a planning aid, not a fixed duration or a platform specification.
| Beat | On screen | Narration | Review check |
|---|---|---|---|
| 1. Customer problem | Show the friction the release addresses. | Frame the problem without overstating it. | Is this problem supported by research? |
| 2. Reveal | Introduce the released feature in context. | Name what is new and who can access it. | Is availability confirmed? |
| 3. Demonstrate | Show the new control and its workflow. | Explain the action and why it helps. | Does this match the shipped build? |
| 4. Result | Show the changed screen or output. | Describe the result without a guarantee. | Is the outcome a real product behavior? |
| 5. Release detail | End on a current product view or end card. | Give date, plan or rollout details. | Are dates and limits approved? |
How to fill it in
- Hook: state the viewer's problem or the outcome they want.
- Context: show only the setup the viewer needs to understand the workflow.
- Main action: focus on one or two meaningful product steps.
- Outcome: show what changed, using only claims you can support.
- Next step: give viewers one specific action to take.
Customize it for your audience
Adapt the sequence to the release state: an announcement can invite viewers to follow updates, while a generally available feature can direct them to use it now. Confirm the audience's eligibility, rollout date, plan and region before recording the availability line. Show the capability in a current product build and include the prerequisite if access requires setup. A launch for existing customers can begin with where to find the change; a prospect-facing version may need a short product context first. Schedule a final status check close to publication so staged access is not described as universal.
Prepare the final handoff
Record the final availability statement, release owner and date checked with the export. If rollout status changes, update the spoken line, on-screen text and linked launch page together. Keep a version without temporary launch wording when the footage may be reused for an evergreen product page.
Production and approval checklist
Before recording or animation, confirm the viewer, destination, desired next action and product version. Replace every illustrative name, number and screen with approved material, or label it as sample content. Check that each scene advances the story and that voiceover fits the time available on screen. Review the draft once for product accuracy, once for audience comprehension and once for permissions, accessibility and destination requirements. Make the final reviewer and approval date explicit; recheck volatile facts such as pricing, availability, release status, event details and platform rules just before publishing. Keep the script, source assets and approved export together so an update can be made without guessing which version is current.
Who it serves
Launch viewers want to know what changed, who can use it and what to do next. Open with the customer problem, reveal the new capability, then demonstrate the released state.
Evidence and review
Confirm release date, rollout status, plan availability and behavior with the release owner. Separate features available now from announcements or future plans.
Do not call a feature generally available if access is staged, plan-specific or region-specific. Put those limits in the video and supporting copy.
A worked example
Illustrative scenario, not a customer story: Introduce the audience problem, reveal the newly launched capability, show where it appears, and close with availability details. Confirm the release date and access limits against the launch plan.
Make it automatically
DemoVexa can use your product code and project context to draft a brief, script, and scene plan. Review every screen, claim, permission, and recording before publishing.
Frequently asked questions
What belongs in a product launch video?
Show the problem, the new capability in context, who can access it and one next step. Give unrelated release items their own clips so the main announcement stays clear.
Can a launch video go out before release?
Yes, as a clearly labeled preview or announcement, with approved timing and access details. Do not show a future capability as available in the current product.
Can I use this template for free?
Yes. The outline is page content you can copy without an account. Adapt it to your product, check the destination's current requirements, and verify every claim, date, permission and third-party asset before publication.
Make your next product video with DemoVexa
Download the app to make a video from your code, or start a free trial with 15 renders.