How to brief a product video.

Why the brief matters more than the budget

The brief decides what the video says; the animation only decides how it looks. A beautiful video with the wrong message is still the wrong video.

Late changes almost always come from something the brief didn't say: an audience nobody mentioned, a feature that “has to be in there”, or a new person who joins the approval at the last minute. Ten minutes on a clear brief saves days of revisions.

The eight questions a good brief answers

1. What should viewers understand after watching?

   One sentence. If you can't write it, the video isn't ready to be made. Example: “Clinics can let patients book online without changing their software.”

2. Who's watching?

   Their role, and how much they already know. A CTO and a clinic receptionist need different videos about the same product.

3. Where will the video live?

   Homepage, paid social, sales emails, onboarding or a pitch. This decides the length, the format (16:9 or 9:16) and whether it needs to work without sound.

4. What's the problem, in your customer's words?

   Not your positioning statement, but what they'd actually say. The best hooks come from real sales calls, support tickets and reviews.

5. How does the product solve it?

   The one to three flows that show the value. More than three and nobody remembers any of them.

6. Why should anyone believe you?

   Customers, results you can share, integrations, security, or who's behind the product.

7. What should viewers do next?

   One action: start a trial, book a demo, join the waitlist, download the app.

8. The practical details

   Ideal length, deadline, budget range, languages and, most importantly, who approves the final video.

What to attach

• Product access: a demo or staging account, or screenshots of each step you want shown.
• Brand guidelines: logo files, colours and fonts. If you don't have guidelines, your website is fine.
• Your current messaging: the homepage, a pitch deck or a sales one-pager.
• Reference videos: two or three you like, and one line on what you like about each. “The pace of this one” is more useful than “something like Apple”.

Five mistakes to avoid

• Too many messages. A 60-second video can carry one idea well. Give the rest their own videos.
• Features instead of outcomes. “Real-time sync” means little; “your team stops double-booking” means a lot.
• No single decision maker. Feedback from five people who disagree is the fastest way to a muddled video.
• Leaving the budget blank. A range, even a rough one, lets an agency suggest the right scope instead of guessing.
• Asking for the script first. The script is the agency's job; your job is the thinking behind it, which is exactly what the brief captures.

A template you can copy

Copy this into an email or a document, fill in what you can, and leave blank what you don't know yet. A good agency will ask.

1. After watching, viewers should understand:
2. Who's watching (role, what they already know):
3. Where the video will live (homepage / ads / sales emails / onboarding / other):
4. The problem, in your customer's words:
5. How the product solves it (1–3 key flows):
6. Proof (customers, results, integrations):
7. What viewers should do next:
8. Length · deadline · budget range · languages:
9. Who approves the final video:
10. Attached: product access, brand guidelines, reference videos:

What happens after you send it

At Neo Agency, our project brief asks these questions in six quick steps, in about two minutes. Within 24 hours you get a short video walkthrough of how we'd approach your project, and within 48 hours a fixed, itemised quote. Everything happens in writing, so you can answer whenever it suits you. Wondering about budget first? Read how much a SaaS explainer video costs.