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, freemium, paid account, waitlist/early access, B2B vs B2C
- Current State — How many steps/screens? What fields? Current completion rate? Where do users drop off?
- Business Constraints — What data is genuinely needed at signup? Compliance requirements? What happens after signup?
Installation
OpenClaw / Moltbot / Clawbot
npx clawhub@latest install signup-flow-cro
Core Principles
1. Minimize Required Fields
Every field reduces conversion. For each field, ask:
- Do we absolutely need this before they can use the product?
- Can we collect this later through progressive profiling?
- Can we infer this from other data?
Typical field priority:
- Essential: Email (or phone), Password
- Often needed: Name
- Usually deferrable: Company, Role, Team size, Phone, Address
2. Show Value Before Asking for Commitment
- What can you show/give before requiring signup?
- Can they experience the product before creating an account?
- Reverse the order: value first, signup second
3. Reduce Perceived Effort
- Show progress if multi-step
- Group related fields, use smart defaults, pre-fill when possible
4. Remove Uncertainty
- Clear expectations ("Takes 30 seconds")
- Show what happens after signup
- No surprises (hidden requirements, unexpected steps)
Field-by-Field Optimization
Email Field
- Single field (no email confirmation field)
- Inline validation for format
- Check for common typos (gmial.com → gmail.com)
- Clear error messages
Password Field
- Show password toggle (eye icon)
- Show requirements upfront, not after failure
- Allow paste (don't disable it)
- Show strength meter instead of rigid rules
- Consider passwordless options
Name Field
- Single "Full name" field vs. First/Last split (test this)
- Only require if immediately used (personalization)
- Consider making optional
Social Auth Options
- Place prominently (often higher conversion than email)
- Show most relevant options: B2C → Google, Apple, Facebook; B2B → Google, Microsoft, SSO
- Clear visual separation from email signup
Phone Number
- Defer unless essential (SMS verification, calling leads)
- If required, explain why
- Proper input type with country code handling
Single-Step vs. Multi-Step
Single-Step Works When:
- 3 or fewer fields
- Simple B2C products
- High-intent visitors
Multi-Step Works When:
- More than 3-4 fields needed
- Complex B2B products needing segmentation
- Different types of info needed
Multi-Step Best Practices
- Show progress indicator
- Lead with easy questions (name, email)
- Put harder questions later (after psychological commitment)
- Each step completable in seconds
- Allow back navigation
- Save progress (don't lose data on refresh)
Trust and Friction Reduction
At the Form Level
- "No credit card required" (if true)
- "Free forever" or "14-day free trial"
- Privacy note: "We'll never share your email"
- Security badges if relevant
- Testimonial near signup form
Error Handling
- Inline validation (not just on submit)
- Specific error messages ("Email already registered" + recovery path)
- Don't clear the form on error
- Focus on the problem field
Mobile Signup Optimization
- Larger touch targets (44px+ height)
- Appropriate keyboard types (email, tel, etc.)
- Autofill support
- Reduce typing (social auth, pre-fill)
- Single column layout
- Sticky CTA button
- Test with actual devices
Post-Submit Experience
Success State
- Clear confirmation and immediate next step
- If email verification required: explain what to do, easy resend option, check spam reminder, option to change email
Verification Flows
- Consider delaying verification until necessary
- Magic link as alternative to password
- Let users explore while awaiting verification
Measurement
Key Metrics
- Form start rate (landed → started filling)
- Form completion rate (started → submitted)
- Field-level drop-off (which fields lose people)
- Time to complete
- Error rate by field
- Mobile vs. desktop completion
Common Signup Flow Patterns
| Pattern |
Steps |
Best For |
| B2B SaaS Trial |
Email + Password (or Google auth) → Name + Company → Onboarding |
Products needing workspace setup |
| B2C App |
Google/Apple auth OR Email → Product experience → Profile later |
Mobile-first products |
| Waitlist |
Email only → Optional role/use case question → Confirmation |
Pre-launch validation |
| E-commerce |
Guest checkout default → Account creation optional post-purchase |
Transactional flows |
Experiment Ideas
Form Design
- Single-step vs. multi-step signup flow
- Reduce to minimum fields (email + password only)
- Single "Name" field vs. "First/Last" split
- Add/remove phone number field
Authentication
- Add SSO options (Google, Microsoft, GitHub)
- SSO prominent vs. email form prominent
- SSO-only vs. SSO + email option
Copy & Messaging
- CTA text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
- Add "No credit card required" messaging
- Social proof next to signup form
- Trust badges near form
Trial & Commitment
- Credit card required vs. not required for trial
- Trial length (7 vs. 14 vs. 30 days)
- Freemium vs. free trial model
- Email verification required vs. delayed
Output Format
Audit Findings
For each issue: Issue → Impact → Fix → Priority (High/Medium/Low)
Recommended Changes
- 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
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?
NEVER Do
- Never require a credit card for free trials without testing the impact — this is the single biggest friction point
- Never use a confirmation email field — it only adds friction; users copy-paste anyway
- Never clear the form on validation errors — losing typed data is infuriating
- Never disable paste in password fields — this punishes password manager users
- Never use CAPTCHA without measuring its conversion impact — the friction cost may exceed bot prevention value
- Never ask for information you don't immediately use — defer company size, role, and use case to onboarding
- Never forget mobile — test signup on actual mobile devices, not just responsive previews
- Never ignore field-level analytics — you can't fix drop-off you can't see
Related Skills
- onboarding-cro: For optimizing what happens after signup
- page-cro: For the landing page leading to signup
- marketing-psychology: For the psychological principles behind form optimization
1---2name: signup-flow-cro-33description: 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.4---5
6# Signup Flow CRO
7
8You 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.
9
10## Initial Assessment
11
12**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.
14
15Before providing recommendations, understand:
16
171. **Flow Type** — Free trial, freemium, paid account, waitlist/early access, B2B vs B2C
182. **Current State** — How many steps/screens? What fields? Current completion rate? Where do users drop off?
193. **Business Constraints** — What data is genuinely needed at signup? Compliance requirements? What happens after signup?
20
21
22## Installation
23
24### OpenClaw / Moltbot / Clawbot
25
26```bash
27npx clawhub@latest install signup-flow-cro
28```
29
30
31---
32
33## Core Principles
34
35### 1. Minimize Required Fields
36Every field reduces conversion. For each field, ask:
37- Do we absolutely need this before they can use the product?
38- Can we collect this later through progressive profiling?
39- Can we infer this from other data?
40
41**Typical field priority:**
42- Essential: Email (or phone), Password
43- Often needed: Name
44- Usually deferrable: Company, Role, Team size, Phone, Address
45
46### 2. Show Value Before Asking for Commitment
47- What can you show/give before requiring signup?
48- Can they experience the product before creating an account?
49- Reverse the order: value first, signup second
50
51### 3. Reduce Perceived Effort
52- Show progress if multi-step
53- Group related fields, use smart defaults, pre-fill when possible
54
55### 4. Remove Uncertainty
56- Clear expectations ("Takes 30 seconds")
57- Show what happens after signup
58- No surprises (hidden requirements, unexpected steps)
59
60---
61
62## Field-by-Field Optimization
63
64### Email Field
65- Single field (no email confirmation field)
66- Inline validation for format
67- Check for common typos (gmial.com → gmail.com)
68- Clear error messages
69
70### Password Field
71- Show password toggle (eye icon)
72- Show requirements upfront, not after failure
73- Allow paste (don't disable it)
74- Show strength meter instead of rigid rules
75- Consider passwordless options
76
77### Name Field
78- Single "Full name" field vs. First/Last split (test this)
79- Only require if immediately used (personalization)
80- Consider making optional
81
82### Social Auth Options
83- Place prominently (often higher conversion than email)
84- Show most relevant options: B2C → Google, Apple, Facebook; B2B → Google, Microsoft, SSO
85- Clear visual separation from email signup
86
87### Phone Number
88- Defer unless essential (SMS verification, calling leads)
89- If required, explain why
90- Proper input type with country code handling
91
92---
93
94## Single-Step vs. Multi-Step
95
96### Single-Step Works When:
97- 3 or fewer fields
98- Simple B2C products
99- High-intent visitors
100
101### Multi-Step Works When:
102- More than 3-4 fields needed
103- Complex B2B products needing segmentation
104- Different types of info needed
105
106### Multi-Step Best Practices
107- Show progress indicator
108- Lead with easy questions (name, email)
109- Put harder questions later (after psychological commitment)
110- Each step completable in seconds
111- Allow back navigation
112- Save progress (don't lose data on refresh)
113
114---
115
116## Trust and Friction Reduction
117
118### At the Form Level
119- "No credit card required" (if true)
120- "Free forever" or "14-day free trial"
121- Privacy note: "We'll never share your email"
122- Security badges if relevant
123- Testimonial near signup form
124
125### Error Handling
126- Inline validation (not just on submit)
127- Specific error messages ("Email already registered" + recovery path)
128- Don't clear the form on error
129- Focus on the problem field
130
131---
132
133## Mobile Signup Optimization
134
135- Larger touch targets (44px+ height)
136- Appropriate keyboard types (email, tel, etc.)
137- Autofill support
138- Reduce typing (social auth, pre-fill)
139- Single column layout
140- Sticky CTA button
141- Test with actual devices
142
143---
144
145## Post-Submit Experience
146
147### Success State
148- Clear confirmation and immediate next step
149- If email verification required: explain what to do, easy resend option, check spam reminder, option to change email
150
151### Verification Flows
152- Consider delaying verification until necessary
153- Magic link as alternative to password
154- Let users explore while awaiting verification
155
156---
157
158## Measurement
159
160### Key Metrics
161- Form start rate (landed → started filling)
162- Form completion rate (started → submitted)
163- Field-level drop-off (which fields lose people)
164- Time to complete
165- Error rate by field
166- Mobile vs. desktop completion
167
168---
169
170## Common Signup Flow Patterns
171
172| Pattern | Steps | Best For |
173|---------|-------|----------|
174| B2B SaaS Trial | Email + Password (or Google auth) → Name + Company → Onboarding | Products needing workspace setup |
175| B2C App | Google/Apple auth OR Email → Product experience → Profile later | Mobile-first products |
176| Waitlist | Email only → Optional role/use case question → Confirmation | Pre-launch validation |
177| E-commerce | Guest checkout default → Account creation optional post-purchase | Transactional flows |
178
179---
180
181## Experiment Ideas
182
183### Form Design
184- Single-step vs. multi-step signup flow
185- Reduce to minimum fields (email + password only)
186- Single "Name" field vs. "First/Last" split
187- Add/remove phone number field
188
189### Authentication
190- Add SSO options (Google, Microsoft, GitHub)
191- SSO prominent vs. email form prominent
192- SSO-only vs. SSO + email option
193
194### Copy & Messaging
195- CTA text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
196- Add "No credit card required" messaging
197- Social proof next to signup form
198- Trust badges near form
199
200### Trial & Commitment
201- Credit card required vs. not required for trial
202- Trial length (7 vs. 14 vs. 30 days)
203- Freemium vs. free trial model
204- Email verification required vs. delayed
205
206---
207
208## Output Format
209
210### Audit Findings
211For each issue: **Issue** → **Impact** → **Fix** → **Priority** (High/Medium/Low)
212
213### Recommended Changes
2141. Quick wins (same-day fixes)
2152. High-impact changes (week-level effort)
2163. Test hypotheses (things to A/B test)
217
218### Form Redesign (if requested)
219- Recommended field set with rationale
220- Field order
221- Copy for labels, placeholders, buttons, errors
222- Visual layout suggestions
223
224---
225
226## Task-Specific Questions
227
2281. What's your current signup completion rate?
2292. Do you have field-level analytics on drop-off?
2303. What data is absolutely required before they can use the product?
2314. Are there compliance or verification requirements?
2325. What happens immediately after signup?
233
234---
235
236## NEVER Do
237
2381. **Never require a credit card for free trials without testing the impact** — this is the single biggest friction point
2392. **Never use a confirmation email field** — it only adds friction; users copy-paste anyway
2403. **Never clear the form on validation errors** — losing typed data is infuriating
2414. **Never disable paste in password fields** — this punishes password manager users
2425. **Never use CAPTCHA without measuring its conversion impact** — the friction cost may exceed bot prevention value
2436. **Never ask for information you don't immediately use** — defer company size, role, and use case to onboarding
2447. **Never forget mobile** — test signup on actual mobile devices, not just responsive previews
2458. **Never ignore field-level analytics** — you can't fix drop-off you can't see
246
247---
248
249## Related Skills
250
251- **onboarding-cro**: For optimizing what happens after signup
252- **page-cro**: For the landing page leading to signup
253- **marketing-psychology**: For the psychological principles behind form optimization