A website is not a strategy

At some point, most leadership teams have a version of the same conversation.

The website is not good enough. It does not reflect the organisation. Enquiries are low. Clients cannot find what they need. Something needs to change.

The conclusion is often the same: commission a new website.

Sometimes that is the right call. Often, it is not. Because the website is not the problem. It is where the problem has become visible.

The brief that reveals the problem

When organisations sit down to brief a website project, a pattern tends to emerge.

The brief describes symptoms: outdated design, poor mobile experience, not enough enquiries. But when you ask what should replace it, clarity drops quickly.

Who owns the content? What happens after a user makes an enquiry? How is the site maintained once it is live?

When a brief cannot answer these questions, the new website usually inherits the same problems as the old one. Better design. Same confusion underneath.

What it usually reflects

A website does not exist in isolation. It reflects the organisation that built and maintains it.

Ownership without clarity

Content is owned collectively, which means no one owns it. Pages go stale. No one has agreed what the site is for, who should write for it, or when it gets reviewed. This is not a technology problem. It is an operating problem.

Services without shape

Organisations grow and their offer becomes more complex. The website tries to describe everything and explains nothing well. Users cannot tell whether the organisation does the specific thing they need, or what happens after they make contact.

Systems without connection

The enquiry form submits to an inbox. No one is quite sure what happens next. Client data lives in several places simultaneously. As search visibility research consistently shows, organisations invest in driving traffic to experiences that cannot convert it, because the operational layer behind the website has not been thought through.

What good looks like

The organisations with strong digital performance are not necessarily the ones who spent the most. They are the ones who sorted out the things the website depends on.

Named ownership

Someone is responsible. Not a committee. A named person with the authority to make decisions about content, structure, and priorities. Content is reviewed regularly and reflects what the organisation actually does.

Content that works for users

The content answers the questions users actually have, not the questions the organisation wishes they had. Every page has a purpose. The route from finding the organisation to making contact is short and obvious.

Connected systems

Enquiries go somewhere reliable. Client information is held in one place. The people managing relationships have visibility of what has happened. The Salesforce State of the Connected Customer report has noted repeatedly that customers expect organisations to present as one connected entity. When data is fragmented across systems, that experience becomes difficult to deliver regardless of how the website looks.

This is not about complex technology. It is about having a clear operating layer that connects the digital front of the organisation to the people and processes behind it.

Where to start

Before briefing an agency, it is worth understanding why the current site is not working. Three questions usually surface the real issues quickly.

• Who owns the website, and what does that ownership actually include?
• What happens when a user makes an enquiry today?
• What would need to be true for the site to work well in twelve months?

The answers tend to reveal whether the problem is the website or the organisation behind it. Often, the honest answer is both. Knowing which is which changes what you should do first.

A new website built on the same unclear foundations will, within eighteen months, look much like the one it replaced.

It may not be a website problem at all. It may be a clarity problem.