There is a neat digital marketing line that says businesses do not want websites, they want more customers.
Sometimes that is true. But my experience building websites for local businesses taught me that it is too simple.
I had clients who absolutely wanted more enquiries. I also had clients who already had enough work. They were not trying to fill an empty diary. They wanted a website because not having one was beginning to look odd.
That distinction taught me something that has stayed with me ever since: before deciding how a website should work, you need to understand what job the business actually needs it to do.
For some businesses, the website was proof
When I was building websites for local businesses around Felixstowe and Suffolk, simply having a proper presence online still meant something.
A potential customer might hear about a company through somebody else, see a van, pick up a leaflet or already know the name. The website was not necessarily responsible for creating that demand. It was where the person went afterwards to check that the business looked legitimate.
They wanted to see the services offered, contact details, perhaps some examples of work and enough information to feel comfortable making the next move.
In that situation, judging the website only by how much new traffic it generated would miss its real purpose. The site was supporting a decision that had already started somewhere else.
Some businesses genuinely did want more work
Of course, other clients wanted exactly what the marketing textbooks say they wanted: more enquiries, more calls and more customers.
For those businesses, search visibility mattered differently. Being found for the right local search could put them in front of somebody who was actively looking for what they sold.
That was where SEO became commercially useful. It was not about sprinkling keywords across a page for the sake of saying it had been optimised. It was about making sure that somebody looking for the service could find the business and quickly understand what to do next.
The difference between those two types of client mattered.
One website might primarily need to reassure people who already knew the company. Another might need to create demand from search. Another might need to do both.
The website was not automatically the finished product
This was probably one of the earliest versions of an idea I still come back to now: the website itself is rarely the objective.
A business does not become successful because it owns five pages of HTML. The website is part of a wider system.
Sometimes it generates an enquiry. Sometimes it answers a question before the customer phones. Sometimes it gives somebody confidence that the business is genuine. Sometimes it simply gives the company somewhere credible to send people.
That is why I eventually wrote The Website Was Never Really the Finished Product. The value is in what the website enables, not in the existence of the website itself.
SEO could have the same problem
The same mistake happened with SEO. Once rankings became measurable, it was tempting to treat the ranking itself as the result.
Number one for a phrase looked impressive. More traffic looked impressive. But neither mattered very much if the business did not need that traffic, or if the people arriving were not the right people.
Paid search later made that even clearer to me because every click had a cost. It forced me to think much more carefully about intent and about what happened after somebody arrived.
That eventually became a much stronger way of looking at websites generally. Instead of asking, "How much traffic can this get?" the better question was, "What does this visitor need, and what does the business need them to do next?"
It still affects the way I build things now
I am no longer interested in building websites simply because a project needs "a website". I am much more interested in the system around it.
With my own projects, that can mean content, data, automation, analytics, payments, affiliate links, internal tools and whatever else is needed to make the thing actually work.
Control Room is a good example. The public-facing site is only one part of what I am building. A lot of the value is in everything behind it: the data, the connections between projects and the ability to understand what is happening without manually jumping between systems.
That thinking started much earlier than Control Room. Building local-business websites taught me that the same-looking product can be doing very different jobs for different people.
Sometimes "we need a website" really did mean exactly that
Looking back, I think that is the part that gets lost when early web design is retold through a modern marketing lens.
Not every local business was desperately chasing growth. Some were busy enough already. They simply understood that customers were starting to expect them to exist online.
The website gave them a place in that new world.
For other businesses it became a direct source of customers. For many it sat somewhere between the two.
The lesson for me was not that businesses secretly wanted SEO, leads or conversion funnels. It was that the technology only made sense once I understood what the business actually wanted it to achieve.
