How many fields does an inquiry form need before sales can quote?

A buyer types "please send price for 500 pcs" into a contact form late at night. The next morning a rep replies with a list of questions: which model, which country, when do you need it. The buyer answers two days later, or doesn't, and somewhere in between a competitor sent a number.

Making the form longer does not fix that, and neither does making it shorter. The useful question is narrower: which answers does a price depend on? Everything else can move into the reply.

Write the quote before you design the form

Get the person who actually quotes prices to produce three quotes for three recent inquiries, from scratch, without reopening the original email thread. Note every question they had to answer in order to reach a number. That list is your field list, and it is usually shorter than the form you already have.

It tends to come out as five items: what the item is, how many, where it ships, when it is needed, and an address that reaches a human. Everything else is comfort.

Give each candidate field a job

Question	Can the quote be produced without it?	First form?
Model or part number	No	Required
Quantity	No	Required
Delivery country and city	No — freight and tax move with it	Required
Rough timing	Sometimes	Dropdown, with an empty default
Working email address	No — there is nowhere to send the quote	Required
Company name	Only if you sell to companies exclusively	Required in B2B, optional otherwise
Contact name	No	Optional
Phone	No	Optional, never required
Free-text message	No	Optional, marked as optional
Budget	No — and asking too early costs the inquiry	Leave out
How did you hear about us	No	Leave out, or ask on the thank-you page
Tax or VAT number	No, that is an onboarding step	Leave out

The test for anything not on this list: if a blank answer would not stop the quote, it belongs in the reply, not on the form. Budget is the one field people insist on and buyers rarely answer honestly at first contact — if the number matters, ask after you have shown you understand the requirement.

Friction is rarely the field count

Six clean fields convert better than four bad ones. What kills inquiries:

A required phone number, on a form used by buyers in another country who do not want a call. A country dropdown with every territory in it, on a phone. A required company name when the buyer is an individual sourcing one sample. A field that only accepts uploads, which fail on mobile data and give no feedback when they do. Validation that clears the form on error. A blank thank-you page that does not say what happens next.

Every one of those is fixable without removing a question sales needs.

The form itself

Plain HTML, labels outside the inputs, input types that bring up the right keyboard on a phone:

<form action="/inquiry" method="post"> <label for="email">Work email</label> <input id="email" name="email" type="email" autocomplete="email" required> <label for="company">Company <span>(optional)</span></label> <input id="company" name="company" type="text" autocomplete="organization"> <label for="item">Model or part number</label> <input id="item" name="item" type="text" required> <label for="qty">Quantity</label> <input id="qty" name="qty" type="text" inputmode="numeric" autocomplete="off" required> <label for="dest">Delivery country and city</label> <input id="dest" name="dest" type="text" autocomplete="address-level2" required> <label for="when">When do you need it?</label> <select id="when" name="when"> <option value="">Not sure yet</option> <option value="2w">Within two weeks</option> <option value="1m">This month</option> <option value="1q">This quarter</option> </select> <label for="notes">Anything else <span>(optional)</span></label> <textarea id="notes" name="notes" rows="4"></textarea> <p class="hp" aria-hidden="true"> <label for="website">Website</label> <input id="website" name="website" type="text" tabindex="-1" autocomplete="off"> </p> <button type="submit">Get a quote</button> </form> <style> .hp { position: absolute; left: -9999px; } </style>

Notes on the choices. Quantity is type="text" with inputmode="numeric" rather than type="number", because number inputs change value on a scroll wheel and reject the way people write quantities. The timing dropdown has an empty first option so nobody is pushed into a false answer. The honeypot replaces a captcha: reject the submission server-side if website is not empty, and skip the whole puzzle that real buyers fail on a train.

If a file matters — a drawing, a bill of materials, a photo of a damaged part — ask for it in the confirmation, not on the form. By then the buyer has committed, and a link is easier than a failing upload widget.

Keep the form to one column on every screen size. Preserve what was typed when a validation error fires, and put the error next to the field that caused it.

Say what happens after submit

The thank-you page is part of the form. Two things belong on it: what you will send and when, and the one or two details that would speed it up if they have them to hand. "We reply within one working day with a price and lead time. If you have a drawing or a target price, send it to this address and we will include it."

That single paragraph removes most of the second round trip without adding a field.

Read the messages for a fortnight

The free-text box is a research tool. Read every message that arrives for two weeks and count how often the same question appears — "do you ship to X", "is this the same as model Y". Anything asked repeatedly is either a missing field, a missing explanation on the product page, or a shipping restriction nobody wrote down. Fix the page before you fix the form.

What to measure afterwards

The share of inquiries where the first reply could be the quote itself, with no clarifying email. And the share that reach your order system without anyone re-keying or chasing a missing detail. If both stay flat after trimming fields, the problem is upstream of the form — usually the product pages do not state what the buyer needs to know to describe their requirement.