Feature announcement video: the 30-second formula

Why feature announcements deserve a video

Shipping a feature doesn't mean users find it. In Pendo's analysis of product usage across 615 software subscriptions, 80% of features in the average product were rarely or never used (Pendo, 2019). A release note tells users a feature exists; a 30-second video shows them the gesture, which is what turns a changelog line into a habit.

Feature videos are also the most frequent video a SaaS makes. That changes the economics: you need a format you can repeat every month, not a one-off film. The feature release video page shows how Sitso structures them.

The 30-second formula: before, gesture, after, where

One feature, four beats. Copy this template and fill in the brackets.

• Before (0:00–0:05): “[The old friction, in your user's words].” Show the slow way: the extra tab, the copy-paste, the spreadsheet.
• The new gesture (0:05–0:20): “Now, [verb] [object] in one [click / shortcut / prompt].” The feature in action on your real UI, zoomed on what matters.
• After (0:20–0:25): “[The result]: [time saved or work avoided].” Only use a number you have measured.
• Where to find it (0:25–0:30): “[Menu / shortcut / plan]. Live today.”

Thirty seconds is a target, not a rule. A simple improvement fits in 20 seconds; a feature that changes a workflow may need 60. Wistia reports an average engagement of 52% for videos under one minute, with drop-off typically around the halfway point (Wistia), so the gesture must land in the first half.

Examples worth studying

Three different ways real SaaS teams have announced features:

• Linear Initiatives (2024), the walkthrough. A 4:15 demo where the Head of Product sits in a small webcam bubble and the interface fills the frame (YouTube, Moonb breakdown). Right for a feature that changes how teams plan.
• Figma Motion (2026), the reveal made with the feature. A 1:09 film of animated designs that keeps the easing presets panel in frame, so cause and effect appear together (YouTube, Moonb breakdown).
• Slack, the feature series. After its main walkthrough, Slack and the agency Thinkmojo produced six shorter videos on specific features for onboarding (Wistia). Same voice, same look, one feature each.

More launch-scale examples in our 7 SaaS launch videos analyzed.

Where to post a feature announcement video

Existing users matter most for a feature, so start where they already are.

Production tips for feature clips

Feature clips are short, so every frame counts.

• Real interface, cleaned up. Realistic data, no loading states, zoom on the gesture.
• Readable muted. In a Verizon Media and Publicis Media survey, 69% of US adults said they watch video with the sound off in public (Streaming Media). Put the key sentence on screen.
• Same name everywhere. The feature name in the video, the UI, the docs and the e-mail must match.
• A recognizable series. Same intro sting, type, colors and outro, so users know a new feature video when they see one.
• One feature per video. Bundling five updates into one clip buries all of them.

Write the words around the video

The video rarely travels alone. In the changelog, the in-app message and the release e-mail, it sits under a headline and above a button, and those few words decide whether anyone presses play. Write them from the same sentence as the video's “after” beat.

• Headline: the outcome, not the feature name. “Reports now build themselves” beats “Introducing Auto-Reports”.
• One line of context: who it's for and which plan includes it.
• The video, with a thumbnail that shows the result, not a logo.
• One button that opens the feature itself, not the homepage.
• A link to the docs for users who want the details.

Keep in-app messages short enough to read in a few seconds: the video does the explaining. And decide which releases deserve a video at all. A good rule: make one when the change alters a gesture users repeat often, or when it's the reason a prospect would choose you. Bug fixes and small tweaks belong in the changelog text.

How to measure it

Views are the least useful number. Track what the video is for: the share of active users who try the feature in the weeks after the announcement, clicks from the in-app message and the changelog, and support tickets about the feature. Compare against a previous feature announced with text only. That comparison, on your own product, is worth more than any industry benchmark.

Making a feature video every month

The hard part is not one clip, it's the cadence. Agencies often quote weeks per video (see our cost guide), which is longer than many release cycles. Sitso makes the full video, up to 1:15, from your URL in under 4 hours, remembers your brand and past videos so every release looks like part of the same series, and delivers 16:9 and 9:16. Sitso Pro includes one video a month for $2,500; many teams cut a longer video into several feature clips. Try it on your next release with a free 20-second teaser.