By Mehdi HassanHow many fields should a landing page form have?
A landing page form should have as few fields as your follow-up process actually needs, which for most B2B lead forms is three or four. There's no magic number, because the right count depends on the offer. A newsletter needs one field. A demo request for an enterprise product might reasonably need five.
The better question is not "how many" but "which". Each field is a small cost to the visitor and should buy something for you. The form is the second half of your call to action, as our call to action guide explains: the button makes a promise and the form either keeps it or breaks it.
What rule decides which form fields to keep?
Keep a form field only if its answer changes who follows up, how quickly, or with what. If sales would send the same email to every lead regardless of the answer, the field isn't routing anything, and it's costing you completions for data you could gather later.
List every field on the current form
Include hidden fields and the consent checkbox. Write each one down with the reason someone gave for adding it.
Ask what each answer changes
For each field, ask sales or whoever follows up what they do differently based on the answer. Be specific: a different person, a different speed, a different email.
Cut the fields that change nothing
If the answer is "nothing, but it's nice to know", remove it or move it to the thank-you page, onboarding or the first call.
Check what enrichment can fill
A work email domain often gives you company name, size and industry through enrichment tools or your CRM, so you don't need to ask.
Make the rest easy
For the fields that survive, choose the simplest input: a dropdown or radio buttons instead of free text, optional instead of required where possible.
Which form fields should you keep or cut?
Most lead form fields fall into three groups: fields that route the lead and should stay, fields that enrichment or a later step can replace, and fields that rarely help. Here's how the common ones usually come out for a B2B landing page form.
Field | Usual decision | Why |
|---|---|---|
Work email | Keep | Needed to follow up, and the domain tells you the company |
Name | Keep (or first name only) | Makes follow-up personal and costs little |
Company name | Usually cut | Inferred from the email domain in most cases |
Company size | Keep if it routes leads | Often decides sales-led vs self-serve follow-up |
Role or job title | Keep if it changes the message | A developer and a CFO need different first emails |
Phone number | Optional or cut | Frequently faked; only required if you really call first |
Website | Cut | Duplicates the email domain |
Budget | Usually cut on first contact | Visitors guess or leave; ask on the call instead |
How did you hear about us | Optional, last | Useful attribution, but never required |
Message | Optional | Valuable when filled, but required free text deters people |
The table is a default, not a law. If your sales team routes enterprise leads to a different person based on company size, keep it and make it a quick radio choice. If nothing is routed, cut it.
Do fewer form fields always increase conversions?
Fewer form fields usually increase the number of submissions, but not always the number of good leads. Removing a qualifying field can flood sales with leads they can't help, which looks like a win in the form report and a loss in the pipeline. Measure what happens after the form, not just the form completion rate.
The offer also changes the maths. A visitor requesting a custom proposal expects to answer questions, and a form that asks nothing can feel unserious. A visitor downloading a checklist expects to give an email and nothing more. Match the effort of the form to the value of what's behind it, and explain any field that isn't obvious with a short helper line. Our guide to conversion microcopy has examples of those lines.
Hypothetical example: cutting a demo form from eight fields to four
For example, suppose a SaaS demo form asks for first name, last name, work email, phone, company, company size, job title and a message. Sales says it only uses company size to choose between two reps, and calls nobody.
The new form asks for name, work email, company size as four radio options, and an optional message. Phone is gone, company comes from the email domain, and job title moves to the scheduler that appears after submission. The team then tracks both form completions and how many leads become meetings, to check the shorter form isn't just producing more unqualified leads. This illustrates the method; it isn't a measured result.
What are lead form best practices for field design?
Lead form best practices for field design are about making each remaining field quick and error-free: clear labels, the right input type, helpful errors and visible progress. A short form with bad field design can lose more people than a longer, well-designed one.
- Labels above fields. Placeholder text that disappears when typing starts forces people to remember what the field was.
- The right input type. Email and phone fields should bring up the matching keyboard on phones.
- Autocomplete on. Let the browser fill name, email and company where it can.
- One column. Two-column forms make people zigzag and skip fields.
- Inline errors. Show the problem next to the field, in plain words, and keep what the visitor already typed.
- Forgiving formats. Accept phone numbers with or without spaces and country codes.
- A specific button. "Book my demo" rather than "Submit". See our CTA button text examples.
Free work email checks deserve care. Blocking personal email addresses can protect sales time, but it also blocks founders and freelancers who use them. Decide based on who you actually sell to, and if you block, say why in the error message.
Should a long form be split into steps?
A long form can be split into steps when every field is genuinely needed and the first step is easy. Starting with a low-effort question builds momentum, and asking for contact details last means the visitor has already invested something. Splitting a form that should simply be shorter only hides the problem.
Be sceptical of the big numbers quoted for multi-step forms. Our research traced the most-shared "86%" and "300%" lift claims to misattributed or unsourced figures rather than controlled studies. Our comparison of multi-step vs single-step forms explains when each format fits, and our guide to form design for web apps covers validation and smart defaults in more depth.
How do you know whether your form is costing you leads?
You know your form is costing you leads when many visitors start it and few finish, or when recordings show people stopping at the same field. Track form starts and form submits as separate events, so you can tell a page problem (nobody starts) from a form problem (people start and leave).
Our guide to landing page conversion tracking shows how to set those events up in GA4. Once they're in place, compare your rate against your own history rather than chasing an external figure, and use our landing page audit checklist to check the rest of the page around the form. Then follow the lead past the form: the thank-you page is where a submission turns into a meeting.
