form-cro

Form CRO Optimization

Skill Overview

Optimizes non-registration forms (such as lead capture, contact, demo requests, quote, and survey forms) by evaluating form health, reducing friction points, and improving field design to increase form completion rates and lead quality.

Use Cases

1. Lead Capture & Contact Forms

When your contact form or lead capture form converts below expectations, this skill can assess form health, identify redundant fields and friction points, and provide optimization recommendations. It is suitable for B2B companies, SaaS businesses, and any organization that relies on forms to generate leads.

2. Demo Request & Quote Forms

Demo request and quote forms typically require more information, but each additional field reduces completion rate. This skill helps balance data collection needs with user experience by designing multi-step flows and optimizing field order and submit button copy.

3. Survey & Feedback Forms

Survey participation is often low and friction is more pronounced. This skill provides cognitive load management, improved error handling, and mobile adaptation recommendations to help increase survey completion rates and data quality.

Core Features

1. Form Health & Friction Index Assessment

Before offering any optimization suggestions, it calculates a diagnostic index from 0–100. It evaluates the form across six dimensions: field necessity, value-effort balance, cognitive load, error handling, trust signals, and mobile usability. Based on the score, it determines whether the form needs incremental improvements, structural changes, or a complete redesign.

2. Field-Level Optimization Recommendations

Provides best practices for common field types (email, name, phone, company, etc.), such as whether an email field should be confirmed, whether a name field should be split, whether the phone field is required, and how to infer company information. Each recommendation includes clear rationale rather than blindly removing fields.

3. Layout, Flow, and Mobile Optimization

Covers field ordering strategies, single-column vs multi-column layout choices, multi-step form design principles, best practices for error messaging, and mobile form requirements (touch target sizes, keyboard types, and support for autofill). Ensures the form can be completed smoothly across different devices.

FAQs

How is this skill different from signup-flow-cro (Registration Flow CRO)?

Form CRO focuses on non-registration forms such as lead capture, contact, demo requests, quote, and survey forms. Registration Flow CRO specifically addresses account creation and user registration flows. Their optimization goals differ: Form CRO targets lead quality and completion rate, while Registration Flow CRO focuses on activation and successful user onboarding.

How many fields should a form have?

There is no fixed standard, but every required field tends to reduce completion rate. General guidance: 3 fields as a baseline; 4–6 fields may reduce completion rate by 10–25%; 7+ fields may lead to 25–50%+ drop-off. More importantly, ensure each field has a clear business purpose and is used in real workflows.

How can I tell if my form needs optimization?

Use the skill’s “Form Health & Friction Index” assessment. Scores of 85–100 indicate high performance and support incremental optimization. Scores of 70–84 indicate opportunities to reduce friction. Scores of 55–69 indicate structural problems. Scores below 55 suggest a redesign. If field-level analysis data is missing, the skill provides a list of key metrics that should be collected.

Can the skill directly modify my form code?

No. The skill provides optimization recommendations, best practices, and testing hypotheses, but it does not write code. It is recommended that you or your development team run A/B tests to validate improvements based on the assessment results.

What types of forms does it support?

It works for any non-account-registration forms: lead capture, contact pages, demo/sales requests, application forms, survey/feedback, quote/estimation, and checkout forms (non-account-creation scenarios). It does not apply to user registration and account creation flows.