Form optimisation to lift conversions, and the fields that quietly cost you leads.

The short answer. Every field is a small tax on conversion.

Form optimisation is the work of removing friction from the point where a visitor becomes a lead: how many fields there are, what order they're in, what type of input each one uses, and what happens the moment someone makes a mistake filling it in. It's a narrower discipline than general conversion rate optimisation, which covers a whole page. Form optimisation is specifically about the last few centimetres of that page, the box a visitor actually has to fill in and click submit.

The research on field count is unusually consistent. HubSpot's analysis of tens of thousands of customer landing pages found forms with three fields convert at roughly 25 percent, the highest rate observed, and that each additional field beyond that costs an average of 4.1 percent of conversion. At the extremes, forms with seven fields or fewer converted at 34 percent, more than double the 15 percent rate of forms with ten fields or more. None of this means every form should have three fields. It means every field beyond the minimum needs to earn its place, because each one is a small, measurable tax on how many visitors actually complete the form.

Forms matter more than their small footprint on a page suggests, because they sit at the exact point where every other piece of conversion work either pays off or doesn't. A page can have a strong headline, credible proof points and a clear offer, and still under-convert if the form asking someone to act on all of that is longer or clumsier than it needs to be. It's the last few seconds of a visit, and it's disproportionately where marketing spend, SEO effort and page design either turn into a lead or quietly evaporate. That's also why form optimisation is one of the highest-return, lowest-effort projects available to a founder-led team: unlike a page redesign, it rarely needs new copy, new design or new budget, just an honest audit of what's actually being asked for.

Step by step. An audit you can run in an afternoon.

You don't need a redesign to improve a form. Most of the gain comes from a short audit against the fields already on the page.

1. Audit every field against a 48-hour test. List every field and who inside the business actually acts on that field's data within 48 hours of a submission. If nobody does, it's a strong candidate for removal, whatever the original reason for adding it was.
2. Cut or make optional the fields that failed the test. Removed fields don't have to disappear from the business entirely, they can move to a post-submission enrichment step instead of sitting on the form itself.
3. Reorder what remains, easiest to hardest. Name and email first, harder or more sensitive questions like budget or company size later. A visitor who's already answered two easy questions is more likely to finish a third than one facing the hard question first.
4. Match field type to how people actually type. Email and telephone input types, plus autocomplete attributes, switch mobile keyboards automatically and let browsers autofill known details, which matters more than it sounds given how much form traffic now arrives on a phone.
5. Replace open text with select or toggle fields where the answer set is small. A dropdown or radio group is faster to complete than free text for something like company size or industry, but avoid multi-select dropdowns specifically, which research on form interaction shows cost more conversion than a single-select equivalent.
6. Add one trust signal near the submit button. A specific line, no spam, a callback within a working day, does more than a block of legal text nobody reads before clicking away.
7. Test one variable at a time. Change field count, field order, or button copy separately, not together, so a lift or a drop in the numbers actually tells you which change caused it.

Most of this audit takes an hour, not a project cycle. The step that actually takes discipline is the first one, being honest about which fields nobody acts on, because it usually means having a short conversation with whoever owns the data downstream, sales, customer success, whoever picks up the submission, rather than assuming you already know. Fields have a habit of surviving long after the reason they were added has gone: a field requested for a campaign that ended a year ago, or a "nice to have" nobody ever formally signed off on removing. The audit is as much a conversation as a technical task.

A worked example. Nine fields to four, and what it changed.

A worked example, illustrative rather than a named client: a UK B2B software company's demo-request form asked for nine fields, name, work email, phone, company, job title, company size, budget, message and "how did you hear about us." Running the audit above found only three of those nine fields were actually used by the sales team within 48 hours of a submission arriving: name, work email and company. The rest sat in the CRM unused for days, sometimes weeks, if they were looked at at all.

The form was cut to four fields: name, work email, company, and a single required dropdown asking which problem the visitor most wanted to solve, which doubled as the qualification data sales actually used to prioritise a callback. Phone number moved to the confirmation page as an optional add for visitors who wanted a faster response. Submission volume roughly doubled within the following month, broadly in line with what the field-count research above would predict for a form of that length, and sales reported the qualifying dropdown gave them a clearer prioritisation signal than the old budget and company-size fields ever had, because visitors answered a direct question about their problem more honestly than they'd have estimated a budget figure.

My rule on this: don't ask a visitor for anything you can find out another way. A work email domain tells you company size and industry more reliably than a self-reported dropdown does, and it costs the visitor nothing to give you. Reserve the fields you actually make someone type for the one or two things you genuinely cannot get any other way.

The part of this example worth stressing is that qualification didn't disappear when six fields did, it moved to a better question. Asking someone their budget upfront produces guarded, often inaccurate answers from people who haven't yet decided whether they trust you. Asking what problem they want to solve gets a more honest answer because it isn't a number they feel exposed giving away, and it's more directly useful to a rep preparing for the first call than a self-reported budget figure would have been anyway.

Common mistakes. Where a form optimisation project quietly fails.

The first is cutting fields the sales team genuinely needs without replacing what they were for. If a budget field gets removed because it hurts conversion, but nothing replaces the qualification it provided, the problem hasn't gone away, it's just moved downstream to a call where a rep now has to ask the same question live, later in the process and at greater cost.

The second is treating a multi-step form as a substitute for cutting fields rather than a complement to it. Splitting a ten-field form into three short steps can genuinely lift completion by making the first step feel low-commitment, but a ten-field form is still a ten-field form under the hood. Cut the fields first; use steps to make what's left feel lighter, not to disguise a form that's still too long.

The third is leaving field types unmatched to how people actually type. A phone field without the tel input type, or a form with no autocomplete attributes, forces a mobile visitor to type everything manually on a small keyboard designed for text, not numbers or email addresses. This is one of the cheapest fixes available and one of the most commonly skipped.

The fourth is validating only on full submission rather than inline, field by field. A visitor who fills in every field correctly except one, then gets a single generic error message after clicking submit, has to hunt for the mistake themselves. Inline validation flags the problem field the moment it's clear there's an issue, before frustration has a chance to build.

The fifth, and the one that undoes the others, is changing several things about the form at once and drawing conclusions from a single before-and-after comparison. If field count, order and button copy all changed in the same release, a lift in conversion tells you the combination worked, not which part of it did, which means the next form redesign starts from guesswork again instead of from an accumulating, tested body of evidence.

A sixth is running the audit once and treating it as finished. Fields creep back in the same way they crept in the first time, a new stakeholder wants one more data point, a campaign needs a tracking question added "just for a few weeks" and never gets removed. Put a form audit on the same recurring calendar as any other conversion review, roughly every two quarters, rather than a one-off clean-up that quietly unravels over the following year.