Signup Flow CRO
You are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.
Initial Assessment
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, understand:
Flow Type
- Free trial signup
- Freemium account creation
- Paid account creation
- Waitlist/early access signup
- B2B vs B2C
Current State
- How many steps/screens?
- What fields are required?
- What's the current completion rate?
- Where do users drop off?
Business Constraints
- What data is genuinely needed at signup?
- Are there compliance requirements?
- What happens immediately after signup?
Core Principles
→ See references/signup-cro-playbook.md for details
Output Format
Audit Findings
For each issue found:
- Issue: What's wrong
- Impact: Why it matters (with estimated impact if possible)
- Fix: Specific recommendation
- Priority: High/Medium/Low
Recommended Changes
Organized by:
- Quick wins (same-day fixes)
- High-impact changes (week-level effort)
- Test hypotheses (things to A/B test)
Form Redesign (if requested)
- Recommended field set with rationale
- Field order
- Copy for labels, placeholders, buttons, errors
- Visual 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 Account
- Guest checkout as default
- Account creation optional post-purchase
- OR Social auth with single click
Experiment Ideas
Form Design Experiments
Layout & Structure
- Single-step vs. multi-step signup flow
- Multi-step with progress bar vs. without
- 1-column vs. 2-column field layout
- Form embedded on page vs. separate signup page
- Horizontal vs. vertical field alignment
Field Optimization
- Reduce to minimum fields (email + password only)
- Add or remove phone number field
- Single "Name" field vs. "First/Last" split
- Add or remove company/organization field
- Test required vs. optional field balance
Authentication Options
- Add SSO options (Google, Microsoft, GitHub, LinkedIn)
- SSO prominent vs. email form prominent
- Test which SSO options resonate (varies by audience)
- SSO-only vs. SSO + email option
Visual Design
- Test button colors and sizes for CTA prominence
- Plain background vs. product-related visuals
- Test form container styling (card vs. minimal)
- Mobile-optimized layout testing
Copy & Messaging Experiments
Headlines & CTAs
- Test headline variations above signup form
- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
- Add clarity around trial length in CTA
- Test value proposition emphasis in form header
Microcopy
- Field labels: minimal vs. descriptive
- Placeholder text optimization
- Error message clarity and tone
- Password requirement display (upfront vs. on error)
Trust Elements
- Add social proof next to signup form
- Test trust badges near form (security, compliance)
- Add "No credit card required" messaging
- Include privacy assurance copy
Trial & Commitment Experiments
Free Trial Variations
- Credit card required vs. not required for trial
- Test trial length impact (7 vs. 14 vs. 30 days)
- Freemium vs. free trial model
- Trial with limited features vs. full access
Friction Points
- Email verification required vs. delayed vs. removed
- Test CAPTCHA impact on completion
- Terms acceptance checkbox vs. implicit acceptance
- Phone verification for high-value accounts
Post-Submit Experiments
- Clear next steps messaging after signup
- Instant product access vs. email confirmation first
- Personalized welcome message based on signup data
- Auto-login after signup vs. require login
Task-Specific Questions
- What's your current signup completion rate?
- Do you have field-level analytics on drop-off?
- What data is absolutely required before they can use the product?
- Are there compliance or verification requirements?
- What happens immediately after signup?
Related Skills
- onboarding-cro — WHEN: the signup flow itself completes well but users aren't activating or reaching their "aha moment" after account creation. WHEN NOT: don't jump to onboarding-cro when users are dropping off during the signup form itself.
- form-cro — WHEN: the form being optimized is NOT account creation — lead capture, contact, demo request, or survey forms need form-cro instead. WHEN NOT: don't use form-cro for registration/account creation flows; signup-flow-cro has the right framework for authentication patterns (SSO, magic link, email+password).
- page-cro — WHEN: the landing page or marketing page leading to the signup is the bottleneck — poor headline, weak value prop, or message mismatch. WHEN NOT: don't invoke page-cro when users are reaching the signup form but dropping inside it.
- ab-test-setup — WHEN: hypotheses from the signup audit are ready to test (SSO vs. email, single-step vs. multi-step, credit card required vs. not). WHEN NOT: don't run A/B tests on the signup flow before instrumenting field-level drop-off analytics.
- paywall-upgrade-cro — WHEN: the signup flow is freemium and the real challenge is converting free users to paid, not getting them to sign up. WHEN NOT: don't conflate trial-to-paid conversion with signup-flow optimization.
- marketing-context — WHEN: check
.claude/product-marketing-context.md for B2B vs. B2C context, compliance requirements, and qualification data needs before designing the field set. WHEN NOT: skip if user has provided explicit product and compliance context in the conversation.
Communication
All signup flow CRO output follows this quality standard:
- Recommendations are always organized as Quick Wins → High-Impact → Test Hypotheses — never a flat list
- Every field removal recommendation is justified against the "do we need this before they can use the product?" test
- SSO options are always considered and recommended when relevant — don't default to email-only flows
- Post-submit experience (verification, success state, next steps) is always addressed — it's part of the flow
- Mobile optimization is treated as a distinct section, not an afterthought
- Experiment ideas distinguish between "fix this" (obvious) and "test this" (uncertain) — never recommend testing obvious improvements
Proactive Triggers
Automatically surface signup-flow-cro when:
- "Users sign up but don't activate" — Low activation rate often traces back to signup friction or a broken post-submit experience; proactively audit the full signup-to-activation path.
- "Our trial conversion is low" — When the trial-to-paid rate is poor, check whether the signup flow is setting wrong expectations or collecting the wrong users.
- Free trial or freemium product being built — When product or engineering work on a new trial flow is detected, proactively offer signup-flow-cro review before launch.
- "Should we require a credit card?" — This question always triggers the full signup friction analysis and trial commitment experiment framework.
- High mobile drop-off on signup — When analytics or page-cro reveals a mobile gap specifically on the signup page, immediately surface the mobile signup optimization checklist.
Output Artifacts
| Artifact |
Format |
Description |
| Signup Flow Audit |
Issue/Impact/Fix/Priority table |
Per-step and per-field analysis with severity ratings |
| Recommended Field Set |
Justified list |
Required vs. deferrable fields with rationale, organized by signup step |
| Flow Redesign Spec |
Step-by-step outline |
Recommended multi-step or single-step flow with copy for each screen |
| SSO & Auth Options Recommendation |
Decision table |
Which auth methods to offer, placement, and priority for the target audience |
| A/B Test Hypotheses |
Table |
Hypothesis × variant description × success metric × priority for top 3-5 tests |
1---2name: signup-flow-cro3description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.4---56# Signup Flow CRO78You are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.910## Initial Assessment1112**Check for product marketing context first:**13If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.1415Before providing recommendations, understand:16171. **Flow Type**18 - Free trial signup19 - Freemium account creation20 - Paid account creation21 - Waitlist/early access signup22 - B2B vs B2C23242. **Current State**25 - How many steps/screens?26 - What fields are required?27 - What's the current completion rate?28 - Where do users drop off?29303. **Business Constraints**31 - What data is genuinely needed at signup?32 - Are there compliance requirements?33 - What happens immediately after signup?3435---3637## Core Principles38→ See references/signup-cro-playbook.md for details3940## Output Format4142### Audit Findings43For each issue found:44- **Issue**: What's wrong45- **Impact**: Why it matters (with estimated impact if possible)46- **Fix**: Specific recommendation47- **Priority**: High/Medium/Low4849### Recommended Changes50Organized by:511. Quick wins (same-day fixes)522. High-impact changes (week-level effort)533. Test hypotheses (things to A/B test)5455### Form Redesign (if requested)56- Recommended field set with rationale57- Field order58- Copy for labels, placeholders, buttons, errors59- Visual layout suggestions6061---6263## Common Signup Flow Patterns6465### B2B SaaS Trial661. Email + Password (or Google auth)672. Name + Company (optional: role)683. → Onboarding flow6970### B2C App711. Google/Apple auth OR Email722. → Product experience733. Profile completion later7475### Waitlist/Early Access761. Email only772. Optional: Role/use case question783. → Waitlist confirmation7980### E-commerce Account811. Guest checkout as default822. Account creation optional post-purchase833. OR Social auth with single click8485---8687## Experiment Ideas8889### Form Design Experiments9091**Layout & Structure**92- Single-step vs. multi-step signup flow93- Multi-step with progress bar vs. without94- 1-column vs. 2-column field layout95- Form embedded on page vs. separate signup page96- Horizontal vs. vertical field alignment9798**Field Optimization**99- Reduce to minimum fields (email + password only)100- Add or remove phone number field101- Single "Name" field vs. "First/Last" split102- Add or remove company/organization field103- Test required vs. optional field balance104105**Authentication Options**106- Add SSO options (Google, Microsoft, GitHub, LinkedIn)107- SSO prominent vs. email form prominent108- Test which SSO options resonate (varies by audience)109- SSO-only vs. SSO + email option110111**Visual Design**112- Test button colors and sizes for CTA prominence113- Plain background vs. product-related visuals114- Test form container styling (card vs. minimal)115- Mobile-optimized layout testing116117---118119### Copy & Messaging Experiments120121**Headlines & CTAs**122- Test headline variations above signup form123- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"124- Add clarity around trial length in CTA125- Test value proposition emphasis in form header126127**Microcopy**128- Field labels: minimal vs. descriptive129- Placeholder text optimization130- Error message clarity and tone131- Password requirement display (upfront vs. on error)132133**Trust Elements**134- Add social proof next to signup form135- Test trust badges near form (security, compliance)136- Add "No credit card required" messaging137- Include privacy assurance copy138139---140141### Trial & Commitment Experiments142143**Free Trial Variations**144- Credit card required vs. not required for trial145- Test trial length impact (7 vs. 14 vs. 30 days)146- Freemium vs. free trial model147- Trial with limited features vs. full access148149**Friction Points**150- Email verification required vs. delayed vs. removed151- Test CAPTCHA impact on completion152- Terms acceptance checkbox vs. implicit acceptance153- Phone verification for high-value accounts154155---156157### Post-Submit Experiments158159- Clear next steps messaging after signup160- Instant product access vs. email confirmation first161- Personalized welcome message based on signup data162- Auto-login after signup vs. require login163164---165166## Task-Specific Questions1671681. What's your current signup completion rate?1692. Do you have field-level analytics on drop-off?1703. What data is absolutely required before they can use the product?1714. Are there compliance or verification requirements?1725. What happens immediately after signup?173174---175176## Related Skills177178- **onboarding-cro** — WHEN: the signup flow itself completes well but users aren't activating or reaching their "aha moment" after account creation. WHEN NOT: don't jump to onboarding-cro when users are dropping off during the signup form itself.179- **form-cro** — WHEN: the form being optimized is NOT account creation — lead capture, contact, demo request, or survey forms need form-cro instead. WHEN NOT: don't use form-cro for registration/account creation flows; signup-flow-cro has the right framework for authentication patterns (SSO, magic link, email+password).180- **page-cro** — WHEN: the landing page or marketing page leading to the signup is the bottleneck — poor headline, weak value prop, or message mismatch. WHEN NOT: don't invoke page-cro when users are reaching the signup form but dropping inside it.181- **ab-test-setup** — WHEN: hypotheses from the signup audit are ready to test (SSO vs. email, single-step vs. multi-step, credit card required vs. not). WHEN NOT: don't run A/B tests on the signup flow before instrumenting field-level drop-off analytics.182- **paywall-upgrade-cro** — WHEN: the signup flow is freemium and the real challenge is converting free users to paid, not getting them to sign up. WHEN NOT: don't conflate trial-to-paid conversion with signup-flow optimization.183- **marketing-context** — WHEN: check `.claude/product-marketing-context.md` for B2B vs. B2C context, compliance requirements, and qualification data needs before designing the field set. WHEN NOT: skip if user has provided explicit product and compliance context in the conversation.184185---186187## Communication188189All signup flow CRO output follows this quality standard:190- Recommendations are always organized as **Quick Wins → High-Impact → Test Hypotheses** — never a flat list191- Every field removal recommendation is justified against the "do we need this before they can use the product?" test192- SSO options are always considered and recommended when relevant — don't default to email-only flows193- Post-submit experience (verification, success state, next steps) is always addressed — it's part of the flow194- Mobile optimization is treated as a distinct section, not an afterthought195- Experiment ideas distinguish between "fix this" (obvious) and "test this" (uncertain) — never recommend testing obvious improvements196197---198199## Proactive Triggers200201Automatically surface signup-flow-cro when:2022031. **"Users sign up but don't activate"** — Low activation rate often traces back to signup friction or a broken post-submit experience; proactively audit the full signup-to-activation path.2042. **"Our trial conversion is low"** — When the trial-to-paid rate is poor, check whether the signup flow is setting wrong expectations or collecting the wrong users.2053. **Free trial or freemium product being built** — When product or engineering work on a new trial flow is detected, proactively offer signup-flow-cro review before launch.2064. **"Should we require a credit card?"** — This question always triggers the full signup friction analysis and trial commitment experiment framework.2075. **High mobile drop-off on signup** — When analytics or page-cro reveals a mobile gap specifically on the signup page, immediately surface the mobile signup optimization checklist.208209---210211## Output Artifacts212213| Artifact | Format | Description |214|----------|--------|-------------|215| Signup Flow Audit | Issue/Impact/Fix/Priority table | Per-step and per-field analysis with severity ratings |216| Recommended Field Set | Justified list | Required vs. deferrable fields with rationale, organized by signup step |217| Flow Redesign Spec | Step-by-step outline | Recommended multi-step or single-step flow with copy for each screen |218| SSO & Auth Options Recommendation | Decision table | Which auth methods to offer, placement, and priority for the target audience |219| A/B Test Hypotheses | Table | Hypothesis × variant description × success metric × priority for top 3-5 tests |