Signup

---
name: Signup
description: Use when the user wants to optimize a signup, registration, or trial-activation flow with friction, drop-off, or low completion — not post-signup onboarding or generic lead forms.
category: CRO
version: 2.0.0
tools: []
---

# Signup Flow CRO

Reduce friction in signup and registration flows, increase completion rates, and set users up for successful activation.

## Initial Assessment

Search the Knowledge Base for existing product-marketing context first, and only ask what isn't already covered. Understand: **Flow type** (free trial, freemium, paid account, waitlist/early access, B2B vs. B2C). **Current state** (number of steps/screens, required fields, completion rate, drop-off points). **Business constraints** (what data is genuinely needed at signup, compliance requirements, what happens immediately after signup).

## Core Principles

**Minimize required fields** — for each field ask whether it's absolutely needed before the user can use the product, whether it can be collected later via progressive profiling, or inferred from other data. Typical priority: essential (email/phone, password), often needed (name), usually deferrable (company, role, team size, phone, address). **Show value before commitment** — let users experience the product before requiring signup where possible; reverse the order so value comes first. **Reduce perceived effort** — show progress on multi-step flows, group related fields, use smart defaults, pre-fill when possible. **Remove uncertainty** — set clear expectations ("Takes 30 seconds"), show what happens after signup, avoid hidden requirements or surprise steps.

## Field-by-Field Optimization

**Email:** single field (no confirmation field), inline format validation, catch common typos (gmial.com → gmail.com), clear error messages.

**Password:** show/hide toggle, requirements shown upfront rather than after failure, real-time requirement indicators, allow paste, prefer a strength meter over rigid rules, consider passwordless options.

**Name:** test a single "Full name" field vs. First/Last split; only require it if immediately used for personalization; consider making it optional.

**Social auth:** place prominently — often converts higher than email. B2C: Google, Apple, Facebook. B2B: Google, Microsoft, SSO. Give it clear visual separation from email signup; consider it the primary option.

**Phone:** defer unless essential (SMS verification, calling leads); explain why if required; use proper input type with country-code handling and live formatting.

**Company/organization:** defer if possible, auto-suggest as typed, infer from email domain when possible.

**Use case/role:** defer to onboarding if possible; if needed at signup, keep to one question with progressive disclosure rather than showing all options at once.

## Single-Step vs. Multi-Step

Single-step works with 3 or fewer fields, simple B2C products, and high-intent visitors (ads, waitlist). Multi-step works with more than 3-4 fields, complex B2B segmentation needs, or multiple distinct data types. Multi-step best practices: show a progress indicator, lead with easy questions (name, email), put harder questions later — after psychological commitment — keep each step completable in seconds, allow back navigation, and save progress on refresh. Progressive commitment pattern: (1) email only, (2) password + name, (3) optional customization questions.

## Trust and Friction Reduction

At the form: "No credit card required" (if true), "Free forever"/"14-day free trial", a privacy note, security badges, a testimonial near the form. Error handling: inline validation (not just on submit), specific messages (e.g., "Email already registered" plus a recovery path), never clear the form on error, focus the problem field. Microcopy: use placeholders for examples not labels, keep labels visible since placeholders disappear when typing and leave users unsure what they're filling in, and place help text close to the field only when needed.

## Mobile Signup Optimization

Touch targets 44px+ height, appropriate keyboard types (email, tel, etc.), autofill support, reduced typing via social auth/pre-fill, single-column layout, sticky CTA button, and testing on actual devices.

## Post-Submit Experience

Show a clear confirmation and immediate next step. If email verification is required: explain what to do, offer easy resend, remind to check spam, allow changing the email if wrong. Consider delaying verification until necessary, offering a magic link instead of a password, letting users explore while verification is pending, and re-engaging clearly if verification stalls.

## Measurement

Track form start rate (landed → started filling), form completion rate (started → submitted), field-level drop-off, time to complete, error rate by field, and mobile vs. desktop completion — plus per-field interaction events (focus, blur, error), step progression in multi-step flows, social-auth vs. email ratio, and time between steps.

## Output Format

Report audit findings as issue / impact (with estimated impact where possible) / fix / priority (High/Medium/Low). Organize recommendations into quick wins (same-day fixes), high-impact changes (week-level effort), and test hypotheses. If redesigning a form, specify the recommended field set with rationale, field order, copy (labels, placeholders, buttons, errors), and layout suggestions.

## Common Signup Flow Patterns

**B2B SaaS trial:** email + password (or Google auth) → name + company (optional role) → onboarding flow. **B2C app:** Google/Apple auth or email → product experience → profile completion later. **Waitlist/early access:** email only → optional role/use-case question → waitlist confirmation. **E-commerce:** guest checkout as default, account creation optional post-purchase, or social auth with a single click.

## Experiment Ideas

**Layout:** single-step vs. multi-step; progress bar vs. none; 1-column vs. 2-column; embedded vs. separate signup page; horizontal vs. vertical field alignment.

**Fields:** minimum fields (email + password only) vs. more; phone field on/off; single "Name" vs. First/Last split; company field on/off; required vs. optional field balance.

**Authentication:** add SSO (Google, Microsoft, GitHub, LinkedIn); SSO-prominent vs. email-prominent; which SSO options resonate varies by audience; SSO-only vs. SSO + email.

**Visual design:** button color/size for CTA prominence; plain background vs. product visuals; card vs. minimal form container; mobile-optimized layout.

**Copy:** headline variations above the form; CTA text ("Create Account" vs. "Start Free Trial" vs. "Get Started"); trial-length clarity in the CTA; value-proposition emphasis in the header; label minimalism; placeholder text; error-message tone; password requirements shown upfront vs. on error.

**Trust:** social proof near the form; trust/security/compliance badges; "no credit card required"; privacy assurance copy.

**Trial/commitment:** credit card required vs. not; trial length (7 vs. 14 vs. 30 days); freemium vs. free trial; limited vs. full-access trial. **Friction:** email verification required vs. delayed vs. removed; CAPTCHA impact; terms checkbox vs. implicit acceptance; phone verification for high-value accounts.

**Post-submit:** clear next-steps messaging; instant access vs. email confirmation first; personalized welcome based on signup data; auto-login vs. require login.

## Task-Specific Questions

1. What's your current signup completion rate?
2. Do you have field-level drop-off analytics?
3. What data is absolutely required before product use?
4. Are there compliance or verification requirements?
5. What happens immediately after signup?

## Related Skills

onboarding (optimizing what happens after signup), cro (non-signup forms and the landing page leading to signup), ab-testing (testing signup flow changes).