Ask for information needed to respond and route the enquiry. The right field count depends on what the team must decide before the first conversation. There is no ideal number for every B2B form.
Write the purpose of each question. If no answer changes assignment, response or estimating, consider asking later.
Which fields belong at first contact?
| Field | When it helps | Alternative to consider |
|---|---|---|
| Reply to the request | Phone if the visitor prefers a call | |
| Company | Understand the business context | Ask later if routing does not need it |
| Type of need | Route to the right person | Short choices including “other” |
| Description | Understand a non-standard project | Example answer and a manageable field |
| Budget | Identify a real mismatch | Ranges and “to be defined” |
| Timing | Prioritise or check availability | Approximate period |
A short version asking for contact and need can be a starting point. A technical quotation may need more. Explain why the information is necessary.
Do not automatically reject personal email addresses. Sole traders and directors may use them. Require a phone number only when the service needs a call and you explain that.
One page or several steps?
A single page often suits a few questions. Several steps can make a long quote form more readable, especially with conditional questions.
Show progress, allow going back and retain answers during the journey. Test branches so “other” never leads to an impossible question.
Splitting a form may add clicks or hide its length. Compare submissions and resulting opportunities on your traffic rather than assuming abandonment improves.
If you save data before final submission, define and explain that processing. Abandoning a form does not, by itself, authorise a marketing sequence. Visitors should know when information is transmitted.
Which defects should you fix before removing questions?
Test on a phone: email keyboard, autofill, visible button and understandable errors. An invalid field should not erase other answers.
Use visible field labels. Text only inside an input disappears during typing. The W3C forms guidance covers labels, instructions and error feedback, including for screen-reader users.
Verify actual sending, confirmation and receipt. A short form losing enquiries needs correction before a debate over an additional qualification field.
What can you ask later?
The first call can establish role, timing or constraints. If the system recognises an existing contact, avoid repeated questions while allowing changed information to be corrected.
Lead scoring helps identify what is missing for a decision. Keep the journey simple instead of gating every resource to complete a record.
How do you measure an improvement?
Track visits, form starts, successful submissions and opportunities within the same scope. Record errors and steps without copying personal field contents into analytics.
For illustration, a variant can raise enquiries from twenty to thirty while opportunities fall from eight to six. Submissions improve but the commercial outcome worsens. Examine quality and refusal reasons before rollout.
With little traffic, fix observed defects and monitor without attributing all variation to the form. For the wider journey, read the CRO guide. Website work can begin with this form and the enquiries it receives.
