Answer
What questions should you ask on an enquiry form?
Only what changes what you do next. Every other field is a reason for someone to leave.
Only the fields that change your next action. Contact route, what they need, where they are, and when. Anything you would ask in the first conversation anyway belongs in that conversation, not on the form.
Enquiry forms grow the way most business artefacts grow: somebody wishes they had known something, a field is added, and nothing is ever removed. The result is a form that asks a stranger for a set of details assembled from years of individual frustrations, most of which do not change what happens next and none of which the stranger has any reason to provide.
The test for each field is narrow and worth applying literally. Does the answer change what you do in the next hour? If it changes who responds, how urgently, or whether you can help at all, it earns its place. If it is something you would establish in the first thirty seconds of a conversation anyway, it belongs in that conversation, where the person is already engaged and answering costs them nothing.
On most forms that leaves four things. A way to reach them, and their preferred route. A short description of what they need, in their own words rather than as a category. Where they are, if you have a service area. And when they need it, which is usually the single most useful field because it separates the urgent from the exploratory and lets a small team allocate attention honestly.
The free-text description does more work than the structured alternatives and is frequently replaced by a dropdown, which is a downgrade. A category tells you which bucket the enquiry falls in; a sentence in the customer's own words tells you what they actually think their problem is, how urgent it feels, and often the detail that determines whether the job is straightforward. Categories exist for the business's convenience and cost the information that made the enquiry useful.
Budget is the field most often added and the one most likely to do harm. Asked on a form, before any trust exists, it reads as a filter designed to sort people rather than help them, and the honest answers you receive are worth less than the enquiries you lose asking. It is a reasonable question once a conversation is running and there is a reason for it — a genuine scope choice, a range to place them in — but as a field on a first form it costs more than it returns.
One thing worth adding rather than removing is a statement of what happens next. A single line saying when they will hear back and from whom converts the form from a void into a commitment. It also sets the expectation you then have to meet, which is uncomfortable and is precisely why it works: a business that publishes a response promise on its form usually starts keeping one.
Every field on an enquiry form is a small negotiation with someone who has not yet decided you are worth the trouble, and most businesses hold that negotiation over data they never read.
Answer Production Engine, Context Theory
Related questions
Should the form ask how they found us?
Only if you cannot get it another way, and usually you can. Self-reported attribution is unreliable — people misremember, choose the most recent touch, or pick whichever option sounds right — and it costs a field. Where source really matters, tracking on the channel gives a better answer for free, and asking during the first conversation gets a fuller one when they are already talking.
Do required fields help or hurt?
Each required field is a point at which someone can abandon, so require only what makes a response possible: a way to reach them and enough to know what they want. Making everything required to improve data quality reliably improves the quality of a smaller set of enquiries, which is the wrong trade for almost every small business.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Firms that never responded to a web enquiry at all | 23% | Category-wide |
| Share of the buying journey completed before contacting a vendor | 60% | Category-wide |
| Teams responding to an inbound lead within 5 minutes | 7% | Category-wide |
Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads", Harvard Business Review (March 2011) · 1.25M inbound leads across 2,241 US firms · verified
2026 B2B buyer surveys · verified
2026 speed-to-lead benchmark · range ~5% FinTech to ~15% RevOps · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Workflow | A form field earns its place only if the answer changes what the business does within the next hour — who responds, how urgently, or whether it can help at all — and anything establishable in the first thirty seconds of a conversation fails that test. | Each existing field, checked against whether any past enquiry was routed or prioritised differently because of its value. |
| Buying behaviour | A free-text description in the customer's own words carries urgency, framing and the detail that determines complexity, all of which a category dropdown discards in exchange for the business's convenience. | Comparing a sample of free-text enquiry descriptions against the category each would have been assigned. |
| Buying behaviour | A budget field on a first-contact form reads as a sorting filter before any trust exists, so the enquiries lost to it outweigh the value of the answers given by those who complete it. | Form completion rates measured with and without the budget field over comparable periods. |
| Workflow | Stating on the form when the enquirer will hear back and from whom converts submission into a commitment the business must meet, which is why publishing it tends to produce the behaviour it describes. | The business's own response times before and after a response promise was added to the form. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one