# Friction-reduction signals are present on conversion forms

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

## Why it matters

A bare form with four input fields and a submit button reads as commitment when the visitor is still evaluating. Friction-reduction signals — OAuth buttons ("Continue with Google"), a "No credit card required" line, or a "Takes less than 2 minutes" note — each remove a specific concern without asking the visitor to do more work, and their presence compounds into meaningful lifts on signup completion rates, especially for first-time visitors with no prior brand trust.

## Severity rationale

High because a form with zero friction-reducers loses signups that a single OAuth button or reassurance line would have captured.

## Remediation

Add at least one friction-reduction signal to the primary conversion form — an OAuth provider button, a "no credit card" line, a time-expectation note, or a progress indicator on multi-step flows. If `next-auth`, `clerk`, `auth0`, or `better-auth` is already in `package.json`, wire up a Google or GitHub button:

```tsx
<Button variant="outline" type="button">
  <GoogleIcon /> Continue with Google
</Button>
<p className="text-xs text-muted-foreground mt-2">
  No credit card required · Setup takes 2 minutes
</p>
```

## Detection

- **ID:** `signup-friction-reduction`
- **Severity:** `high`
- **What to look for:** Check signup and conversion forms for friction-reduction patterns: (1) Social/OAuth login options — "Sign in with Google", "Continue with GitHub"; (2) "No credit card required" copy near the CTA or form; (3) "Takes less than 2 minutes" or similar time-expectation setting copy; (4) Progress indicators on multi-step forms showing how many steps remain. Check `package.json` for OAuth provider integrations (next-auth, clerk, auth0, better-auth) — their presence suggests OAuth is or could be implemented.
- **Pass criteria:** Count all friction-reduction signals on the primary conversion form (OAuth, no-CC copy, time-expectation, progress indicator). At least 1 friction-reduction signal must be present. No more than 4 bare fields without any friction-reduction signal. Report: "X friction-reduction signals found on primary conversion form."
- **Fail criteria:** The primary conversion form has none of the above friction reducers — just bare form fields and a submit button.
- **Skip (N/A) when:** No conversion form found. Or the product requires credit card for all plans and accurate disclosure is present (credit card requirement honestly disclosed is not a friction problem).
- **Detail on fail:** `"Signup form has 3 fields and submit button with no OAuth options, no 'no credit card' copy, and no time-expectation signal."`.
- **Remediation:** Small copy additions near a form reduce hesitation without engineering effort:

  ```tsx
  <form>
    {/* OAuth button if available */}
    <Button variant="outline" type="button">
      <GoogleIcon /> Continue with Google
    </Button>
    <div className="relative my-4">
      <Separator /><span className="absolute-center bg-white px-2 text-sm">or</span>
    </div>
    <Input type="email" placeholder="Work email" />
    <Input type="password" placeholder="Password" />
    <Button type="submit">Create Free Account</Button>
    <p className="text-xs text-center text-muted-foreground mt-2">
      No credit card required · Setup takes 2 minutes
    </p>
  </form>
  ```

  For a deeper analysis of authentication friction and OAuth implementation, the Authentication & Onboarding audit in the SaaS Launch Pack covers this in detail.

Taxons: user-experience

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