1---
2name: signup-flow-cro
3description: 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," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
4metadata:
5  version: 1.1.0
6---
7 
8# Signup Flow CRO
9 
10You 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.
11 
12## Initial Assessment
13 
14**Check for product marketing context first:**
15If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
16 
17Before providing recommendations, understand:
18 
191. **Flow Type**
20   - Free trial signup
21   - Freemium account creation
22   - Paid account creation
23   - Waitlist/early access signup
24   - B2B vs B2C
25 
262. **Current State**
27   - How many steps/screens?
28   - What fields are required?
29   - What's the current completion rate?
30   - Where do users drop off?
31 
323. **Business Constraints**
33   - What data is genuinely needed at signup?
34   - Are there compliance requirements?
35   - What happens immediately after signup?
36 
37---
38 
39## Core Principles
40 
41### 1. Minimize Required Fields
42Every field reduces conversion. For each field, ask:
43- Do we absolutely need this before they can use the product?
44- Can we collect this later through progressive profiling?
45- Can we infer this from other data?
46 
47**Typical field priority:**
48- Essential: Email (or phone), Password
49- Often needed: Name
50- Usually deferrable: Company, Role, Team size, Phone, Address
51 
52### 2. Show Value Before Asking for Commitment
53- What can you show/give before requiring signup?
54- Can they experience the product before creating an account?
55- Reverse the order: value first, signup second
56 
57### 3. Reduce Perceived Effort
58- Show progress if multi-step
59- Group related fields
60- Use smart defaults
61- Pre-fill when possible
62 
63### 4. Remove Uncertainty
64- Clear expectations ("Takes 30 seconds")
65- Show what happens after signup
66- No surprises (hidden requirements, unexpected steps)
67 
68---
69 
70## Field-by-Field Optimization
71 
72### Email Field
73- Single field (no email confirmation field)
74- Inline validation for format
75- Check for common typos (gmial.com → gmail.com)
76- Clear error messages
77 
78### Password Field
79- Show password toggle (eye icon)
80- Show requirements upfront, not after failure
81- Consider passphrase hints for strength
82- Update requirement indicators in real-time
83 
84**Better password UX:**
85- Allow paste (don't disable)
86- Show strength meter instead of rigid rules
87- Consider passwordless options
88 
89### Name Field
90- Single "Full name" field vs. First/Last split (test this)
91- Only require if immediately used (personalization)
92- Consider making optional
93 
94### Social Auth Options
95- Place prominently (often higher conversion than email)
96- Show most relevant options for your audience
97  - B2C: Google, Apple, Facebook
98  - B2B: Google, Microsoft, SSO
99- Clear visual separation from email signup
100- Consider "Sign up with Google" as primary
101 
102### Phone Number
103- Defer unless essential (SMS verification, calling leads)
104- If required, explain why
105- Use proper input type with country code handling
106- Format as they type
107 
108### Company/Organization
109- Defer if possible
110- Auto-suggest as they type
111- Infer from email domain when possible
112 
113### Use Case / Role Questions
114- Defer to onboarding if possible
115- If needed at signup, keep to one question
116- Use progressive disclosure (don't show all options at once)
117 
118---
119 
120## Single-Step vs. Multi-Step
121 
122### Single-Step Works When:
123- 3 or fewer fields
124- Simple B2C products
125- High-intent visitors (from ads, waitlist)
126 
127### Multi-Step Works When:
128- More than 3-4 fields needed
129- Complex B2B products needing segmentation
130- You need to collect different types of info
131 
132### Multi-Step Best Practices
133- Show progress indicator
134- Lead with easy questions (name, email)
135- Put harder questions later (after psychological commitment)
136- Each step should feel completable in seconds
137- Allow back navigation
138- Save progress (don't lose data on refresh)
139 
140**Progressive commitment pattern:**
1411. Email only (lowest barrier)
1422. Password + name
1433. Customization questions (optional)
144 
145---
146 
147## Trust and Friction Reduction
148 
149### At the Form Level
150- "No credit card required" (if true)
151- "Free forever" or "14-day free trial"
152- Privacy note: "We'll never share your email"
153- Security badges if relevant
154- Testimonial near signup form
155 
156### Error Handling
157- Inline validation (not just on submit)
158- Specific error messages ("Email already registered" + recovery path)
159- Don't clear the form on error
160- Focus on the problem field
161 
162### Microcopy
163- Placeholder text: Use for examples, not labels
164- Labels: Keep visible (not just placeholders) — placeholders disappear when typing, leaving users unsure what they're filling in
165- Help text: Only when needed, placed close to field
166 
167---
168 
169## Mobile Signup Optimization
170 
171- Larger touch targets (44px+ height)
172- Appropriate keyboard types (email, tel, etc.)
173- Autofill support
174- Reduce typing (social auth, pre-fill)
175- Single column layout
176- Sticky CTA button
177- Test with actual devices
178 
179---
180 
181## Post-Submit Experience
182 
183### Success State
184- Clear confirmation
185- Immediate next step
186- If email verification required:
187  - Explain what to do
188  - Easy resend option
189  - Check spam reminder
190  - Option to change email if wrong
191 
192### Verification Flows
193- Consider delaying verification until necessary
194- Magic link as alternative to password
195- Let users explore while awaiting verification
196- Clear re-engagement if verification stalls
197 
198---
199 
200## Measurement
201 
202### Key Metrics
203- Form start rate (landed → started filling)
204- Form completion rate (started → submitted)
205- Field-level drop-off (which fields lose people)
206- Time to complete
207- Error rate by field
208- Mobile vs. desktop completion
209 
210### What to Track
211- Each field interaction (focus, blur, error)
212- Step progression in multi-step
213- Social auth vs. email signup ratio
214- Time between steps
215 
216---
217 
218## Output Format
219 
220### Audit Findings
221For each issue found:
222- **Issue**: What's wrong
223- **Impact**: Why it matters (with estimated impact if possible)
224- **Fix**: Specific recommendation
225- **Priority**: High/Medium/Low
226 
227### Recommended Changes
228Organized by:
2291. Quick wins (same-day fixes)
2302. High-impact changes (week-level effort)
2313. Test hypotheses (things to A/B test)
232 
233### Form Redesign (if requested)
234- Recommended field set with rationale
235- Field order
236- Copy for labels, placeholders, buttons, errors
237- Visual layout suggestions
238 
239---
240 
241## Common Signup Flow Patterns
242 
243### B2B SaaS Trial
2441. Email + Password (or Google auth)
2452. Name + Company (optional: role)
2463. → Onboarding flow
247 
248### B2C App
2491. Google/Apple auth OR Email
2502. → Product experience
2513. Profile completion later
252 
253### Waitlist/Early Access
2541. Email only
2552. Optional: Role/use case question
2563. → Waitlist confirmation
257 
258### E-commerce Account
2591. Guest checkout as default
2602. Account creation optional post-purchase
2613. OR Social auth with single click
262 
263---
264 
265## Experiment Ideas
266 
267### Form Design Experiments
268 
269**Layout & Structure**
270- Single-step vs. multi-step signup flow
271- Multi-step with progress bar vs. without
272- 1-column vs. 2-column field layout
273- Form embedded on page vs. separate signup page
274- Horizontal vs. vertical field alignment
275 
276**Field Optimization**
277- Reduce to minimum fields (email + password only)
278- Add or remove phone number field
279- Single "Name" field vs. "First/Last" split
280- Add or remove company/organization field
281- Test required vs. optional field balance
282 
283**Authentication Options**
284- Add SSO options (Google, Microsoft, GitHub, LinkedIn)
285- SSO prominent vs. email form prominent
286- Test which SSO options resonate (varies by audience)
287- SSO-only vs. SSO + email option
288 
289**Visual Design**
290- Test button colors and sizes for CTA prominence
291- Plain background vs. product-related visuals
292- Test form container styling (card vs. minimal)
293- Mobile-optimized layout testing
294 
295---
296 
297### Copy & Messaging Experiments
298 
299**Headlines & CTAs**
300- Test headline variations above signup form
301- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
302- Add clarity around trial length in CTA
303- Test value proposition emphasis in form header
304 
305**Microcopy**
306- Field labels: minimal vs. descriptive
307- Placeholder text optimization
308- Error message clarity and tone
309- Password requirement display (upfront vs. on error)
310 
311**Trust Elements**
312- Add social proof next to signup form
313- Test trust badges near form (security, compliance)
314- Add "No credit card required" messaging
315- Include privacy assurance copy
316 
317---
318 
319### Trial & Commitment Experiments
320 
321**Free Trial Variations**
322- Credit card required vs. not required for trial
323- Test trial length impact (7 vs. 14 vs. 30 days)
324- Freemium vs. free trial model
325- Trial with limited features vs. full access
326 
327**Friction Points**
328- Email verification required vs. delayed vs. removed
329- Test CAPTCHA impact on completion
330- Terms acceptance checkbox vs. implicit acceptance
331- Phone verification for high-value accounts
332 
333---
334 
335### Post-Submit Experiments
336 
337- Clear next steps messaging after signup
338- Instant product access vs. email confirmation first
339- Personalized welcome message based on signup data
340- Auto-login after signup vs. require login
341 
342---
343 
344## Task-Specific Questions
345 
3461. What's your current signup completion rate?
3472. Do you have field-level analytics on drop-off?
3483. What data is absolutely required before they can use the product?
3494. Are there compliance or verification requirements?
3505. What happens immediately after signup?
351 
352---
353 
354## Related Skills
355 
356- **onboarding-cro**: For optimizing what happens after signup
357- **form-cro**: For non-signup forms (lead capture, contact)
358- **page-cro**: For the landing page leading to signup
359- **ab-test-setup**: For testing signup flow changes
360