Skip to content

Template — July 2026

Free Launch Film Brief Template.

The exact brief structure Kino needs from a real client — and the structure that forces the production decisions that matter before a single frame is built. Copy it, complete it, own it.

No email required. No gating. Copy the whole thing and use it.

Launch Film Brief Template — 5 sections, plain text, ready to fill in

launch-film-brief.txt Free to use
01

Product name

[Your product name]

One-liner (fill in)

[Product] is [what it does] for [who], so they can [outcome] without [the thing it replaces/removes].

Example (Loom)

Loom is async video messaging for teams, so they can share context without scheduling a meeting.

What is launching right now?

[New feature / new model / public beta / v2 / etc. — be specific]

02

The one feature or capability to prove (fill in)

[Name the single feature — e.g. "real-time collaborative editing", "sub-second inference latency", "automated invoice parsing"]

What does the viewer see when this feature works?

[Describe the screen state — what appears, what changes, what the cursor does. Be as specific as possible.]

Why does this matter to the user? (the benefit, not the spec)

[Not "100ms latency" — "the model replies before you finish typing, so the loop feels instant"]

What are you NOT trying to cover in this video?

[Name 1–2 things explicitly out of scope for this launch film. This prevents scope creep during production.]

03

Access method — choose one

Working login / Staging environment URL / Loom walkthrough of the specific flow / Screen recording at 2x+ resolution

Product URL or staging link

[URL — staging or live; or "will provide login separately"]

The specific user flow to capture (fill in)

[Step 1: user does X. Step 2: the product does Y. Step 3: result is Z. Walk through the exact flow as if narrating it to someone who has never seen the product.]

Any UI elements to avoid showing?

[Sensitive data, beta features not ready for public, competitor names, etc.]

04

Logo — SVG preferred; high-res PNG (1000px+) accepted. Transparent background. Both light and dark variants if they exist.

Primary brand hex codes — your main brand colour(s). If you only have one, name it. If you have a palette, name the primary and one secondary.

Typography preference — the font(s) used in your product or brand, if any. If none, note "no preference" and production will match the product UI.

Reference videos — 1–3 launch videos you admire (links). These set the motion register and energy level. They do not need to be in your industry.

Tone — one of: technical / approachable / premium / bold / calm. Or name a company whose communication style you want to match.

Asset delivery method

[Dropbox link / Google Drive link / Notion page / email attachment — your preference]

05

The aha moment question — answer this (fill in)

When a new user first understands your product is working, what are they looking at on screen? Describe the exact screen state and the specific moment of recognition — not the feature, but the feeling of "I get it now."

Your answer

[Describe in 2–4 sentences. Example: "The first aha is when the user pastes their first invoice and sees the line items appear in the Xero draft in real time, correctly mapped to the right accounts — without having typed anything. The moment is the cursor disappearing from the invoice and reappearing in Xero with the work already done."]

How long should the video be? (for reference)

15–30 seconds for a feed-first post (X, LinkedIn). 30–60 seconds for a product page hero. 60–90 seconds for a launch demo with full feature walkthrough.

What should the viewer do at the end of the video?

[Specific CTA — "sign up for the beta", "get early access", "join the waitlist", "try it free". One action, not two.]

Why each section exists

01 — Product one-liner

If it cannot be written in one sentence, the video cannot argue it.

A launch film is an argument to a specific buyer that a specific problem is now solved in a specific way. If the one-liner takes three sentences, the video will try to make three arguments — and will make none of them well. Writing the one-liner forces the clarity the video needs before production starts, not after.

The most common brief failure is "we want to show what the product can do." That is not a brief — it is a request for a walkthrough. A launch film needs a thesis.

02 — The one feature to prove

One feature, credibly proven, outperforms five features vaguely implied.

The instinct on a launch is to show everything. The result is a video that shows nothing convincingly. A viewer who leaves a launch film unable to answer "what is the one thing it does?" will not take action — even if the video was technically impressive.

The "out of scope" field matters as much as the rest. Naming what the video is not covering prevents brief creep that adds production time and dilutes the argument.

03 — Real UI access

The real product UI is the only proof that the product exists and works.

A design-aware technical buyer — which is the primary audience for an AI startup launch — can identify AI-generated UI immediately. Hallucinated menus, garbled text, and approximate interfaces signal "this team could not show their real product." That is a credibility loss at the launch moment.

Important: AI-generated video cannot render legible product UI text as of June 2026 — confirmed across Kling 3.0, Seedance, and Veo 3. Any launch video that relies on AI-generated footage for the product UI is showing a hallucinated version of the product, not the real thing. Real UI access is what makes this avoidable.

04 — Brand assets

Missing assets on day one add more time than gathering them before the brief.

The brand asset checklist is mechanical — but it is the most commonly incomplete part of a first brief. A missing logo vector or an absent hex code surfaces at the moment the title card is being built, which is the worst time to wait for assets. The checklist makes "we are ready to start" checkable before the brief is submitted.

The reference videos field is the highest-leverage part of this section. References set the motion register and energy level in a way that 500 words of brief cannot. One good reference video is worth more than a detailed motion description.

05 — The aha moment

The video must be built toward the moment the product becomes real to the viewer.

The aha moment question is the most important in the brief because it names the destination. A launch film is not a tour of the product — it is a journey to the moment of understanding. Every scene before the aha builds tension or context; the aha resolves it.

Most founders have never been asked to name this moment explicitly. The exercise of answering it — "what is the exact screen state when a new user first thinks, I get it now" — produces the brief's most useful content. The answer tells production precisely what the film must build toward and what evidence it must show to get there.

Kino — Premium launch video for funded SaaS marketing teams

Brief complete? Kino can build from it in 48 hours.

Kino takes a complete brief, captures your real product UI, and delivers a motion-designed launch film in 48–72 hours — entirely async, no calls, no meetings. View the sample work or apply for the founding rate.