Who this is for: Founders and product marketers preparing a new software product announcement.
What to prepare
- Approved positioning and a defined launch audience
- Screens or other evidence of one verified product action
- Exact brand assets and product terminology
- Current public availability and the intended destination
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative launch brief: introduce a fictional request-triage product to team coordinators who need a visible handoff. The film's promise is that a request can show its next owner. Begin with one unassigned example request, introduce the product through that task, show the verified assignment action and hold on the matching assigned state. Use readable interface crops and one active focal point at a time. Keep the request title visible across the sequence. Do not claim time savings, complete request capture or customer adoption. If the product is not publicly available, close with its actual waitlist or access-request status. Supply the starting, action and resulting screens before production. Treat any missing state as an unresolved dependency, and label all fictional sample data.
When this job fits
Use a launch film when someone needs to understand what the new product is for and why its demonstrated task might matter to them. The film can lead into a detailed demo, but it should not promise to teach a complex workflow in a brief montage.
A narrow task is especially useful when the broader product has many capabilities. Showing one meaningful action gives the viewer an entry point. A launch with several unrelated audiences or no approved product evidence may need more positioning work before motion production.
Choose suitable inputs and identify gaps
Useful inputs include matching interface states, a concise description of the intended user, exact product labels and approved access wording. A source document can explain the brief, but it should not be treated as evidence for capabilities it merely proposes.
Poor inputs include unrelated screenshots from different versions, a list of unsourced benefit claims or a prototype presented as shipping UI. A concept asset can still be useful if its status is explicit and the story is framed as a concept or waitlist preview.
Avoid inventing customer proof to make the launch feel established. A fictional scenario should remain clearly illustrative, and any real quotation, metric or endorsement needs its own approved source.
Move from brief to storyboard to review
First select the promise and check its evidence. Then arrange the scene sequence so the viewer can recognize the problem, follow the action and inspect the result. Approve that message before refining visual style.
Use the illustrative brief above as a handoff starting point, not a claim of a generated video. The producer still needs the actual assets and a verified workflow. Review the storyboard for missing context and unsupported visual implications, then inspect the real final artifact for readability, continuity and accurate closing copy.
This resource explains how to prepare the creative job; it does not promise automatic imports or one-click use of the example. Keep your own product's closing invitation aligned with its current availability.
Review checklist
- The launch has one primary viewer and useful promise.
- Required evidence exists for the demonstrated action.
- Prototype and fictional material are clearly identified.
- The result remains readable without narration.
- The next action matches current public availability.