Inquiry forms: why fewer fields bring more inquiries

Why every field costs something

A form is a negotiation. On one side is what the company would like to know. On the other is how much effort someone is willing to put in who isn't even sure yet whether they want to work with you.

This willingness is limited and drops with every field. Three types are especially costly: the phone number, because it signals a call nobody wants. Company size as a dropdown, because it smells like pre-screening. And the budget field, because it demands an answer the person inquiring doesn't know yet themselves.

That doesn't mean you can never ask for these fields. It means each of them has a price you should pay consciously, not out of habit, because the form has looked like this for five years.

The test that shows everything

A form is a negotiation. On one side is what the company would like to know. On the other is how much effort someone is willing to put in who isn't even sure yet whether they want to work with you.

This willingness is limited and drops with every field. Three types are especially costly: the phone number, because it signals a call nobody wants. Company size as a dropdown, because it smells like pre-screening. And the budget field, because it demands an answer the person inquiring doesn't know yet themselves.

That doesn't mean you can never ask for these fields. It means each of them has a price you should pay consciously, not out of habit, because the form has looked like this for five years.

The shortest form that makes sense

For a project inquiry, four fields are enough.

Name. One field, not two. Splitting it into first and last name serves the database, not the user.

Email. The only technically required field.

Company. Short, optional, helps with context before calling back.

Message. The actual field. Everything that matters goes in here, if the question above it is well phrased.

The phone number can stay optional. People who want to be called will enter it; that is also a signal about urgency.

Everything else (industry, timeframe, budget, preferred date) belongs in the initial consultation, not in the form. A conversation clarifies in three minutes what a form needs five fields for and still produces misunderstandings.

The question above the message field

This is the biggest underestimated lever. Most forms label the text field Your message. The result is inquiries like: Please call me back.

If you ask a concrete question instead, you get concrete answers. For example: What is the task, and what should be different at the end compared to today? Or: Briefly describe your project and what you have tried so far.

Three to four lines of placeholder text cost nothing and change the quality of incoming inquiries far more than any dropdown. The reason: a dropdown forces the person inquiring into a category they might choose wrongly. An open question lets them describe the problem in their own words, and that is the information that really helps in the initial consultation.

The form becomes shorter and delivers more.

The technical reasons for drop-offs

Four points cause drop-offs nobody notices, because they leave no trace.

Validation only after submitting. Someone who finds out after clicking that three fields are wrong and loses their text in the process doesn't come back. Validation has to happen when leaving the field, not at the end.

Error messages without a solution. Invalid input says nothing. Please use the format name@firma.de says everything.

No state after clicking. If the submit button stays unchanged after the click, people click again, or they assume it didn't work.

No confirmation page. A message that disappears after two seconds is not a conversion. A dedicated page with a thank you, processing time and a sensible next step creates trust, and it is the prerequisite for measuring conversions at all.

On smartphones, there is a fifth point: the keyboard. An email field should open the email keyboard, a phone field the number pad. That is one line of code and saves every user several seconds of frustration.

Data protection without friction

Consent is mandatory, how you handle it is a design question.

A pre-ticked box is not permitted. A checkbox with four lines of legal text in front of it is permitted, but it slows people down. The practical way is one sentence below the submit button that says in plain language what happens, with a link to the privacy policy.

The wording matters. Your data will only be used to process your inquiry and will not be passed on is a sentence that removes concerns. A reference to Art. 6(1)(a) GDPR is a sentence that raises them.

For questions about the specific setup in an individual case, it is worth consulting a specialist lawyer. This article is not legal advice.

What you should measure

Without measurement, every change is opinion. Three values are enough.

Form views to submissions. How many people see the form, how many submit it? Below five percent points to a problem, above fifteen is good.

Drop-offs per field. Where do people stop? Most analytics tools can capture this. A field where an above-average number of people stop is the first candidate for cutting.

Quality of inquiries. How many of the incoming inquiries lead to a conversation? That is the only value that really counts. A shorter form that brings twice as many but worse inquiries is not progress.

Changes should be made one at a time. If you change three things at once, you won't know afterwards which one worked.