Tasks / Growth

Activation & onboarding review

Can the model find the friction that matters most and prioritise the fixes?

Task type v1.1 · 2 tasksLast changed 6 Oct 2026 · ChangelogDifficulty

What AI gets right here, and what you’ll still have to catch

From 18 graded outputs by 9 models. 67% were usable with at most a quick edit.

Reliably right

  1. Respects explicit constraints100% pass
    The output is a review addressed to Omar, well under 800 words, and respects the requested form.
    GPT-6 Luna · API · The checklist isn't the moment
  2. Produces the required deliverable100% pass
    The review covers activation definition, evidence, changes, design proposal, and goal, is addressed to Omar, within length, and is actionable.
    GPT-6 Luna · API · The checklist isn't the moment
  3. Activation defined by what predicts retention100% pass
    Activation is defined by the behaviour that predicts retention (bank+cat 10+), and fixes are judged by their effect on that event.
    GPT-6 Luna · API · The checklist isn't the moment

Where it slips

  1. Avoids unsupported claims26% pass
    States 'App-open frequency is an outcome, not a cause' as an established fact, but only correlation is shown in the data; this causal direction is an unsupported interpretation.
    Haiku 5.5 · API · The checklist isn't the moment
  2. Identifies material uncertainty61% pass
    Does not name specific unknowns that could change the decision, only suggests tracking metrics before expanding.
    GPT-6 Luna · API · Analytics tool losing users at setup
  3. Uses the supplied evidence correctly64% pass
    The output states 'we have no step-level data for screens 2–8', 'a blank builder is hard for non-analysts', and 'people invite colleagues to something useful, not to a setup screen' as facts, none of which appear in the brief or follow from arithmetic.
    Opus 5.5 · Claude · Analytics tool losing users at setup

How it’s graded

Each check is built on how world-class product and growth leaders do this work, as they’ve described it on Lenny’s Podcast, and names the leader it comes from.

  1. Activation defined by what predicts retention

    Does the review define (or question) the activation event by whether it predicts retention, and judge fixes by their effect on that event rather than on step completion?

    Passes when Names the activation behaviour and its link to retention (from the supplied data, or as an explicit assumption to verify), and ranks fixes by their effect on it.

  2. Gets people to value sooner

    Do the recommended fixes shorten the path to the first moment of value, by removing or deferring steps before it or starting people with templates or sample data, rather than adding tours, tooltips or extra steps?

    Passes when The main fixes cut or defer steps before first value, or give a warm start, and say which steps go.

Plus our standard checks

Uses the supplied evidence correctly · Addresses the actual decision · Respects explicit constraints · Identifies material uncertainty · Avoids unsupported claims · Produces the required deliverable · Gets the base of every number right · and 1 written for each task, which you’ll see in the tasks below.

The tasks

Read the brief, then compare up to three outputs, each with the LLM judge’s verdict on every check. Highlights mark what a PM had to fix.

The brief

Review our onboarding flow and funnel below. Write a memo to the onboarding squad saying where we are losing people and what to fix, in the order you would fix it, with the reason for each. Keep it under 500 words.

What the model was given4 items: Scenario, Funnel (last 90 days, 12,400 signups), Onboarding flow, screen by screen, Support
ScenarioChartwise is a self-serve product-analytics tool. Most people who sign up are product managers or marketers, not data engineers. Pricing starts at $49 a month after a 14-day free trial.
Funnel (last 90 days, 12,400 signups)Signup 100% → Connect data source 41% → First chart 33% → Invite teammate 9%. Week-2 retention: 62% for users who reach a first chart, 11% otherwise.
Onboarding flow, screen by screen1. Sign up: email, password, company name. 2. Verify email: the flow pauses until the link is clicked. 3. “What's your role?” (seven options). 4. “How big is your team?” (five options). 5. Connect your data: choose Postgres, BigQuery, Snowflake or CSV upload. There is no sample data and no skip. 6. Connection form: host, port, database, username, password and SSL mode. The help link opens a 14-page setup guide. 7. Choose tables: a list of every table in the database. 8. Syncing: a progress bar that can take up to 20 minutes; leaving the page cancels the sync. 9. Pick a dashboard template (twelve options). 10. First chart: a chart builder with an empty canvas. 11. Invite teammates: email fields, with a “Skip for now” link.
SupportThe most common onboarding ticket (41% of them) is some version of “I don't have the database credentials.” The next is “my sync failed” (18%).
What a strong answer doesThe answer key the graders mark against

The data-source connection step (screens 5–8) is the activation bottleneck; prioritise a sample-data or CSV-first path to a first chart, then non-admin credential handoff and a sync that survives leaving the page, ahead of cosmetic fixes.

Task

Mid-level · v1.13

The outputs

9 setups answered this brief.

Usable with a quick edit6 of 10 checks passed

The memo is well-structured, evidence-based, and actionable; a quick edit to rephrase the unsupported SSL-mode claim and add a condition-note would make it fully usable without redoing research.

Output

MEMO To: Onboarding Squad From: Product Leadership Subject: Fixing the Onboarding Funnel

Team,

Looking at the last 90 days, the story is clear: getting users to their first chart is everything. Week-2 retention jumps from 11% to 62% once a user builds a chart.

Right now, we are losing 59% of signups before they ever connect data, and another 8% before they build that first chart. Why? Because our signups are PMs and marketers, yet we are forcing them through a data-engineer onboarding flow.

Here is where we are losing people and what we need to fix, in priority order:

1. Add a “Send to an Engineer” flow & Sample Data (Screens 5–6) * The Problem: 59% of users drop off before connecting data, and 41% of support tickets are “I don’t have database credentials.” PMs and marketers don't have Postgres passwords or understand SSL modes, and a 14-page guide won't help them. Because there is no skip option, they hit a hard wall. * The Fix: Add two buttons to Screen 5: “Explore with Sample Data” and “Invite an Engineer to connect data.” Let the PM experience the "aha" moment immediately with a sandbox dataset while their engineer handles the credentials in parallel. This also instantly fixes our low 9% teammate-invite rate by giving users a real reason to invite a colleague early.

2. Make data syncing asynchronous (Screen 8) * The Problem: We lose 8% of our total signups (nearly 20% of those who actually manage to connect data) between connecting a source and building a chart. A 20-minute progress bar that cancels if you close the tab is a conversion killer, and it's driving 18% of our support tickets. * The Fix: Move syncing to the background. Let users close the tab (or play with sample data) and email them the moment their data is ready. Also, replace the raw list of every database table (Screen 7) with smart defaults so non-technical users aren't overwhelmed.

3. Eliminate the "Empty Canvas" (Screens 9–10) * The Problem: A user picks a dashboard template on Screen 9, only to be dropped into a blank chart builder on Screen 10. Blank canvases cause analysis paralysis. * The Fix: Make the templates on Screen 9 actually populate pre-built charts on Screen 10 using their data (or the sample data). Give them a working chart immediately that they can tweak, getting them across that 62% retention threshold automatically.

4. Remove pre-value friction (Screens 2–4) * The Problem: We pause the flow for email verification and ask two CRM-style profiling questions before the user has seen the product. Every step here costs us momentum. * The Fix: Let users into the product immediately and require email verification later (e.g., before they can share a chart). Cut the “team size” question entirely, and only keep “role” if we use it to auto-select their dashboard template in Step 9.

Let's scope Item #1 for this sprint.

Claims the judge couldn’t find in the brief

  • PMs and marketers don't have Postgres passwords or understand SSL modes, and a 14-page guide won't help them.

Grades and run details

Decision model 70 · LLM judge 64
Decision model checks
  • passUses the supplied evidence correctly69%
  • failAddresses the actual decision49%
  • passRespects explicit constraints61%
  • failIdentifies material uncertainty100%
  • failAvoids unsupported claims86%
  • passProduces the required deliverable95%
  • passPrioritises by impact97%
  • passActivation defined by what predicts retention100%
  • passGets the base of every number right45%
  • passGets people to value sooner97%
Run
Run
#1
API response time
8 s
Submitted
13 Oct 2026

Needs more than a quick edit5 of 10 checks passed

The output contains a factual error (treating 41% of support tickets as a user share) and unsupported claims, so a PM would need to re-check the evidence and correct the reasoning before using it.

Output

To: Onboarding Squad Subject: Fixing Our Activation Funnel: Priorities & Action Plan

Where We Are Losing People

Our biggest drop-off occurs at Step 5–8 (Connect Data): 59% of signups leave without connecting a data source.

We are asking PMs and marketers for database ports, SSL modes, and passwords they do not possess. 41% of our support tickets are “I don't have credentials,” followed by 18% for failed syncs. Furthermore, requiring a 20-minute, open-tab sync kills momentum.

Because Week-2 retention jumps from 11% to 62% once a user builds their first chart, our sole objective is getting non-technical users to that "aha!" moment in under two minutes.

---

What to Fix (In Priority Order)

#### 1. Add “Explore with Sample Data” & a Clear “Skip” Button (Step 5) * What: Let users bypass database connection entirely using a fully populated e-commerce or SaaS demo dataset. * Why: This is the highest-leverage fix. It immediately unblocks the 59% who drop off at Step 5 and the 41% who lack DB credentials, giving them an instant path to create a first chart and experience the product’s value on Day 1.

#### 2. Introduce “Invite a Data Teammate” at Connection (Step 6) * What: Add a 1-click option: “Don't have credentials? Send an invite link to your data lead to connect your warehouse.” * Why: Replaces a dead end with collaboration. The PM stays in the app using sample data while the engineer handles credentials asynchronously.

#### 3. Make Syncing Asynchronous (Step 8) * What: Run syncing in the background. Notify users via email/in-app alert when ready instead of forcing them to keep a 20-minute tab open. * Why: Directly addresses our second-biggest support issue (18% sync failures/cancellations) and eliminates the drop-off caused by tab abandonment.

#### 4. Pre-Populate the Dashboard; Kill the Blank Canvas (Steps 9 & 10) * What: When a user selects a template, generate it automatically with 3–4 standard charts instead of dropping them onto an empty canvas. Prompt them to tweak one existing chart. * Why: Bridges the 8% drop-off between connecting data (41%) and creating a first chart (33%). Editing an existing chart is far lower friction than building from scratch.

#### 5. Defer Email Verification and Profiling Questions (Steps 2, 3, & 4) * What: Move verification to a non-blocking banner at the top of the app, and cut or defer the role/team-size questions until after the user creates their first chart. * Why: Every barrier before core value reduces trial-to-paid conversion. Let users reach the product before demanding administrative tasks.

---

Next Step

Let’s implement Priority 1 (Sample Data) this sprint. It requires zero infrastructure changes to our warehouse sync logic and directly targets our biggest activation leak.

Claims the judge couldn’t find in the brief

  • requiring a 20-minute, open-tab sync kills momentum.
  • the 41% who lack DB credentials (as a proportion of users).
  • It requires zero infrastructure changes to our warehouse sync logic.

Grades and run details

Decision model 70 · LLM judge 45
Decision model checks
  • passUses the supplied evidence correctly49%
  • failAddresses the actual decision41%
  • passRespects explicit constraints53%
  • failIdentifies material uncertainty98%
  • failAvoids unsupported claims73%
  • passProduces the required deliverable95%
  • passPrioritises by impact98%
  • passActivation defined by what predicts retention100%
  • passGets the base of every number right56%
  • passGets people to value sooner100%
Run
Run
#1
API response time
21 s
Submitted
1 Oct 2026

Usable with a quick edit6 of 10 checks passed

The memo is actionable and well-structured; a PM could remove the unsupported 'strongest' claim and still use it with a quick edit.

Output

To: Onboarding Squad Subject: Where onboarding is leaking—and what to fix first

The biggest loss is before a data source is connected: only 41% of signups get that far. Another 8 percentage points drop before a first chart. Just 9% of signups invite a teammate. The strongest activation signal is the chart: week-2 retention is 62% for users who reach one, versus 11% for those who don’t. Prioritize getting people to a useful chart; treat invites as a later step.

Fixes, in priority order

  1. Offer a sample-data path that reaches a real first chart. Let users skip connecting their own data and explore a preloaded dataset, with a clear route to connect later. Many signups are PMs and marketers, and the most common onboarding ticket is missing database credentials (41%). A required technical connection is an especially poor first step for them. This also gives users value while they wait for access.
  1. Make connecting data simpler and recoverable. Replace or supplement the 14-page guide with short, connector-specific instructions and troubleshooting. Validate credentials early, explain the required access, and offer a clear retry path. Don’t cancel a sync when someone leaves the page; send progress and failure notices and let users resume. The credential and sync tickets point to concrete blockers, and successful connection is the gateway to the high-retention chart experience.
  1. Get users to a chart with fewer decisions. Replace the database-wide table list with suggested tables and plain-language descriptions; cut the 12 dashboard templates to a few recommended starting points. Provide a prebuilt chart or guided first-chart flow rather than an empty canvas. The 8-point drop between connection and first chart, plus the sync burden, suggests too much work remains after connection.
  1. Remove early friction that doesn’t create value. Test deferring email verification until after users enter the product, and move role/team questions until they can personalize something useful. These steps currently delay access before users see value.
  1. Make inviting a teammate contextual, not a hurdle. Keep it optional; prompt after a user has made or shared a chart, and explain the benefit. Only 9% of signups invite someone, but chart reach—not inviting—is the clearest retention signal.

Track step conversion and time-to-first-chart by path, especially sample-data versus live connection, before expanding the changes.

Claims the judge couldn’t find in the brief

  • The strongest activation signal is the chart
  • chart reach—not inviting—is the clearest retention signal

Grades and run details

Decision model 90 · LLM judge 64
Decision model checks
  • passUses the supplied evidence correctly82%
  • passAddresses the actual decision56%
  • passRespects explicit constraints67%
  • partialIdentifies material uncertainty67%
  • partialAvoids unsupported claims27%
  • passProduces the required deliverable97%
  • passPrioritises by impact98%
  • passActivation defined by what predicts retention100%
  • passGets the base of every number right72%
  • passGets people to value sooner100%
Run
Run
#1
API response time
12 s
Submitted
29 Sept 2026

Check by check

Where the outputs differ comes first. Open a check to read the judge’s reasons. “Mixed” means the two graders disagreed.

Where they differ 2

Addresses the actual decisionWrongWrongMixed
Gemini 4 Argon · API

The output does not state any condition or result that would change the prioritized answer, as required by the criteria.

Gemini 3.8 Flash · API

The output does not state what result or condition would change the recommended priority order.

GPT-6 Luna · API

The output does not specify what result or condition would change the ranked order, only to track metrics before expanding changes.

Gets the base of every number rightRightMixedRight
Gemini 4 Argon · API

All derived percentages (59%, 8%) are correctly computed from the funnel steps, and bases like support tickets are stated where ambiguous.

Gemini 3.8 Flash · API

The phrase 'the 41% who lack DB credentials' is ambiguous and could be read as a user share; the base (support tickets) is not restated, leading to a misrepresentation.

GPT-6 Luna · API

All percentages use correct bases: signups for funnel steps, users for retention, tickets for support share.

All got wrong 2

Identifies material uncertaintyWrongWrongWrong
Gemini 4 Argon · API

It does not name any unknowns that could change the decision or say how they would be resolved.

Gemini 3.8 Flash · API

No unknowns that could change the decision are named, nor how they would be resolved.

GPT-6 Luna · API

Does not name specific unknowns that could change the decision, only suggests tracking metrics before expanding.

Avoids unsupported claimsWrongWrongWrong
Gemini 4 Argon · API

It presents interpretations like 'PMs don't understand SSL modes' and 'blank canvases cause analysis paralysis' as established facts without labelling them as hypotheses.

Gemini 3.8 Flash · API

It presents 'kills momentum' and 'zero infrastructure changes' as established facts without evidence, and mislabels the 41% ticket share as a user proportion.

GPT-6 Luna · API

Presents 'strongest activation signal' and 'clearest retention signal' as facts without labeling them as hypotheses, when the evidence only shows correlation for chart reach.

All mixed 1

Uses the supplied evidence correctlyMixedMixedMixed
Gemini 4 Argon · API

The claim 'PMs and marketers don't understand SSL modes' is not supported by the brief or supplied context; it is invented.

Gemini 3.8 Flash · API

The output misuses the 41% support-ticket share as a user percentage ('the 41% who lack DB credentials') and presents unsupported interpretations as fact.

GPT-6 Luna · API

Claims that chart is the strongest activation signal and clearest retention signal are not supported by the context, which only provides retention for chart reach, not comparative data.

All got right 5

Respects explicit constraintsRightRightRight
Gemini 4 Argon · API

The memo is under 500 words, addressed to the onboarding squad, and proposes fixes that respect the brief's constraints.

Gemini 3.8 Flash · API

The output is a memo to the onboarding squad, under 500 words, and respects the requested form.

GPT-6 Luna · API

Memo is under 500 words, addressed to the onboarding squad, and respects the requested form.

Produces the required deliverableRightRightRight
Gemini 4 Argon · API

The deliverable is a complete memo with a prioritized list of fixes and reasons, under 500 words, ready for the onboarding squad.

Gemini 3.8 Flash · API

The memo is complete, correctly addressed, within the word limit, and actionable with light edits.

GPT-6 Luna · API

Provides a memo with prioritized fixes and reasons, usable by the squad.

Prioritises by impactRightRightRight
Gemini 4 Argon · API

Fixes are ordered by impact on the activation bottleneck, starting with the biggest drop-off before connecting data.

Gemini 3.8 Flash · API

Fixes are ranked by likely impact on activation, starting with the biggest drop-off at data connection.

GPT-6 Luna · API

Fixes are ranked by likely impact on activation, starting with sample-data path to address the biggest drop.

Activation defined by what predicts retentionRightRightRight
Gemini 4 Argon · API

It explicitly defines activation as building a first chart because of its retention lift (62% vs 11%) and ranks fixes by their effect on reaching that event.

Gemini 3.8 Flash · API

It defines activation as building a first chart, links it to retention (11% vs 62%), and ranks fixes by their effect on reaching that event.

GPT-6 Luna · API

Defines activation as reaching a first chart based on retention data, and ranks fixes by effect on that event.

Gets people to value soonerRightRightRight
Gemini 4 Argon · API

Main fixes cut or defer steps before first value (sample data, invite engineer, defer email verification) and give a warm start with pre-populated charts.

Gemini 3.8 Flash · API

The main fixes cut or defer steps before first value (sample data bypasses connection, invite defers credentials, async sync removes wait, pre-populated dashboard gives warm start, verification/questions deferred).

GPT-6 Luna · API

Main fixes cut or defer steps before first chart (sample data, defer email verification, reduce decisions), shortening path to value.

Results

Every setup we’ve tested on this task type, across all its tasks and repeats, graded on the current checklist. Calibrated. Where our PM checked the graders by hand, they agreed on 72% of 53 checks.

#Model · HarnessTask scoreDecision modelLLM judgeRunsCritical failures
1Sonnet 5.5withAPI83.6100.02None
2GPT-6 AstrawithChatGPT86.195.52None
3GPT-6.1 SolwithAPI83.690.92None
4Haiku 5.5withAPI88.086.72None
5GPT-6 LunawithAPI92.781.82None
6Opus 5.5withClaude81.478.42None
7Gemini 4 ArgonwithAPI73.665.22None
8Gemini 3.8 FlashwithAPI71.451.92None
9Gemini 3.5 Flash-LitewithGemini60.039.42None

What you get for the cost

GPT-6 Luna · API scores within 5 points of Sonnet 5.5 · API at about a thirtieth of the cost.

Task score against relative cost for each setup. The table below has the same figures.4050607080901001×3×10×30×100×Cost per output, relative to the cheapest setup (log scale) →↑ Task scoreSonnet 5.5 · API: task score 93, 32× the cheapestGPT-6 Astra · ChatGPT: task score 91, 122× the cheapest (1 of 2 outputs estimated)GPT-6.1 Sol · API: task score 88, 15× the cheapestHaiku 5.5 · API: task score 88, 1.8× the cheapestGPT-6 Luna · API: task score 88, the cheapestOpus 5.5 · Claude: task score 79, 101× the cheapest (1 of 2 outputs estimated)Gemini 4 Argon · API: task score 68, 15× the cheapestGemini 3.8 Flash · API: task score 59, 13× the cheapestGemini 3.5 Flash-Lite · Gemini: task score 47, 3.4× the cheapest (1 of 2 outputs estimated)Sonnet 5.5 · APIGPT-6 Astra · ChatGPTGPT-6.1 Sol · APIHaiku 5.5 · APIGPT-6 Luna · APIOpus 5.5 · ClaudeGemini 4 Argon · APIGemini 3.8 Flash · APIGemini 3.5 Flash-Lite · Gemini
Best valueNobody beats these on both score and costCost partly estimated (app runs with no usage meter)
Task score and relative cost by setup
SetupTask scoreRelative cost (cheapest = 1)
GPT-6 Luna · API881.0×
Haiku 5.5 · API881.8×
Gemini 3.5 Flash-Lite · Gemini473.4× (partly estimated)
Gemini 3.8 Flash · API5913×
GPT-6.1 Sol · API8815×
Gemini 4 Argon · API6815×
Sonnet 5.5 · API9332×
Opus 5.5 · Claude79101× (partly estimated)
GPT-6 Astra · ChatGPT91122× (partly estimated)

Cost is each output’s tokens at the model’s list price, shown relative to the cheapest setup. Runs done in an app have no usage meter, so theirs are estimated from the same setup’s measured runs. How we compare cost

About the task

The PM job

Reviewing a signup and onboarding flow that is losing users.

Why it matters

Anyone can list fifty UX nits. The job is finding the two that explain the drop-off, backed by the funnel data supplied.

What good looks like

  • Ties each issue to the funnel data
  • Prioritises by likely impact
  • Defines activation as the behaviour that predicts retention, not finishing onboarding

Deliberately not measured

  • Accessibility audit completeness
  • Visual redesign
Capability tested

Consequential critique

The failure we’re looking for

A generic UX checklist

Grading

Decision model and LLM judge, calibrated against a blind PM review