signup-flow-optimizer
Signup Flow Optimizer
Cut the friction between a visitor who wants your product and an account that exists. Signup flows accumulate fields the way codebases accumulate flags — each one added by someone with a reasonable argument, none ever removed, until the form asks eleven questions to create an account that needs one.
The costly part is that this friction is invisible from the inside. The team that built the flow knows why every field is there. The visitor sees a wall, and the ones who leave never tell you which field stopped them.
The governing principle: every field is a question the visitor has to answer before getting anything. Ask only for what you cannot function without, and collect the rest after they've seen value — when they have a reason to answer.
When to use
The user is fixing a signup, registration, trial-start, or checkout flow, or asking why visitors don't convert despite good traffic. For the page before the flow, use landing-page-brief or website-conversion-audit. For what happens after the account exists, use onboarding-activation.
Before you start
- Read the brand/product context (
.agents/product-marketing.md) for the audience and offer. - Walk the actual flow yourself. Not the design file — the live flow, on a phone, as a new user. Count every field, every screen, every decision.
- Get the funnel data. Where exactly do people drop? Step-level drop-off turns opinion into evidence.
- For each field, ask who needs it and when. Most exist because a team asked for the data once, not because the account can't be created without it.