form-cro

Reduce the number of fields, since each added field lowers completion, and start with easy fields like name and email before sensitive ones. Use visible labels, inline validation, a specific CTA button like "Get My Free Quote", and trust signals such as a privacy statement near the form.

Three fields is the baseline; 4-6 fields typically reduce completion by 10-25%, and 7 or more can cut it by 25-50% or more. For gated content, email-only or email plus name is often enough, with enrichment handled after submission.

Use multi-step when a form has more than 5-6 fields, logically distinct sections, or conditional paths, such as applications and quote requests. Include a progress indicator, start with easy questions, allow back navigation, and save progress so data is not lost.

Make phone optional when possible, since required sensitive fields increase abandonment. If it is required, explain why, auto-format input as the user types, and consider offering a preferred contact method choice instead.

Track form start rate, completion rate, field-level drop-off, error rate by field, time to complete, and mobile versus desktop splits. Field-level analytics reveal exactly which questions cause users to leave.

No, it explicitly excludes signup and registration flows, which are handled by the signup-flow-cro skill. Forms embedded in popups or modals are covered by the popup-cro skill instead.