Form CRO
Production-grade form optimization framework covering field-cost analysis, layout engineering, multi-step form architecture, validation UX patterns, mobile-specific optimization, and structured A/B test design. Applicable to lead capture, contact, demo request, application, survey, and checkout forms. For signup/registration flows, use signup-flow-cro.
Table of Contents
Clarify First
Before optimizing the form, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
- Form type: lead capture, contact, demo, application, or checkout (sets the optimal field count and playbook).
- Current fields + which are used in follow-up: reveals which fields to cut or enrich (the core of field-cost analysis).
- Current completion rate + where users abandon: baseline and the specific friction point to target.
- Compliance requirements: GDPR/HIPAA fields that cannot be removed (constrains the field reduction).
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
Initial Assessment
Required Context
Field-Cost Analysis Framework
Every field has a cost measured in abandonment. The question is not "what data would be nice to have" but "what data is worth the conversion loss."
Field Cost Matrix
The Enrichment Test
Before including any field, ask: Can this be enriched after submission?
Recommended Field Sets by Form Type
Multi-Step vs Single-Step Decision
Decision Criteria
Multi-Step Best Practices
Step structure:
- Step 1: Easiest fields (email, name) -- lowest friction to start
- Step 2: Qualifying information (company, role, use case)
- Step 3: Specific details (budget, timeline, message)
Progress indication:
- Show progress bar with step count ("Step 2 of 3")
- Show completion percentage
- Label each step with what it covers ("Your Details", "Company Info", "Project Details")
Psychological commitment:
- Once a user completes Step 1, they are 40-60% more likely to complete the form (sunk cost effect)
- Capture the email in Step 1 so you can follow up even if they abandon later
Back navigation:
- Always allow users to go back to previous steps
- Preserve entered data when navigating between steps
- Never reset the form on back navigation
Field Design Patterns
Field Labels
Field Types
Conditional Fields
Show additional fields based on earlier answers. This reduces visible complexity while capturing necessary data.
Example: "What is your primary goal?" dropdown shows "Budget range" only if they select "Ready to buy" or "Evaluating solutions."
Rules:
- Conditional fields appear with smooth animation (not instant jump)
- Only 1-2 conditional fields per trigger
- Conditional fields are never required (the trigger answer may change)
Validation UX
Real-Time vs Submit-Time Validation
Error Message Design
Success Indicators
- Green checkmark on valid fields (especially email and phone)
- Positive microcopy: "Looks good!" on valid email
- Do NOT flash green/red on every keystroke -- validate on blur (when user leaves the field)
CTA and Submit Button Optimization
Button Copy Framework
Rules:
- Use first person ("Get My..." not "Get Your...")
- Specify what they get, not what they do
- Include "Free" when applicable
- Keep under 5 words
Button Design
Mobile Form Optimization
Mobile-Specific Rules
Mobile vs Desktop Form Differences
Trust and Context Elements
Trust Signals Near Forms
Context Reinforcement
Form Type Playbooks
Lead Capture (Gated Content)
Goal: Maximize completions while capturing qualified leads.
- Fields: Email only (or Email + First name maximum)
- CTA: Value-specific ("Get My Report", "Download Checklist")
- Trust: "No spam, unsubscribe anytime"
- Post-submit: Immediate download + thank you page + follow-up email
Demo Request
Goal: Capture qualified prospects ready for sales conversation.
- Fields: Email + Name + Company (+ Phone and Team size optional)
- CTA: "Schedule My Demo"
- Trust: "30-minute call, no commitment"
- Post-submit: Calendar booking page or confirmation with scheduling link
- Consider: Embedded calendar (Calendly/Cal.com) instead of form
Contact Form
Goal: Enable communication while routing to correct team.
- Fields: Email + Name + Subject dropdown + Message
- CTA: "Send Message"
- Trust: "We respond within [X] hours"
- Post-submit: Confirmation with expected response time
- Consider: Adding department/topic routing dropdown
Quote Request
Goal: Capture enough detail for accurate quoting.
- Fields: Multi-step form with project details
- CTA: "Get My Quote"
- Trust: "Free quote, no obligation"
- Post-submit: Quote delivery timeline + human follow-up
A/B Test Framework
High-Impact Tests (Run First)
Medium-Impact Tests
Measurement Rules
- Run each test for minimum 2 weeks or 200 conversions per variant (whichever is longer)
- Track both quantity (completion rate) and quality (lead score, SQL rate)
- A test that increases completions but decreases lead quality is not a win
Metrics and Measurement
Key Metrics
Instrumentation Requirements
Track these events in your analytics:
- Form view (impression)
- Form interaction (first field focus)
- Per-field completion (on blur, per field)
- Form submission attempt
- Form submission success
- Form validation error (per field)
Output Artifacts
Related Skills
- signup-flow-cro -- Use when the form is an account creation or trial registration flow. Form-cro is for lead capture, contact, and demo forms.
- popup-cro -- Use when the form lives inside a modal or popup. Form-cro handles the form itself; popup-cro handles the trigger, timing, and container.
- page-cro -- Use when the page surrounding the form needs optimization (headline, value prop, layout).
- onboarding-cro -- Use when post-form-submission activation is the bottleneck, not the form itself.
Tool Reference
1. form_scorer.py
Purpose: Score a form against CRO best practices across field count, field types, CTA quality, mobile readiness, and trust signals.
python scripts/form_scorer.py form_config.json
python scripts/form_scorer.py form_config.json --json
2. field_cost_analyzer.py
Purpose: Calculate the estimated abandonment cost of each form field and recommend fields to remove, keep, or make enrichable.
python scripts/field_cost_analyzer.py form_fields.json
python scripts/field_cost_analyzer.py form_fields.json --json
3. ab_test_calculator.py
Purpose: Calculate A/B test sample size, duration, and statistical significance for form optimization experiments.
python scripts/ab_test_calculator.py --baseline 25 --lift 10 --traffic 500
python scripts/ab_test_calculator.py --baseline 25 --lift 10 --traffic 500 --json
Troubleshooting
Success Criteria
- Form completion rate above 25% for lead capture forms (above 35% is excellent)
- Mobile completion rate within 20% of desktop rate
- Error rate below 10% of form interactions
- Field-level drop-off identifies specific friction points with clear remediation
- Each form field has documented justification (business need or enrichable post-submission)
- A/B tests run for minimum 200 conversions per variant before declaring winner
- Post-form-submission follow-up occurs within 24 hours for demo and contact forms
Scope & Limitations
- In scope: Form field optimization, CTA copy, validation UX, mobile optimization, trust signal placement, A/B test design, field cost analysis
- Out of scope: Page-level CRO (use page-cro), popup trigger optimization (use popup-cro), signup/registration flows (use signup-flow-cro), post-submission nurture sequences
- Data dependency: Field-level analytics (per-field drop-off) provide the most actionable data but require analytics instrumentation
- Compliance constraint: GDPR/HIPAA may require specific fields that cannot be removed; document compliance requirements before optimizing
- Statistical validity: A/B test recommendations require sufficient traffic volume; low-traffic forms may need longer test durations or alternative evaluation methods
Integration Points
- page-cro -- When the form converts well but the surrounding page does not drive form interactions, optimize the page-level elements first
- popup-cro -- When the form is inside a popup or modal, trigger timing and container design are handled by popup-cro
- signup-flow-cro -- For account creation and registration forms (not lead capture), use signup-flow-cro which handles multi-step auth flows
- onboarding-cro -- When post-form-submission activation is the bottleneck, not the form completion rate itself
- free-tool-strategy -- Free tools often include lead capture forms; use form-cro to optimize the capture form within the tool