# Signup and conversion forms minimize required fields

- **Pattern:** `ab-001752` (`marketing-conversion.form-optimization.form-field-minimization`)
- **Severity:** critical
- **Lifecycle:** active
- **Last modified:** 2026-04-18
- **Canonical URL:** https://auditbuffet.com/patterns/ab-001752
- **License:** CC-BY-4.0 — attribute to AuditBuffet Pattern Catalog (https://auditbuffet.com/patterns/ab-001752)

## Why it matters

Every additional required field on a signup form removes a measurable percentage of completions — a four-field form loses meaningfully more signups than an email-plus-password form, and a six-field form asking for phone number and team size before first login discards the majority of interested users. Worse, a "free trial" form that silently requires a credit card without prominent disclosure reads as a bait-and-switch and destroys trust at the exact moment you are trying to build it.

## Severity rationale

Critical because excess form fields and hidden credit-card gates directly reject the majority of interested signups.

## Remediation

Reduce the primary conversion form to the minimum viable fields — typically email and password — and collect name, company, phone, and use case in a post-signup onboarding flow instead. Disclose credit-card requirements prominently on the CTA button if they apply. Edit the signup form in `app/signup/page.tsx`:

```tsx
<form>
  <Input name="email" type="email" placeholder="Work email" required />
  <Input name="password" type="password" placeholder="Create password" required />
  <Button type="submit">Create Account</Button>
</form>
```

## Detection

- **ID:** `form-field-minimization`
- **Severity:** `critical`
- **What to look for:** Locate all signup, trial, and conversion forms in the codebase (not contact forms or support forms — specifically the primary conversion action forms). Count the number of required input fields. The benchmark: email-only or email + password is optimal for a trial/signup. Each additional required field beyond email/password reduces completion rates. Specifically flag: (1) forms requiring phone number before trial; (2) forms requiring company name, team size, or use case before first login; (3) forms requiring credit card for a "free" trial without prominent disclosure.
- **Pass criteria:** Count all fields on the primary conversion form. The primary conversion form requires no more than 3 fields to complete the core action. OR the form uses a progressive disclosure pattern (email first, additional fields only after initial step). Report the count: "Primary conversion form has X fields."
- **Fail criteria:** The primary conversion form requires 4 or more fields before the user can complete signup. OR a credit card is required for a "free trial" with no prominent disclosure that payment info is required.
- **Skip (N/A) when:** No conversion/signup forms found in the codebase.
- **Detail on fail:** List the required fields found. Example: `"Signup form requires 6 fields: email, password, first name, last name, company name, and phone number — before account creation."` or `"'Free trial' form requires credit card with no disclosure on the CTA button or pricing page."`.
- **Remediation:** Every additional form field removes a percentage of completions. The minimum viable signup is email + password. Name, company, and phone can be collected after first login via an onboarding flow.

  Reduce your signup form to essentials:

  ```tsx
  // Minimal conversion form
  <form>
    <Input name="email" type="email" placeholder="Work email" required />
    <Input name="password" type="password" placeholder="Create password" required />
    <Button type="submit">Create Account</Button>
  </form>
  ```

  Collect profile information in a post-signup onboarding flow instead.

Taxons: user-experience

HTML version: https://auditbuffet.com/patterns/ab-001752
