Find onboarding checklist drop-off

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

Updated · published

markdown for agents →

difficulty beginner · time to value 3 minutes · execution on demand

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

Agentry gives coding agents production context from errors, product analytics, and deploys through one HTTP API. Fetch and read https://agentry.sh/install.md completely, then install Agentry's full first-time telemetry baseline in this repository. I authorize device-code login, saving the owner key only to ~/.agentry/credentials.json, creating one Agentry project for this repository, and read-only inspection of shipped source plus hidden CI/provider configuration. Deeply analyze the product's business logic and complete value flow before choosing telemetry. Save the complete source-backed plan and show me its exact contents and hash. Until I explicitly approve that plan or request a replacement, do not edit app/CI source, place runtime/CI credentials, commit, exercise product traffic, start proof, push, or deploy. After approval, I authorize only the reviewed targets: place the required scoped browser/server/CI credentials through the established environment or secret mechanism, preserve existing telemetry, implement and test the baseline, commit it, push that reviewed commit when the shipped CI/provider path requires it, exercise safe proof paths with test/non-customer data, and perform one deployment through the reviewed shipped CI/provider path. Ask first if proof would charge money, contact a third party, change real customer data, or require new external access. After the plan is saved, immediately before every onboarding state-changing POST, GET current onboarding state, perform only its single returned next_action, then read state again; do not batch or infer later stages. Continue until status is verified, installation_complete is true, and next_action is null. Keep all secrets, source snapshots, proof markers, and scratch files outside the repository.

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