Choose B2B enquiry fields around the first decision your team needs to make. Balance useful qualification with a manageable initial contact experience.
A B2B enquiry form should not attempt to conduct the entire discovery meeting on one screen. Too little information can lead to poor routing; too many required fields can make the task unnecessarily difficult. The right set depends on the decision that follows submission. Ask what the team will actually do with each requested detail.
Define the first assessment
Describe what happens after submission: routing to a service team, checking suitability, arranging a conversation or preparing a quote for a standard product. Those actions need different inputs. If project requirements will be clarified through discovery, requiring a complete technical specification at first contact may be inappropriate.
Review information sales repeatedly requests after recent enquiries. Which details are essential immediately and which belong in the next conversation? A frequently asked question should not automatically become required. The person may not know the answer yet; an “uncertain” option can produce a more truthful record for some project fields.
Choose fields by the job they perform
Separate the information needed to reply from details needed to understand the project. Before requiring two contact methods, establish why both are necessary. Check whether company size or budget ranges are genuinely used for initial routing rather than collected by habit.
W3C's form-instructions guidance addresses explaining what information and format are expected. A short example may help more than a long instruction, but it should not steer the person into describing a need they do not have.
| Field group | When useful | Detail that may come later |
|---|---|---|
| Contact | To respond to the request | Billing address and additional stakeholders |
| Need or service | To reach the appropriate team | Detailed implementation specification |
| Current situation | To understand the starting point | Technical access to every system |
| Timing | To identify a real constraint | A final project schedule |
| Brief description | To capture context outside the options | Complete discovery notes |
Leave room for a need that is not yet defined
Consider a hypothetical manufacturer seeking more suitable website enquiries without knowing whether it needs SEO, a redesign or advertising. A form that requires a specialist-service selection can encourage the wrong answer. A business-need option and brief explanation can provide a more useful starting point.
This does not mean converting the entire form into free text. Combine a limited set of routing options with room for uncertainty. If attachments are accepted, explain what is useful and whether uploading is optional. Avoid requesting sensitive documents unnecessarily at the first contact.
Design what happens after the form
The success message should explain what the person can expect. Do not promise a response time the business does not operate. Verify that fields reach the relevant team correctly, the selected service is preserved and the person is not immediately asked to repeat the same details.
Evaluate field changes through record quality as well as submission volume. Which missing details delay the process, and which collected fields remain unused? Use real sales feedback to refine the form. A shorter first interaction can still be more informative when each question serves a clear purpose.