Video Marketing

The SaaS Social Launch Video Blueprint: Engineer Repetition, Not Virality

SaaS launch week: one post is one shot, take five in a week

Why it matters

Most launch videos get one shot

Most SaaS launch videos get one post on one day. Then the feed moves on. If that post doesn't take off, the team calls the launch a flop.

Supabase, the open-source database company, decided one day was the wrong unit for a launch. Its blog post on how it launches lays out a different method, and it's one you can copy with video.

How Supabase launchesWhat its blog says
FormatOne major feature or announcement a day for a week, after a three-month build
First Launch WeekMarch 2021: seven major features, and an immediate uptick in growth
GrowthDatabases managed grew 47% month on month for 18 months, with Launch Week a key part of its product-led strategy
UI library launchFront-end and design channels, plus Product Hunt
Storage launchHacker News and technical audiences
Launch day ruleNo shipping to production on launch day itself

Supabase credits the 47% to its wider product-led strategy, not to launch weeks alone.

The short answer: stop betting the launch on one viral post. Take five good shots in one week. Send each feature to the channel whose audience cares about it, let the builder tell the story, and build every clip the same way: working product first, proof in the middle, one link at the end. Each section below includes a launch or feature video we made for a software client.

Planning a launch week?

Talk to the Advids team about a set of launch videos cut for each feature and each channel.

Let’s talk

Reach, not viral

Going viral is luck; reaching the right people is a system

You can't control which post an algorithm picks. You can control how many good shots you take.

"Make it go viral" isn't a plan. It's a hope. What you can control is how many good shots you take, and whether each one reaches the right people.

Eleken, a SaaS design agency, puts it simply: you don't need to go viral, you just need to get in front of the right people.

Think of it like fishing. One cast in the biggest lake might catch something. Five casts, each in the spot where that fish actually lives, almost always do. So instead of engineering virality, engineer repetition.

That changes what a social media teaser has to do. It doesn't need to please everyone. It needs to stop the right person in the first seconds.

Atlas: it names its viewer first

Our launch video for Atlas, a teamwork directory, opens on its viewer's problem in kinetic type: "As you scale", "more teams grow", "more work happens", "It's hard to make sense of it all". Then "Meet Atlas", and four short questions, each with a product screen: what you're doing, why you're doing it, who's working on it and how it's going. See how we made it.

What works here:

  • The first words tell a scaling team the video is for them.
  • Every claim is on screen as text, so the clip still works on mute.

The move: Open on the situation your right viewer is in. People outside it can scroll past. That's fine.

Repetition needs a calendar. Here's how Supabase builds one.

Launch week

Turn launch day into launch week

One major feature or announcement a day, for a week.

Instead of one launch day, Supabase runs a launch week: one major feature or announcement every day for a week, at the end of a three-month build cycle. In its first one, in March 2021, it shipped seven major features and saw an immediate uptick in growth.

Here's the line worth pinning on every marketing team's wall. Supabase found you can launch a feature many times over and still reach people who missed it the first few times. We all overestimate how many people saw our last post. So each product announcement video can run again, in a new place, and still be news to most of the people who see it.

DayFeatureVideo
MondayThe headline feature30-second clip, plus a longer walkthrough
TuesdayA feature for developers30-second clip with real code on screen
WednesdayA feature for designers30-second clip of the UI in use
ThursdayAn integration30-second clip of the two products working together
FridayA customer or community story30-second clip with the proof up front

That plan is our example, not Supabase's schedule. Your days follow your own features.

Slack canvas: one feature, its own video

Our video for Slack canvas gives one feature the whole runtime. Familiar Slack icons fold into a single page, then one project, "Project Alpha", fills it: an action items checklist, a manager approval request, a comment that catches a wrong date, linked canvases, and a search that finds "Technical Resources" again. See how we made it.

What works here:

  • It's made for people already in Slack, so it starts from what they know.
  • One fictional project carries every feature, so the page fills up in front of the viewer.

The move: Give each day of your launch week one feature and one example the viewer can follow from start to finish.

So that's the calendar. Now, where does each day's video go?

Channel per feature

Pick the channel per feature, and let the builder tell it

Supabase doesn't post everything everywhere. Each feature goes where its audience already is.

When Supabase launched its UI library, it went after front-end and design channels and made sure it ranked on Product Hunt. When it launched file storage, it went to Hacker News and technical audiences, because that crowd cares about how it's built.

So match the video to the channel. A Product Hunt launch video shows the product doing the job fast. A Hacker News post earns its clicks with how it works, so the clip can show the code.

There's one more detail worth stealing. At Supabase, the person who built the feature usually writes the marketing for it. On video, that's gold. The engineer who built it, explaining why it matters, is more believable than any voiceover.

Sisense Compose SDK: made for developers

Our 50-second video for the Sisense Compose SDK speaks to one audience. It never shows a Sisense screen. The charts appear inside two example apps, a shoe store and a finance tool. Then TypeScript, Angular, Vue and React logos rise on discs, and a code editor types out a React component that imports from "@sisense/sdk-ui". See how we made it.

What works here:

  • Framework logos and real code answer a developer's first questions without a word.
  • The video is short enough for a developer feed and specific enough for a technical forum.

The move: Decide which channel a feature belongs to, then put on screen what that channel's audience checks first.

Now let's build the clip itself.

Clip structure

Build every clip to travel

Thirty seconds, captions on, with one action at the end.

Each day's clip follows the same shape. In the first three seconds, show the feature actually working. Not a logo, and not "we're excited to announce". Then the builder says why it matters. Then proof. Then one link, not three.

SecondsBeatWhat's on screen
0 to 3It workingThe feature doing its job, no logo first
3 to 20Why it mattersThe builder on camera, captions on
20 to 30ProofA beta user, a community post, a known developer trying it
EndOne actionOne link

That's our recommended structure, not a rule from Supabase. Video ad producer Fraser Cottrell explains why the proof beat matters. Social proof works not because the majority is always right, but because we're afraid we might be wrong. So cut in real reactions.

Captions matter because many people watch feeds on mute, and silent video has to carry the message alone. Vertical suits short-form video placements.

Chargebee: the proof is a customer

Our animated video for Chargebee, the subscription billing platform, is built around one customer, Study.com. A laptop opens on an e-learning maze, alerts pop up across a globe, and the screen asks "What does this CHANGE". A revenue and billing dashboard follows, then the customer's scale on screen: "18,000+ Learning tools" and "25 MILLION hours of education". See how we made it.

What works here:

  • The proof is a named customer and its numbers, not the vendor's own claims.
  • Each number gets the screen to itself, so it can be read in a feed.

The move: Find the customer or community post that proves your feature, and give it the middle of the clip.

Then cut a longer version from the same footage for the channels that want depth, such as a three-minute walkthrough for YouTube or for Hacker News readers. Supabase stopped shipping to production on launch day itself. Do the same with your videos and lock them a week early.

Five days, one channel per feature, one shape per clip. Here's where to begin.

Where to start

Where to start

The short answer: list your features, then match each one to the audience that cares most.

If the feature isIts audienceChannelClipExample to copy
Your headline launchEveryone you want to reachYour main feed, Product Hunt30 seconds plus a longer cutAtlas
A new surface in an app they useExisting usersIn-app, email, socialOne feature, one exampleSlack canvas
An SDK, API or infrastructureDevelopersHacker News, developer feedsReal code on screenSisense
Backed by a customer resultBuyers comparing toolsLinkedIn, sales follow-upProof in the middleChargebee

After launch, keep going. Feature adoption grows when each clip keeps working. Use it to communicate product updates in your changelog, docs and onboarding. We've made video for software teams such as Slack, Sisense, Chargebee and Atlas. See the software teams we've made video for.

FAQ

Questions about SaaS social launch videos

What is a launch week for a SaaS product?
A week with one major feature or announcement each day, instead of one launch day. Supabase runs them, and shipped seven major features in its first one, in March 2021.
How long should a social launch video be?
About 30 seconds for each day's clip, with the feature working in the first three seconds. Cut a longer walkthrough from the same footage for channels wanting depth.
Should the same launch video go on every channel?
No. Match each feature to the channel whose audience cares about it, like design channels for a UI library and Hacker News for infrastructure.
Who should appear in a feature launch video?
The person who built the feature, where possible. An engineer explaining why it matters is more believable than a voiceover, and captions keep it clear on mute.
What belongs in the first three seconds of a launch clip?
The feature actually working. Skip the logo and the "we're excited to announce" line, and show the viewer the result they would get first.
How early should launch videos be finished?
Lock them about a week before launch. Supabase stopped shipping to production on launch day, and the same rule keeps last-minute video fixes out of launch week.

About the author

About Jai Ghosh

Video Producer at Advids · LinkedIn

Jai Ghosh is a Video Producer at Advids, where he has planned and produced videos for B2B software and technology companies for 7 years. He works on product demos, explainer videos and brand videos, from the first script to the final cut, for clients from startups to enterprises.

Before Advids, Jai spent over 11 years in freelance media consulting, after starting out in digital journalism. He writes the Advids blog's breakdowns of product and demo videos, sorting real examples by the question each one answers for a buyer.

  • Focus: SaaS product demos, explainer videos and brand videos
  • Experience: 7 years at Advids, over 11 years in media consulting
  • Background: digital journalism

Connect with Jai Ghosh on LinkedIn

Sources

Sources