How to Create an Interactive Demo with Supademo

November 15, 2026

Supademo records your clicks in a Chrome extension and rebuilds them as a clickable walkthrough — hotspots, tooltips and optional branching — so viewers explore a demo on their own instead of watching a video. A 12-step interactive demo takes about 30 minutes from record to publish.

What is the difference between a demo and a video?

The viewer controls it. In a video, the pacing belongs to you. In a Supademo, the viewer clicks the highlighted area to advance.

That changes two things: engagement, because viewers who click are paying attention, and analytics, because you can see which step they abandon. Step-level drop-off is the most useful data in the product — if 60% of viewers quit at step 5, step 5 is your problem.

How do you record the raw flow?

Install the Chrome extension, hit Capture, and perform the task once at normal speed.

Rules that prevent re-recording:

  1. Use a demo account with clean data. Real customer names in a demo are a data problem.
  2. Resize the browser first. Record at the aspect ratio you will publish — 16:9 for website embeds, taller if it sits inside a phone mockup.
  3. Wait a beat after each click. The recorder needs the next screen rendered or the screenshot catches a loading spinner.
  4. One flow per demo. Twelve steps is the sweet spot. Past twenty, viewers drop.

How do you turn the raw recording into something usable?

Select each step and confirm the hotspot — the highlighted area the viewer must click. The auto-detected hotspot is often the wrong element, especially on pages with a persistent sidebar or a cookie banner overlapping the target.

Then rewrite the tooltip. The generated text names the UI element: “Click Settings.” A viewer exploring a demo wants to know what they are about to get, so “Open Settings to connect your calendar” does more work in the same space.

Editing pass priorities, in order:

  • Fix hotspots that point at the wrong element. This is the difference between a demo that works and one that strands people.
  • Shorten tooltips to under 15 words.
  • Remove steps that are pure navigation filler.
  • Add a final step that lands on the result, not on another menu.

How does branching work?

Branching lets one step offer two paths — “new user” and “returning user” — with different subsequent steps. Configure it in the step settings.

Use it sparingly. Two branches is understandable. Four branches turns a self-serve demo into a decision tree viewers abandon. Supademo supports branching but has no visual flow editor for complex trees, so tracing a five-branch demo means clicking through it in preview mode.

How do you publish and measure it?

Publishing options: hosted link, website embed (iframe or script snippet) and export to video. The hosted link is the default and includes analytics.

Funding on the free tier is limited to a small number of demos with Supademo branding, while paid plans run from roughly $20/month per seat and unlock custom branding, lead capture forms and no watermarks.

Analytics worth watching: completion rate, median time per step, and drop-off. A step where the median time spikes means the hotspot is confusing, not that viewers are reading carefully.

Lead capture can be placed at the start or as a gate in the middle. Mid-demo gates convert better than entry gates in practice, because the viewer has already invested attention — but they also cut completion, so measure after a week before deciding.

Where it falls short

Browser only. Chrome extension capture cannot record a desktop app or a native mobile app, so the demo is of your web product or nothing.

No real logic. The demo replays screenshots, so it cannot respond to what a viewer types, and anything that depends on live data looks frozen. If your product’s appeal is generated content, a screenshot demo undersells it.

And the styling is fixed. You can change the frame and accent color, not the layout of the viewer.

Who should use it

Sales teams that need a self-serve demo without booking a call. Marketing teams putting a product tour on a landing page. Onboarding teams teaching an internal tool where a clickable walkthrough beats a help article.

Not for desktop software, not for demos that depend on live data, and not for anyone who needs a scripted presentation with narration — that is still a video.

Quick Summary

  • Supademo records clicks in Chrome and rebuilds them as a clickable walkthrough.
  • A 12-step demo takes about 30 minutes including editing.
  • Auto-detected hotspots are often wrong; every demo needs a hotspot audit.
  • Analytics show step-level drop-off, which is the main reason to use it over video.
  • Paid plans start near $20/month; the free tier carries Supademo branding.
  • Best fit: web product tours and sales demos. Poor fit: desktop apps and live-data demos.