At a glance
Which kind of product tour software do you need?
An external demo for people without an account, an in-app tour for signed-in users. If the viewer hasn't signed up yet, they need a tour they can open from a link. If they're already in your product, the guidance has to run inside it. Some teams need both, owned by different people.
| Format | Where it runs | Who sees it | Who sets it up |
|---|---|---|---|
| External interactive demo | A link or an embed on your site, emails, or docs | Anyone, before they sign in | Marketing or customer success, with no install in your product |
| In-app product tour | Inside your signed-in product | Signed-in users, based on their account | Product or engineering, who install it in the app |
| Recorded video walkthrough | A video player | Anyone who presses play | Whoever records and edits it |
Research and trust
Arclet makes interactive demos you share outside your product. It doesn't include an in-app tour builder, and we don't sell one. That boundary decides your shortlist. For external demos, compare interactive demo tools. For the vendors behind them, see every Arclet comparison.
Why teams pick Arclet for external product tours
Arclet gives prospects a product tour before they have an account. Record a workflow with the Chrome extension, rewrite the steps, and share it. Anyone with the link can click through, with no signup and no script in your product.
Free gives one creator five published demos. Starter is $25 a month billed annually for unlimited demos. See Arclet pricing.
Show the product before signup
Put the tour on your homepage or in an outbound email. Prospects see the workflow without creating an account, and nobody installs anything in your product.
See how to share an Arclet demo outside your product.
Pick who can open a demo, then copy the embed code for a page on your site or a help article. The panel copies the link rather than showing it, so the recording ends before a visible URL. Nothing in it runs inside another product.
Embed a tour in your docs
Paste the embed into a help article. Readers click through the steps right next to the written instructions.
Know what Arclet doesn't do
Arclet doesn't read a signed-in user's account or change your product's interface. For checklists and tooltips inside your app, you need an in-app tour tool.
When another kind of tour fits
An external demo is the wrong tool when the job looks like one of these.
New users need help inside the product
Onboarding checklists, feature announcements, and tooltips that react to each user belong in an in-app tour tool installed in your product.
Everyone needs the same short overview
A short video works for a release note or a company update. Nobody needs to click, so a demo adds nothing.
The steps change with each customer's setup
A written guide handles branches and settings better than one recorded path.
Choose by who is viewing
Name the viewer first. That tells you which kind of tour you're buying. For SaaS teams covering several stages, see SaaS demo software.
Prospects on your website
They don't have an account. Give them an external demo they can open from your homepage or pricing page.
New users in their first session
They're signed in. An in-app checklist that reacts to their progress is the right tool, and Arclet isn't it.
Customers reading your docs
They're looking for steps. Embed an external demo in the help article so they can click through the workflow.