Putting an Interactive Demo in Your Onboarding Emails
New users skip the docs and half-read the welcome email. A short demo in the right onboarding email gets them to 'I see how this works' without opening the app. Which emails get one, how to include it, and how to measure the lift.
New users skip the documentation and half-read the welcome email, so the value has to land fast — and a short demo in the right onboarding email does that without them opening the app. You can't make the demo clickable inside an email (clients strip the code), so you embed a still or GIF that links to the hosted interactive version. The first one or two onboarding emails are where it belongs: the welcome email, where the user is deciding whether signing up was worth it, and a day-two follow-up for people who haven't come back. It doesn't replace the app — it primes the user so their first real session goes better.
Why the onboarding email is the right place
A new user's attention is highest right after signup and drops fast. The welcome email lands in that window. But most welcome emails spend it on a bulleted list of features and a "get started" button that leads to an empty app.
A two-minute walkthrough of the actual outcome — the thing the product produces, clicked through step by step — uses that attention better. The user sees where they're headed before they have to build anything.
Which emails get a demo
- Welcome email (send immediately). The demo here shows the core outcome: what a finished result looks like, walked through. One clear "now do this" CTA under it.
- Day 1–2 re-engagement (send to users who haven't returned). Same or a different short walkthrough, framed as "here's the two-minute version if you didn't get a chance to look." This catches the people who drifted.
- Feature-nudge emails (later, situational). When you want to drive adoption of a specific feature, a walkthrough of just that feature.
Don't put a demo in every email — it stops being a signal.
How to include it
Email clients won't run the interactive demo, so:
- Host the interactive demo on the web (a shareable link or an embed page).
- In the email, show a preview — a clean screenshot of the first step, or a short GIF of a few steps, with a clear play affordance.
- Link the preview to the hosted demo, which opens in the browser fully interactive.
- Keep the CTA under it pointed at the app ("Open your workspace"), so the demo primes and the button converts.
For the mechanics of hosting and sharing, see how to embed a demo on a website; for making the GIF preview, how to make a GIF of your screen.
Build one walkthrough and reuse it across the welcome email, the re-engagement email, the empty state in the app, and the docs. The marginal cost of another placement is zero once the demo exists.
Measuring the lift
- Email click-through on the demo preview — easy to move, not the point on its own.
- Activation rate for the cohort that got the demo email vs one that didn't (or vs the prior period). This is the number that matters — see user activation.
- First-week retention for the same cohorts — does the primer make the first session stick?
If click-through is high but activation doesn't move, the demo isn't showing the right thing, or the hand-off from demo to app is broken.
Related: demo-first marketing, the SaaS onboarding email sequence, self-serve onboarding.
Frequently asked questions
Can you embed an interactive demo in an email?
Not the interactive version — email clients strip the scripts and iframes that make a demo clickable. What you embed is a still image or short GIF of the demo that links out to the full interactive version hosted on the web. The email shows a preview; the click opens the real thing in the browser.
Which onboarding email should contain a demo?
The first one or two. The welcome email is where a new user is deciding whether this was worth signing up for, so a two-minute walkthrough of the core outcome belongs there. A follow-up email a day or two later, aimed at users who have not returned, is the second place — it re-shows the value to people who drifted.
Should the demo email replace the app?
No — it lowers the barrier to it. A new user who has watched a walkthrough arrives in the app knowing what they are aiming for, which makes the first session go better. The demo is a primer, not a substitute.
How do you measure whether a demo in an onboarding email works?
Compare the cohort that received the demo email against one that did not (or against the period before you added it) on the metrics that matter: click-through on the email, then activation rate and first-week retention. The email click is easy to move; the point is whether it moves activation downstream.