By Mehdi HassanWhat is a SaaS product tour page?
A SaaS product tour page is a dedicated page that shows how the product works before a visitor signs up or talks to sales. It answers "what will I actually see and do?" with real product UI, in the order a new user would experience it. It sits between feature pages, which explain capabilities, and the trial or demo request, which asks for commitment.
The format you pick for that page is a real decision with build and maintenance costs attached. It shapes page speed, how often marketing has to chase product for updates and how much a buyer can learn without a call. We cover where the tour fits in the overall site structure in our SaaS website design guide.
Interactive demo vs video vs screenshots: how do they compare?
Screenshots win on speed and upkeep, video wins on storytelling and interactive demos win on self-serve depth. None of them is best in general, so compare them on the attributes that matter for your product and team.
Attribute | Annotated screenshots | Narrated video | Interactive demo |
|---|---|---|---|
Best for | Simple products, clear UI | Workflow products, a before/after story | Complex or configurable products |
Effort to make | Low | Medium (script, record, edit) | Medium to high (capture, annotate, branch) |
Effort to keep current | Low: swap images | High: re-record on UI changes | Medium: recapture changed steps |
Page speed impact | Small if images are optimized | Medium; lazy-load the player | Medium to high; embed loads scripts |
Works without sound or attention | Yes | Needs captions | Yes, but needs clicks |
What the buyer learns | What it looks like | Why it matters, in order | How it feels to use |
Typical tooling | Figma or product captures | Screen recorder plus a video host | A dedicated interactive demo platform |
Interactive demo platforms (Arcade, Navattic, Storylane and Walnut are common names) capture your product's screens or HTML and let you add hotspots and steps. Check each tool's current plan page for analytics, branching and lead capture, because those features vary and change.
When should a product tour page use screenshots?
Use annotated screenshots when the product is understandable from its interface and the main value is visible on one or two screens. Most early-stage SaaS products fall here, even when the founders think the product is complicated. Screenshots also suit products whose UI changes often, because replacing an image takes minutes.
- Crop tightly. Show the part of the screen that proves the point, not the whole app at 30% scale.
- Annotate with outcomes. A callout that says "Approvals route to the right manager automatically" beats one that says "Approval settings".
- Use real-looking data. Placeholder text like "Lorem" or "Test User 1" reads as unfinished.
- Export at the right size and serve modern formats, so the page stays fast on mobile.
When is a video the right format for a product tour?
Video is the right format when your product's value is a sequence: data comes in, something happens, a result comes out. A two-minute narrated walkthrough explains that cause and effect better than any static image. It also helps buyers who forward the page to a colleague who wasn't on the call.
The costs are real. Video goes stale every time the UI changes, needs captions for people watching on mute, and adds weight to the page if it autoplays. Keep it short, start with the outcome rather than the login screen, and load the player only when someone presses play. A related CTA test is worth knowing: in an Optimizely test reported by Convertica, a "Watch a Demo" button converted at 1.59% against 0.91% for "Get Started". Treat that as one test, not a rule, but it shows how much a concrete label can matter.
Should the product video be animated instead of recorded?
A recorded screen video is honest and quick to update. An animated product demo, built as a coded or Lottie animation of simplified UI, looks more polished and loads lighter, but every UI change means re-animating. We compare those options in detail in our guide to animated product demos on websites.
Our rule of thumb: use recorded video on the tour page, where accuracy matters most, and reserve coded animation for the homepage hero, where clarity and speed matter most.
When does an interactive product demo make sense on a website?
An interactive product demo makes sense when buyers need to try the product's logic before they'll trust it, and when a trial is expensive to set up. Data tools, configurable workflow products and anything that needs an integration before it shows value are the usual candidates. The demo lets the buyer click through a realistic path without connecting their own data.
Pros
- Buyers learn at their own pace, without booking a call.
- It works as a sales asset too: reps can send a link before or after a call.
- Most platforms report which steps people complete, which shows where interest drops.
Cons
- Someone has to recapture steps after every meaningful release.
- Embeds add scripts and can slow the page, especially on mobile.
- Long demos lose people. More than about a dozen steps usually needs branching or chapters.
Keep the interactive demo off the homepage hero in most cases. It works best on a dedicated tour page, linked from the hero as a secondary action. We look at the homepage question specifically in our guide on interactive demos and product tours on the homepage.
How do you choose by product complexity?
Choose by how many steps it takes a new user to see value. If it's one screen, use screenshots. If it's a short sequence, use video. If it depends on choices the user makes, use an interactive demo.
- One-screen value (a dashboard, an inbox, a calendar): annotated screenshots, plus an optional 30-second loop.
- Linear workflow (import, process, output): a narrated video of under three minutes, with screenshots below for skimmers.
- Branching or configurable product (rules engines, data pipelines, admin-heavy tools): an interactive demo with two or three paths by role or use case.
- Developer product: real code, a sandbox or a quickstart often beats all three. Show the first API call working.
Your buying motion matters too. A product-led company needs the tour to push people into sign-up, so keep it short and end every path at the trial. A sales-led company can use the tour as qualification and end it at the demo request. Our SaaS website examples by buying motion show both patterns on live sites, and our book-a-demo page examples show what should happen after the click.
Which format should you pick?
Pick the simplest format that answers the buyer's real question, then add depth only where the product demands it. Most teams overbuild the tour and underbuild the copy around it.
Whichever you choose, the words around the visuals do most of the work. A clear headline and one sentence per step will rescue an average screenshot, while a polished demo with vague copy still leaves the buyer guessing. If your whole site needs that treatment, our guide to a SaaS website redesign covers the bigger picture.
