# How to Write a Video Brief for a Product Demo

> For anyone commissioning a product demo video: what the brief must cover, a copy-paste template, and a filled-in example that works with an agency, a freelancer, or uscale.

**Key takeaways**

- A video brief should open with three lines: the goal, the audience, and the one action the viewer should take.
- Recommended lengths vary by platform: LinkedIn ads 15–30 seconds, Instagram Reels up to 90 seconds, YouTube Shorts up to 3 minutes.
- Agency production typically costs $15,000–$50,000 per minute, freelancers $1,000–$5,000, and AI-generated video roughly $20–$220 per minute.

Published Oct 22, 2026 · uscale · https://uscale.ai/blog/video-brief-product-demo

## Why the First Cut Comes Back Wrong

Nobody looks up how to write a video brief for a product demo until the first cut comes back wrong.

Picture the edit landing on a Thursday. The demo opens on the settings page instead of the screen your buyers care about. The narration tours every feature in menu order, and the last frame is a logo. There's no trial link, no "book a call", nothing for the viewer to do next. The brief never said what should happen after the video ends, so every choice in the cut was a guess.

Then comes a week of rework: a new screen order, a new closing line, and another review round with someone who never saw the brief.

It all traces back to one missing line. Below are the fields a brief needs, a template to copy, a filled-in example, and how the same page goes to an agency, a freelancer or an AI video tool. First, the line that cut was missing.

[Video: Launch film for Orbit Desk](https://uscale.ai/examples/orbitdesk-launch-film.mp4) — A hypothetical launch film for a shared inbox tool, built from a written brief rather than a script read aloud.

## What Should a Video Brief for a Product Demo Say First?

A video brief for a product demo opens with three lines, in this order: the goal, the audience, and the one action the viewer should take. Nobody picks a screen until all three are written. Most teams do it the other way round. They start with "show the dashboard" and only decide what the video is for once a cut is already in review.

![The three lines a brief states first: 1. The goal: what this video is for 2. The audience: the role watching it 3. The action: what they do next](https://uscale.ai/blog-media/video-brief-product-demo/steps-the-three-lines-a-brief-states-first-1200x360.svg)
### The three lines to write today

**The goal, in one sentence.** Write it as an outcome, such as "Get evaluators to book a demo call" or "Get new signups to activate their free trial." If the sentence needs an "and", it describes two videos.

**The audience, in one sentence, as a role.** "A support lead comparing shared-inbox tools" tells the maker what this viewer already knows and what they need to see proved. A persona with a name and a coffee order says little about which screen matters.

**The action, as a single verb.** Book. Start. Install. Invite. A video ends on one screen and one closing line, so the viewer can do only one thing next.

### Why the action comes before the screens

Every screen in a demo earns its place by moving the viewer toward the action. Without a named action, each reviewer applies their own test. Sales wants the booking page, product wants the newest feature, and the founder wants the integrations. The edit can satisfy only one of them, and the others send it back. That is how a finished video turns into a week of rework.

Name the verb first and the last screen picks itself. You then choose every screen before it by working backward from that ending, which is the next part of the brief.

## Which Screens, Messages, and Proof Belong in the Brief?

The brief lists three things: the product's screens in the order a viewer should see them, the two or three messages the narration must land, and the proof behind each message. With those written down, whoever makes the video can build the cut without guessing.

### Map your screens onto a shape everyone knows

A product demo script is [commonly defined](https://www.whatastory.agency/blog/how-to-write-a-product-demo-video-script) as a structured outline that drives one viewer action through six beats: hook, problem, solution, walkthrough, proof and call to action. Use those beats as rows in your brief and put one screen or one claim against each. An empty row shows you what's missing before the edit does. The script itself comes later (see [how to write a product demo script](https://uscale.ai/blog/product-demo-script)). The brief only fixes the order.

Most briefs get the order backwards. They list screens the way the app's menu lists them, because that's how the team knows the product. A viewer doesn't know the menu. **Order the screens by the question the viewer asks next: what's wrong, what do I do, what do I get.**

### Pair every message with its proof

Keep the messages to two or three, and give each one a single piece of proof: a number you can source, a customer you have permission to name, or the same screen before and after. A message with no proof belongs on the claims-to-avoid list, not in the narration.

### A worked example (hypothetical)

Say you're launching a SaaS reporting tool next week. The flow in the brief reads:

1. **Problem:** the dashboard with an empty reports panel. Message: your numbers are here, but nobody gets a report.
2. **Core action:** the user picks a template and schedules it. Message: one setup replaces a weekly chore.
3. **Result:** the finished report in the inbox, shown beside the old manual version as the proof.

![The flow a brief hands to whoever makes the video: 1. Open on the problem screen 2. Show the core action 3. End on the result or proof](https://uscale.ai/blog-media/video-brief-product-demo/steps-the-flow-a-brief-hands-to-whoever-makes--1200x360.svg)
That is three screens and three lines, short enough for the person signing off to read in one pass. How long each beat can run depends on where the video is published, and that is the next field in the brief.

## How Long Should a Product Demo Video Be, and What Size?

It depends on where the video runs. Name the destination in the brief first, then take the length and size from that platform's spec.

LinkedIn recommends video ads of 15–30 seconds so they qualify for every placement, though it accepts anything from three seconds to 30 minutes. An Instagram Reel can run up to 90 seconds at 1080×1920 (9:16). A YouTube Short can run up to 3 minutes, a cap YouTube raised from 60 seconds in October 2024. A standard YouTube upload allows up to 12 hours, so length there sets no limit on a demo.

![Recommended video length by platform (seconds): LinkedIn video ad 15–30, Instagram Reel 3–90, YouTube Short 3–180](https://uscale.ai/blog-media/video-brief-product-demo/chart-recommended-video-length-by-platform-sec-1200x452.svg "Sources: LinkedIn Help / Video ads advertising specifications, Oct 1, 2026; AdLibrary / Instagram Video Ad Specifications 2026, Jun 1, 2026; PostLinkApp / YouTube Shorts Max Length 2026, Aug 1, 2026")
### Write the number, not "keep it short"

"Keep it short" means 30 seconds to one reader and two minutes to another, and the editor ends up choosing. Write the destination's length and ratio instead, for example "LinkedIn ad, 15–30 seconds, 4:5."

A 30-second cut is not a 90-second cut with the ending removed. The one action you named at the top of the brief has to land inside the shorter window, and that changes which screens come first. If the video goes to two places, the brief asks for two cuts.

### Add file limits only where they change the delivery

| Destination | Ratio | Length | File |
|---|---|---|---|
| LinkedIn video ad | 4:5 recommended; 16:9, 1:1, 9:16 also listed | 15–30 s recommended | MP4, 75 KB–200 MB |
| Instagram Reel | 9:16, 1080×1920 | Up to 90 s | MP4 or MOV (H.264), up to 4 GB |
| Instagram feed | 4:5, 1080×1350 recommended | n/a | n/a |
| YouTube Short | n/a | Up to 3 min | n/a |
| YouTube upload | 16:9, 1920×1080 recommended | Up to 12 hours | Up to 256 GB |

Most of these limits never cause a problem. Two can.

- **LinkedIn's 200 MB cap:** a long, high-resolution MP4 may need compressing before upload.
- **The 4:5 recommendation for Instagram feed:** a wide screen recording needs a vertical layout planned from the start. Cropping it afterwards cuts off the screens the viewer needs to see.

Size is a creative decision as much as a technical one, so it belongs in the brief rather than in an export setting. With length and size fixed, the remaining lines cover access to the product, brand, and who approves the finished cut.

## What Else Should the Brief Cover: Access, Brand, and Who Approves It?

The rest of the brief is five short lines. Name the screens that must appear and the claims to avoid. Say how the maker reaches screens behind a login and which brand assets to use. Then name the one person who signs off. Each line answers a question the maker would otherwise guess at, and guesses are what get reworked.

### Screens and claims

Name the screens that must be on camera, for example "the shared inbox, the assignment rule, the weekly report." Then list the claims to avoid: anything the product can't back up today, such as a beta feature or a number with no source. A maker who doesn't know a claim is off-limits will often write it, because it sounds good.

### Access

A logged-in app needs one explicit line on access: a demo account with sample data, or a note that someone will sign in once. Without it, the maker stalls or films whatever account they can reach. With uscale, you sign in yourself, once, in a browser streamed into the page. SSO, two-factor codes and captchas work there. The film shows whatever that account shows, so name the demo account in the brief. That keeps real customer data off screen.

![The uscale Access tab: Check access, Add login and Log in here](https://uscale.ai/blog-media/how-to/access-stage-1616x502.webp "Where a brief's access line gets used: signing in once, in a streamed browser, so screens behind a login still get filmed.")
### Brand

Name the logo, colours and fonts, or write "use the live site." uscale reads the logo, colours and fonts from your live site, so the brief needs a brand line only when the site's logo isn't the one you want.

### Approver

Most teams treat sign-off as the last step. It is the first decision. Write one name, and separately list who is consulted but doesn't decide. A finished video is usually rewritten by someone who never saw the brief and judges it against a different goal. A video gets approved by the person the brief names, or rewritten by the person it forgot.

With these five lines added, every field a brief needs is accounted for. The next section puts them all into one copy-paste table.

## What Does a Video Brief Template for a Product Demo Look Like?

A video brief template is one table with thirteen fields, each with a line on what to write. Copy it into a doc, fill every row, and send it to whoever makes the video.

| Field | What to write |
|---|---|
| Goal | The business outcome in one sentence, such as a trial signup. |
| Audience | The viewer's role and the decision they are making, in one sentence. |
| Action | The single verb the viewer should act on when the video ends. |
| Flow | The screens in viewing order, from first frame to call to action. |
| Key messages | The two or three points the narration must land, one line each. |
| Proof | The evidence behind each message: a sourced number, a named customer, a before and after. |
| Tone | Three words for how the voice should sound, and one it must never sound like. |
| Length and size | The exact length and aspect ratio from the destination's own spec page, never "keep it short". |
| Screens that must appear | Any screen the video can't ship without, even in a tight cut. |
| Claims to avoid | Anything the product can't back up today: roadmap features, unmeasured results, competitor comparisons. |
| Access | How the maker reaches screens behind a sign-in: a demo account with sample data, or a one-time sign-in. |
| Brand assets | Where the logo, colours and fonts live, and which version to use. |
| Approver | One named person who signs off, and the stage they sign off at. |

### Fill it top to bottom

Most people start at Flow because screens feel concrete. That gets the order backwards. Screens chosen first argue for themselves, and the action gets fitted around them. Write Goal, Audience and Action first, then let Action decide which screens earn a place in Flow.

Leave no row blank. A blank row isn't neutral. It's a decision handed to whoever reads the brief next. If a row doesn't apply, write "none" so the maker knows you thought about it. The table also works as the outline for a [product demo script](https://uscale.ai/blog/product-demo-script).

The next section fills in every row for one product, so you can see how much detail each row needs.

## What Does a Filled-In Product Demo Brief Look Like?

A filled-in brief replaces every instruction with a decision someone else can check. Here is the template filled in for a hypothetical case: a shared-inbox product launches next week, and the demo is posted with the launch on LinkedIn.

| Field | Filled in |
|---|---|
| Goal | Get a trial signup from the launch post |
| Audience | A support lead evaluating tools to replace a shared email address |
| Action | Start a free trial |
| Flow | Unassigned emails → assign one to a teammate → add an internal note → reply sent, thread closed |
| Key messages | Every email has one owner; nobody answers it twice; notes stay off the customer's thread |
| Proof | The same email handled in a shared mailbox, then in the inbox with its owner shown |
| Tone | Calm and practical |
| Length and size | 15–30 seconds, vertical 4:5 |
| Screens that must appear | Assignment menu, internal note, closed thread |
| Claims to avoid | Response-time figures nobody has measured; integrations not yet shipped |
| Access | Demo workspace with sample customers |
| Brand assets | Logo and colours from the live site |
| Approver | Head of product marketing, before anything is posted |

You paste this same document to uscale's director as the note. It is not a second version. The director reads it alongside the product's site and returns a storyboard with every narration line, for your approval before anything is filmed. The site shows the product. The brief adds what the site can't say: the one action, the claims to avoid, and who signs off. Because the access row names a demo workspace, you sign in to it once, and the film shows that account instead of real customers.

![The uscale director summarising a product and asking what the video should be about](https://uscale.ai/blog-media/how-to/chat-questions-800x1694.webp "The filled-in brief pasted as a note to the director, who turns it into a storyboard line by line.")
If a storyboard line can't be traced to a row here, the brief has a gap. The next section names the common ones.

## What Gaps in a Brief Cause the Most Rework?

Most finished demo videos that come back for changes trace to one of four missing lines. Each one is quick to write and saves a full round of edits.

| Gap in the brief | What goes wrong | The line that prevents it |
|---|---|---|
| No named action | The edit optimizes for the wrong outcome, so the strongest screen and the closing ask point in different directions | "Action: start a free trial." |
| No claims-to-avoid list | The narration promises something the product can't back, and someone pulls the line after the cut | "Claims to avoid: no uptime figures, nothing that says it replaces a CRM." |
| No named approver | Two people approve two different things, and the second approval undoes the first | "Approver: head of product signs off on the storyboard and the final cut." |
| No access note for a logged-in app | The maker films the wrong account, shows real customer data, or stalls waiting for a password | "Access: demo account with sample data, signed in once before filming." |

A complete brief still won't cover everything. Products change mid-project: a screen gets renamed or a button moves a week before launch. That calls for updating the brief, not writing a new one. Edit the Flow or Screens row and send the revised line to whoever is making the video. The goal, audience, action, claims and approver rarely move, which is why they go in writing first.

With uscale, the tour is saved with the project, so a new cut of the same tour picks up the new screens. The updated brief tells the director what changed and what to keep.

So the brief holds up when the product moves. That leaves the practical question: who you hand it to.

## How Does the Same Brief Work With an Agency, a Freelancer, or Uscale?

The brief is the same input whichever route makes the video. Only what happens to it next changes. An agency turns it into a scope, a freelancer turns it into a quote, and an AI tool turns it into a first draft.

![Typical cost per finished minute, agency vs. freelancer vs. AI-generated: Agency 15000–50000, Freelancer 1000–5000, AI-generated 20–220](https://uscale.ai/blog-media/video-brief-product-demo/chart-typical-cost-per-finished-minute-agency--1200x470.svg "Source: LTX / How Much Does AI Video Generation Actually Cost? (2026 Guide), Aug 1, 2026")
**Pick the route by deadline and budget.** Agency production typically costs $15,000 to $50,000 or more per minute over 4 to 8 weeks. Freelance production costs $1,000 to $5,000 over 1 to 3 weeks, [according to LTX](https://ltx.io/blog/ai-video-generation-cost). AI-generated video runs roughly $20 to $220 per minute for generation alone, in hours to days. You're done when the route is written at the top of the brief.

**Send the brief before any kickoff call.** Ask an agency or freelancer to repeat your Action, Flow and Approver rows back in the scope or quote. If you are the agency, fill in the Approver row with your client before you quote. You're done when the reply names your one action in its own words.

**Or hand it to an AI tool.** [Synthesia](https://www.synthesia.io/tools/product-demo-video-maker) and [HeyGen](https://www.heygen.com/tool/product-demo-video-generator) both start from a pasted script, and your Flow and Key messages rows already are one. With uscale, paste the website or GitHub repository of your [software product](https://uscale.ai/industries/software-products) and put the brief in the note to the director. The director reads the product and proposes a storyboard with every narration line. The brief adds what the site can't say: the one action, the claims to avoid and who approves. Screens behind a login need one sign-in from you. You're done when your named approver signs off the storyboard.

**Record a rough draft this hour.** Open the screen recorder you already have. Follow the Flow row screen by screen and read the key messages aloud. It costs nothing and shows which rows are still vague.

If you do only one thing, send the finished brief to the approver and get a yes before any route starts.

You'll know it worked when the scope or storyboard repeats your action back to you, the video sits on your product demo page, and sales has one link to send.

**Try it:** [make a product demo video](https://uscale.ai/use-cases/product-demo-video) from your own brief, and approve every narration line before anything is filmed.

## Write the Brief, Then Make the Video

A demo video that comes back with the wrong screen is rarely a filming problem. It is a brief that left one question open. Before your next demo, write three things down:

1. **Name the goal, the audience and the action.** Write one sentence each, with the action as a single verb.
2. **List the screens and the claims to avoid.** Put the screens in the order a viewer should see them, and list anything the product can't back up.
3. **Name who approves it before anything is filmed.** Write one person into the brief, so the sign-off happens on paper instead of in the edit.

Your first video with uscale is free, and after that [the credit packs](https://uscale.ai/pricing) need no subscription. You can paste that brief into the director chat today and get back a storyboard with every narration line for approval. To see what comes back, watch [the example films](https://uscale.ai/examples). Start with a [product demo video from your own site or app](https://uscale.ai/use-cases/product-demo-video).

The demo doesn't need a bigger budget. It needs a few lines somebody agreed on before anything was filmed.

## Questions

### What is a video brief?

A video brief for a product demo is a short document that tells whoever makes the demo what it is for before any script or filming starts. It names the goal, the audience, and the one action the viewer should take, then lists the product's screens in order, the key messages and their proof, the length and size, the claims to avoid, and the one person who approves the finished cut.

### How do you write a video brief for a product demo?

To write a video brief for a product demo, start with three sentences: the goal as an outcome, the audience as a role, and the viewer's next action as a single verb. Then list the screens in the order a viewer should see them, two or three messages each with one piece of proof, the destination's exact length and ratio, claims to avoid, access to logged-in screens, brand assets, and one named approver.

### How do you brief a video production agency for a SaaS launch?

Briefing a video production agency for a SaaS launch works best in writing, before any kickoff call. Send a brief that names the launch goal, the buyer's role, the one action the video should drive, the screens in viewing order, the claims to avoid, and how the agency reaches screens behind a sign-in, such as a demo account with sample data. Ask the agency to repeat the action, flow and approver back in its scope.

### How do you create a video brief?

Creating a video brief starts with a one-page table filled in from top to bottom. Write the goal, audience and viewer action first, then the flow of scenes or screens, key messages with proof, tone, length and size, must-have scenes, claims to avoid, access, brand assets and one approver. Leave no row blank; write "none" where a row doesn't apply, so the maker knows it was considered.

### What does a product demo video cost?

A product demo video's cost depends on who makes it. Agency production typically runs $15,000 to $50,000 or more per minute over 4 to 8 weeks, and freelance production $1,000 to $5,000 over 1 to 3 weeks. AI-generated video runs roughly $20 to $220 per minute for generation alone. With uscale, the first video is free, then credit packs start at $29 for 25 credits, with no subscription.

---
Source: https://uscale.ai/blog/video-brief-product-demo