The short answer

Ask for the fewest fields needed to deliver the promised next step and follow up responsibly. For a simple email resource, that may be email only. For a qualified service estimate, five to eight well-chosen questions may save both people a pointless call.

Give every field a job

Beside each requested item, write what you will do with it now. Remove “future segmentation” fields nobody uses. Do not ask for a phone number if you plan to email. Do not mark optional fields as required because the software makes it easy.

Separate the form into three levels:

• Necessary now: information required to fulfill or respond.
• Helpful but optional: information that improves the response.
• Later: details better collected after trust or booking.

Sensitive information needs an especially strong reason and appropriate security. Privacy and data-collection rules vary, so check the requirements that apply to your visitors and obtain qualified guidance when needed.

Improve the experience before cutting fields blindly

Use visible labels, explain unusual formats, show which fields are required, and write errors that tell the person how to fix the problem. W3C’s forms tutorial recommends associated labels, clear instructions, validation, and confirmation of successful submission (W3C forms tutorial). Its detailed instructions guidance says to identify required and optional inputs and explain unusual formats (W3C form-instructions guide). Placeholder text alone is not a dependable label.

For a longer application, group related questions and show progress. Save answers when appropriate so a temporary error does not erase ten minutes of work. Explain why you request anything that might feel surprising.

Test lead quality as well as completion

Compare form starts, completions, qualified leads, booked calls, sales, and support problems. Removing a project-budget question may increase submissions while wasting hours on impossible fits. Adding one clear qualifying question can lower raw conversion and improve the business result.

Watch a few consenting users complete the form and ask where they hesitated. Fix confusing copy before assuming the number of fields is the only problem.

Sources and further reading

• W3C Web Accessibility Initiative: Forms Tutorial
• W3C: Form Instructions

A free next step

You don't have to build this alone

Bring your questions, share what you're working on, and meet other women building businesses from home. It is free to join.

Join Our Community Free

Helpful WAHMN tool

Use the Landing Page Wireframe to ask only for the information needed at this step and move later questions to later.

Related Questions

• What should a professional website handoff include so the client can take over safely?
• When should a landing page remove the navigation menu, and when should it keep it?
• What should I A/B test first on a landing page when traffic is limited?
• How fast does a landing page need to load, and what should I fix first if it is slow?

Related WAHMN resource

If you want to turn this website task into a service or build a stronger process for your own site, this system walks through the work in more depth. See Website & Landing Page Build System.