Your website is an operations problem

The handover nobody designs

Most website projects end at the form. The enquiry arrives in an inbox, and what happens next is left to whoever notices it. That gap is where the money goes: leads that sat overnight, duplicate follow-ups, and the enquiry that was answered twice because two people saw it.

The website is the front of an operation. If the operation behind it is undefined, a better website produces more of the same problem, faster.

Questions worth answering before design starts

Who owns an enquiry once it arrives, by name? What is the target time to first response, and who notices when it slips? Where does the record live so that the second conversation does not start from nothing? What happens to enquiries that arrive at nine on a Friday night?

These are not technical questions and they change the design. A form that captures three fields makes sense if a person calls back within the hour. A form that captures twelve makes sense if the first reply is a written proposal two days later.

Make the site do the routing

Enquiries can be classified as they arrive, routed to the right person, written to the CRM, and acknowledged immediately with something more useful than a thank-you page. None of that is exotic, and all of it is cheaper than hiring someone to watch an inbox.

Where volume is high or arrives out of hours, a voice or chat agent can qualify before a person sees it, so the queue a human works through is shorter and better prepared.

Then the marketing has somewhere to land

Search visibility and paid traffic are worth buying once the operation behind the form is defined. Bought before that, they mostly increase the number of people who conclude you did not reply.