Do Not Start a Launch Video with the Hero Script: Build the Release Map First

The most expensive mistake in product launch video production is not an unattractive hero film. It is making every other asset wait for the hero film. The team finishes a 60-second master first, then tries to extract teasers, an event opener, vertical cutdowns and an English version from whatever footage remains.

A week before launch, the gaps become obvious. The strongest teaser shot reveals too much of the product. The vertical edit has no usable close-up. The feature demo only makes sense with the hero voice-over. The international team is still waiting for a clean master.

The practical fix is to build a release map before writing the main script. Start with the moments when information may be released, turn each product claim into filmable proof, and then define the versions required at each moment. The script and storyboard follow that map.

Split one launch date into three information states

A launch date usually contains at least three different information states.

• Tease: people may know that something is coming, but which details, product views, names, prices or functions must remain confidential?
• Reveal: what must the hero film, event screen and website make clear at the same moment, and who has final release authority?
• Sustain: after the reveal, what proof do sales teams, media, channel partners and social audiences still need?

These are not simply three colours on a content calendar. They are information gates. A teaser may need to create expectation without showing an unreleased interface. A launch film may need to establish the complete product value, yet still be unsuitable as a 9:16 ad. A later feature video may need an uninterrupted operating sequence that the hero film never captured.

For each gate, write two sentences: “What may the audience know now?” and “What should the audience do next?” Those answers change the shot priority before a camera is booked.

Turn each selling point into a proof chain

“Lighter,” “faster” and “professional grade” are not shots. A claim becomes useful to production only after it has four layers:

1. The claim: what the brand intends to say.
2. The visible action: what the audience can watch to understand it.
3. The conditions: which sample, environment, accessory, software version or demonstration method must be present.
4. The limits: what could overstate the claim, and which details are not yet approved.

For example, “faster switching” might require a real interface capture, a hand action, a visible response and a comparable before-and-after state. If the firmware is still changing, filming a tight view of the interface may carry more risk than filming the product’s physical use. The team can first capture product movement, materials and interactions that do not depend on the final interface, then keep screen content, narration and data graphics in replaceable layers.

This is also a better way to choose between live action, CGI and AIGC. The choice should follow the responsibility of the proof, not a preference for one visual style. If the physical product must be exact, use the approved sample and controlled product photography. If a setting is not yet available but does not alter a product fact, CGI or AIGC may extend the environment. If the claim depends on real function, human interaction or safety, preserve a verifiable demonstration. Generative tools can expand the version space; they cannot decide which facts the brand is authorised to release.

A useful release map answers six questions

The map does not need to become a complicated spreadsheet. For every deliverable, define:

• release gate: tease, reveal or sustain;
• audience and context: event screen, website, press kit, sales presentation or social feed;
• one job: create anticipation, explain the central value, prove one feature or encourage a next step;
• required proof: opening image, product action, use context, spokesperson explanation or closing action;
• delivery interface: aspect ratio, duration, captions, voice-over, clean master and language versions;
• approval owner: who approves the product fact, the brand expression and the final release.

Platform requirements change, so the delivery map should use the official specifications current at the time of media planning. In the current Google Ads video specifications, Google recommends 16:9 horizontal, 9:16 vertical and 1:1 square assets, and provides safe-zone references. That does not mean the editor only needs to export three dimensions. The product, action and essential graphics must remain legible in each composition; some scenes need a separate vertical pass on set.

If the media plan is not final, separate confirmed versions from provisional ones. For the provisional group, capture safe compositions, clean plates and footage without embedded text. That creates useful flexibility without filling the shoot day with shots that have no defined job.

Separate shared masters from gate-specific shots

Shared masters are efficient to capture together: standard product views, material details, hand interactions, general use scenes, clean backgrounds, room tone and footage without graphics. These assets can support the hero film, feature cuts, sales presentations and later localisation.

Gate-specific footage needs its own priority:

• the teaser may need partial views that do not reveal the complete product;
• the reveal needs the first complete product appearance and the main promise;
• the launch event needs pacing and sound designed for a large screen and a live room;
• a social cut needs an opening and ending that make sense on their own;
• an international version needs another review of interface language, caption length and voice timing.

When these two groups sit in one undifferentiated shot list, teams often capture plenty of generally useful beauty footage but miss the decisive first image or release action for a particular gate. Secure the gate-specific shots first, then expand the shared library. The hero film is not the parent of every version. It is one important output of the release map.

Use four gates before release

Backward planning protects the order of decisions, not just the date.

The product gate confirms whether the sample, colour, packaging, interface and function represent an approved public version. If not, production can continue on shots that do not depend on those variables, but a temporary state should not be presented as the final product.

The information gate confirms the product name, claims, price, release time and embargoed details. Without it, teaser and reveal content easily contaminate each other.

The footage gate checks that every version has the opening, proof, composition and ending it requires—not merely that there is enough material for the hero edit.

The delivery gate confirms file naming, aspect ratio, captions, voice-over, clean masters, usage rights, release ownership and replacement rules. Google’s current specifications also note that some AI-edited or AI-generated ad assets may require platform labelling or disclosures under applicable rules. A platform setting does not replace legal review for the markets where the campaign will run.

Know when a pickup is the responsible plan

Not every launch should aim to finish all filming in one session. A defined pickup window is often more responsible when:

• the sample appearance, packaging or colour is not final;
• firmware, app interfaces or displayed data may still change;
• the live event, spokesperson or real audience response is itself part of the story;
• a key claim still awaits testing, legal or channel approval;
• international markets use materially different accessories, languages or contexts.

Work can still begin. The team can complete concept tests, lighting tests, static product masters and footage that does not depend on the final state, while reserving higher-risk scenes for a second phase. A pickup is not automatically the expensive choice. Completing all post-production against the wrong product version is usually more wasteful.

Do not accept the project by asking only whether the hero film is approved

A launch content system is complete when three questions can be answered:

1. Does every release gate have a version that can stand on its own?
2. Does every core claim have traceable visual proof and an approval owner?
3. Can the team find clean masters, layered graphics, captions and necessary source assets when a new ratio, language or feature cut is requested?

If the only answer is “the 60-second hero has been approved,” the launch content is not finished. Product launch communication releases information in stages. Production should follow the same path.

ONCE’s brand film production service can scope the hero film, feature content and platform versions from the launch timing, approved claims and release map. Teams still organising product information can also review how to distribute a shot list across production departments. Bring the launch date, target markets and confirmed product claims, and we can turn them into a practical production recommendation.