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](#initial-assessment)
- [Authentication Strategy](#authentication-strategy)
- [Field Reduction Methodology](#field-reduction-methodology)
- [Multi-Step Flow Architecture](#multi-step-flow-architecture)
- [Credit Card Requirement Analysis](#credit-card-requirement-analysis)
- [Post-Submit Experience](#post-submit-experience)
- [Mobile Signup Optimization](#mobile-signup-optimization)
- [Signup Flow Patterns by Product Type](#signup-flow-patterns-by-product-type)
- [Progressive Profiling](#progressive-profiling)
- [Error and Edge Case Handling](#error-and-edge-case-handling)
- [A/B Test Framework](#ab-test-framework)
- [Metrics and Benchmarks](#metrics-and-benchmarks)
- [Output Artifacts](#output-artifacts)
- [Related Skills](#related-skills)
Initial Assessment
Required Context
| Question | Why It Matters | |----------|---------------| | Flow type? (free trial, freemium, paid, waitlist) | Determines friction tolerance | | B2B or B2C? | B2B tolerates more fields, B2C needs minimal friction | | How many steps/screens currently? | Baseline for optimization | | What fields are required? | Identifies reduction opportunities | | Current completion rate? | Benchmark for improvement | | Where do users drop off? (field-level data) | Pinpoints specific friction | | What data is needed before first product use? | Separates must-have from nice-to-have | | What compliance requirements exist? | Constrains what can be deferred |
Authentication Strategy
Authentication Methods Ranked by Friction
| Method | Friction Level | Best For | Conversion Impact | |--------|---------------|----------|------------------| | Google SSO (one-click) | Very low | B2B SaaS, productivity tools | +15-30% vs email+password | | Apple Sign In | Very low | iOS/Mac-heavy audience | +10-20% on Apple devices | | Microsoft SSO | Low | Enterprise B2B | +10-15% for enterprise | | GitHub SSO | Low | Developer tools | +15-25% for dev audience | | Magic link (email) | Low | Security-conscious, B2B | +5-10% vs password | | Email + password | Medium | Universal fallback | Baseline | | Phone + OTP | Medium | Mobile-first, B2C | Varies by market | | Email + password + verification | High | When verification is required | -10-20% vs no verification |
SSO Strategy Decision
| Your Audience | Primary SSO | Secondary SSO | Keep Email+Password? | |--------------|-------------|---------------|---------------------| | B2B SaaS (general) | Google Workspace | Microsoft | Yes | | Developer tools | GitHub | Google | Yes | | Enterprise | Microsoft/Okta | Google | Yes (for personal evals) | | B2C consumer | Google | Apple | Yes | | Mobile-first | Apple / Google | Phone OTP | Optional | | Privacy-focused | Magic link | Email+password | Yes |
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?
| Field | Passes Test? | Action | |-------|-------------|--------| | Email | Yes (account identity) | Keep | | Password | Yes (account security) | Keep (or use SSO/magic link) | | First name | Usually no | Defer to onboarding or profile | | Last name | No | Defer or drop entirely | | Company name | Usually no | Enrich from email domain | | Phone number | Rarely | Defer unless SMS verification required | | Job title | No | Defer to onboarding or enrich | | Team size | No | Defer to onboarding | | How did you hear about us? | Never | Post-signup survey or attribution | | Industry | No | Enrich from company data |
Enrichment Sources
| Field | Enrichment Method | Timing | |-------|-------------------|--------| | Company name | Email domain lookup (Clearbit, Apollo) | Immediately post-signup | | Company size | Company data API | Immediately post-signup | | Industry | Company data API | Immediately post-signup | | Job title | LinkedIn API or manual CSM research | Before first sales contact | | Location | IP geolocation | On signup |
Minimum Viable Field Sets
| Signup Type | Minimum Fields | Additional (if needed) | |------------|----------------|----------------------| | Freemium | Email only (or SSO) | -- | | Free trial (product-led) | Email + Password (or SSO) | -- | | Free trial (sales-assisted) | Email + Password + Company | + Role (for routing) | | Paid signup | Email + Password + Payment | -- | | Waitlist | Email | + One qualifying question | | Enterprise trial | Email + Company + Role | + Team size (for provisioning) |
Multi-Step Flow Architecture
When to Use Multi-Step
| Condition | Single-Step | Multi-Step | |-----------|------------|------------| | Total fields | 1-4 | 5+ | | Need to qualify/route | No | Yes | | Product needs configuration | No | Yes | | B2B with team setup | No | Yes |
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
| Factor | Require CC | Do Not Require CC | |--------|-----------|------------------| | Trial conversion goal | > 60% trial-to-paid | > 30% trial-to-paid with higher volume | | Product complexity | Simple, immediate value | Complex, needs exploration | | ACV | > $100/month | < $100/month | | Sales motion | Product-led | Sales-assisted | | Competitor practice | Competitors require CC | Competitors offer CC-free trial | | Target audience | Enterprise (committed buyers) | SMB/prosumer (browsers) |
Impact Analysis
| Approach | Signup Volume | Trial Quality | Trial-to-Paid | Net Revenue | |----------|-------------|---------------|---------------|-------------| | No CC required | Higher (+40-80%) | Lower (more tire-kickers) | Lower (2-15%) | Often higher net | | CC required | Lower | Higher (committed) | Higher (40-70%) | Depends on volume | | CC with "$0 charge" | Middle | Middle | Middle (20-40%) | Middle |
Recommendation Framework
Default to no CC required unless:
- Your product delivers immediate, obvious value (no learning curve)
2