How to Make a Feature Announcement Video for Your SaaS (Release Notes People Actually Watch)
Your team spent weeks on a new feature. You wrote the release notes, sent the email, and a month later support is still answering “can I export this report?”, the very thing you shipped. Users do not read changelogs; they skim them, if they open them at all. A short feature announcement video fixes that: in 30 to 90 seconds it shows the change on the real screen, where users will find it. This guide shows you how to script one, make it without recording your screen, and put it where people will see it.
Why release notes go unread
A line like “Added CSV export to Reports” makes sense to the team that built it. To a user it raises questions: which report? where is the button? what do I get? Most people will not go and look. A video answers all three without asking anyone to read, and it works for the users who never open your emails but do watch a short clip inside the app.
| Format | What the user gets | Best for |
|---|---|---|
| Text changelog | A list of changes to read | Small fixes, a full record of every release |
| Screenshot or GIF | One silent picture of the new screen | Visual tweaks that need no explanation |
| ✨ Announcement video | The change shown working, with a voice and subtitles, in 30–90 s | Features you want people to actually use |
Keep the text changelog: it is your record. Add a video for the changes that matter.
A four-part script that works
An announcement video is not a tour and not a full lesson. Your viewers already know the product, so skip the introduction and go straight to the change:
- What is new, in one sentence. “You can now export any report to CSV.”
- Where to find it. “Open Reports, and you will see the new Export button at the top right.”
- Show it working once. One click, one result on screen: the file is ready.
- Why it helps, in one sentence. “Your numbers go straight into your spreadsheet, with no copying.”
End with a “try it now” line that names the place again: “Try it now in Reports.” That is the whole video: usually three to five scenes and about a minute.
How to make it with DashCast, step by step
Recording a clean take, then editing, voicing and subtitling it, takes hours for a one-minute clip. With DashCast there is no recording:
- Start a new video and choose the type ✨ What's new. It sets everything for an announcement: 30 to 90 seconds, three to five scenes, a direct and upbeat tone, and a camera that goes straight to the new feature with no tour of other screens on the way.
- Choose ✨ Write it for me automatically: paste your app link, a test login, and one sentence about the change, for example “Show the new Export button on the Reports page.”
- Pick the language and the screen: Desktop, or Mobile for a portrait video that fits social feeds and phones.
- The AI opens your app, writes each scene with its sentence, zoom and highlight, and checks every click on your real screens. Change anything you like in the Scene Designer.
- Press Render. You get an MP4 with a natural voice and a subtitles file, ready to share.
Want to see a real render first? Try it live on the home page, with no account.
A release with several changes? One video per change
Do not pack five features into one long video: viewers stop at the second one. Make one short video for each change. If a release is big, choose Lesson series and create them together: each lesson announces one change and stands on its own, so a user can watch the one about the report they use and skip the rest. Together they become your release notes as videos.
Where to put the video so users see it
- Inside your app, in the “what's new” pop-up or panel, so users see it right after logging in.
- On your changelog page, at the top of the entry, above the text.
- In the update email, as a thumbnail that links to the video. A picture with a play button gets more clicks than a list.
- In the help center, in the article about that feature, so new users find it later too.
- On social media, in the portrait version with subtitles on. A new feature is a good reason to post.
- In your users' languages: open Other versions of this video to make a copy in another of the 14 narration languages.
Tips for better announcement videos
- Make it on release day. The video is ready in minutes, so it can go out with the release, not a week later.
- Use a test account with real-looking data. An empty report announces nothing. Blur anything private that still shows.
- The feature must be live and reachable. DashCast opens your app from the internet with a username and password, so use an account without a code sent to a phone.
- Name the exact place. “Reports, top right” beats “in the app”.
- Skip the hype. “We're thrilled to announce” wastes the first five seconds. Start with what changed.
- Link to a tutorial when the feature needs more than a minute. Read more in six types of software videos.
When the feature changes again
A DashCast video is a written scenario, not a recording, so the next redesign does not mean starting over. Press “🔍 Check selectors”: it lists every step that no longer finds its button or field. Fix those steps and render again. More in updating video docs without re-recording.
What it costs. A free account includes 10 minutes of video with no credit card, enough for several announcements. After that, video minutes start at $5 for 100 minutes, or plans from $9 a month. A one-minute announcement uses about one minute, and a failed render is never charged.
Making a video for new visitors instead of existing users? Read how to make a product demo video.
Frequently asked questions
How long should a feature announcement video be?
Between 30 and 90 seconds. Say what is new, show where to find it, show it working once, and say why it helps. If users need to learn a whole new task, make a separate tutorial and link to it.
Do I need to record my screen to make one?
No. In DashCast you choose the ✨ What's new type, give your app link, a test login and one sentence about the change. The AI writes the scenes, and DashCast plays them in a real browser and adds the voice and subtitles.
What if a release has several changes?
Make one short video per change. With a Lesson series you can create them together: each lesson announces one change and stands on its own, so users watch only the ones they care about.
Can I make the video in my users' languages?
Yes. Open Other versions of this video to make a copy in another of the 14 narration languages, with its own voice and subtitles.
Your next release, announced in a video.
Sign up free and get 10 minutes of video with no credit card. Choose ✨ What's new, paste your app link and describe the change in one sentence.