Solution Explainer Video SOP

A solution explainer video SOP tests whether people understand your solution and want it after watching 60 to 90 seconds about it, and it takes two to three weeks. You script a short video, check that target customers can retell it correctly, then share it and measure who watches to the end and who clicks. A video shows a product that doesn't exist yet in motion, which is why it works for ideas that a headline can't carry. Eric Ries recounts in The Lean Startup that Dropbox's beta waiting list jumped from 5,000 to 75,000 people overnight after Drew Houston posted a demo video, long before the product was ready for the public.

What is a solution explainer video and when should you use it?

A solution explainer video is a short, simple video that shows the problem, how your solution handles it and the result for the customer, ending with one call to action. In this SOP the video is a test instrument. You measure two things: comprehension (can viewers say what it does and for whom) and demand (do they watch to the end and sign up).

Use this SOP:

• When your solution takes more than one sentence to explain, such as a new workflow, a device or a product category people haven't seen.
• When your landing page converts poorly and visitors seem confused.
• Before a crowdfunding campaign or a pitch, where the video does most of the selling.
• When you need to show a workflow that a static page can't.

The video comes after the story is clear. Draw the scenes first with the solution storyboarding SOP, and pick the promise you lead with through solution value proposition testing.

What do you need before you start?

• One sentence saying who it is for, the problem, how it works and the result.
• A storyboard or shot list of six to eight scenes.
• A production method you can afford: a Loom screen recording, slides animated in Canva, an animation tool such as Vyond, or phone footage of a prototype.
• 10 target customers for comprehension tests, on 15-minute calls.
• A host with audience retention data, such as Wistia or YouTube, and a landing page with one signup button.

How do you run it, step by step?

1. Write the one-sentence summary

"For [customer] who [problem], [product] [does what] so they [result]." If you can't write this sentence, the video will wander. Every scene must serve it.

2. Script 60 to 90 seconds

At a natural speaking pace of about 150 words a minute, 90 seconds holds roughly 225 words. Split them: problem (15 seconds), solution in action (35 seconds), result (20 seconds), call to action (10 seconds). Show the customer in the first five seconds, so viewers know at once whether the video is for them.

3. Turn the script into scenes

Match every line to a visual from your storyboard. Show the product doing the job, even as a mock-up or a clickable prototype, rather than talking about features. Add captions so the video works with the sound off.

4. Produce the cheapest version that looks honest

A screen recording with a clear voice-over beats a polished animation that hides how the product works. Use Descript to edit by text and Canva for titles. Label mock-ups as previews.

5. Run a comprehension test with 10 people

Show the video once to each target customer, then ask: "In your own words, what does this do and who is it for?" and "What was unclear?" Score each retelling as correct, partly correct or wrong. If viewers can't retell it, numbers from a wider audience won't help.

6. Fix and retest

Change what confused people, such as an unclear opening or a skipped step in the workflow, and retest with five new viewers. Repeat until 7 of 10 retell it correctly.

7. Share it with the target audience

Put the video at the top of a landing page and run it as an ad to your segment, or share it in communities where the rules allow. Keep the call to action single and specific: "Join the early access list."

8. Read the retention graph and decide

Look at where viewers drop off in Wistia or YouTube analytics. A cliff at second 8 means the opening fails; a cliff before the call to action means the video runs too long. Compare clicks and signups with your pass line, then decide whether to build, change the story or change the audience.

Template you can copy

EXPLAINER SCRIPT (75-90 seconds, about 190-225 words)

0:00-0:05  HOOK: show the customer in the problem moment.
           Caption: "[Customer] spends [time] every [period] on [task]."
0:05-0:15  PROBLEM: what goes wrong today, in their words.
0:15-0:50  SOLUTION IN ACTION: 3 steps, each shown on screen.
           Step 1: [action]  Step 2: [action]  Step 3: [action]
0:50-1:10  RESULT: the after picture, with one number (time or money saved).
1:10-1:20  CALL TO ACTION: "[Product] is in early access. Join at [URL]."

COMPREHENSION TEST (per viewer)
Viewer | Correct / Partly / Wrong retelling | Their words |
What was unclear | Timestamp of confusion | Would sign up Y/N

DISTRIBUTION LOG
Channel | Views | % watched to end | CTA clicks | Click rate | Signups |
Signups per 100 viewers | Biggest drop-off (timestamp)

Worked example: progress reports for renovation contractors

This example is illustrative. A founder plans a tool that turns a contractor's job-site photos into a client-ready progress report. She scripts a 75-second video of about 190 words and records it with a clickable prototype.

• Round one: 6 of 10 contractors retold it correctly. Four thought it was an app for homeowners, because the first scene showed the client.
• She reshot the opening to show a contractor on site. Round two: 9 of 10 correct.
• Distribution: $150 of ads aimed at contractors plus posts in two trade groups brought 1,240 views.
• 58% watched to the end, 96 viewers (7.7%) clicked the call to action, and 41 signed up.

The retention graph showed a small drop at second 40, where the voice-over listed features. She cut the list, kept the video and used it as the hero of her landing page test.

What should you measure, and when do you stop?

Stop the comprehension rounds when 7 of 10 pass. Stop distribution when the video reaches about 1,000 views from your target segment. If people understand the video and still don't click, the issue is demand or audience, and editing the video won't fix it. Go back to concept testing or try a different segment.

Which mistakes should you avoid?

• Starting with the logo and the founder story. Viewers decide in seconds whether the video is for them. Open with the customer.
• Listing features. Show one job done start to finish instead.
• Spending the budget on polish before the comprehension test. A $2,000 animation that confuses people is worse than a free screen recording that doesn't.
• Testing with friends. They already know what you are building, so they "understand" everything.
• Showing a product you can't deliver. Mock-ups are fine when labelled. Fake features turn signups into refunds later.

How can AI speed this up?

An AI assistant can draft the 190-word script from your one-sentence summary and storyboard, then cut it to time. AI voice tools generate a clean voice-over, and Descript can remove filler words and add captions automatically. After the comprehension test, paste the retellings into the assistant and ask where the misunderstandings cluster. The human check: you watch every comprehension session yourself, because the pause before someone says "so it's for... clients?" tells you more than any transcript.

For distribution, the free social media module covers posting video where your audience is, and the marketing ideas generator suggests places to share it. For more reading on testing ideas cheaply, our sister site lists 100 startup books for founders.

Where does this SOP fit in your validation plan?

The explainer video sits in the second half of Solution Validation, once the story and the promise are clear.

1. Before: draw the scenes with solution storyboarding and choose the promise with solution value proposition testing.
2. Next: use the video on a landing page test or as the centrepiece of a crowdfunding campaign.
3. Later: reuse the winning lines across channels with marketing message testing.

See the full list of Solution Validation SOPs.

FAQ

How long should a startup explainer video be?

60 to 90 seconds. That is enough to show the problem, the solution and the result, and short enough that half the viewers reach the call to action.

How much does an explainer video cost?

From $0 with a screen recording and free editing tools to $1,000 or more for animation. For a validation test, start with the cheapest version that shows the product honestly.

Can I make an explainer video before the product exists?

Yes, with a clickable prototype or mock-ups labelled as previews. The Dropbox video in The Lean Startup is the best-known case.

How do I test if my explainer video works?

Show it to 10 target customers and ask them to retell it in their own words. If 7 or more get it right, share it widely and measure watch time and signups.