To make an explainer video for your startup homepage, build the whole video around one diagram of what your product does, and make it work with the sound off. Keep it to 60 to 90 seconds (150 to 225 spoken words), put the outcome on screen in the first five seconds, and add burned-in captions or on-screen labels for every point the narration makes. Place it beside or just below your headline, not in a pop-up, with a poster frame that already explains something before anyone presses play. Then measure it: compare signup rate for visitors who played it against those who did not, and cut it if it is not earning its place above the fold.

The homepage is a hostile place for video

A homepage visitor is deciding in a few seconds whether to stay. They did not come for a video, and most of them will never press play. Of those who do, many will watch muted, on a phone, with a notification arriving halfway through.

That gives a homepage explainer constraints that a sales or onboarding video does not have:

• Muted by default. Browsers block autoplay with sound, so if the video starts on its own it starts silent. If the story needs the narration to make sense, most viewers get no story.
• Five seconds to earn the next five. Viewers decide quickly whether to keep watching. A logo animation or a "Meet Acme" title card spends those seconds on nothing.
• It competes with your headline. The video and the headline should say the same thing in two forms, not two different things.
• It costs page speed. A heavy video file loaded eagerly can slow the first paint of the page it is meant to help.

So the homepage version of an explainer is shorter, more visual and more literal than the one you would send a prospect. The general structure for SaaS explainers (situation, idea, change, next step) is covered in how to make a product explainer video for a SaaS app; this post is about bending it to fit the homepage.

One diagram, built up

The pattern that survives the constraints above is a single diagram that builds through the video. Scene one draws the first part of it, each later scene adds a part, and the last scene is the whole diagram with your call to action. Anyone who stops watching at any point has still seen a coherent piece of the picture, and the final frame works as a summary.

The diagram is usually one of three shapes:

If your product does not fit any of these, write your one-sentence pitch and look for its verb. "Joins" is the first shape, "skips" or "automates" the second, "warns" or "catches" the third.

Worked example: "what our product does, in one diagram"

Take a startup whose product joins a small company's support channels into one queue. Here is the spine of the script, about 80 words, with the diagram state at the end of each scene. Give each line a second sentence of detail and it reaches a full minute.

1. "Your customers write to you in four places: email, chat, Instagram, and the contact form." Four scattered icons, each with a small pile of messages.
2. "Your team checks all four, and some messages get answered twice while others wait three days." Two people running between icons; one message turning red, labelled 3 days.
3. "We put every message in one queue, in the order it arrived." Arrows from all four icons into a single list in the middle.
4. "Each one gets one owner. Nobody answers twice, nothing waits unseen." A name tag appears on each row of the list.
5. "Most teams get their first reply time under an hour in the first week." A clock on the list showing under 1 hour. (Only if that number comes from your own customers. Otherwise, cut the line.)
6. "Connect your inbox and see your queue in five minutes." The whole diagram, the logo once, the button text matching the button on the page.

Scene 1 is your poster frame candidate, but scene 3 is usually better: it already shows the product's idea, so the still image explains something to the visitors who never press play.

Every scene puts the key words on screen as labels (four places, 3 days, one queue, one owner, under 1 hour), so the muted version tells the same story as the narrated one.

Embedding it without hurting the page

A few settings matter more than the video itself.

• Poster image. Set a still frame that makes sense on its own. The default first frame is often blank or a title.
• Lazy loading. Do not load the full video until the visitor interacts with it or scrolls near it. Your headline should paint first.
• Autoplay only if muted and captioned. If you autoplay, the video must be muted (browsers require it) and should loop quietly or stop on the final diagram. On iPhones, inline playback needs the playsinline attribute or the video jumps to full screen.
• A visible play control with the length. "Watch, 75 seconds" sets an expectation and gets more plays than an unlabelled thumbnail.
• Captions that are part of the picture. Burned-in labels or captions survive every player and every social share. A separate caption file is still worth adding for accessibility.
• No watermark. A third-party watermark on your homepage tells visitors what you used rather than what you sell. If you made the video on a free tier, pay to export a clean version before it goes live.

Make it

1. 1

   Pick the diagram shape

   Joins, skips or warns. Write your one-sentence pitch and use its verb to choose. Sketch the final diagram on paper before writing a word of script.

2. 2

   Write 150 to 225 words, one diagram part per line

   Each sentence adds one piece to the diagram. Put the outcome in the first line and the call to action, matching your button text, in the last.

3. 3

   Paste it and keep your wording

   In openCanviz, paste the script with Keep my wording on, set a target of about a minute, and pick one style. Poster suits a single bold before and after; whiteboard suits a product that is explained more than sold.

4. 4

   Put every key word on screen

   Go through each scene in the editor and make sure the number or phrase the narration stresses appears as a label, so the muted version works on its own.

5. 5

   Record the founder's voice

   Replace the generated narration with your own recording. For a homepage, a real founder's voice is a credibility signal on its own.

6. 6

   Export clean and embed lazily

   Pay for the clean export of this one project so there is no watermark, choose a poster frame that explains, and load the video only when the visitor reaches it or presses play.

How to tell whether it is working

A homepage video has to earn its space, and the only way to know is to measure.

• Play rate. The share of homepage visitors who press play. Low play rate usually means the poster frame or the label is not doing its job, not that the video is bad.
• Completion to the last scene. If most viewers drop at scene two, your opening is the problem. Rewrite it before touching anything else.
• Signup rate for players versus non-players. This is the number that matters, with one caveat: people who press play are already more interested, so the gap overstates the effect. A cleaner test is to show the video to half your visitors and compare signups between the halves over a few weeks.
• Support questions. If people still ask "so what does it actually do?", the video is not saying it.

If the test shows no difference, try a stronger poster frame and a shorter cut before removing it. If it still shows nothing, take it off the homepage and use it in sales follow-ups, where viewers have more patience.

Common questions

How long should a startup homepage video be? Sixty to ninety seconds. Under sixty is fine if the diagram is simple. Over ninety, cut the situation scenes first: homepage visitors already have the problem or they would not be there.

Should the homepage video autoplay? Only muted, with captions or labels carrying the story, and ideally looping or stopping on the final diagram. If your video needs its narration to make sense, do not autoplay; use a clear play button with the length instead.

Should I show the product's interface? Briefly, at most, near the end. Early-stage products change their UI often, and the diagram of what the product does lasts much longer than a screenshot. If your audience is developers, a short request journey can work better; see how to make a video that explains how your API works.

Can I make it before the product is finished? Yes, and it is a useful exercise. If you cannot draw the diagram of what the product does, the positioning is not settled yet. Make a draft, show it to five people in your target market, and ask them to say back what the product does.