How to Demo Your SaaS in 60 Seconds

The one-job rule

Most 60-second demos fail because they try to show everything. A feature tour at that length becomes a blur of screens, none on screen long enough to understand. The fix is simple and uncomfortable: choose one job your product does, and show it from start to finish. Everything else goes into a five-second summary near the end, or into a longer video.

Viewers do not need to see every feature to decide whether to try your product. They need to see one thing work clearly enough to imagine using it themselves.

How to choose the job

Pick the job that best answers "why would I sign up?". Good candidates share three traits:

• It is the first meaningful thing a new user does. Not account settings, the thing they came for.
• It has a visible result. A report appears, a message is sent, a draft is written, a chart updates.
• It can be shown in under 40 seconds of edited footage.

If you are torn between two jobs, ask a few customers what they use most, or look at which action correlates with users sticking around. Use the other job for your next video.

The second-by-second plan

Notice that the job takes up more than half the running time. That is the point. If your hook or name beats grow, take the time from the breadth beat, never from the job.

An example 60-second script

Here is the plan applied to a fictional invoicing product. Replace the details with yours; the launch video script template has more blank scripts.

1. [0–4s] "Chasing late invoices shouldn't be a second job."
2. [4–8s] "[Product] gets you paid on time, without the awkward emails."
3. [8–16s] "Create an invoice from a template, or import one from your accounting tool."
4. [16–32s] "Set a payment schedule once. [Product] sends friendly reminders before and after the due date, in your tone of voice, and stops as soon as the client pays."
5. [32–45s] "When payment comes in, it's matched to the invoice automatically, and your dashboard shows exactly who still owes what."
6. [45–55s] "Recurring invoices, multiple currencies, card and bank payments, and a client portal are all included."
7. [55–60s] "Get paid on time. Start free at [product].com."

That is about 115 words, which leaves room for pauses at a relaxed pace.

Making a minute feel complete

A minute is short, so editing does a lot of the work:

• Cut the waiting. Loading spinners, page transitions and typing can all be shortened or sped up. Label anything sped up.
• Zoom, don't pan around. Show the panel that matters at a readable size rather than the full screen.
• Use highlights to point at the one element that changes in each scene.
• Animate typing rather than recording yourself typing, so form-filling takes two seconds instead of ten.
• Let the result breathe. Hold the outcome on screen for a beat longer than feels necessary. It is the moment the viewer decides.
• Keep a headline on every scene, so the demo works muted.

Adapting the plan to different products

The structure holds for most software, but the "job" looks different by product type:

• AI tools: the job is input to output. Show the prompt or file going in and the real result coming out, and show the user editing it. The AI tool template follows this pattern.
• Developer tools: the job is install to working code. Put the command and a few lines of code on screen early, then show it running.
• Collaboration tools: the job involves two people. Show one person starting something and another receiving it, so the viewer sees the hand-off.
• Analytics products: the job is question to answer. Start with the question, then zoom into the chart that answers it.
• Mobile apps: the job is usually a single tap-through flow. Record on the device and consider a vertical version first.

Whatever the product, resist the urge to add a second job "because it only takes ten seconds". Ten seconds is a sixth of the video, and it is almost always better spent letting the first job land.

Recording footage for a short demo

Short demos are unforgiving: there is no time to explain a confusing screen. Record in a demo account with realistic, fictional data, at a consistent window size, with notifications off. Record the start, the work and the result as separate clips, move the mouse slowly, and pause before every click. Our guide to turning a screen recording into a launch film covers this in detail.

Where a 60-second demo works

• Your homepage, as a click-to-play video or a silent loop.
• Product Hunt and launch-day posts. See the Product Hunt launch video guide.
• Sales follow-ups, so prospects can share the product with colleagues.
• Investor updates, as a quick look at the current product; the investor demo video use case covers this.
• Onboarding emails, to show new users the first job to do.

For social feeds, cut it down to 20–30 seconds by keeping the hook, the result and the call to action.

Common 60-second demo mistakes

• Opening on the dashboard. A full dashboard with no context is overwhelming. Start from the beginning of the job.
• Logging in on camera. Nobody needs to see the login screen.
• Too many features. If you show more than one job, you are probably showing none of them well.
• Fake data that looks fake. "Lorem ipsum" and "Test Client 1" break the illusion.
• No ending. Always finish on one clear next step.

Building it faster

If you would rather not assemble the zooms, highlights and captions by hand, Cadenzova Spotlight can draft the demo for you. Paste your URL, upload the clips of your one job, and the AI director plans a first cut you can refine, for example by asking it to "tighten the pacing" or "spend longer on the result". The product demo video maker page explains the editor, and plans are on the pricing page.