The enquiry path
Turning visits into enquiries — after finding out where they are actually being lost.
Yes, this is the work you came looking for: finding why visits are not becoming enquiries, and fixing it. The reason the page starts with diagnosis rather than a list of tactics is that in at least two of the four places demand gets lost, changing the page is the wrong intervention — and doing it anyway is how a quarter gets spent with nothing to show.
It is not a separate service here. It is the second half of one outcome, and the number we answer for is enquiries you can act on, not a conversion rate.
What this work is usually brought in to do
A site receives visits and produces few enquiries, and somebody has been asked to improve the conversion rate. The brief is usually already a solution: redesign the page, shorten the form, move the button.
Sometimes that is right. Often the loss is somewhere else entirely, and the page was never the problem.
Working out which of the four it isIf you do not yet know where the loss is, that page is the honest place to start, and it costs nothing.The four places demand gets lost
Two of the four are not the page.
What the work involves
Diagnosis first.
What the traffic actually is and what intent it arrived with. Whether the page answers that intent. Whether the enquiry path can physically complete — on a phone, on a slow connection, with a real submission that we confirm arrives. Whether anything is being recorded at all.
Then the fixes that follow from it.
In the order the evidence supports. Message and offer where the page is not answering the visit. Form and booking friction where the path is losing people. Delivery and notification where enquiries are being sent and not received. Instrumentation where the loss is invisible.
Built, not just recommended.
The enquiry path includes the form, the booking surface, what happens after submission, and the measurement. A recommendations deck that stops at the design is where most of this work fails.
Measured against a starting point captured first.
Without a baseline there is no before, and no honest way to describe an after.
What we can test, and what we cannot
Below a real threshold, a test cannot reach significance.
Statistically valid A/B testing needs a volume of traffic and conversions most businesses in this market do not have. Running a test anyway produces a decision dressed as evidence.
So there are two different activities and we name them differently. Below the threshold:research, diagnosis, a change, and an observation afterwards — described exactly that way, with no uplift figure attached. Above the threshold: a real test, with the significance reported.
We do not publish conversion benchmarks, industry averages or typical uplifts. None exists in our evidence base and inventing one would be the same failure this page exists to correct.
We also have no before-and-after of our own to show you. We have no analytics history yet, which means we cannot present a pre/post comparison — and saying so is more useful to you than a chart nobody can audit.
We ran this on ourselves first
Our own contact form transmitted nothing, while showing visitors a success message.
We ran this diagnostic on our own site before offering it to anyone. Every enquiry that form received was lost, and no analytics existed to make that visible.
It is the reason the order of work on this page starts where it does. Nothing about that failure would have been found by looking at the design, the copy or the traffic — and no amount of page improvement would have fixed it.
Related: the whole system this sits inside · the method, including what cannot be attributed.
Start with what you can currently see
What arrives, what converts, what you can measure.
If the honest answer is that you are not sure anything is being recorded, that is the most common starting point and the fastest thing to establish.