Guided vs self-serve onboarding
Compares a self-serve checklist, a guided wizard and a video-first walkthrough, scored on activation within 7 days.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Set up the onboarding test
Coming soonBlu builds a step
About this recipe
When to use it
A guided wizard, a self-serve checklist, and a video-first walkthrough all have advocates, and the right one depends on your product's complexity. This tests all three for time-to-value on your own users.
What it delivers
Runs a client-side experiment testing whether a guided wizard, a self-serve checklist, or video-first onboarding produces faster time-to-value.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Compares a self-serve checklist, a guided wizard and a video-first walkthrough, scored on activation within 7 days.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Set up the onboarding testCreate a CLIENT EXPERIMENT on /experiences titled "Onboarding Flow: Guided vs Self-Serve". ═══ PATH 1: Top-level configuration ═══ Experience type: client_experiment Variants: - Control (34%): self-serve checklist (current: list of clickable steps) - Variant B (33%): guided wizard with progressive steps and contextual tooltips - Variant C (33%): video-first onboarding with embedded walkthrough Targeting: - Pages: in-app onboarding page (typically /onboarding or post-signup landing) - Audience: new signups only: segment: User created within 1 hour - Devices: any - Display frequency: once (sticky to user's first session) Primary metric: goal_completed_in_experience where experience_id = <this> (goal fires on the activation event, e.g. Completed a journey goal for the activation journey, within 7 days of exposure) Secondary metrics: - Median time from exposed_to_experience to first key Click on (the canonical "time to value" measurement) - Session start day-2 (returned-after-signup rate: engagement persistence) - Onboarding completion rate (Click on on the final step's target_id) Guardrail: bounce-from-onboarding rate (Session end without any Click on after onboarding render) must not increase >10% Schedule: 30 days minimum ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (self-serve checklist: no DOM changes) Existing onboarding checklist remains in place. Variant: B (guided wizard) HTML target selector: .onboarding-container (replace contents) Replacement HTML: <div class="onboarding-wizard" data-variant="b"> <div class="wizard-progress"> <div class="wizard-step active" data-step="1">1. Welcome</div> <div class="wizard-step" data-step="2">2. Connect data</div> <div class="wizard-step" data-step="3">3. Invite team</div> <div class="wizard-step" data-step="4">4. Create report</div> </div> <main class="wizard-content"> <h2 class="wizard-step-title">Welcome to [Product]</h2> <p class="wizard-step-body">Let's get you set up in 4 quick steps.</p> <div class="wizard-tooltip" role="tooltip">Hover here for tips to </div> <div class="wizard-actions"> <button class="wizard-prev" disabled>Back</button> <button class="wizard-next" id="wizard-next-1">Continue</button> </div> </main> </div> Variant: C (video-first) HTML target selector: .onboarding-container (replace contents) Replacement HTML: <div class="onboarding-video" data-variant="c"> <div class="video-hero"> <video controls autoplay muted poster="/onboarding-poster.jpg"> <source src="/onboarding-walkthrough.mp4" type="video/mp4" /> </video> </div> <div class="video-secondary-actions"> <h3>Or jump straight in</h3> <button class="quickstart-cta" id="quickstart-cta">Skip and start exploring</button> </div> </div> The user supplies their actual onboarding copy, video file, and styling in the Visual Editor. Taxonomy notes: - "Time to first key Click on" is computed by Lovable from exposed_to_experience timestamp to the first downstream Click on event for the same user. Median across users = the variant's TTV. - The "key Click on" identifier (which Click on target_id counts as activation) is project-defined; typically it's the first interaction with a core product feature.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /onboarding-flow-guided-vs-self-serve in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 