What makes a form work
| Element | Do this | Avoid this |
|---|---|---|
| Length | Ask only for what the first call needs | Asking for budget, address and referral source up front |
| Labels | Visible labels above each field | Gray hint text inside the field as the only label |
| Layout | One column, in a natural order | Fields side by side that scramble on phones |
| Errors | Specific messages next to the field | One red line at the top that says "Error" |
| Button | Words that say what happens, like Get a Quote | A button that just says Submit |
Nielsen Norman Group's form research backs each row. It recommends cutting fields you can collect later and keeping labels visible above fields. It also asks for error messages that are specific and easy to see. WCAG requires labels or instructions for every input, which also helps screen reader users.
Match the form to the page
A pest control quote form needs a name, phone, ZIP code and the pest. A law firm consultation form needs more privacy reassurance. A landing page for paid ads should stay shortest of all, because every extra field wastes ad spend.
Good example. A pest control form asks for name, phone, ZIP code and pest issue. The button says "Request a Pest Control Quote," and a line explains when someone will call back.
Bad example. The same page asks for full address, square footage, budget and three required dropdowns, then shows a hard puzzle before sending.
Test it before traffic hits it
- Fill the form on an iPhone and an Android phone.
- Check that it reaches the right inbox or CRM.
- Confirm the thank-you message says what happens next.
- Track submissions as key events in GA4.
Our forms send leads straight into Smarfle or your own CRM, with spam blocked by Cloudflare Turnstile instead of a puzzle. Our web design team builds and tests every form on real phones.