Almost every business we speak to describes its digital problem as a website problem. The site is old, or slow, or it does not bring enquiries. Sometimes that is genuinely the issue. More often the website is the only part of the digital business anyone has ever looked at, so it gets blamed for everything.

It helps to be precise about what a website actually is. It is the place where an interested stranger decides whether to become a customer. That is a real and important job. It is also a narrow one.

The shopfront and the shop

A physical shop has a window, and it has everything behind the window: stock, a till, a stockroom, a record of who ordered what, someone who knows which supplier to call. Nobody would open a shop with an excellent window and no stockroom. In digital, we do it constantly.

A website with no system behind it produces enquiries that arrive as emails, get answered by whoever sees them first, and are never recorded anywhere. That is not a marketing failure. The marketing worked. The business could not receive what the marketing delivered.

The click is only the beginning. Your business still has to receive, process and manage what happens next.

Where projects actually break

In our experience the failure is almost never inside a single system. It is at the handover between two of them. A few that recur:

  • A booking taken on the website that the front desk does not see until someone checks an inbox.
  • An enquiry form that emails one person, who is on leave.
  • A marketplace order that does not reduce the stock figure the shop is working from.
  • A customer who has bought four times and is still treated as new, because each purchase happened in a different system.
  • A campaign that clearly produced revenue, which nobody can prove, because the analytics counted visits and the revenue lives in the accounting software.

Every one of those is a gap between two working systems. You can rebuild the website five times and not fix any of them.

A more useful way to look at it

Instead of asking "is our website good?", ask what happens to one customer from beginning to end. Can they find you. Do they trust what they see. Can they act easily. Does your business receive that properly. Do your systems agree with each other afterwards. Do they come back. Do you know which of these is working.

The website is involved in about two of those seven. That is not an argument for caring less about it — a bad website will sink you at step three regardless. It is an argument for knowing which of the seven is actually your problem before spending money on the one everyone talks about.

What this means in practice

It usually means the first thing worth doing is not a rebuild. It is mapping. Once you can see where enquiries actually go and where information gets carried by hand, the priority list tends to write itself — and it is rarely the list you started with.

Sometimes the answer genuinely is a new website. But it is a much better new website when it is designed knowing what has to happen after someone clicks.