A tour they click instead of watch
Video is passive, and on a pricing page passive is expensive. An interactive demo lets a buyer drive — skipping what they understand, dwelling on what they do not, and reaching the part that matters to them without waiting through ninety seconds of setup.
Click New shipment to open the booking panel.
- 6.1×
- Engagement vs. a video embed
- +38%
- Median demo-request lift
- 0
- Lines of code to embed
- Indexable
- Real DOM, crawlable by search
The same recording
Because the recorder captured the DOM, the interactive demo is generated from the take you already made. No second build, no sandbox to maintain.
Branching by persona
Let the viewer pick their role at step one and route them down a path that shows the three things their role cares about.
Intent you can act on
You learn not just that someone watched, but which path they took, where they stopped, and what they clicked twice.
Generated from the recording, not rebuilt by hand
Competing tools ask you to clone your app into a sandbox, then maintain that clone forever. DemoRiff captures the real DOM during your normal recording and reconstructs it as an interactive surface — real text, real layout, editable. Change a label, redact a customer name, swap a number, all without touching your application.
- Captured from a normal recording session, not a separate build
- Editable text and values — fix a typo without re-recording
- Responsive reconstruction that works on mobile viewports
- Automatic redaction of detected customer data
Click New shipment to open the booking panel.
Hotspots, tooltips, forms and forks
Each step gets a spotlight, a tooltip you write, and a required action. Insert a form to capture a lead mid-tour, a fork that asks what the viewer wants to see, or a checkpoint that unlocks the next section. Steps can be reordered by dragging, and the written guide regenerates to match.
- Spotlight, tooltip, cursor hint and required-click per step
- Branching forks with per-path analytics
- Inline lead capture with CRM field mapping
- Chapters, skip-ahead and a persistent progress rail
Embed it anywhere, including inside your product
One script tag, or an iframe, or a share link. Demos render server-side so search engines index the text, which is a meaningful SEO advantage over a video. Inside your own product, the same demo can run as an onboarding overlay triggered on first login.
- Script tag, iframe, share link, or in-product overlay
- Server-rendered text that search engines can index
- Custom domain support for share pages
- Gated variants that require an email before step three
The technical detail
- Capture
- DOM snapshot per step, with computed styles and assets inlined
- Steps
- Up to 120 per demo, with unlimited branches
- Embed
- Script tag, iframe, or direct link; 6 KB runtime, async
- Responsive
- Reconstructed layouts down to 360px wide
- Analytics
- Per-step, per-branch, per-hotspot, plus CRM sync
We used to budget two weeks and eleven thousand dollars for a launch video. Our last three launches were recorded on a Tuesday and live on Wednesday. The agency invoice line item is gone.
About interactive demos
A sandbox is a running copy of your application that someone has to keep alive, seeded and in sync with production. An interactive demo is a reconstruction of a recording — it cannot drift, cannot break when a deploy goes out, and costs nothing to run. The trade-off is that it follows a path rather than allowing arbitrary exploration, which for a marketing-site demo is usually what you want.
Yes, on inputs you mark as interactive. The demo accepts the input and advances, which makes flows like search or configuration feel real without connecting to anything.
Yes. The captured DOM is reconstructed responsively, and steps can carry a mobile-specific spotlight position. Roughly a third of demo views in our data are on a phone, usually forwarded from a colleague.
Pairs well with
In production at