Find onboarding checklist drop-off

Analyze checklist and setup-step completion so product and CS can see exactly where new users or accounts stall.

Published

difficulty beginner · time to value 3 minutes

Start from this

Analyze onboarding checklist drop-off for new accounts: step started, step completed, time between steps, and accounts stuck for more than 7 days.

Why this matters

Signup funnels stop at account creation. Onboarding checklists reveal the harder question: did the customer reach useful value?

What you get

  • Completion by checklist step
  • Median time between steps
  • Accounts stuck at each step
  • A protected metric report for product or CS

Walk through it

You

Where do accounts stall in onboarding?

Agent

I’ll compute completion and stuck accounts by step.

Endpoint: POST /v1/projects/:project_id/analytics/query
Exact shape: /v1/openapi.json?path=%2Fv1%2Fprojects%2F%7Bproject_id%7D%2Fanalytics%2Fquery&method=post
Custom HogQL goes in the OpenAPI-defined `query` field.
Concept fields:
  query: "SELECT properties.step AS step, countIf(event = 'onboarding_step_started') AS started, countIf(event = 'onboarding_step_completed') AS completed, completed / nullIf(started, 0) AS completion_rate FROM events WHERE event IN ('onboarding_step_started','onboarding_step_completed') AND timestamp > now() - INTERVAL 30 DAY GROUP BY step ORDER BY started DESC"

The output

The agent returns a step table and identifies where intervention matters most. For B2B accounts, it should list stalled accounts for CS follow-up.

Setting it up

Emit started/completed events from each checklist item or setup milestone. Keep step stable and human-readable.

Variations

  • “Only show enterprise accounts created this month.”
  • “After this metric is backed by a real query blueprint, publish it as a weekly onboarding report.”
  • “Compare checklist drop-off before and after the new setup wizard.”

Adapt this playbook in your own agent.

Ask your agent to map the starter prompt to your saved signal map, live events, and the current HTTP API before answering.

Set up Agentry in this repo by following https://agentry.sh/install.md. I authorize you to: run its device-code login and save the key to ~/.agentry/credentials.json, read this repo, propose an instrumentation plan for my approval, and edit code after I approve it.

+ Full access
5.5 Extra High
  1. 1. Open your repo in Codex, Claude Code, Cursor etc.
  2. 2. Paste the install prompt.
  3. 3. Your agent reads the install doc and shows you an implementation plan for approval.