Who this is for: Product marketers, founders and motion producers planning a software launch.
What to prepare
- A rough storyboard
- An asset inventory
- Required versions and destinations
- Reviewers and decision owners
Identify the work units
Two films with the same runtime can require very different effort. A sequence built from approved screenshots differs from one that needs new diagrams, rewritten messaging and several device layouts. Runtime is one input, not a complete scope.
Use an illustrative 30-second product launch: four scenes show a request, assignment, confirmation and closing action. The team already has the logo and two matching screens, but the confirmation screen and approved availability line are missing. Those dependencies affect readiness before any motion work begins.
Complete an effort worksheet
Describe work in concrete units. Assign estimates only after the responsible producer understands the inputs; this example does not invent rates or a universal production time.
- Asset preparation: inspect three product states, replace private example data and obtain the missing confirmation.
- Message work: finalize the owner-assignment promise and current availability wording.
- Scene production: compose four scenes, preserve request continuity and create a readable proof hold.
- Audio: decide whether the message works silently; if narration is required, account for approved copy and timing review.
- Versions: list each required aspect ratio or copy variant as an adaptation task, not an assumed automatic export.
- Review: identify a messaging pass, storyboard pass and final artifact check, with one owner resolving conflicts.
- Delivery: include checking the actual encoded file and destination, plus storing approved source references.
Separate committed work from uncertainty
Create a dependency column for missing assets and unresolved facts. A date based on a complete packet is different from a date that assumes someone will supply screens later. Record the assumption rather than hiding it inside a single estimate.
Ask which changes are included in a revision round. Correcting a misspelled name differs from replacing the central promise or adding a new audience. Define the difference in the scope note so reviewers understand when a request changes the work.
If the available effort is too small, simplify deliberately: use one demonstration, reduce secondary variants or postpone a custom diagram. Do not remove essential proof or final checks merely because they are less visible than creative production.
The resulting worksheet is a basis for a producer's quote or internal estimate. It is not a price benchmark. Keep actual rates, capacity and contractual decisions separate from this creative scoping exercise.
Review checklist
- Required work is listed by asset, scene and delivery task.
- Missing inputs are explicit dependencies.
- Version adaptations and review ownership are included.
- No market price or production-time claim is invented.