The forms we redesigned and why form UX is the last mile that kills conversions

Forms are where many conversion optimisation efforts stop. The campaign gets attention, the landing page gets a redesign, the button text gets A/B tested. Then the form sits there, asking for seven fields when three would do, with error messages that trigger before the user finishes typing and a submit button that does not change state so they have no idea if it worked.

We redesigned forms on three different client sites in the first half of 2024. All three had the same basic pattern: too many fields, poor error handling, no progress indication on longer forms, and a confirmation experience that felt like an afterthought. All three saw meaningful conversion rate improvement after the redesign. The numbers were different but the direction was consistent.

The field count question

The single most impactful change in each case was reducing the number of required fields. The instinct to collect more information is understandable. The sales team wants to know the budget before they call. The marketing team wants to segment by company size. The founder wants to know how the person heard about them. But each additional required field is a small act of friction that compounds with every other field. A form that takes ninety seconds to complete converts at a fraction of one that takes thirty.

Our rule is that the form should only ask for what is genuinely needed to complete the next step in the sales process. Everything else can be gathered in the first conversation. For most service enquiries, that means name, phone number, and one field about what they need help with. That is it.

Error handling and feedback states

The second problem was error handling. Most forms we inherited showed inline validation errors the moment you left a field, regardless of whether the field was complete or not. Clicking into an email field and immediately out triggered an error before the user had typed anything. That is bad feedback design: it creates a sense of failure before any action has been taken.

We changed the trigger logic to validate on form submission, not on blur. If someone submits with an empty field, they see the error clearly. If they are mid-entry, they do not. This small change reduced form abandonment measurably in the sessions we tracked.

The other standard we enforced was explicit confirmation: after submission, the user sees a message that is specific about what happens next. Not "thank you for submitting." Something like "we will call you within one business day." Specificity reduces the anxiety of not knowing if the form worked, and it sets an expectation that the business then needs to meet.

Forms are the end of a long conversion journey. Treating them as an afterthought wastes everything that came before.