Cold visitors do not owe you a five-minute tour. They land with a half-formed question—“is this for me?”—and they will leave if the answer takes a meeting, a sales deck, or a wall of screenshots. A tight 90-second product demo is often the fastest honest answer you can put on the page.
This is a solo-maker playbook. One job. A cold-visitor script with timing. A Loom-or-phone setup that does not need a video team. Thumbnail and landing placement that actually gets watched. A 14-day check on watch-to-signup—not vanity views.
If you already have a polished brand film, keep it for launch day. This post is for the demo that sits above the fold next to your signup button and does the work of a patient founder who cannot hop on every call.
Why 90 seconds (not 4 minutes)
Most founder demos fail the same way: they start with origin story, then architecture, then every feature that took a weekend. Cold traffic never asked for that. They asked whether this tool finishes the job they already have in their head.
Ninety seconds forces a cut. Roughly:
0–15s — Who it’s for + the painful job
15–70s — Show the product doing that job once
70–90s — What “done” looks like + one clear next step
Longer videos can work for warm leads, docs, or YouTube SEO. On a landing page for strangers, length is usually a tax. If you cannot show one complete win in under two minutes, the product story is still mushy—or you are demoing the wrong job.
Before you script, get one outsider to react to a rough cut. The same people who will give you brutal feedback before you launch publicly will tell you within ten seconds if they know what the product is for.
Write a one-job brief before you open the camera
Do not start recording. Fill a half-page brief first. If you cannot fill it, you are not ready for a demo—you are ready for another positioning pass.
One ICP sentence — “Solo founders running a B2B SaaS with under 50 customers.” Not “everyone who wants to grow.”
One job — The verb + object they already understand. “Turn a messy Notion dump into a launch checklist.” Not “AI-powered productivity.”
One success screen — The exact UI state that means “it worked.” Export ready. Invite sent. First report green. Pick one.
One CTA — Signup, book a call, or start trial. Match the button on the page. Do not invent a third path in the video.
What you will not show — Integrations tab, settings, pricing tiers, roadmap. Write them down so you do not “just quickly” open them.
Tape that brief next to your mic. When you drift into feature tourism mid-take, stop and re-record from the job.
Cold-visitor script (beats with timing)
Speak like a human who uses the product, not like a trailer voice. Here is a skeleton you can adapt. Times are targets, not a metronome.
0:00–0:08 — Hook with their words
“If you’re trying to [job] without hiring a [expensive alternative], this is a 90-second look at how [product] does it.”
0:08–0:15 — Who it’s not for (optional but sharp)
“This is not for enterprise teams with a full ops stack. It’s for [ICP] who need [outcome] this week.”
0:15–0:25 — Start on the empty or messy state
Show the before. A blank project. A CSV. A cluttered inbox. Cold visitors need to recognize their Tuesday.
0:25–1:05 — Do the job once, out loud
Click slowly. Narrate the decision, not every button. “I’m pasting the brief… picking the one launch goal… generating the checklist…” Pause half a second when the important UI appears. Silence sells more than filler.
1:05–1:20 — Land on the success screen
Zoom or cursor-highlight the proof: the checklist, the link, the green status. Say what “done” means in one sentence.
1:20–1:30 — CTA that matches the page
“If that job is yours, start a free trial from the button on this page—you’ll hit that same screen in under ten minutes.” Then stop. No outro music marathon. No “like and subscribe.”
Read the script once at conversation speed. If it runs past 100 seconds, cut adjectives, not the success screen.
Record setup: Loom, phone, or both
You do not need a studio. You need a clear face-or-voice track, a readable UI, and audio that does not sound like a bathroom.
Loom (or similar) — Best default for SaaS. Screen + bubbled face, or screen-only with voice. Use a quiet room, wired earbuds mic if your laptop mic is hollow, 1080p, browser zoom so text is readable on mobile.
Phone on a stack of books — Fine for mobile-first products or a talking-head intro cut with screen B-roll. Landscape unless your product is mobile-only. Lock exposure; wipe the lens.
Mic — Any lavalier or USB mic beats built-in from three feet away. If you only have AirPods, sit closer and turn off AC.
Screen hygiene — Clean desktop or a dedicated Chrome profile. Fake/demo data that looks real. Hide Slack badges. Turn off calendar popups. Use a large system font if your UI is dense.
Do three takes max per session. Take two is usually the one. If take three still rambles, your brief is wrong—go rewrite the job, don’t “fix it in edit.”
Edit lightly (resist the trailer)
Cut dead air at the start and end. Remove the one cough. Speed 1.0x unless you speak painfully slow—then 1.1x max. Burn in captions if you can (many cold viewers watch muted on mobile). Do not add whoosh transitions, stock music beds, or logo stingers that burn eight seconds of your ninety.
Export MP4, under ~25MB if your CMS is picky, 1080p. Name the file with the job, not “final-final-v7.”
Thumbnail and landing placement
A demo nobody clicks is a blog post you filmed by accident.
Thumbnail — One readable UI win + your face if you have trust to borrow, or a clear “90-sec demo” label. Avoid mystery abstract gradients. Show the success screen, not your logo wall.
Above the fold — Put the player next to the primary CTA, not buried under six feature sections. Cold visitors decide in the first screen.
Poster frame — First frame should not be a blank Loom countdown. Start on face + title card, or the before-state of the job.
Mobile — Check the player on a phone. If UI text is unreadable, re-record with zoom or a simpler path.
Pair the video with honest proof nearby—one quote, one defended number—not a fake logo strip. If you are still thin on proof, use the same discipline as writing social proof for an indie launch with almost no users: permissioned quotes beat invented authority.
Remember the demo sells the start of the job; activation still has to finish it. A great video into an empty dashboard is a broken promise—fix the first ten minutes the way you’d stop obsessing over the landing page and fix time-to-first-action.
Measure for 14 days (watch → signup, not vanity views)
Ship the demo. Then track a short list for two weeks. If you cannot instrument this, a spreadsheet and daily manual counts still beat vibes.
Play rate — Plays ÷ landing sessions (roughly: are people clicking?)
Watch depth — % reaching ~75% (did the job stick?)
Watch → signup — Signups from sessions that played vs those that didn’t (even a rough split is gold)
Qual — Reply to 5 new signups: “Did the demo match what you got after signup?”
Decision rules that keep you honest:
High play rate, low watch depth → hook or length problem; tighten the first 15 seconds.
High watch depth, low signup → CTA mismatch, pricing shock, or post-click friction—not a “make a cooler video” problem.
Low play rate → thumbnail/placement; move above the fold before you re-film.
Signups say “demo showed X, product is Y” → re-record against the real success screen. Do not add more features to the video to paper over the gap.
Traps that waste a weekend
Feature tourism — Opening every tab “while you’re here.” Cold visitors came for one job.
Origin story tax — Your fundraising arc does not belong in the first 20 seconds of a product demo.
Fake data that lies — Demo accounts with impossible metrics train distrust. Use believable sample data.
Music louder than voice — Mute-first viewers and anyone over 30 will bounce.
CTA drift — Video says “book a call,” page says “Start free.” Pick one.
Perpetual re-cut — Ship a B+ demo this week. Improve from the 14-day numbers.
90-second demo checklist
□ One-job brief filled (ICP, job, success screen, CTA, won’t-show list)
□ Script timed under 90–100 seconds at conversation speed
□ Clean demo environment + believable sample data
□ Mic test; captions if possible
□ Thumbnail shows the win; player above the fold next to CTA
□ CTA spoken in video matches the button on the page
□ 14-day tracking: play rate, watch depth, watch→signup, 5 qualitative replies
□ One outsider watched a rough cut before you publish
Ship the demo, then get it in front of makers
A converting demo is a distribution asset, not a vanity reel. Once it matches the product and the button on your page, put it where builders actually look—your landing page first, then launch threads, then directories that send cold traffic.
When you’re ready to put that page in front of early users, explore what’s launching on MakerHunt—and keep the video honest enough that the first ten minutes after signup feel like the same product they just watched.