How to brief a SaaS product demo video.

Give the film one job.

“Explain our platform” leaves too many choices open. “Show a product marketer how to approve a release without losing the review history” gives the sequence a purpose. Name the audience, the task and the action they should take after watching.

Placement matters too. A homepage visitor may need context; someone reading release notes already knows the product. Decide whether the film belongs on a feature page, in a sales conversation or in a vertical launch post. Choose one aspect ratio for the first scope.

Prepare screens that can be shown.

Supply a short recording of the real workflow, approved interface states, a logo and basic brand guidance. Explain what happens before and after each click. A motion reference can describe pacing, but it cannot replace product evidence.

Use synthetic records or properly redacted screens. Remove customer names, emails, keys and internal URLs before sharing. Confirm permission to use the supplied material and identify any restrictions on AI-assisted production. A production login is not needed.

Try a twelve-second storyboard.

This is an illustrative structure for a single-feature teaser, not a required formula:

1. 0–2 seconds — context. Establish one screen and the task. Keep the label short enough to read.
2. 2–6 seconds — action. Move to the real control, show the selection, then change the interface state.
3. 6–10 seconds — result. Hold on the actual outcome. An approval should appear before its success message.
4. 10–12 seconds — next step. End with one accurate call to action that fits the placement.

Our SyncFlow workflow concept uses this causal principle: the record appears after a human approval. The published example is eighteen seconds and depicts a fictional product. Its sequence is useful to study; its screens and timing are not a ready-made brief for your software.

Screen recording or UI animation?

A recording is useful when viewers need to follow the real interface in detail. Designed UI animation is useful when the story needs tighter framing, a clear transition between states or a diagram around the interface. Simplification should remove distractions while preserving the product’s actual behavior.

For a technical explanation, agree which conditions must remain visible. The DataPulse cache concept, for example, keeps freshness in the explanation rather than suggesting every repeat request skips the network.

Copy this brief.

Audience

Who will watch, and what do they already know?

One feature

Which task or capability should become clear?

Approved claim

What exact statement can the film make? What must it avoid implying?

Workflow

Starting state → user action → actual result → next step.

Placement

Where will it appear? Choose length, one format and required text.

Assets and rights

Approved screens, recording, logo, brand guidance and restrictions.

Review

One decision maker, storyboard approval and consolidated feedback.

Budget and timing

Budget range, intended use date and source-asset availability.

In a first enquiry, describe the project without confidential uploads. Agree a suitable private sharing route after fit is established.

Agree the deliverable before production.

Specify duration, resolution, aspect ratio, revision limits and acceptance checks. Confirm sound, voiceover, extra formats and editable source separately. A final MP4 is a different deliverable from an interactive product demo or an editable After Effects project.

At FrameRelay, Feature Spark starts at $39 for one 10–15-second UI teaser with music, one aspect ratio and one consolidated revision. Product Pulse and Launch Batch cover longer films and include both 16:9 and 9:16. Dates, rights, funding and the final specification are agreed before work begins; the portfolio is original concept work, not evidence of client results.