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.
Add this skill
npx mdskills install sickn33/signup-flow-croComprehensive CRO guide with field-by-field optimization, testing frameworks, and B2B/B2C patterns
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 Assessment1112Before providing recommendations, understand:13141. **Flow Type**15 - Free trial signup16 - Freemium account creation17 - Paid account creation18 - Waitlist/early access signup19 - B2B vs B2C20212. **Current State**22 - How many steps/screens?23 - What fields are required?24 - What's the current completion rate?25 - Where do users drop off?26273. **Business Constraints**28 - What data is genuinely needed at signup?29 - Are there compliance requirements?30 - What happens immediately after signup?3132---3334## Core Principles3536### 1. Minimize Required Fields37Every field reduces conversion. For each field, ask:38- Do we absolutely need this before they can use the product?39- Can we collect this later through progressive profiling?40- Can we infer this from other data?4142**Typical field priority:**43- Essential: Email (or phone), Password44- Often needed: Name45- Usually deferrable: Company, Role, Team size, Phone, Address4647### 2. Show Value Before Asking for Commitment48- What can you show/give before requiring signup?49- Can they experience the product before creating an account?50- Reverse the order: value first, signup second5152### 3. Reduce Perceived Effort53- Show progress if multi-step54- Group related fields55- Use smart defaults56- Pre-fill when possible5758### 4. Remove Uncertainty59- Clear expectations ("Takes 30 seconds")60- Show what happens after signup61- No surprises (hidden requirements, unexpected steps)6263---6465## Field-by-Field Optimization6667### Email Field68- Single field (no email confirmation field)69- Inline validation for format70- Check for common typos (gmial.com → gmail.com)71- Clear error messages7273### Password Field74- Show password toggle (eye icon)75- Show requirements upfront, not after failure76- Consider passphrase hints for strength77- Update requirement indicators in real-time7879**Better password UX:**80- Allow paste (don't disable)81- Show strength meter instead of rigid rules82- Consider passwordless options8384### Name Field85- Single "Full name" field vs. First/Last split (test this)86- Only require if immediately used (personalization)87- Consider making optional8889### Social Auth Options90- Place prominently (often higher conversion than email)91- Show most relevant options for your audience92 - B2C: Google, Apple, Facebook93 - B2B: Google, Microsoft, SSO94- Clear visual separation from email signup95- Consider "Sign up with Google" as primary9697### Phone Number98- Defer unless essential (SMS verification, calling leads)99- If required, explain why100- Use proper input type with country code handling101- Format as they type102103### Company/Organization104- Defer if possible105- Auto-suggest as they type106- Infer from email domain when possible107108### Use Case / Role Questions109- Defer to onboarding if possible110- If needed at signup, keep to one question111- Use progressive disclosure (don't show all options at once)112113---114115## Single-Step vs. Multi-Step116117### Single-Step Works When:118- 3 or fewer fields119- Simple B2C products120- High-intent visitors (from ads, waitlist)121122### Multi-Step Works When:123- More than 3-4 fields needed124- Complex B2B products needing segmentation125- You need to collect different types of info126127### Multi-Step Best Practices128- Show progress indicator129- Lead with easy questions (name, email)130- Put harder questions later (after psychological commitment)131- Each step should feel completable in seconds132- Allow back navigation133- Save progress (don't lose data on refresh)134135**Progressive commitment pattern:**1361. Email only (lowest barrier)1372. Password + name1383. Customization questions (optional)139140---141142## Trust and Friction Reduction143144### At the Form Level145- "No credit card required" (if true)146- "Free forever" or "14-day free trial"147- Privacy note: "We'll never share your email"148- Security badges if relevant149- Testimonial near signup form150151### Error Handling152- Inline validation (not just on submit)153- Specific error messages ("Email already registered" + recovery path)154- Don't clear the form on error155- Focus on the problem field156157### Microcopy158- Placeholder text: Use for examples, not labels159- Labels: Always visible (not just placeholders)160- Help text: Only when needed, placed close to field161162---163164## Mobile Signup Optimization165166- Larger touch targets (44px+ height)167- Appropriate keyboard types (email, tel, etc.)168- Autofill support169- Reduce typing (social auth, pre-fill)170- Single column layout171- Sticky CTA button172- Test with actual devices173174---175176## Post-Submit Experience177178### Success State179- Clear confirmation180- Immediate next step181- If email verification required:182 - Explain what to do183 - Easy resend option184 - Check spam reminder185 - Option to change email if wrong186187### Verification Flows188- Consider delaying verification until necessary189- Magic link as alternative to password190- Let users explore while awaiting verification191- Clear re-engagement if verification stalls192193---194195## Measurement196197### Key Metrics198- Form start rate (landed → started filling)199- Form completion rate (started → submitted)200- Field-level drop-off (which fields lose people)201- Time to complete202- Error rate by field203- Mobile vs. desktop completion204205### What to Track206- Each field interaction (focus, blur, error)207- Step progression in multi-step208- Social auth vs. email signup ratio209- Time between steps210211---212213## Output Format214215### Audit Findings216For each issue found:217- **Issue**: What's wrong218- **Impact**: Why it matters (with estimated impact if possible)219- **Fix**: Specific recommendation220- **Priority**: High/Medium/Low221222### Recommended Changes223Organized by:2241. Quick wins (same-day fixes)2252. High-impact changes (week-level effort)2263. Test hypotheses (things to A/B test)227228### Form Redesign (if requested)229- Recommended field set with rationale230- Field order231- Copy for labels, placeholders, buttons, errors232- Visual layout suggestions233234---235236## Common Signup Flow Patterns237238### B2B SaaS Trial2391. Email + Password (or Google auth)2402. Name + Company (optional: role)2413. → Onboarding flow242243### B2C App2441. Google/Apple auth OR Email2452. → Product experience2463. Profile completion later247248### Waitlist/Early Access2491. Email only2502. Optional: Role/use case question2513. → Waitlist confirmation252253### E-commerce Account2541. Guest checkout as default2552. Account creation optional post-purchase2563. OR Social auth with single click257258---259260## Experiment Ideas261262### Form Design Experiments263264**Layout & Structure**265- Single-step vs. multi-step signup flow266- Multi-step with progress bar vs. without267- 1-column vs. 2-column field layout268- Form embedded on page vs. separate signup page269- Horizontal vs. vertical field alignment270271**Field Optimization**272- Reduce to minimum fields (email + password only)273- Add or remove phone number field274- Single "Name" field vs. "First/Last" split275- Add or remove company/organization field276- Test required vs. optional field balance277278**Authentication Options**279- Add SSO options (Google, Microsoft, GitHub, LinkedIn)280- SSO prominent vs. email form prominent281- Test which SSO options resonate (varies by audience)282- SSO-only vs. SSO + email option283284**Visual Design**285- Test button colors and sizes for CTA prominence286- Plain background vs. product-related visuals287- Test form container styling (card vs. minimal)288- Mobile-optimized layout testing289290---291292### Copy & Messaging Experiments293294**Headlines & CTAs**295- Test headline variations above signup form296- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"297- Add clarity around trial length in CTA298- Test value proposition emphasis in form header299300**Microcopy**301- Field labels: minimal vs. descriptive302- Placeholder text optimization303- Error message clarity and tone304- Password requirement display (upfront vs. on error)305306**Trust Elements**307- Add social proof next to signup form308- Test trust badges near form (security, compliance)309- Add "No credit card required" messaging310- Include privacy assurance copy311312---313314### Trial & Commitment Experiments315316**Free Trial Variations**317- Credit card required vs. not required for trial318- Test trial length impact (7 vs. 14 vs. 30 days)319- Freemium vs. free trial model320- Trial with limited features vs. full access321322**Friction Points**323- Email verification required vs. delayed vs. removed324- Test CAPTCHA impact on completion325- Terms acceptance checkbox vs. implicit acceptance326- Phone verification for high-value accounts327328---329330### Post-Submit Experiments331332- Clear next steps messaging after signup333- Instant product access vs. email confirmation first334- Personalized welcome message based on signup data335- Auto-login after signup vs. require login336337---338339## Questions to Ask340341If you need more context:3421. What's your current signup completion rate?3432. Do you have field-level analytics on drop-off?3443. What data is absolutely required before they can use the product?3454. Are there compliance or verification requirements?3465. What happens immediately after signup?347348---349350## Related Skills351352- **onboarding-cro**: For optimizing what happens after signup353- **form-cro**: For non-signup forms (lead capture, contact)354- **page-cro**: For the landing page leading to signup355- **ab-test-setup**: For testing signup flow changes356
Full transparency — inspect the skill content before installing.