top of page

What a good lead capture looks like from the buyer's side

  • 5 days ago
  • 3 min read

Updated: 4 days ago

Introduction


Lead capture is usually designed backwards. The business lists everything it would like to know, arranges it into a form, and puts it on a page. Nobody asks whether a person who has just decided to make contact will actually complete it, or whether the information collected is needed at that moment or merely useful eventually.

Judged properly, a capture mechanism has two jobs that pull against each other: get as many interested people as possible to make contact, and produce enough information to respond well. Optimising only the first produces enquiries you cannot act on; optimising only the second produces very few enquiries. Good capture is the deliberate balance rather than the maximum of either.


1. What a good lead capture looks like is judged on completed enquiries, not fields


The measure to use.

Not how much information you gather per enquiry, but how many useful enquiries you receive. A shorter form producing three times the volume wins even if each one tells you less. The missing detail can be collected in a reply; the enquiry that never arrived cannot be recovered at all.


2. It asks only what is needed to respond


The scoping rule.

Anything you can find out in the first reply does not belong on the form. Name, contact method, and enough about the job to reply sensibly is usually the entire requirement. Address, budget and timescale are almost always better asked in the conversation than on the form.


3. It sets an expectation about what happens next


The reassurance.

When they will hear from you and how. This is a single sentence, it visibly reduces abandonment, and it is missing from most forms.


4. It offers more than one way to make contact


Meeting different preferences.

A form, a phone number, an email address, a messaging option. People differ substantially in what they will use, and offering only one route eliminates whoever dislikes it. Older buyers and urgent buyers both prefer a phone number; younger and quieter ones frequently avoid calling entirely.


5. It works on a phone, in a hurry


The practical requirement.

Most enquiries begin on a mobile, frequently in the evening. Anything requiring precision typing, zooming, or a desktop is losing a large share of its potential. Test it on an actual phone rather than on a narrowed browser window, because the two behave differently.


6. It confirms the message actually sent


The trust detail.

A visible confirmation, immediately. Without it a proportion of people assume it failed and either resubmit or go elsewhere, and you never learn either happened.


7. It captures where the enquiry came from


The data requirement.

Source, page, and how they found you. This is the field that makes every subsequent marketing decision possible and it is the one most often omitted.


8. It reaches a person who will act on it


The step beyond the form.

A named recipient, a monitored inbox, a defined response time. Capture that works perfectly and delivers to an unattended address is worse than none, because it looks like it worked.


9. It is tested regularly by the business itself


The maintenance.

Submit it monthly from a phone, on mobile data, and confirm it arrives and is replied to. Forms break silently, and the failure is invisible from the inside.

Be careful about collecting personal information you do not need. Data you hold has to be protected, retained appropriately and justified, and the obligations vary by jurisdiction — which is another reason to ask for less rather than more.


Conclusion


Balance volume against usefulness deliberately, and judge it on completed enquiries.

Ask only what you need to reply sensibly, state when they will hear back, offer several contact routes, make sure it works on a phone in poor conditions, confirm visibly that the message sent, capture the source of every enquiry, deliver it to a named person with a response time, and test the whole path yourself every month.


Related reading


 
 
 

Comments


bottom of page