Use case: feature releases
A video for every feature you ship, not just the big ones
Product teams ship every week. The changelog gets a paragraph and maybe a GIF, because a proper video costs more than the feature is worth to promote. Softer makes the per-feature video cheap enough to be routine.
Updated
The economics of the small release
A big launch can justify an agency. A feature announcement usually can't: nobody spends a few thousand dollars and three weeks on a video for bulk export or a new filter. But these are exactly the releases customers ask for, and a 20-second clip that shows the feature working is what gets them used.
On Softer's Volume plan a video costs $8, and every edit inside it is included. That changes the question from "is this feature big enough for a video?" to "which channel does this video go to?"
From changelog entry to video
Paste the changelog entry, or write the brief in one line: "20-second vertical clip announcing CSV export in Trackwise, for ops managers." Softer writes the script, picks up your brand from the kit it captured at signup, records the voiceover, adds a music bed and animates the feature as motion graphics: the export button, the file landing, the spreadsheet filling in. Captions are drawn in word by word, on by default.
| Placement | Suggested format | Length |
|---|---|---|
| Changelog and release notes | 16:9 | 20–40s |
| In-app announcement modal | 16:9 or 1:1 | 15–20s |
| LinkedIn, X, Reels, Shorts | 9:16 | 15–30s |
| Customer newsletter | 16:9 (linked thumbnail) | 30–45s |
| Help-center article | 16:9 | 30–60s |
Changelog and release notes
- Suggested format
- 16:9
- Length
- 20–40s
In-app announcement modal
- Suggested format
- 16:9 or 1:1
- Length
- 15–20s
LinkedIn, X, Reels, Shorts
- Suggested format
- 9:16
- Length
- 15–30s
Customer newsletter
- Suggested format
- 16:9 (linked thumbnail)
- Length
- 30–45s
Help-center article
- Suggested format
- 16:9
- Length
- 30–60s
Keep a house style with Reuse
Once one feature video looks right, you don't start from zero for the next. Reuse branches it: "same format, now announcing saved views". The pacing, voice, music and layout carry over, the content changes, and the original stays intact. Over a quarter your release videos start to look like a series, which is what a brand is.
Changes are a sentence, not a ticket
- "Rename the feature to 'Saved views', marketing changed it."
- "Slower on the second step, people need to read the menu."
- "Swap the voice for something warmer."
- "Turn off captions for the in-app version."
Each one re-renders the video. When the feature name changes the day before release, the video is not the thing that holds you up.
Writing a good feature brief
- Say who it is for. "For admins" and "for end users" produce different scripts.
- Say the before and after. "Used to take a support ticket, now it's one click."
- Pick the channel, which picks the aspect ratio and length.
- Give one call to action: try it now, read the docs or update the app.
Sample feature video
A 20-second feature announcement for an invented SaaS brand. Sample coming soon.
Make yoursQuestions
How short can a feature video be?
Videos run from 15 to 120 seconds. For social and in-app announcements, 15 to 30 seconds works best.
Can I make the same announcement in several languages?
Yes, with Reuse: ask for the video in another language and Softer branches a new version with a new script and voiceover. The original stays as it was.
Do captions come included?
Yes. Word-timed captions are drawn into the animation and are on by default. You can ask to turn them off.