Skip to content

Feature launch videos, recorded in the real release and ready on day one.

100+ videos produced for Jotform. 20+ for Knack.

The problem it solves

What this actually fixes.

A launch happens once. The changelog post, the in-app announcement, the email, the social thread, and the sales follow-up all go out the same morning, and each one needs a different length and a different aspect ratio of the same story. Teams either ship the launch with a screenshot, or spend release week cutting a video instead of watching the rollout. Producing the launch beforehand fixes both.

Who needs it

Who this is for.

  • Product marketing teams with a release calendar and a launch to carry every few weeks.
  • SaaS companies whose changelog and release notes get read but not watched.
  • Teams announcing a feature big enough that a paragraph will not do it justice.
  • Founders shipping publicly who need the announcement to look deliberate.
  • Customer marketing teams who have to tell existing users what changed, not just prospects.

Where they get used

Every video is made for a placement, not a folder.

We ask where a video will be embedded before we script it, because the placement decides the length, the aspect ratio, and whether it has to work with the sound off.

01

Changelog entries, release notes, and the launch blog post.

02

In-app announcements, release banners, and what's-new modals.

03

Launch email to existing customers and to the waitlist.

04

Social posts and threads, using the vertical and square cuts.

05

Sales outreach and renewal conversations, where a new feature is the reason to reopen a thread.

06

Help-center articles for the feature, once the launch week is over.

What’s included

Everything in the list below is standard.

Nothing here is an upsell. If a deliverable is quoted separately, it is named as an extra on the estimate before you agree to anything.

A launch script built around the one thing that changed and why it matters to existing users.
Screen recording inside the real feature, from a production or staging build.
A 16:9 master cut for the blog, changelog, and email.
Vertical and square cuts, reframed rather than cropped, so the interface stays readable on a phone.
A short in-app cut that works silently in a narrow panel.
Launch titles, branding, and on-screen text matched to your release design.
Voiceover, or a narration-free version for autoplay-muted placements.
Burned-in captions plus SRT and VTT files, a thumbnail frame, and a looping silent version.

Length and delivery

How long, and how soon.

Typical length
60–120 seconds for the master cut; 15–30 seconds for the social and in-app versions.
Typical delivery time
About 2–3 weeks from an approved script, scheduled to land before the release date. Rush delivery is available at 30% extra.

The clock starts when the script is approved and a recording environment is available. Those two things are what usually move a schedule, so we agree both before quoting a date.

Every project, the same way

The parts that never change.

Four stages, and you are needed for two: your team scopes the list and approves the scripts, then recording, editing, voiceover and revisions happen without your calendar. Human-recorded English narration is the default, synthetic voice is available where re-cuts are frequent, and every video ships with captions, an SRT and a VTT. Two revision rounds are included and you own the finished files outright.

What affects the price

The variables that move a quote.

Feature Launch Videos is quoted per project, because the same runtime can mean very different amounts of work. These are the factors that change the number.

Factors that affect the price of Software Feature Launch Video Production from DocFlow Studio
FactorHow it moves the price
Number of cutsthe master carries most of the cost. Channel versions are cheap once it exists.
Build stabilityrecording an unfinished staging build usually means re-recording screens as the feature settles.
Motion graphicslaunch titles, transitions, and release branding raise the finish level and the price.
Staging efforta launch needs believable data on screen, and a brand-new feature rarely has any yet.
Turnarounda locked release date with a short runway is priced above the standard schedule.
Release cadencea fixed template reused every launch lowers the per-video cost from the second release onward.

Ongoing work runs on monthly plans priced in production credits — see monthly SaaS video production plans. For a single video, send the product and the problem and you get back a video list, a recommended length for each, and a fixed price — not a discovery call. Request a fixed quote.

Questions

Feature Launch Videos, answered.

Read all FAQs

How is a launch video different from a product demo or a tutorial?

A demo sells the whole product to someone who has not bought yet. A tutorial teaches one task to someone already using it. A launch video does neither: it tells everyone, on one day, that a specific thing is new and why it is worth their attention. It is the shortest of the three and the only one with a deadline.

Can you record the video before the feature is public?

Yes, and that is the usual case. We record in a staging or pre-release build so the video is finished before release day. What we will not do is animate an interface that does not exist yet — if there is no build to record, the video waits or the launch gets a different treatment.

What if the feature changes between recording and launch?

Expected, and planned for. Scripts and project files are kept in segments, so a screen that changes late is a re-record of that segment rather than a rebuild. Late changes are why the schedule works back from your release date rather than forward from the kickoff.

How many versions do we get for the different channels?

One master plus the cuts your channels actually use — typically vertical and square for social, a short silent cut for the in-app announcement, and a thumbnail for email. They come out of the same edit, so the story stays consistent everywhere it lands.

How far in advance should we book a launch video?

Two to three weeks before the release date, counted from an approved script, with a recordable build available at the start of that window. Rush delivery for a fixed date is available at 30% extra, but booking early costs less and produces a calmer week.

Can the launch video be reused after release week?

Yes, and it usually is. The master becomes the feature page video, the short cut goes into the help-center article, and the in-app version stays in the product for new accounts that never saw the announcement. You own all of it outright on delivery.

Do you handle recurring launches?

Yes. Teams shipping on a regular cadence usually settle on a fixed launch template — same titles, same pacing, same structure — which makes each release faster to produce and cheaper than the one before it.

Start with the Feature Launch Videos you need first.

Tell us the product and what your users get stuck on. You get back a video list, a recommended length for each, and what it costs.

Produced by the team behind SaaS Master, reviewing and demonstrating software publicly since 2019.