The form is where all your marketing spend either converts or evaporates. Traffic, targeting, copy, design, all of it funnels into a box that asks for information, and most of those boxes ask for far more than the business will actually use.
The test we run in every audit is simple: for each field on the form, ask what the business does with that answer before the first phone call. Most fields fail it.
The field audit
Print your form. Next to each field write one of three answers: 'used to route the enquiry', 'used to qualify before calling', or 'nobody looks at this until later'. Everything in the third category is costing you enquiries for no benefit, because you can ask it on the call.
Traffic arriving but not enquiring?
We'll review your form field by field and tell you exactly what to cut.
Get a free form reviewCommon fields that fail this test: company name (you'll learn it on the call), postal address (you'll get it when you book), how did you hear about us (your analytics already knows, better than the customer does), preferred contact time (guessed, then ignored), and long free-text 'tell us about your project' boxes that people abandon halfway through.
The minimum viable form
For most service businesses: name, one contact method, and one qualifying question. Three fields.
Name, because the follow-up call needs it and it's zero friction. One contact method, phone for phone-driven businesses, email for considered purchases with longer cycles. Asking for both when you'll only use one adds a field for no benefit.
The one qualifying question should be the single thing that changes how you handle the enquiry: suburb, service type, property type, budget band, or timeframe. Choose the one that routes the lead. Not all five.
When more fields are justified
Two situations. First, when your sales capacity is the constraint rather than your lead volume: if you can only handle eight quotes a week and you're getting thirty enquiries, adding qualification is a deliberate filter and the lost volume is a feature.
Second, for high-value considered purchases where the person expects to give detail. Someone enquiring about a $60,000 renovation is not surprised to answer six questions. Someone enquiring about a blocked drain is.
The rule: add friction on purpose, never by accident.
Optional fields still cost you
A field marked 'optional' still gets read, still gets considered, and still adds perceived length. If a field is genuinely optional, the honest question is why it's there at all. Either it matters enough to ask, or it should be removed.
The exception is a second contact method offered after the primary one, positioned as a convenience rather than a request.
The mobile details that quietly lose enquiries
Most of your form traffic is on a phone, and most forms are designed on a desktop.
Input types. A phone field should trigger the numeric keypad (`type="tel"`), an email field the email keyboard with the @ symbol (`type="email"`). Getting this wrong forces the visitor to switch keyboards manually, and some of them won't.
Autocomplete attributes. Setting `autocomplete="name"`, `"email"`, and `"tel"` lets the browser fill the form in one tap. This is the single cheapest completion improvement available and it's missing from most forms we audit.
Tap targets. Inputs and the submit button need to be at least 44 pixels tall. Cramped desktop-sized fields are hard to hit accurately on a phone and produce mis-taps that read as abandonment.
Label position. Labels above fields, not inside them as placeholder text. Placeholder-only labels disappear the moment someone starts typing, so anyone who hesitates has lost the question.
Keyboard overlap. On a phone the keyboard covers the bottom 40% of the screen. If the submit button sits there, the visitor has to dismiss the keyboard to find it. Test this on a real device.
Validation that helps rather than scolds
Validate on blur, not on every keystroke, so people aren't told their email is invalid while they're still typing it. Show errors next to the field, not in a summary at the top. Preserve what the person already entered when validation fails, because clearing a form on error is the fastest way to lose someone who was nearly finished.
Be generous with phone number formats. A form that rejects '0412 345 678' because of the spaces, or rejects '+61 412 345 678', is rejecting customers. Strip whitespace and formatting characters server-side instead.
Spam without punishing customers
Reasonable forms get bot submissions. The instinct is to add a CAPTCHA, which taxes every genuine visitor to stop a problem they didn't cause.
A honeypot field is better for most sites: an input hidden off-screen and excluded from the tab order, which humans never see and bots reliably fill. If it's completed, discard the submission silently. It costs nothing in friction and stops the majority of automated spam.
If a honeypot isn't enough, a time-based check (submissions completed in under two seconds are almost certainly automated) adds another layer without any visible interface. Reserve visible challenges for forms that are genuinely under attack.
The button
'Submit' describes what the form does for you. Describe what the visitor gets instead: 'Get my free quote', 'Book my consultation', 'Send my enquiry'. Small change, consistently measurable.
Underneath the button, one line that removes the last hesitation: what happens next and how fast. 'We'll call you back within one business hour' does more work than any trust badge.
What happens after submission
Never leave the person on the same page with a small green message. Send them to a dedicated thank you page that confirms what happens next, gives a timeframe, and offers something to do in the meantime.
That page is also where your conversion tracking should fire, which makes it a measurement asset as well as a reassurance one.
Measuring form performance properly
Two numbers. Form view to form start (did anyone begin?) and form start to submission (did they finish?). A low start rate means the form isn't compelling or isn't visible. A low completion rate means the fields are the problem.
If completion is low, add field-level tracking to see which field people abandon on. It's almost always the same one, and it's almost always the one nobody reads the answer to.
Related service: Landing Page Development, Custom landing pages laser-focused on converting visitors into leads.