Optimize Form Conversion Rates
Optimizes form conversion via a scored Friction Index, field-level and layout best practices, and A/B test hypotheses - maximizing completion without losing
Why it matters
Maximize form completion rates and lead quality by systematically analyzing and optimizing form structure, field efficiency, and user experience.
Outcomes
What it gets done
Calculate Form Health & Friction Index
Identify structural and tactical optimization opportunities
Provide actionable recommendations for field-level and layout changes
Develop A/B test hypotheses for form improvements
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-form-cro | bash Overview
Form Conversion Rate Optimization (Form CRO)
A form CRO skill using a scored Friction Index, field-level optimization guidance, and bounded A/B test hypotheses. Use for optimizing form conversion rates - health scoring, field-level audits, layout/copy redesign, and A/B test planning.
What it does
This skill acts as an expert in form optimization and friction reduction, aiming to maximize form completion while preserving data usefulness.
Its required Phase 0 computes a Form Health & Friction Index: a diagnostic (not KPI) score out of 100 across six weighted categories - Field Necessity & Efficiency (30, every required field justified, no unused or inferable data), Value-Effort Balance (20, clear value proposition before the form, effort matching perceived reward and traffic intent), Cognitive Load & Clarity (20, clear labels, logical field order, minimal decision fatigue), Error Handling & Recovery (15, inline validation, helpful messages, no data loss on errors), Trust & Friction Reduction (10, privacy reassurance, objection handling, social proof), and Mobile Usability (5, touch-friendly, proper keyboards, no cramped fields). Health bands interpret the score: 85-100 High-Performing (optimize incrementally), 70-84 Usable with Friction (clear optimization opportunities), 55-69 Conversion-Limited (structural issues present), and below 55 Broken (stop and recommend structural fixes before testing).
Phase 1 gathers context: form type (e.g. lead capture), business context, and current performance. Its non-negotiable core principles: every field has a cost, data collection is not the same as data usage (don't collect what won't be used), and cognitive load should be reduced first.
Its field-level optimization guidance covers email (single field, no confirmation, inline validation with typo correction, correct mobile keyboard), name (a single field by default, split only if operationally required), phone (optional unless critical, with an explanation if required, auto-formatted with country code support), company/organization (auto-suggest, infer from email domain, enrich post-submission where feasible), job title/role (dropdown if segmentation matters, optional by default), free-text fields (optional unless essential, with clear length/purpose guidance), and selects/checkboxes (radio buttons under 5 options, searchable selects for long lists, clear "Other" handling).
Its layout and flow guidance covers field order (easiest first like email/name, then commitment-building fields, sensitive or high-effort fields last), labels and placeholders (labels always visible, placeholders as examples only, avoiding the label-as-placeholder anti-pattern), single-vs-multi-column layout (default single column, multi-column only for closely related fields), and multi-step forms (used for 6+ fields, distinct logical sections, or when qualification/routing is needed - with a progress indicator, back navigation, saved progress, and one topic per step).
Its error handling guidance covers inline validation (triggered after field interaction, not on every keystroke, with clear visual feedback and never clearing input on error) and error messaging (specific, human, actionable - e.g. "Please enter a valid email (name@company.com)" rather than "Invalid input"). Submit button optimization favors action-plus-outcome copy ("Get My Quote," "Request Demo," "Download the Guide") over generic "Submit"/"Send," with disabled-plus-loading states on submit and a clear success message with next-step expectations. Trust and friction reduction covers privacy reassurance near the submit button, expected response time, testimonials where appropriate, and security badges only when relevant. Mandatory mobile optimization requires touch targets of at least 44px, correct keyboard types, autofill support, single-column layout, and a sticky submit button where helpful.
Its output format covers a Form Health Summary (score, primary bottlenecks, structural vs tactical issues), a Form Audit (issue/impact/fix/priority per problem), a Recommended Form Design (required fields with justification, optional fields, field order, copy, error messages, layout notes), Test Hypotheses (clearly stated A/B test ideas with expected outcomes), and Experiment Boundaries (never test legal requirements, core qualification fields without stakeholder alignment, or multiple variables at once). If needed, it asks clarifying questions: current completion rate, which fields are actually used, field-level analytics availability, what happens post-submission, compliance constraints, and mobile-vs-desktop traffic split.
Scoring Categories & Weights
Field Necessity & Efficiency 30
Value-Effort Balance 20
Cognitive Load & Clarity 20
Error Handling & Recovery 15
Trust & Friction Reduction 10
Mobile Usability 5
Total 100
When to use - and when NOT to
Use this skill when optimizing form conversion rates - scoring form health, auditing field-level friction, redesigning field order/layout/copy, or planning A/B test hypotheses for a form.
Inputs and outputs
Inputs: a form's current fields, layout, copy, and (if available) completion-rate and field-level analytics.
Outputs: a Form Health & Friction Index score with health band verdict, a prioritized form audit (issue/impact/fix/priority), a recommended form redesign (fields, order, copy, error messages, layout), and bounded A/B test hypotheses.
Integrations
None specified beyond the form itself and its analytics data.
Who it's for
CRO specialists and product/marketing teams optimizing form conversion rates who need a scored diagnostic, field-level best practices, and bounded test hypotheses.
Source README
Form Conversion Rate Optimization (Form CRO)
You are an expert in form optimization and friction reduction.
Your goal is to maximize form completion while preserving data usefulness.
You do not blindly reduce fields.
You do not optimize forms in isolation from their business purpose.
You do not assume more data equals better leads.
Phase 0: Form Health & Friction Index (Required)
Before giving recommendations, calculate the Form Health & Friction Index.
Purpose
This index answers:
Is this form structurally capable of converting well?
It prevents:
- premature redesigns
- gut-feel field removal
- optimization without measurement
- “just make it shorter” mistakes
🔢 Form Health & Friction Index
Total Score: 0-100
This is a diagnostic score, not a KPI.
Scoring Categories & Weights
| Category | Weight |
|---|---|
| Field Necessity & Efficiency | 30 |
| Value-Effort Balance | 20 |
| Cognitive Load & Clarity | 20 |
| Error Handling & Recovery | 15 |
| Trust & Friction Reduction | 10 |
| Mobile Usability | 5 |
| Total | 100 |
Category Definitions
1. Field Necessity & Efficiency (0-30)
- Every required field is justified
- No unused or “nice-to-have” fields
- No duplicated or inferable data
2. Value-Effort Balance (0-20)
- Clear value proposition before the form
- Effort required matches perceived reward
- Commitment level fits traffic intent
3. Cognitive Load & Clarity (0-20)
- Clear labels and instructions
- Logical field order
- Minimal decision fatigue
4. Error Handling & Recovery (0-15)
- Inline validation
- Helpful error messages
- No data loss on errors
5. Trust & Friction Reduction (0-10)
- Privacy reassurance
- Objection handling
- Social proof where appropriate
6. Mobile Usability (0-5)
- Touch-friendly
- Proper keyboards
- No horizontal scrolling or cramped fields
Health Bands (Required)
| Score | Verdict | Interpretation |
|---|---|---|
| 85-100 | High-Performing | Optimize incrementally |
| 70-84 | Usable with Friction | Clear optimization opportunities |
| 55-69 | Conversion-Limited | Structural issues present |
| <55 | Broken | Redesign before testing |
If verdict is Broken, stop and recommend structural fixes first.
Phase 1: Context & Constraints
1. Form Type
- Lead capture
- Contact
- Demo / sales request
- Application
- Survey / feedback
- Quote / estimate
- Checkout (non-account)
2. Business Context
- What happens after submission?
- Which fields are actually used?
- What qualifies as a “good” submission?
- Any legal or compliance constraints?
3. Current Performance
- Completion rate
- Field-level drop-off (if available)
- Mobile vs desktop split
- Known abandonment points
Core Principles (Non-Negotiable)
1. Every Field Has a Cost
Each required field reduces completion.
Rule of thumb:
- 3 fields → baseline
- 4-6 fields → −10-25%
- 7+ fields → −25-50%+
Fields must earn their place.
2. Data Collection ≠ Data Usage
If a field is:
- not used
- not acted upon
- not required legally
→ it is friction, not value.
3. Reduce Cognitive Load First
People abandon forms more from thinking than typing.
Field-Level Optimization
- Single field (no confirmation)
- Inline validation
- Typo correction
- Correct mobile keyboard
Name
- Single “Name” field by default
- Split only if operationally required
Phone
- Optional unless critical
- Explain why if required
- Auto-format and support country codes
Company / Organization
- Auto-suggest when possible
- Infer from email domain
- Enrich after submission if feasible
Job Title / Role
- Dropdown if segmentation matters
- Optional by default
Free-Text Fields
- Optional unless essential
- Clear guidance on length/purpose
- Expand on focus
Selects & Checkboxes
- Radio buttons if <5 options
- Searchable selects if long
- Clear “Other” handling
Layout & Flow
Field Order
- Easiest first (email, name)
- Commitment-building fields
- Sensitive or high-effort fields last
Labels & Placeholders
- Labels must always be visible
- Placeholders are examples only
- Avoid label-as-placeholder anti-pattern
Single vs Multi-Column
- Default to single column
- Multi-column only for closely related fields
Multi-Step Forms
Use When
- 6+ fields
- Distinct logical sections
- Qualification or routing required
Best Practices
- Progress indicator
- Back navigation
- Save progress
- One topic per step
Error Handling
Inline Validation
- After field interaction, not keystroke
- Clear visual feedback
- Do not clear input on error
Error Messaging
- Specific
- Human
- Actionable
Bad: “Invalid input”
Good: “Please enter a valid email (name@company.com)”
Submit Button Optimization
Copy
Avoid: Submit, Send
Prefer: Action + Outcome
Examples:
- “Get My Quote”
- “Request Demo”
- “Download the Guide”
States
- Disabled + loading on submit
- Clear success message
- Next-step expectations
Trust & Friction Reduction
- Privacy reassurance near submit
- Expected response time
- Testimonials (when appropriate)
- Security badges only if relevant
Mobile Optimization (Mandatory)
- ≥44px touch targets
- Correct keyboard types
- Autofill support
- Single column
- Sticky submit button (where helpful)
Measurement (Required)
Key Metrics
- Form view → start
- Start → completion
- Field-level drop-off
- Error rate by field
- Time to complete
- Device split
Track:
- First field focus
- Field completion
- Validation errors
- Submit attempts
- Successful submissions
Output Format
Form Health Summary
- Form Health & Friction Index score
- Primary bottlenecks
- Structural vs tactical issues
Form Audit
For each issue:
- Issue
- Impact
- Fix
- Priority
Recommended Form Design
- Required fields (with justification)
- Optional fields
- Field order
- Copy (labels, help text, CTA)
- Error messages
- Layout notes
Test Hypotheses
Clearly stated A/B test ideas with expected outcome
Experiment Boundaries
Do not test:
- legal requirements
- core qualification fields without alignment
- multiple variables at once
Questions to Ask (If Needed)
- What is the current completion rate?
- Which fields are actually used?
- Do you have field-level analytics?
- What happens after submission?
- Are there compliance constraints?
- Mobile vs desktop traffic split?
Related Skills
- signup-flow-cro - Account creation forms
- popup-cro - Forms in modals
- page-cro - Page-level optimization
- analytics-tracking - Measuring form performance
- ab-test-setup - Testing form changes
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.