On this page
Choose a workflow with a visible state change. A face can introduce the problem; the product needs to show the solution.
Translate the feature into a user action
“Powerful workspace automation” is hard to film. “Move overdue tasks into one view” gives you a starting screen, an action and an ending. Translate the feature into that sequence before choosing a reaction.
Use sample records with enough variation to make the result obvious. A board full of identical placeholder cards hides what changed. Keep names fictional and avoid exposing a real customer’s account while trying to make the example feel realistic.
Three feature briefs you can adapt
These are suggested examples, not claims about a particular SaaS product. Use a brief only if your product supports the described behavior, including any setup the edit would otherwise hide.
| Feature type | Opening idea | Visible evidence | Important boundary |
|---|---|---|---|
| Task filtering | “Only the things that need attention” | Show the filter and matching tasks | Do not imply the app chose priorities without rules |
| Document search | “Find the note, not the folder” | Enter a query and open the right result | Use an actual successful search |
| Report export | “Take this view into the meeting” | Export the displayed report and open it | Do not hide a required plan or configuration |
Make a dense interface feel smaller
Crop to the panel where the action happens. If the result appears elsewhere, make a second clear shot rather than squeezing both into one unreadable frame. Keep enough context to identify the product and the task.
A short reaction before the screen can create a clean handoff. Keeping a large face over every product frame may reduce the very evidence you need people to see. Test the sequence with a direct cut before trying an overlay.
Show value without making up customer results
A stock expression is not a customer interview. Use editorial language that introduces the feature, and attach any performance claim to evidence you actually have. “Here is the saved view” is a visible fact. “This saved me ten hours” is a separate personal outcome.
If your strongest story is a real customer’s experience, collect that story with appropriate permission and supporting detail. Do not use a generic face to fill in the missing participant.
Send viewers to the next relevant step
The closing instruction should follow the demonstrated action. A short guide, feature page or relevant signup flow can make more sense than sending everyone to an unrelated promotion. Keep the destination consistent if you compare openings.
Watch the export as someone new to the product. They should be able to name the task, see what changed and understand the next step without knowing your internal feature names.
- One task is named in familiar language.
- The starting and ending states are visible.
- The screen is legible at phone size.
- The reaction does not impersonate a customer.
- The destination continues the same product story.
Questions & answers
Can a desktop SaaS product work in vertical video?
Yes, if the relevant panel and result remain readable. A focused crop or two clear shots is better than shrinking an entire desktop window.
Should I list all the benefits?
Start with the benefit demonstrated by the action shown. A list of unrelated claims makes the short video harder to follow.
Find the opening for your next edit.
See the public samples, then unlock the library when you’re ready to work with the originals.
Explore the library