They signed up. Why don't they reach the aha moment?
Paste what a new user meets after signup - the first-run steps one per line, then the welcome form, the checklist, the empty states, the tour and the onboarding emails - and a few lines on your activation event and funnel. Your browser counts the steps before value, checks whether your activation event is a real action or a vanity login, and flags blockers (a forced tour, an email-verification lock, a plan screen before value, a dead-end empty state) and friction (a long welcome survey, a team invite too early, a checklist that opens with a chore). Free, before you sign in, and nothing is uploaded. Then the audit says what to keep, cut or defer, and the design writes the activation flow, the checklist, the empty states and the emails.
The products and numbers in the examples are invented. Two are audits (the B2B one also carries its design, one click after the audit) and one is a design; each comes with a saved model reply, so you can see the whole page without signing in or spending a credit.
What this does, and what it does not
New users decide in the first session whether to stay. They stay when the shortest path from signup to one real outcome - the aha moment - is short, obvious and theirs: no locked screen while an email arrives, no six-question survey, no tour they cannot skip, no plan picker before they have done anything, no empty dashboard with nothing to click. This page lists every step of your walkthrough, counts the ones that stand before value, checks that your activation event is an action rather than a login, reads your checklist, empty states, tour and emails against the skill's rules, and finds where your funnel loses the most people - with the line that shows each problem.
The paid lanes see your walkthrough (the middle is cut past 6,000 characters, and the page says so), your context (past 4,000) and the page's scan. Your input stays in this browser unless you run a lane. Every reply is held to your input: quotes are checked word for word, and no count, rate or window may be invented - the design writes [placeholders] for what only you know. This is for what happens after signup; a signup form is signup-flow optimisation, and the run will say so. Derived from the agent skill @coreyhaines31/onboarding-cro, published in its current form as @coreyhaines31/onboarding, by Corey Haines (coreyhaines31/marketingskills, MIT): its principles, onboarding psychology, the minimum path to value, the first-30-seconds approaches, the checklist, empty-state and tour rules, email and in-app coordination, stalled users, the metrics and the experiment ideas. Sources are listed in llms.txt.