| name | brand-launch-film-production |
| description | Provider-independent production workflow for AI agents creating brand launch films, product reveal videos, manifesto films, campaign hero films, website hero videos, investor/customer launch assets, and social cutdowns. Use when planning, scripting, generating, editing, reviewing, or delivering launch films that must align strategy, claims, brand voice, visual direction, product proof, accessibility, compliance, and multi-platform delivery. |
Brand launch film production
Use this skill to make a launch film behave like a business-critical campaign asset, not just a pretty generated video. A strong brand launch film turns positioning into a memorable audiovisual proof: the audience understands who it is for, what changed, why to believe it, and what to do next.
This is not legal advice. Treat legal, regulatory, medical, financial, securities, privacy, endorsement, talent, music, likeness, trademark, and platform-policy decisions as approval gates for the client, counsel, or the responsible compliance owner.
Core production contract
Produce a launch film only after you can answer:
- Who must change their mind or behavior?
- What is the single launch promise?
- What proof supports that promise?
- What must not be claimed, implied, shown, copied, or simulated?
- Where will the film run, and what cutdowns must ship with it?
- Who approves strategy, claims, brand, legal/compliance, and final delivery?
Separate three categories throughout the work:
- Documented facts: product features, release date, prices, customer names, results, certifications, patents, case-study numbers, awards, partner logos, platform specs, rights records.
- Approved claims: claims the client has substantiated and approved for the target market and channel.
- Production heuristics: creative choices such as pacing, story route, camera style, edit rhythm, music mood, and cutdown structure.
Never let a heuristic become an unsupported claim.
Intake: ask for the launch brief before concepting
Collect or infer a concise brief. If critical information is missing, ask only for what blocks a safe first concept pass.
Minimum intake:
- Product, service, company, or campaign being launched.
- Launch type: new company, rebrand, product reveal, feature launch, category entry, fundraising/customer proof, website hero, paid social, event/opening film.
- Target audience and decision context: buyer, user, investor, candidate, partner, press, internal team, existing customers, skeptical switchers.
- Audience state now: unaware, confused, comparing alternatives, distrustful, price-sensitive, excited but not convinced.
- Desired action: sign up, book demo, buy, invest, apply, share, attend, explore website, remember the brand.
- Positioning: category, alternative, differentiated promise, emotional territory, forbidden comparisons.
- Messaging hierarchy: must-say, should-say, nice-to-say, never-say.
- Proof inventory: product footage, screenshots, prototypes, benchmarks, customer quotes, founder story, data, demos, awards, press, certifications, testimonials.
- Brand system: strategy, voice, logo rules, colors, typography, motion language, photographic style, sonic identity, accessibility requirements.
- Deliverables: master duration, aspect ratios, cutdowns, subtitles, captions, thumbnails, stills, textless versions, clean audio stems, platform placements.
- Constraints: deadline, budget, generation providers, source assets, legal review, regulated categories, geographic markets, languages, music/talent rights.
If the user asks for immediate generation without enough proof, make a low-risk concept/treatment only. Do not fabricate product capabilities, customer outcomes, endorsements, or certifications.
Strategy spine
Write the strategy spine before scripting:
Audience:
They currently believe:
We need them to believe:
Single launch promise:
Proof ladder:
1. Product proof:
2. Human proof:
3. Market/category proof:
Desired feeling:
CTA:
Claims requiring approval:
Things to avoid:
The best launch films usually have one dominant promise and two or three proof beats. If the brief has more than one audience, create audience-specific cutdowns rather than forcing all audiences into one master.
Choose the story route
Present 2-4 concept routes when the creative direction is open. Name each route, give a one-sentence premise, explain why it fits the audience, list proof required, and flag compliance or production risks.
Useful routes:
- Manifesto: belief-led film for a rebrand, category creation, or movement. Best when the brand has a sharp point of view. Risk: vague grandiosity without product proof.
- Product reveal: mystery-to-reveal structure around the product or service. Best when the object/UI/experience is visually distinctive. Risk: overpromising before proof exists.
- Problem/relief: opens with a felt customer pain and resolves through the launch. Best for conversion. Risk: manipulative or fear-based framing.
- Founder conviction: uses a founder or team story to create trust. Best for early-stage, investor, recruiting, or premium craft brands. Risk: self-importance; needs audience relevance.
- Customer transformation: centers a customer/user before-and-after. Best with authorized testimonials or case studies. Risk: endorsement disclosures and substantiation.
- Demo-as-drama: turns product interaction into a cinematic sequence. Best for software, devices, tools, and workflows. Risk: fake UI, impossible latency, misleading results.
- Category contrast: compares old way vs new way without naming competitors unless approved. Best for challenger brands. Risk: comparative claims require support.
- Launch event opener: designed to energize a room, then work online. Best for keynotes and sales kickoffs. Risk: too much atmosphere, not enough clarity.
Messaging hierarchy and script discipline
Build the script as a hierarchy, not a paragraph.
- Hook: create tension, curiosity, or recognition in the first seconds.
- Promise: state the launch idea plainly.
- Proof: show what makes it true.
- Meaning: connect proof to the audience's life or decision.
- CTA or memory lock: close with action, URL, event date, product name, or campaign line.
For a 15-second cut, keep one idea and one proof beat. For 30 seconds, allow one setup, one turn, and one proof cluster. For 60-90 seconds, use three movements: world/problem, launch/proof, invitation. Longer manifesto or investor films need clear chaptering and should earn every abstraction with a concrete image or data point.
Write voiceover and title cards so either can carry the film if the other is muted. Social and website hero placements often autoplay silently; assume the first pass may be watched without sound.
Claims and compliance discipline
Documented facts from official sources:
Production rules:
- Mark every express and implied claim in the script, visuals, UI, supers, testimonials, captions, and CTA.
- Ask for substantiation for superiority, performance, health, financial, environmental, safety, security, AI capability, customer-result, and savings claims.
- Do not transform a customer quote into a broader result claim. If one customer saved 20 hours, do not imply every customer will.
- Avoid fake dashboard numbers, fake app screens, fake testimonials, fake logos, invented awards, invented press quotes, and synthetic "customer" endorsements unless the client explicitly approves the fictionalization and disclosure.
- Keep qualifications close to the claim they qualify, readable, audible where needed, and present in each cutdown where the claim appears.
- Do not bury material disclosures in end slates, tiny supers, or captions only when the claim is prominent in voiceover or image.
- If an influencer, customer, employee, investor, advisor, expert, or partner appears to endorse the launch, require approval for disclosure language and placement.
- If using "first," "only," "best," "fastest," "most accurate," "clinically proven," "guaranteed," "carbon neutral," "secure," "private," or similar claims, trigger substantiation and counsel/client review.
Escalate before production when:
- The product is in a regulated area: health, finance, insurance, employment, housing, education, children, alcohol, political, environmental, legal, safety, security, or investment.
- The film targets or depicts minors.
- The film uses real customers, employees, public figures, synthetic likenesses, voice clones, private data, medical/financial outcomes, or third-party marks.
- The launch is tied to fundraising, securities, acquisition, public-company communications, or forward-looking statements.
- The concept relies on competitor comparison, benchmark data, survey results, certifications, awards, reviews, or scientific claims.
Brand voice and concept translation
Translate brand strategy into usable direction:
Voice:
Vocabulary to use:
Vocabulary to avoid:
Sentence length:
Humor/irony level:
Confidence level:
Technical depth:
Emotional temperature:
Visual system:
Color behavior:
Typography/title behavior:
Composition:
Camera/motion:
Product/UI treatment:
People:
Texture/materials:
Things this brand would never do:
Sonic system:
Music role:
VO role:
SFX role:
Silence:
Protect distinctiveness. After each route, ask: could this be any other company in the category? If yes, add a product-specific behavior, brand-specific line, proprietary proof, or sharper world view.
Visual system and product demonstration
Choose visuals according to proof needs:
- Use real product footage or UI capture when accuracy matters more than spectacle.
- Use generated metaphor, cinematic scenes, or motion graphics when the launch idea is abstract or unavailable to film.
- Use founder/customer footage when trust and specificity matter.
- Use animation or hybrid UI when the product is not yet camera-ready, but label prototype states clearly if needed.
For product/service demos:
- Script the user journey before generating shots.
- Confirm every UI state, result, metric, latency, notification, and integration is real or clearly illustrative.
- Keep screen text legible in every target aspect ratio.
- Do not show impossible workflows, unavailable features, unapproved partner logos, or misleading before/after comparisons.
- Capture "proof moments": click, solve, compare, export, receive result, handoff, outcome.
For generated media prompts:
- Convert strategy into shot facts: subject, environment, action, camera, light, motion, brand palette, product constraints, forbidden elements.
- Use product reference images, logo files, UI captures, packaging photos, or style boards when available.
- Keep claims out of image/video prompts unless the generated shot must include approved text. Claim language belongs in controlled script/title layers.
- Ask for separate clean plates when title cards, supers, or localized copy may change.
- Avoid asking a model to render exact logos, app screens, small UI text, legal disclaimers, or dense typography unless the provider is known to handle text reliably. Prefer compositing text in edit.
- Preserve provenance: record provider, model, prompt, seed/job ID when available, source assets, license terms, edits, approvals, and whether AI was used.
Shot list and asset plan
Create a production table before asset generation:
| Beat | Purpose | Visual | Source/generation plan | Audio/text | Claims | Approval risk |
|---|
| Hook | Stop scroll | Customer struggling with old workflow | Generate metaphor or film source | Title: "Launch line" | Implied pain claim | Low/medium/high |
| Proof | Show product | Real UI walkthrough | Screen capture | VO + callout | Feature and time claim | Requires substantiation |
| Close | Convert | Product hero + URL | Composite | CTA | Availability/pricing | Requires launch-date approval |
Asset plan checklist:
- Brand assets: logos, color values, fonts, icon rules, motion rules.
- Product assets: UI captures, device renders, packaging, prototypes, screenshots, API diagrams.
- People assets: releases, approved names/titles, wardrobe guidance, likeness/voice permissions.
- Customer assets: testimonial approval, disclosure language, case-study substantiation.
- Music/SFX/VO: licenses, usage territories, paid-ad rights, term length, exclusivity, union/talent constraints if applicable.
- Generated assets: prompts, source references, model/provider metadata, content credentials/provenance notes, edit history.
Audio, music, VO, SFX, and title cards
Use sound to clarify the launch, not to compensate for weak messaging.
- Music: define energy curve, reference mood, instrumentation, brand fit, edit points, and rights. Avoid famous-song soundalikes unless explicitly licensed and reviewed.
- VO: specify persona, pace, accent/language, pronunciation, disclosure needs, and whether the voice should feel founder-led, narrator-led, customer-led, or purely typographic.
- SFX: use for product proof, transitions, tactile interaction, and memory cues. Avoid UI sounds that imply unavailable features.
- Title cards: make the promise, proof, and CTA readable without sound. Keep legal qualifiers close to qualified claims.
- Silence: use pauses for premium launches, reveals, or founder/customer authenticity.
Accessibility and inclusive delivery
Documented facts from official sources:
Production rules:
- Deliver captions or subtitles for every spoken/audio-led version unless the client explicitly declines and the channel permits it.
- Include non-speech audio that matters to meaning: music cues, laughter, alarms, product sounds, applause, silence if intentional.
- Keep captions away from platform UI/safe-zone overlays and important product visuals.
- Use readable contrast and type size across 16:9, 9:16, 1:1, and any website hero crop.
- Provide transcript or descriptive transcript for website and investor/customer-facing assets when practical.
- Consider audio description or a descriptive transcript when visual-only information is necessary to understand the launch.
- Avoid relying only on color, tiny UI text, fast flashes, or dense kinetic type to convey essential information.
Delivery, platform specs, and volatile facts
Platform requirements change. Re-check specs at production time and record the date checked. As of 2026-07-10:
Do not hardcode a single "universal" spec. Build a delivery matrix:
| Deliverable | Purpose | Ratio | Duration | Text-safe notes | Audio | Captions | File notes | Owner approval |
|---|
| Hero master | Website/event/sales | 16:9 or site crop | 60-90s | Keep key action center-safe | Full mix | Optional/open captions per need | Client/site spec | Brand + legal |
| Paid vertical | Reels/TikTok/Shorts | 9:16 | 6/15/30s variants | Avoid top/bottom UI | Mix for mobile | Burned or sidecar | Re-check platform | Paid media |
| Square/feed | Feed/LinkedIn variant | 1:1 or 4:5 | 15/30s | Larger titles | Mix for mute/autoplay | Burned or sidecar | Re-check platform | Paid/social |
| Textless clean | Localization/future edits | Same as master | Same | No baked copy | M&E/stems | None | Archive | Producer |
Edit, mix, color, and handoff
Edit for comprehension first, then emotion:
- Confirm the audience can state the product, promise, and next step after one viewing.
- Put the product or launch object earlier than feels comfortable unless the route is deliberately reveal-led.
- Ensure every abstraction is anchored by a concrete visual, product behavior, person, or proof.
- Build cutdowns from the strategy spine, not by chopping the master mechanically.
- Keep the first frame, thumbnail, and first title useful; many surfaces preview before playback.
- Version claims carefully: when a claim is removed from VO but remains in a super, caption, or product screen, it still needs approval.
Audio finishing:
Color/visual finishing:
- Keep product colors accurate enough for brand/product review.
- Check skin tones, UI readability, gradients, and compression banding.
- Verify logo clear-space, minimum size, background contrast, and end-card legibility.
- Deliver textless, captioned, uncaptioned, clean, and localized-safe versions as required.
Rights, provenance, and AI transparency
Documented facts from official sources:
Production rules:
- Keep a rights ledger for every image, video clip, voice, music cue, font, UI asset, logo, testimonial, dataset, and generated output.
- Record whether AI-generated or AI-assisted media is used, and whether disclosure is required by platform, client policy, law, or brand trust strategy.
- Do not use a real person's likeness or voice clone without documented permission.
- Do not imply a real customer, expert, media outlet, partner, or public figure endorsed the launch unless approved.
- Treat C2PA/Content Credentials as helpful provenance signals, not as a complete legal or trust solution.
- Preserve source projects, prompts, approvals, model/provider metadata, licenses, releases, caption files, stems, and final exports.
Review cycles
Use explicit review passes:
- Strategy review: audience, promise, proof, CTA, route.
- Script/claims review: every line, title, product screen, customer quote, disclaimer, and implied claim.
- Brand review: voice, visual system, logo, typography, product accuracy, sonic identity.
- Rough cut review: story, pacing, proof clarity, emotional arc, cutdown logic.
- Compliance/accessibility review: disclosures, endorsements, captions, safe zones, rights, platform specs.
- Final QC: exports, audio, captions, color, compression, metadata, naming, delivery matrix.
At each pass, record decisions, unresolved risks, owner approvals, and changes that must propagate to cutdowns.
Brand-launch QA checklist
Before final handoff:
- The first 5 seconds identify the tension, promise, or brand world.
- The product/service is understandable without reading the brief.
- The film has one primary promise and a visible proof ladder.
- Every express and implied claim is approved or removed.
- Required disclosures travel with every cutdown where the claim/endorsement appears.
- UI, product behavior, pricing, launch date, integrations, and availability are accurate.
- Customer/founder/employee/actor/voice/music/font/logo rights are documented.
- Captions/subtitles are accurate, synchronized, complete, readable, and not blocked by UI.
- The film works muted and with sound.
- Text and product details survive each aspect ratio and crop.
- Audio does not clip; dialogue/VO is intelligible on phone speakers.
- Color, logo, and product representation pass brand review.
- All platform specs were re-checked at production time.
- Textless, captioned, clean, localized, thumbnail, still, stem, and project/archive deliverables are present when required.
Example: SaaS product reveal film
Example production intent: a 60-second website hero and 15/30-second social cutdowns for a B2B SaaS launch.
Brief:
- Audience: operations leaders who know manual reporting is slow but distrust automation claims.
- Promise: "Close the gap between messy data and board-ready decisions."
- Proof: live dashboard ingest, rules engine, export to board deck, customer-approved quote.
- Risk: "saves 10 hours/week" is only approved for one case study; do not generalize.
Strategy spine:
Audience: VP Ops / Chief of Staff
They currently believe: automation demos hide the cleanup work
We need them to believe: this product handles the messy middle with visible controls
Single launch promise: board-ready operating rhythm without spreadsheet archaeology
Proof ladder:
1. Shows real import and exception handling
2. Shows audit trail and approval handoff
3. Uses one approved customer quote with disclosure
Desired feeling: relief plus control
CTA: Book a launch demo
Claims requiring approval: time saved, integrations, customer quote, "board-ready"
Things to avoid: magic AI, fake charts, unapproved logos
Shot/prompt direction:
Beat 1, hook:
Visual: macro sequence of overlapping spreadsheet windows becoming a pressure map, no fake brand logos.
Prompt: cinematic close-up of abstract spreadsheet grids reflected on a dark glass desk, tense late-evening operations room, premium blue-gray palette, shallow depth of field, slow lateral camera move, no readable company names, no charts with specific numbers.
Text layer in edit: "The month-end scramble has a pattern."
Beat 2, product proof:
Visual: real screen capture of import, exceptions, approvals, export.
Direction: capture at 2x resolution, hide customer data, composite callouts in edit, freeze on the audit trail.
VO: "LaunchFlow turns raw operating data into an approved board packet — with every exception visible."
Claim note: "board packet" and workflow steps require product owner approval.
Beat 3, customer proof:
Visual: customer name/title only if release is signed; otherwise anonymized role card.
Title: "Pilot customer, Series B software company"
Disclosure: "Pilot result; individual results vary" if approved by counsel/client.
Why this structure works: the film answers the audience's objection before it celebrates the launch. It avoids unsupported AI-magic language and uses real UI where proof matters.
Expected failures to watch for: generated UI with fake numbers, overbroad time-saving claims, unreadable vertical crop, disclosure only in the 60-second master but missing from paid cutdowns.
Example: founder-led brand manifesto
Example production intent: a 90-second launch film for a climate hardware company debuting at an event, with a 30-second investor cut.
Concept route: Founder conviction plus demo-as-drama.
Script skeleton:
0-8s: Founder in workshop, not at a podium. "We were told the grid was too old to learn new tricks."
8-25s: Physical problem: heat, demand spikes, aging infrastructure. No disaster imagery unless accurate and approved.
25-50s: Product reveal through materials, assembly, installation, dashboard telemetry.
50-70s: Proof: pilot location, measured variable, approved partner line, no unapproved savings claim.
70-90s: Invitation: "Built for the next thousand local grids." CTA/event reveal.
Visual rules:
- Use real prototypes and macro details wherever possible.
- Generate environmental context only as non-specific atmosphere unless locations and infrastructure claims are approved.
- Keep the founder imperfect and specific; avoid generic "changing the world" language unless paired with proof.
- Capture a clean 10-second product hero loop for website use.
Compliance notes:
- Environmental, energy-savings, safety, pilot-performance, and partner claims require substantiation and client/counsel approval.
- Any utility/partner logos, worker uniforms, or location identifiers need permission.
Example: launch cutdown matrix
Example matrix for a master film with social, website, and sales needs:
| Cut | Audience | Job | Duration | Primary proof | CTA | Notes |
|---|
| 90s hero | Website/event | Explain the launch | 90s | Founder + product + pilot | "See how it works" | Full story, captions, transcript |
| 30s investor | Investors/partners | Show traction | 30s | Pilot metric + market reason | "Meet us at..." | Counsel review for forward-looking language |
| 15s vertical | Paid social | Stop scroll | 15s | Product moment | "Book demo" | No dense disclaimers; use only claims that fit |
| 6s bumper | Retargeting | Recall brand | 6s | Product name + visual mnemonic | URL | Avoid claims requiring qualifiers |
| Textless loop | Website hero | Atmosphere | 8-12s loop | Product beauty | None | No VO; readable crop; lightweight file |
Do not create cutdowns by simply trimming the master. Rebuild each cut around the audience, claim burden, and placement.
