Most software companies I know release something every week or two. A new integration, a better report, a setting customers asked for. The product team writes a release note, the change goes live, and the product is a little better than it was.
Then marketing has to decide what to do with it. The big releases get a launch plan. The rest get a line in the changelog and maybe a post on LinkedIn. Video, if it happens at all, happens a few times a year. That gap between how often you release and how often you show it is where buyers stop hearing from you.
The release gap
Every release is proof that the product is moving. For a buyer comparing three vendors, that matters. A company that shows a steady stream of improvements looks alive, responsive and worth betting on. A company that goes quiet for a quarter looks the opposite, even if its team worked harder than anyone.
Your existing customers notice too. Some of the features they asked for go live without them ever finding out. A short video on the day of the release tells them, in a form they will actually watch.
So the question is not whether releases deserve video. It is why so few of them get one.
Why does a launch video take weeks?
Because the usual process was built for a few big videos a year, not one a week. We described it in Agency video is broken: a brief, a storyboard, review rounds, a first cut, corrections, more review rounds. Each step waits for the one before it. By the time the video is ready, the release is old news and the UI has often changed.
The time does not go into the creative work. It goes into handoffs. Somebody has to explain the feature to someone who has never used the product. Somebody has to explain the brand to someone who did not make it. Then everyone has to check that both were understood.
Remove the handoffs and the weeks fall away. That is a change of workflow, not of budget.
What a same-day launch video needs
To make a video on the day a release goes live, you need four things in place before the release, not after it:
- Approved copy. The release note or support article is the script. It already says what changed and why it matters, and it has already been checked.
- A brand that is learned once. Fonts, colours, motion and voice should not be explained again for each video. They should be the starting point.
- A launch format. A fixed shape for release videos, so nobody designs from a blank page and buyers learn to recognise your launches.
- Versions for each channel. Widescreen for YouTube and your website, square and vertical for the social feeds, cut from the same video.
With those in place, the work on launch day is short: give the release note to the system, check the draft against the release, and publish. One person can do it between meetings.
That is the workflow Saltfish Video is built for. Your team links a release note, a support article or a blog post, and gets a video in your launch format, trained on your brand book, website and best videos. Saltfish then reframes it for each channel, and on our Scale plan redoes the voice, captions and text on screen for each language. If you want a release pipeline to trigger videos on its own, the API, CLI and MCP add-on lets you make them from your own tools.
A worked example: from support article to launch video
Here is a real one. IcePanel, which helps software teams model their architecture, documented a new feature called Agent skills in a support article. IcePanel pasted that article into Saltfish, and Saltfish made the launch video “Your code becomes the model” in IcePanel’s brand.
Nobody wrote a script, because the article already was one. Nobody briefed a designer, because the brand was already learned. You can watch the video next to the article it came from in the examples on our home page.
The same pattern works for any release with a written source: a release note, a help article, a changelog entry, a short internal brief.
Tiering: which releases get a video?
A video for every release does not mean the same video for every release. A simple tiering keeps the effort in proportion:
- Major launches get the full treatment: a hero video, cut-downs for every channel, a version for sales and, where it matters, other languages.
- Notable features get a launch video on the day they go live, plus a social cut.
- Smaller improvements get grouped into a monthly round-up video, so they still add up to a story.
- Fixes and internal changes stay in the changelog.
Agree the tiers with product once, then tag each release as it is planned. When launch day comes, nobody has to argue about whether it deserves a video.
When a big launch still needs an agency
There are still moments for a production crew. A brand film, a keynote opener, a customer story shot on location, a campaign that needs a creative idea nobody has had yet. Those are worth the time and the budget, and a good agency earns its fee on them.
The point is that those moments are rare. The weekly work of showing a product that keeps getting better should not wait for them. Let the agency and your in-house team focus on the big productions, and give the weekly volume a workflow of its own.
If you want to close your own release gap, start with one release. Your first video is on us. When you are ready for more, our Growth and Scale plans are built for on-brand video every week, or book a demo and bring your latest release note.
