Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
borghei avatar

Signup Flow Cro

  • 76 installs
  • 451 repo stars
  • Updated July 21, 2026
  • borghei/claude-skills

Signup Flow CRO is a Claude skill that optimizes signup and registration conversion through SSO strategy, field reduction, multi-step flow design, progressive profiling and A/B testing.

About

Signup Flow CRO is a conversion-rate-optimization framework for signup and registration flows. It covers authentication strategy and SSO selection, field-reduction methodology, multi-step flow architecture, credit-card-requirement analysis, post-submit experience, mobile signup patterns, progressive profiling and an A/B test framework. It ranks auth methods by friction with conversion-impact estimates and applies a 'Before First Use' test to decide which fields to keep, defer or drop. Growth teams use it to raise signup completion rates.

  • Optimizes signup and registration flows: SSO strategy, field reduction, multi-step design and mobile patterns
  • Ranks auth methods by friction with conversion-impact estimates (e.g. Google SSO +15-30%)
  • Applies a 'Before First Use' test to cut or defer every non-essential field

Signup Flow Cro by the numbers

  • 76 all-time installs (skills.sh)
  • Ranked #498 of 853 Sales & Marketing skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

signup-flow-cro capabilities & compatibility

Free; a guidance and analysis framework, no API keys.

Capabilities
saas metrics coach
Use cases
ui design · marketing
Pricing
Free
From the docs

What signup-flow-cro says it does

Signup and registration flow optimization covering SSO strategy, progressive profiling, field reduction, multi-step flow design, authentication UX, post-submit experience, and mobile registration
SKILL.md
Current fields + completion rate + drop-off** — baseline and the friction point to cut (each removed field ~+10%)
SKILL.md
For every field, ask: **Does the product literally not function without this data?**
SKILL.md
npx skills add https://github.com/borghei/claude-skills --skill signup-flow-cro

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs76
repo stars451
Last updatedJuly 21, 2026
Repositoryborghei/claude-skills

What it does

Optimize signup and registration flow conversion via SSO, field reduction and multi-step flow design.

Who is it for?

Growth and product teams raising signup completion rates on free-trial, freemium, paid or waitlist flows.

Skip if: Post-signup onboarding (use onboarding-cro) or lead-capture forms that are not account creation (use form-cro).

When should I use this skill?

You need to reduce signup friction, choose an SSO strategy, cut form fields, or A/B test a registration flow.

What you get

A lower-friction signup flow with the right SSO mix, a minimal field set, and an A/B test plan.

  • Authentication and SSO strategy
  • Reduced field set
  • Multi-step flow design

By the numbers

  • 8 auth methods ranked by friction
  • each removed field estimated at ~+10% completion
  • Google SSO estimated +15-30% vs email+password

Files

SKILL.mdMarkdownGitHub ↗

Signup Flow CRO

Production-grade signup and registration optimization framework covering authentication strategy, field reduction methodology, multi-step flow architecture, SSO implementation, progressive profiling, credit card requirement analysis, post-submit experience design, and mobile-specific registration patterns. For post-signup onboarding, use onboarding-cro. For lead capture forms (not account creation), use form-cro.

---

Table of Contents

---

Clarify First

Before optimizing the signup flow, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] Flow type — free trial, freemium, paid, or waitlist (determines friction tolerance and minimum field set)
  • [ ] B2B or B2C — B2B tolerates more fields; B2C needs minimal friction (sets SSO priority and field count)
  • [ ] Current fields + completion rate + drop-off — baseline and the friction point to cut (each removed field ~+10%)
  • [ ] Data truly needed before first product use — separates must-have fields from those to defer or enrich (the "Before First Use" test)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the audit.

Initial Assessment

Required Context

QuestionWhy It Matters
Flow type? (free trial, freemium, paid, waitlist)Determines friction tolerance
B2B or B2C?B2B tolerates more fields, B2C needs minimal friction
How many steps/screens currently?Baseline for optimization
What fields are required?Identifies reduction opportunities
Current completion rate?Benchmark for improvement
Where do users drop off? (field-level data)Pinpoints specific friction
What data is needed before first product use?Separates must-have from nice-to-have
What compliance requirements exist?Constrains what can be deferred

---

Authentication Strategy

Authentication Methods Ranked by Friction

MethodFriction LevelBest ForConversion Impact
Google SSO (one-click)Very lowB2B SaaS, productivity tools+15-30% vs email+password
Apple Sign InVery lowiOS/Mac-heavy audience+10-20% on Apple devices
Microsoft SSOLowEnterprise B2B+10-15% for enterprise
GitHub SSOLowDeveloper tools+15-25% for dev audience
Magic link (email)LowSecurity-conscious, B2B+5-10% vs password
Email + passwordMediumUniversal fallbackBaseline
Phone + OTPMediumMobile-first, B2CVaries by market
Email + password + verificationHighWhen verification is required-10-20% vs no verification

SSO Strategy Decision

Your AudiencePrimary SSOSecondary SSOKeep Email+Password?
B2B SaaS (general)Google WorkspaceMicrosoftYes
Developer toolsGitHubGoogleYes
EnterpriseMicrosoft/OktaGoogleYes (for personal evals)
B2C consumerGoogleAppleYes
Mobile-firstApple / GooglePhone OTPOptional
Privacy-focusedMagic linkEmail+passwordYes

SSO Placement

┌──────────────────────────────────┐
│  Create your account             │
│                                  │
│  [Continue with Google]          │  ← SSO options first
│  [Continue with Microsoft]       │
│                                  │
│  ──── or ────                   │  ← Visual separator
│                                  │
│  Email: [_______________]       │  ← Email+password as alternative
│  Password: [_______________]    │
│                                  │
│  [Create Account]               │
└──────────────────────────────────┘

Rules:

  • SSO buttons above the email form (not below)
  • Use branded button styles (Google's official button, etc.)
  • "or" divider between SSO and email options
  • SSO reduces fields to zero (name and email come from the provider)

---

Field Reduction Methodology

The "Before First Use" Test

For every field, ask: Does the product literally not function without this data?

FieldPasses Test?Action
EmailYes (account identity)Keep
PasswordYes (account security)Keep (or use SSO/magic link)
First nameUsually noDefer to onboarding or profile
Last nameNoDefer or drop entirely
Company nameUsually noEnrich from email domain
Phone numberRarelyDefer unless SMS verification required
Job titleNoDefer to onboarding or enrich
Team sizeNoDefer to onboarding
How did you hear about us?NeverPost-signup survey or attribution
IndustryNoEnrich from company data

Enrichment Sources

FieldEnrichment MethodTiming
Company nameEmail domain lookup (Clearbit, Apollo)Immediately post-signup
Company sizeCompany data APIImmediately post-signup
IndustryCompany data APIImmediately post-signup
Job titleLinkedIn API or manual CSM researchBefore first sales contact
LocationIP geolocationOn signup

Minimum Viable Field Sets

Signup TypeMinimum FieldsAdditional (if needed)
FreemiumEmail only (or SSO)--
Free trial (product-led)Email + Password (or SSO)--
Free trial (sales-assisted)Email + Password + Company+ Role (for routing)
Paid signupEmail + Password + Payment--
WaitlistEmail+ One qualifying question
Enterprise trialEmail + Company + Role+ Team size (for provisioning)

---

Multi-Step Flow Architecture

When to Use Multi-Step

ConditionSingle-StepMulti-Step
Total fields1-45+
Need to qualify/routeNoYes
Product needs configurationNoYes
B2B with team setupNoYes

Step Design

Step 1: Account Creation (lowest friction)

  • Email + Password (or SSO)
  • NOTHING else on this step
  • This is where 60%+ of abandonment happens if overloaded

Step 2: Personalization (if needed)

  • Role / goal / use case selection
  • This personalizes their product experience
  • Skip button available ("Set up later")

Step 3: Configuration (if needed)

  • Team invite, integration connect, data import
  • Each sub-step is optional with "Skip for now"
  • Show value of completing each ("Invite your team to collaborate")

Progress Design

  • Show step count: "Step 1 of 3"
  • Show progress bar
  • Label each step descriptively: "Create Account", "Your Role", "Your Team"
  • Allow back navigation (preserve entered data)
  • Never reset the form on back navigation or browser back button

---

Credit Card Requirement Analysis

Decision Framework

FactorRequire CCDo Not Require CC
Trial conversion goal> 60% trial-to-paid> 30% trial-to-paid with higher volume
Product complexitySimple, immediate valueComplex, needs exploration
ACV> $100/month< $100/month
Sales motionProduct-ledSales-assisted
Competitor practiceCompetitors require CCCompetitors offer CC-free trial
Target audienceEnterprise (committed buyers)SMB/prosumer (browsers)

Impact Analysis

ApproachSignup VolumeTrial QualityTrial-to-PaidNet Revenue
No CC requiredHigher (+40-80%)Lower (more tire-kickers)Lower (2-15%)Often higher net
CC requiredLowerHigher (committed)Higher (40-70%)Depends on volume
CC with "$0 charge"MiddleMiddleMiddle (20-40%)Middle

Recommendation Framework

Default to no CC required unless: 1. Your product delivers immediate, obvious value (no learning curve) 2. Your trial-to-paid with CC is > 50% 3. You have a high-touch sales team to handle lower volume 4. Support costs for free trials are unsustainable

If requiring CC: Display prominently:

  • "You won't be charged until [date]"
  • "Cancel anytime before [date]"
  • "We'll email you 3 days before your trial ends"

---

Post-Submit Experience

Immediately After Signup

ElementImplementation
Auto-loginLog the user in immediately (never force a separate login)
Welcome screenShow a clear next step, not a blank dashboard
Confirmation emailSend immediately, include: what to expect, key features, support contact
Email verificationDefer if possible. If required, send inline and let them continue using the product before verifying

Email Verification Strategy

ApproachImpact on ActivationWhen to Use
No verificationBest activation rateLow-risk products, freemium
Verify to unlock specific featureGood -- users activate firstB2B SaaS with free tier
Verify within 24 hoursModerate -- creates urgencyProducts that send emails
Verify before any useWorst activation rateRegulated industries, financial products

Default recommendation: Let users use the product immediately. Verify within 24-48 hours. Gate only the features that require a verified email (e.g., sending emails, team invites).

---

Mobile Signup Optimization

Mobile-Specific Rules

RuleImplementation
SSO firstGoogle/Apple Sign In is one tap on mobile
One columnNever use side-by-side fields on mobile
Large inputsMinimum 44px height for all touch targets
Appropriate keyboardstype="email", type="tel", type="password"
Auto-fill supportUse standard field names for browser auto-fill
Sticky CTAPin "Create Account" button to bottom of viewport
No CAPTCHAUse invisible reCAPTCHA or alternatives
Password visibilityToggle to show/hide password

Mobile vs Desktop Signup Differences

AspectDesktopMobile
Primary authSSO or Email+PasswordSSO preferred (one-tap)
Fields per screenUp to 5Max 3
Password rulesShow requirements upfrontShow on interaction
CAPTCHAStandard reCAPTCHA acceptableInvisible or none
Social proofSidebar or adjacentBelow form or above

---

Signup Flow Patterns by Product Type

B2B SaaS Trial

[Google SSO] or [Email + Password]
→ Auto-login to product
→ Welcome screen: "What brings you here?" (3 options)
→ Guided first action based on selection
→ Team invite prompt (optional, day 2-3)

B2C Consumer App

[Apple Sign In] or [Google Sign In] or [Email]
→ Immediately into product
→ Personalization (follows, preferences) inline
→ Profile completion deferred

Enterprise/Sales-Assisted

[Work Email + Password + Company Name]
→ Auto-login to sandbox
→ Role + team size (for provisioning)
→ CSM outreach triggered for qualified accounts
→ Guided setup with dedicated support

Waitlist / Early Access

[Email only]
→ Confirmation page: position in waitlist
→ Referral mechanism: "Jump ahead by sharing"
→ Weekly update email on progress
→ Access granted email with one-click activation

---

Progressive Profiling

Collect information over multiple sessions instead of one long form.

Progressive Profiling Schedule

SessionWhat to CollectHow
Signup (session 1)Email + authSignup form
First use (session 1-2)Role, primary goalIn-product prompt or setup wizard
Day 3-5Team size, use caseContextual question in product
Day 7-14Industry, company sizeSurvey or enrichment
Before first paymentBilling infoUpgrade flow

Implementation Rules

  • Each profiling touchpoint asks 1-2 questions maximum
  • Always explain why you are asking ("So we can personalize your experience")
  • Always provide a "Skip" option
  • Never ask for information you can enrich automatically
  • Store partial profiles and build over time

---

Error and Edge Case Handling

Password Requirements

ApproachUser ExperienceSecurity
Show requirements upfrontBest -- user knows what to enterGood
Show requirements on focusGoodGood
Show errors only after submitBad -- frustratingSame
Real-time checkmarksBest -- progressive validationGood

Recommended: Show password requirements as a checklist that checks off in real-time as the user types.

Common Error Scenarios

ErrorBad UXGood UX
Email already registered"Error: account exists""This email already has an account. [Log in] or [Reset password]"
Weak password"Password too weak"Checkmarks showing which requirements are met/unmet
SSO failureGeneric error page"Something went wrong with Google login. [Try again] or [Use email instead]"
Network errorForm clears, no message"Connection issue. Your data is saved. [Try again]"
Rate limitingBlocked with no explanation"Too many attempts. Please try again in [N] minutes"

---

A/B Test Framework

High-Impact Tests

TestHypothesisMetric
Add Google SSOSSO increases completion by 15-30%Signup completion rate
Remove non-essential fieldsFewer fields = higher completionCompletion rate + activation rate
Single-step vs multi-stepMulti-step feels easier for 5+ field formsCompletion rate
CC required vs notNo CC increases volume enough to offset lower conversionNet revenue
Defer email verificationImmediate product access increases activationActivation rate

Measurement Rules

  • Track signup completion rate AND downstream activation rate
  • A test that increases signups but decreases activation is not a win
  • Track by traffic source (paid vs organic may respond differently)
  • Track mobile and desktop separately

---

Metrics and Benchmarks

Key Metrics

MetricFormulaBenchmark
Signup page visit-to-completionCompletions / Page views30-50% (B2B), 40-60% (B2C)
SSO adoption rateSSO signups / Total signups30-60% when offered
Field-level drop-offAbandonment per fieldIdentify highest-drop field
Time to completeMedian seconds from first interaction to submit< 45s for simple, < 2min for multi-step
Mobile completion rateMobile completions / Mobile page viewsShould be within 15% of desktop
Email verification rateVerified / Total signups> 70% within 48 hours

---

Output Artifacts

ArtifactFormatDescription
Signup Flow AuditIssue/Impact/Fix/Priority tablePer-step analysis with estimated impact
Recommended Field SetJustified listRequired vs deferrable fields with rationale
Authentication StrategyDecision matrixSSO options, placement, priority
Flow Redesign SpecStep-by-step outlineScreen-by-screen design with copy
Progressive Profiling PlanSession-by-session scheduleWhat to collect, when, and how
A/B Test PlanPrioritized tableTop 5 tests with hypothesis and expected impact
Mobile Optimization ChecklistPer-element rulesTouch targets, keyboards, auto-fill, sticky CTA

---

Tool Reference

1. signup_field_auditor.py

Audits a signup form configuration for unnecessary fields, missing enrichment opportunities, and friction points. Evaluates each field against the "Before First Use" test and recommends which to keep, defer, or enrich.

python scripts/signup_field_auditor.py fields.json --format text
python scripts/signup_field_auditor.py fields.json --format json
FlagTypeDescription
fields.jsonpositionalPath to JSON file with form field configuration
--formatoptionalOutput format: text (default) or json

2. signup_flow_scorer.py

Scores a complete signup flow against conversion best practices. Evaluates SSO availability, field count, step count, mobile optimization, error handling, and post-submit experience. Outputs a 0-100 score with itemized improvements.

python scripts/signup_flow_scorer.py flow.json --format text
python scripts/signup_flow_scorer.py flow.json --format json
FlagTypeDescription
flow.jsonpositionalPath to JSON file with signup flow configuration
--formatoptionalOutput format: text (default) or json

3. cc_requirement_analyzer.py

Analyzes whether to require a credit card for trial signup. Takes business metrics (ACV, trial-to-paid rate, support costs, competitors) and recommends CC-required, CC-free, or "$0 charge" approach with projected volume and revenue impact.

python scripts/cc_requirement_analyzer.py business.json --format text
python scripts/cc_requirement_analyzer.py business.json --format json
FlagTypeDescription
business.jsonpositionalPath to JSON file with business metrics
--formatoptionalOutput format: text (default) or json

---

Troubleshooting

ProblemLikely CauseResolution
Signup completion rate below 30% (B2B) or 40% (B2C)Too many fields, no SSO option, or form on a separate page from the CTAReduce to email-only or SSO; keep form on the same page as the value proposition; each removed field improves conversion ~10%
SSO adoption rate below 30% when offeredSSO buttons placed below the email form, or wrong SSO providers for the audienceMove SSO buttons above the email form with "or" divider; match SSO to audience (Google for B2B, Apple for iOS users)
Mobile completion rate >15% below desktopForm not optimized for touch (small inputs, wrong keyboard types, no auto-fill)Ensure 44px min touch targets, use type="email"/type="tel", enable browser auto-fill, pin CTA to bottom of viewport
High drop-off on password fieldComplex password requirements shown only after submission, or no password visibility toggleShow requirements as real-time checklist, add show/hide toggle, consider magic link or SSO to eliminate password entirely
Email verification kills activationVerification required before any product use blocks the critical first-session experienceDefer verification to 24-48 hours; allow product use immediately; gate only email-sending features behind verification
"Email already registered" errors are frequentUsers forget they have accounts; error message does not help them recoverChange error to "This email has an account. [Log in] or [Reset password]" with direct links
High abandonment on multi-step flowsSteps are not progressive, no progress indicator, or too many fields per stepShow step count and progress bar; limit step 1 to account creation only; add "Skip for now" on non-essential steps

---

Success Criteria

  • Signup page visit-to-completion rate reaches 30-50% (B2B) or 40-60% (B2C) within 60 days of optimization
  • SSO adoption reaches 30-60% of total signups when SSO is properly offered
  • Median time-to-complete stays below 45 seconds for simple flows and below 2 minutes for multi-step
  • Mobile completion rate falls within 15% of desktop completion rate
  • Email verification rate exceeds 70% within 48 hours of signup
  • Field-level drop-off analysis shows no single field causing >10% incremental abandonment
  • Post-signup activation rate (first key action) improves alongside signup rate (not a vanity metric tradeoff)

---

Scope & Limitations

In scope: Authentication strategy (SSO, magic link, email+password), field reduction methodology, multi-step flow architecture, credit card requirement analysis, post-submit experience design, mobile signup optimization, progressive profiling schedules, error and edge case handling, and A/B testing frameworks for registration flows.

Out of scope: Post-signup onboarding and activation (use onboarding-cro), non-registration forms like lead capture or contact forms (use form-cro), landing page conversion before the signup form (use page-cro), in-app upgrade and paywall flows (use paywall-upgrade-cro). Scripts operate on local data only -- no integrations with authentication providers (Auth0, Clerk, etc.) or analytics platforms.

Limitations: Conversion benchmarks are aggregate SaaS/app industry data and vary by vertical, price point, and audience. SSO adoption rates depend heavily on audience composition (developer audiences adopt GitHub SSO at 40%+, while SMB audiences may prefer email). Credit card requirement analysis is modeled on industry averages -- actual impact requires A/B testing in your specific context. Progressive profiling recommendations assume standard SaaS lifecycle stages.

---

Integration Points

  • onboarding-cro -- Signup flow ends at account creation; onboarding-cro picks up from first login through activation
  • form-cro -- Field-level optimization principles (validation, keyboard types, error handling) apply to signup forms
  • page-cro -- Landing page quality directly impacts signup form reach; optimize the page before optimizing the form
  • paywall-upgrade-cro -- Trial signup configuration (CC-required, trial length) affects downstream upgrade flow design
  • pricing-strategy -- Pricing model (freemium vs trial) determines signup flow type and field requirements
  • referral-program -- Referred user signups should pre-fill referrer context and display incentive

---

Related Skills

  • onboarding-cro -- Use for post-signup activation optimization. Signup-flow-cro ends when the user has an account; onboarding-cro starts there.
  • form-cro -- Use for non-signup forms (lead capture, contact, demo request). Different optimization framework than registration.
  • page-cro -- Use when the landing page leading to signup is the bottleneck, not the signup form itself.
  • paywall-upgrade-cro -- Use when the real challenge is converting free users to paid, not getting them to sign up.

Related skills

FAQ

How much does removing a field help?

The skill estimates roughly +10% completion per removed field, using a 'Before First Use' test to decide what to keep.

What auth method converts best?

One-click Google SSO is ranked very-low friction with about +15-30% versus email plus password.

Sales & Marketinglifecyclecontent

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.