The Lead Form Question That Matters

A lead form on a small business website is a tiny conversation.

Someone has read enough of the page to want a reply. They are about to spend two minutes filling something in. Whether you can help them is largely decided by what you ask, in what order, and how it lands when the reply lands in your inbox.

Most service-business forms get this wrong by asking too much, in the wrong order, and learning the wrong thing.

The form should help you reply

It is easy to write a form for the business. Sales wants a budget band. Marketing wants the source. Operations wants the company size. Someone added a dropdown for service area in 2022 and nobody has touched it since.

By the time a buyer arrives, the form is built around what the company wants to know about them, not what the company needs in order to reply usefully.

The test is simple. Look at every field on your form and ask whether the answer would change the reply. If the answer is "no, but it is nice to have", the field is making the visitor pay for your reporting habit.

The GOV.UK design system puts this plainly. Only ask for information you actually need. Mark optional fields as optional. Do not punish people for not filling in something that should not have been required in the first place.

Ask what the customer needs help with

For most service businesses, the single most useful field is not the budget, the company size, the lead source, or the timeline.

It is one open box that asks what they are trying to get done, or what is not working.

Worded carefully, that question does several jobs at once. It tells you whether the buyer is in your line of work or somebody else's. It tells you whether they have a clear problem or a vague worry. It tells you whether they have a deadline. It often tells you the rough size of the work without ever asking about money. And it gives you something to react to in the first reply, instead of opening with "thanks for getting in touch, could we get on a call?"

That single answer is usually the difference between a generic reply and one that makes the buyer feel met.

If your form already has that field but it sits underneath nine others, almost no one is filling it in well. The buyer has spent their patience working out which budget band to lie about.

Common fields create noise

A few patterns turn good prospects into thin enquiries.

Required budget pickers make small jobs feel awkward and big jobs feel exposed. Many buyers either pick the lowest band, skip if they can, or close the tab. The information you get back is mostly noise.

Required phone numbers cost more enquiries than they save. Some buyers will not give a phone number on a first form. Some will give a wrong one. The buyers who genuinely want a call will tell you.

Long service dropdowns force the buyer to map their work onto your taxonomy before you have spoken. If they pick the wrong category, your reply starts in the wrong place. If they cannot find a category that fits, they leave.

"How did you hear about us?" is a research question, not a buying one. It belongs in a follow-up email or a quiet analytics field, not in the sequence that decides whether a stranger keeps typing.

None of these are forbidden. They just have to earn their place. Baymard's research on checkout flows is a good sanity check even outside ecommerce. The average checkout has more than eleven fields, and field count is the strongest driver of abandonment they measure. A lead form is not a checkout, but the visitor is even less committed, and every extra field is paid for in attention.

A short form usually works better

A useful service-business lead form often comes down to four things.

A name, so the reply has somewhere to land. An email, so the reply can land. The single context question. And a short, plain submit button that names the next action, not the verb "submit".

That is usually enough to write a reply that respects the visitor's time, qualifies the work gently, and either books a conversation, sends something useful, or makes a polite "we are probably not the right fit for this" easy to write.

Anything beyond that should be optional and labelled optional. If you genuinely need a phone number for some kinds of work, ask after a real conversation, not in the doorway.

Complex enquiries need more detail

This is not a universal rule.

A high-volume ecommerce form, a recruitment form, a regulated service, or a workflow that has to route to a specific team will need more structure. The point is not "ask less". It is "ask for the things that change what you do next, and stop asking for the rest".

It is also not a substitute for a clear page above the form. If the visitor arrives unsure what you do or who you do it for, no field design will save the enquiry. The form sits on top of the rest of the website. It cannot do the website's job for it.

Check whether every field changes the reply

If you only do one thing this week, count the fields on your main lead form, then read each one and ask whether the answer would change your first reply.

Anything that would not change the reply, drop or make optional. Anything that is missing because nobody bothered, add. Then write one open question that gives the visitor permission to tell you what is going on.

We watch our own form for this. The enquiries that turn into work almost always come from people who could finish a single sentence about what was not working. The ones that do not, mostly could not finish that sentence anywhere else either, and a longer form would not have helped.

A lead form is not a sales tool. It is the first half of a conversation. The website is working when the form gives you enough to start the second half well.