Signup Flow CRO

Production-grade signup and registration optimization framework covering authentication strategy, field reduction methodology, multi-step flow architecture, SSO implementation, progressive profiling, credit card requirement analysis, post-submit experience design, and mobile-specific registration patterns. For post-signup onboarding, use onboarding-cro. For lead capture forms (not account creation), use form-cro.

Table of Contents

• Initial Assessment
• Authentication Strategy
• Field Reduction Methodology
• Multi-Step Flow Architecture
• Credit Card Requirement Analysis
• Post-Submit Experience
• Mobile Signup Optimization
• Signup Flow Patterns by Product Type
• Progressive Profiling
• Error and Edge Case Handling
• A/B Test Framework
• Metrics and Benchmarks
• Output Artifacts
• Related Skills

Initial Assessment

Required Context

Authentication Strategy

Authentication Methods Ranked by Friction

SSO Strategy Decision

SSO Placement

┌──────────────────────────────────┐
│  Create your account             │
│                                  │
│  [Continue with Google]          │  ← SSO options first
│  [Continue with Microsoft]       │
│                                  │
│  ──── or ────                   │  ← Visual separator
│                                  │
│  Email: [_______________]       │  ← Email+password as alternative
│  Password: [_______________]    │
│                                  │
│  [Create Account]               │
└──────────────────────────────────┘

Rules:

• SSO buttons above the email form (not below)
• Use branded button styles (Google's official button, etc.)
• "or" divider between SSO and email options
• SSO reduces fields to zero (name and email come from the provider)

Field Reduction Methodology

The "Before First Use" Test

For every field, ask: Does the product literally not function without this data?

Enrichment Sources

Minimum Viable Field Sets

Multi-Step Flow Architecture

When to Use Multi-Step

Step Design

Step 1: Account Creation (lowest friction)

• Email + Password (or SSO)
• NOTHING else on this step
• This is where 60%+ of abandonment happens if overloaded

Step 2: Personalization (if needed)

• Role / goal / use case selection
• This personalizes their product experience
• Skip button available ("Set up later")

Step 3: Configuration (if needed)

• Team invite, integration connect, data import
• Each sub-step is optional with "Skip for now"
• Show value of completing each ("Invite your team to collaborate")

Progress Design

• Show step count: "Step 1 of 3"
• Show progress bar
• Label each step descriptively: "Create Account", "Your Role", "Your Team"
• Allow back navigation (preserve entered data)
• Never reset the form on back navigation or browser back button

Credit Card Requirement Analysis

Decision Framework

Impact Analysis

Recommendation Framework

Default to no CC required unless:

1. Your product delivers immediate, obvious value (no learning curve) 2