Product tours that get new users to their first win

A product tour is a short, guided walkthrough inside your app that points at real screens and shows a new user how to reach their first win. It works best for products with a clear first task and a layout new users find confusing. Keep it short, start it when the user chooses to, and aim it at one outcome, such as the aha moment, rather than a feature parade.

How to do it

1. Map what activated users actually do. Look at your analytics for the path between signup and the first moment of value. Pick one task, such as sending the first campaign or inviting a teammate.
2. Write the tour for that one task. Five steps or fewer. Each step is one sentence plus one action the user can take on the real screen.
3. Let users start it. Put a "Show me around" button or a help launcher where they will see it, and offer the tour on first login as a choice they can dismiss.
4. Build it with a tool. Hosted no-code builders include Chameleon (tours and modals), Appcues (in-app onboarding) and Userpilot (in-app onboarding flows without code). If you have a developer, open-source libraries do the job: driver.js is MIT-licensed. Intro.js is AGPL, and commercial use needs a paid license.
5. Measure the right thing. Completion rate of the tour matters less than whether people who saw it reach the first-value event more often than people who did not. Hold back a small group if you can.
6. Fix, then repeat. Watch where people quit, cut steps there, and rewrite the copy.

What the benchmarks say

Chameleon publishes data from its own customers' tours. Read these as one vendor's numbers, not a universal rule. In its 2025 benchmark report:

• tours beyond five steps "lose attention from more than half of users"
• launcher-driven tours had a 67% completion rate, the highest tour completion rate in the data
• self-triggered tours get roughly double the engagement of automated, blanket-triggered ones

The report's dataset is 550+ million interactions across all its formats, and it does not give a tour-only sample size for these figures.

What it looks like in practice

Say you sell invoicing software. Your activated customers all send a first invoice within a day. The tour has four steps: click "New invoice", pick a client, add a line item, press "Send". It opens only when the user clicks "Show me around" on the empty dashboard. A tooltip appears over each real button. The last step is the send button itself, so finishing the tour means the user has sent an invoice.

When it backfires

• Forced tours get skipped. A tour that blocks the screen on first login is the easiest thing to close. Chameleon's data above points the same way.
• Tours rot. Every UI change can break a step that points at a moved button. Someone has to own the tour after each release.
• Tours cannot fix a confusing product. If users stall on the same screen, redesign it before you annotate it.
• Licensing. Intro.js is AGPL-licensed, and its site says a commercial app or website needs a commercial license, sold as a one-time lifetime payment.

If tours are not enough, an onboarding checklist gives users a visible path across several sessions.

Questions people ask

What is a product tour? A guided sequence of tooltips or modals inside the product that walks a user through key actions.

How many steps should a product tour have? Five or fewer, going by Chameleon's data. Fewer is fine if the task is short.

Are there free product tour tools? Yes for developers: driver.js is MIT-licensed and free. Hosted tools charge, so check each vendor's current pricing.

Sources

• Chameleon benchmark report 2025, read Oct 8, 2026
• driver.js, read Oct 8, 2026
• Chameleon, read Oct 8, 2026
• Appcues, read Oct 8, 2026
• Userpilot, read Oct 8, 2026
• Intro.js licensing, read Oct 8, 2026