Signup form collects only essential fields
Why it matters
Every required field past email and password measurably lowers signup completion. Consumer SaaS funnels typically lose 10-30% of users per additional required field, and fields like phone number or company name trigger abandonment from users who resent handing over data before seeing the product. The user experience taxon captures this: friction at the account-creation step is the highest-leverage conversion point in the funnel, and asking for data you do not need yet is pure leakage.
Severity rationale
Medium because the impact is conversion loss rather than a security or data-integrity failure.
Remediation
Strip the signup form down to email and password (or OAuth only) and move everything else to a post-signup profile step. Edit src/app/(auth)/signup/page.tsx to render only the two required inputs, then redirect to src/app/(app)/onboarding/page.tsx where non-essential fields like company, phone, and role can be collected progressively once the account exists.
<form onSubmit={handleSignup}>
<Input name="email" type="email" required />
<Input name="password" type="password" required />
<Button type="submit">Create account</Button>
</form>
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Onboarding UX Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from saas-onboarding·automated