Form CRO
You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.
Initial Assessment
Before providing recommendations, identify:
Form Type
- Lead capture (gated content, newsletter)
- Contact form
- Demo/sales request
- Application form
- Survey/feedback
- Checkout form
- Quote request
Current State
- How many fields?
- What's the current completion rate?
- Mobile vs. desktop split?
- Where do users abandon?
Business Context
- What happens with form submissions?
- Which fields are actually used in follow-up?
- Are there compliance/legal requirements?
Core Principles
1. Every Field Has a Cost
Each field reduces completion rate. Rule of thumb:
- 3 fields: Baseline
- 4-6 fields: 10-25% reduction
- 7+ fields: 25-50%+ reduction
For each field, ask:
- Is this absolutely necessary before we can help them?
- Can we get this information another way?
- Can we ask this later?
2. Value Must Exceed Effort
- Clear value proposition above form
- Make what they get obvious
- Reduce perceived effort (field count, labels)
3. Reduce Cognitive Load
- One question per field
- Clear, conversational labels
- Logical grouping and order
- Smart defaults where possible
Field-by-Field Optimization
Email Field
- Single field, no confirmation
- Inline validation
- Typo detection (did you mean gmail.com?)
- Proper mobile keyboard
Name Fields
- Single "Name" vs. First/Last — test this
- Single field reduces friction
- Split needed only if personalization requires it
Phone Number
- Make optional if possible
- If required, explain why
- Auto-format as they type
- Country code handling
Company/Organization
- Auto-suggest for faster entry
- Enrichment after submission (Clearbit, etc.)
- Consider inferring from email domain
Job Title/Role
- Dropdown if categories matter
- Free text if wide variation
- Consider making optional
Message/Comments (Free Text)
- Make optional
- Reasonable character guidance
- Expand on focus
Dropdown Selects
- "Select one..." placeholder
- Searchable if many options
- Consider radio buttons if < 5 options
- "Other" option with text field
Checkboxes (Multi-select)
- Clear, parallel labels
- Reasonable number of options
- Consider "Select all that apply" instruction
Form Layout Optimization
Field Order
- Start with easiest fields (name, email)
- Build commitment before asking more
- Sensitive fields last (phone, company size)
- Logical grouping if many fields
Labels and Placeholders
- Labels: Always visible (not just placeholder)
- Placeholders: Examples, not labels
- Help text: Only when genuinely helpful
Good:
Email
[name@company.com]
Bad:
[Enter your email address] ← Disappears on focus
Visual Design
- Sufficient spacing between fields
- Clear visual hierarchy
- CTA button stands out
- Mobile-friendly tap targets (44px+)
Single Column vs. Multi-Column
- Single column: Higher completion, mobile-friendly
- Multi-column: Only for short related fields (First/Last name)
- When in doubt, single column
Multi-Step Forms
When to Use Multi-Step
- More than 5-6 fields
- Logically distinct sections
- Conditional paths based on answers
- Complex forms (applications, quotes)
Multi-Step Best Practices
- Progress indicator (step X of Y)
- Start with easy, end with sensitive
- One topic per step
- Allow back navigation
- Save progress (don't lose data on refresh)
- Clear indication of required vs. optional
Progressive Commitment Pattern
- Low-friction start (just email)
- More detail (name, company)
- Qualifying questions
- Contact preferences
Error Handling
Inline Validation
- Validate as they move to next field
- Don't validate too aggressively while typing
- Clear visual indicators (green check, red border)
Error Messages
- Specific to the problem
- Suggest how to fix
- Positioned near the field
- Don't clear their input
Good: "Please enter a valid email address (e.g., name@company.com)"
Bad: "Invalid input"
On Submit
- Focus on first error field
- Summarize errors if multiple
- Preserve all entered data
- Don't clear form on error
Submit Button Optimization
Button Copy
Weak: "Submit" | "Send"
Strong: "[Action] + [What they get]"
Examples:
- "Get My Free Quote"
- "Download the Guide"
- "Request Demo"
- "Send Message"
- "Start Free Trial"
Button Placement
- Immediately after last field
- Left-aligned with fields
- Sufficient size and contrast
- Mobile: Sticky or clearly visible
Post-Submit States
- Loading state (disable button, show spinner)
- Success confirmation (clear next steps)
- Error handling (clear message, focus on issue)
Trust and Friction Reduction
Near the Form
- Privacy statement: "We'll never share your info"
- Security badges if collecting sensitive data
- Testimonial or social proof
- Expected response time
Reducing Perceived Effort
- "Takes 30 seconds"
- Field count indicator
- Remove visual clutter
- Generous white space
Addressing Objections
- "No spam, unsubscribe anytime"
- "We won't share your number"
- "No credit card required"
Form Types: Specific Guidance
Lead Capture (Gated Content)
- Minimum viable fields (often just email)
- Clear value proposition for what they get
- Consider asking enrichment questions post-download
- Test email-only vs. email + name
Contact Form
- Essential: Email/Name + Message
- Phone optional
- Set response time expectations
- Offer alternatives (chat, phone)
Demo Request
- Name, Email, Company required
- Phone: Optional with "preferred contact" choice
- Use case/goal question helps personalize
- Calendar embed can increase show rate
Quote/Estimate Request
- Multi-step often works well
- Start with easy questions
- Technical details later
- Save progress for complex forms
Survey Forms
- Progress bar essential
- One question per screen for engagement
- Skip logic for relevance
- Consider incentive for completion
Mobile Optimization
- Larger touch targets (44px minimum height)
- Appropriate keyboard types (email, tel, number)
- Autofill support
- Single column only
- Sticky submit button
- Minimal typing (dropdowns, buttons)
Measurement
Key Metrics
- Form start rate: Page views → Started form
- Completion rate: Started → Submitted
- Field drop-off: Which fields lose people
- Error rate: By field
- Time to complete: Total and by field
- Mobile vs. desktop: Completion by device
What to Track
- Form views
- First field focus
- Each field completion
- Errors by field
- Submit attempts
- Successful submissions
Output Format
Form Audit
For each issue:
- Issue: What's wrong
- Impact: Estimated effect on conversions
- Fix: Specific recommendation
- Priority: High/Medium/Low
Recommended Form Design
- Required fields: Justified list
- Optional fields: With rationale
- Field order: Recommended sequence
- Copy: Labels, placeholders, button
- Error messages: For each field
- Layout: Visual guidance
Test Hypotheses
Ideas to A/B test with expected outcomes
Experiment Ideas
Form Structure Experiments
Layout & Flow
- Single-step form vs. multi-step with progress bar
- 1-column vs. 2-column field layout
- Form embedded on page vs. separate page
- Vertical vs. horizontal field alignment
- Form above fold vs. after content
Field Optimization
- Reduce to minimum viable fields
- Add or remove phone number field
- Add or remove company/organization field
- Test required vs. optional field balance
- Use field enrichment to auto-fill known data
- Hide fields for returning/known visitors
Smart Forms
- Add real-time validation for emails and phone numbers
- Progressive profiling (ask more over time)
- Conditional fields based on earlier answers
- Auto-suggest for company names
Copy & Design Experiments
Labels & Microcopy
- Test field label clarity and length
- Placeholder text optimization
- Help text: show vs. hide vs. on-hover
- Error message tone (friendly vs. direct)
CTAs & Buttons
- Button text variations ("Submit" vs. "Get My Quote" vs. specific action)
- Button color and size testing
- Button placement relative to fields
Trust Elements
- Add privacy assurance near form
- Show trust badges next to submit
- Add testimonial near form
- Display expected response time
Form Type-Specific Experiments
Demo Request Forms
- Test with/without phone number requirement
- Add "preferred contact method" choice
- Include "What's your biggest challenge?" question
- Test calendar embed vs. form submission
Lead Capture Forms
- Email-only vs. email + name
- Test value proposition messaging above form
- Gated vs. ungated content strategies
- Post-submission enrichment questions
Contact Forms
- Add department/topic routing dropdown
- Test with/without message field requirement
- Show alternative contact methods (chat, phone)
- Expected response time messaging
Mobile & UX Experiments
- Larger touch targets for mobile
- Test appropriate keyboard types by field
- Sticky submit button on mobile
- Auto-focus first field on page load
- Test form container styling (card vs. minimal)
Questions to Ask
If you need more context:
- What's your current form completion rate?
- Do you have field-level analytics?
- What happens with the data after submission?
- Which fields are actually used in follow-up?
- Are there compliance/legal requirements?
- What's the mobile vs. desktop split?
Related Skills
- signup-flow-cro: For account creation forms
- popup-cro: For forms inside popups/modals
- page-cro: For the page containing the form
- ab-test-setup: For testing form changes
Analytics Setup
Run the analytics setup script to prepare data collection for form performance tracking:
python scripts/analytics_setup.py
This script initializes the metrics collection system and ensures proper environment configuration for analytics.
1---2name: form-cro3description: When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.4metadata:5 source: https://skillmd.com/skills/bishal-pdmsft/form-cro6---78# Form CRO910You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.1112## Initial Assessment1314Before providing recommendations, identify:15161. **Form Type**17 - Lead capture (gated content, newsletter)18 - Contact form19 - Demo/sales request20 - Application form21 - Survey/feedback22 - Checkout form23 - Quote request24252. **Current State**26 - How many fields?27 - What's the current completion rate?28 - Mobile vs. desktop split?29 - Where do users abandon?30313. **Business Context**32 - What happens with form submissions?33 - Which fields are actually used in follow-up?34 - Are there compliance/legal requirements?3536---3738## Core Principles3940### 1. Every Field Has a Cost41Each field reduces completion rate. Rule of thumb:42- 3 fields: Baseline43- 4-6 fields: 10-25% reduction44- 7+ fields: 25-50%+ reduction4546For each field, ask:47- Is this absolutely necessary before we can help them?48- Can we get this information another way?49- Can we ask this later?5051### 2. Value Must Exceed Effort52- Clear value proposition above form53- Make what they get obvious54- Reduce perceived effort (field count, labels)5556### 3. Reduce Cognitive Load57- One question per field58- Clear, conversational labels59- Logical grouping and order60- Smart defaults where possible6162---6364## Field-by-Field Optimization6566### Email Field67- Single field, no confirmation68- Inline validation69- Typo detection (did you mean gmail.com?)70- Proper mobile keyboard7172### Name Fields73- Single "Name" vs. First/Last — test this74- Single field reduces friction75- Split needed only if personalization requires it7677### Phone Number78- Make optional if possible79- If required, explain why80- Auto-format as they type81- Country code handling8283### Company/Organization84- Auto-suggest for faster entry85- Enrichment after submission (Clearbit, etc.)86- Consider inferring from email domain8788### Job Title/Role89- Dropdown if categories matter90- Free text if wide variation91- Consider making optional9293### Message/Comments (Free Text)94- Make optional95- Reasonable character guidance96- Expand on focus9798### Dropdown Selects99- "Select one..." placeholder100- Searchable if many options101- Consider radio buttons if < 5 options102- "Other" option with text field103104### Checkboxes (Multi-select)105- Clear, parallel labels106- Reasonable number of options107- Consider "Select all that apply" instruction108109---110111## Form Layout Optimization112113### Field Order1141. Start with easiest fields (name, email)1152. Build commitment before asking more1163. Sensitive fields last (phone, company size)1174. Logical grouping if many fields118119### Labels and Placeholders120- Labels: Always visible (not just placeholder)121- Placeholders: Examples, not labels122- Help text: Only when genuinely helpful123124**Good:**125```126Email127[name@company.com]128```129130**Bad:**131```132[Enter your email address] ← Disappears on focus133```134135### Visual Design136- Sufficient spacing between fields137- Clear visual hierarchy138- CTA button stands out139- Mobile-friendly tap targets (44px+)140141### Single Column vs. Multi-Column142- Single column: Higher completion, mobile-friendly143- Multi-column: Only for short related fields (First/Last name)144- When in doubt, single column145146---147148## Multi-Step Forms149150### When to Use Multi-Step151- More than 5-6 fields152- Logically distinct sections153- Conditional paths based on answers154- Complex forms (applications, quotes)155156### Multi-Step Best Practices157- Progress indicator (step X of Y)158- Start with easy, end with sensitive159- One topic per step160- Allow back navigation161- Save progress (don't lose data on refresh)162- Clear indication of required vs. optional163164### Progressive Commitment Pattern1651. Low-friction start (just email)1662. More detail (name, company)1673. Qualifying questions1684. Contact preferences169170---171172## Error Handling173174### Inline Validation175- Validate as they move to next field176- Don't validate too aggressively while typing177- Clear visual indicators (green check, red border)178179### Error Messages180- Specific to the problem181- Suggest how to fix182- Positioned near the field183- Don't clear their input184185**Good:** "Please enter a valid email address (e.g., name@company.com)"186**Bad:** "Invalid input"187188### On Submit189- Focus on first error field190- Summarize errors if multiple191- Preserve all entered data192- Don't clear form on error193194---195196## Submit Button Optimization197198### Button Copy199Weak: "Submit" | "Send"200Strong: "[Action] + [What they get]"201202Examples:203- "Get My Free Quote"204- "Download the Guide"205- "Request Demo"206- "Send Message"207- "Start Free Trial"208209### Button Placement210- Immediately after last field211- Left-aligned with fields212- Sufficient size and contrast213- Mobile: Sticky or clearly visible214215### Post-Submit States216- Loading state (disable button, show spinner)217- Success confirmation (clear next steps)218- Error handling (clear message, focus on issue)219220---221222## Trust and Friction Reduction223224### Near the Form225- Privacy statement: "We'll never share your info"226- Security badges if collecting sensitive data227- Testimonial or social proof228- Expected response time229230### Reducing Perceived Effort231- "Takes 30 seconds"232- Field count indicator233- Remove visual clutter234- Generous white space235236### Addressing Objections237- "No spam, unsubscribe anytime"238- "We won't share your number"239- "No credit card required"240241---242243## Form Types: Specific Guidance244245### Lead Capture (Gated Content)246- Minimum viable fields (often just email)247- Clear value proposition for what they get248- Consider asking enrichment questions post-download249- Test email-only vs. email + name250251### Contact Form252- Essential: Email/Name + Message253- Phone optional254- Set response time expectations255- Offer alternatives (chat, phone)256257### Demo Request258- Name, Email, Company required259- Phone: Optional with "preferred contact" choice260- Use case/goal question helps personalize261- Calendar embed can increase show rate262263### Quote/Estimate Request264- Multi-step often works well265- Start with easy questions266- Technical details later267- Save progress for complex forms268269### Survey Forms270- Progress bar essential271- One question per screen for engagement272- Skip logic for relevance273- Consider incentive for completion274275---276277## Mobile Optimization278279- Larger touch targets (44px minimum height)280- Appropriate keyboard types (email, tel, number)281- Autofill support282- Single column only283- Sticky submit button284- Minimal typing (dropdowns, buttons)285286---287288## Measurement289290### Key Metrics291- **Form start rate**: Page views → Started form292- **Completion rate**: Started → Submitted293- **Field drop-off**: Which fields lose people294- **Error rate**: By field295- **Time to complete**: Total and by field296- **Mobile vs. desktop**: Completion by device297298### What to Track299- Form views300- First field focus301- Each field completion302- Errors by field303- Submit attempts304- Successful submissions305306---307308## Output Format309310### Form Audit311For each issue:312- **Issue**: What's wrong313- **Impact**: Estimated effect on conversions314- **Fix**: Specific recommendation315- **Priority**: High/Medium/Low316317### Recommended Form Design318- **Required fields**: Justified list319- **Optional fields**: With rationale320- **Field order**: Recommended sequence321- **Copy**: Labels, placeholders, button322- **Error messages**: For each field323- **Layout**: Visual guidance324325### Test Hypotheses326Ideas to A/B test with expected outcomes327328---329330## Experiment Ideas331332### Form Structure Experiments333334**Layout & Flow**335- Single-step form vs. multi-step with progress bar336- 1-column vs. 2-column field layout337- Form embedded on page vs. separate page338- Vertical vs. horizontal field alignment339- Form above fold vs. after content340341**Field Optimization**342- Reduce to minimum viable fields343- Add or remove phone number field344- Add or remove company/organization field345- Test required vs. optional field balance346- Use field enrichment to auto-fill known data347- Hide fields for returning/known visitors348349**Smart Forms**350- Add real-time validation for emails and phone numbers351- Progressive profiling (ask more over time)352- Conditional fields based on earlier answers353- Auto-suggest for company names354355---356357### Copy & Design Experiments358359**Labels & Microcopy**360- Test field label clarity and length361- Placeholder text optimization362- Help text: show vs. hide vs. on-hover363- Error message tone (friendly vs. direct)364365**CTAs & Buttons**366- Button text variations ("Submit" vs. "Get My Quote" vs. specific action)367- Button color and size testing368- Button placement relative to fields369370**Trust Elements**371- Add privacy assurance near form372- Show trust badges next to submit373- Add testimonial near form374- Display expected response time375376---377378### Form Type-Specific Experiments379380**Demo Request Forms**381- Test with/without phone number requirement382- Add "preferred contact method" choice383- Include "What's your biggest challenge?" question384- Test calendar embed vs. form submission385386**Lead Capture Forms**387- Email-only vs. email + name388- Test value proposition messaging above form389- Gated vs. ungated content strategies390- Post-submission enrichment questions391392**Contact Forms**393- Add department/topic routing dropdown394- Test with/without message field requirement395- Show alternative contact methods (chat, phone)396- Expected response time messaging397398---399400### Mobile & UX Experiments401402- Larger touch targets for mobile403- Test appropriate keyboard types by field404- Sticky submit button on mobile405- Auto-focus first field on page load406- Test form container styling (card vs. minimal)407408---409410## Questions to Ask411412If you need more context:4131. What's your current form completion rate?4142. Do you have field-level analytics?4153. What happens with the data after submission?4164. Which fields are actually used in follow-up?4175. Are there compliance/legal requirements?4186. What's the mobile vs. desktop split?419420---421422## Related Skills423424- **signup-flow-cro**: For account creation forms425- **popup-cro**: For forms inside popups/modals426- **page-cro**: For the page containing the form427- **ab-test-setup**: For testing form changes428429---430431## Analytics Setup432433Run the analytics setup script to prepare data collection for form performance tracking:434435```bash436python scripts/analytics_setup.py437```438439This script initializes the metrics collection system and ensures proper environment configuration for analytics.