Skip to main content
Intempt
Coming soon

Onboarding checklist length test

Compares a 3, 5 and 7 step onboarding checklist for new signups, scored on activation within 7 days.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

Coming soon

1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Set up the checklist length test

    Coming soon

    Blu builds a step

About this recipe

When to use it

A longer checklist covers more of the product, but a shorter one might get finished more often. This tests both directly against 7-day activation, the metric that actually matters.

What it delivers

Runs a client-side experiment testing whether shorter or longer in-app onboarding checklists improve 7-day activation.

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 3, 5 and 7 step onboarding checklist for new signups, 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.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. 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.

    1. 01Set up the checklist length testCreate a CLIENT EXPERIMENT on /experiences titled "Onboarding Checklist Length". ═══ PATH 1: Top-level configuration ═══ Experience type: client_experiment Variants: - Control (34%): 3 steps: Connect data, Invite team, Create first report - Variant B (33%): 5 steps: adds Set goals, Customize dashboard - Variant C (33%): 7 steps: adds Watch tutorial, Configure notifications Targeting: - Pages: in-app dashboard URL where the onboarding checklist component renders - Audience: new signups only: segment definition: User created within 24 hours - Devices: any - Display frequency: always (during user's first session) or once (sticky to first visit) Primary metric: goal_completed_in_experience where experience_id = <this> (the goal fires when the user completes their nominated activation milestone within 7 days of exposure) Secondary metrics: - Click on per checklist step (per-step completion rate) - Completed a journey goal within 7 days (existing activation journey completion) - Session start day-2 / day-7 (engagement after onboarding) Guardrail: 14-day Session start retention must not drop >3 percentage points Schedule: 30 days ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (3 steps) HTML target selector: .onboarding-checklist Replacement HTML: <div class="onboarding-checklist" data-variant="control" data-step-count="3"> <h2>Get started in 3 steps</h2> <ol class="checklist-steps"> <li class="checklist-step" id="step-1"><a href="/setup/data">Connect your data</a></li> <li class="checklist-step" id="step-2"><a href="/team/invite">Invite your team</a></li> <li class="checklist-step" id="step-3"><a href="/reports/new">Create your first report</a></li> </ol> <div class="checklist-progress" data-completed="0" data-total="3"></div> </div> Variant: B (5 steps) Same wrapper, add 2 additional <li> entries: <li class="checklist-step" id="step-4"><a href="/goals/setup">Set your goals</a></li> <li class="checklist-step" id="step-5"><a href="/dashboard/customize">Customize your dashboard</a></li> Variant: C (7 steps) Same wrapper, add 2 more: <li class="checklist-step" id="step-6"><a href="/tutorial">Watch the tutorial</a></li> <li class="checklist-step" id="step-7"><a href="/settings/notifications">Configure notifications</a></li> User refines the step copy, icons, and ordering in the Visual Editor. Ensure each step has a stable target_id (step-1, step-2, etc.) so per-step Click on metrics roll up consistently. Taxonomy notes: - The "activation milestone" is project-defined: typically Completed a journey goal for the activation journey. This recipe assumes the activation journey is configured separately. - Session start is the canonical engagement signal.

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /onboarding-checklist-length in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost 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 Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Intempt Technologies

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post 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 Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe