For many years, building websites was the main part of my work. Businesses would come to me saying they needed a new one, and I would usually begin by asking why.
That question often stopped them in their tracks. It seemed an odd thing for a web developer to ask, rather like walking into a car showroom and being asked whether you really needed a new car. It was still the right question.
If a website has previously worked well for the business, there should be a clear reason why it now needs replacing. The business may have changed, the market may have moved on, search behaviour may be different, or demand may have fallen. None of those automatically means the website itself has failed.
A website can certainly become outdated, ineffective or technically unviable, but it doesn’t suddenly stop being good without something changing. Before committing a substantial amount of money to a rebuild, it is worth finding out what that change was.
Why do you think you need a new website?
The usual answers are easy to recognise. For instance, the website looks dated, enquiries have fallen, or traffic isn’t what it used to be. Staff might find it awkward to update, or the business no longer feels well represented by what appears online. All of those concerns are valid, but they point towards different problems and potentially very different solutions.
I have websites still running today that are close to twenty years old and continue to serve their businesses well. That doesn’t mean the original software has been left untouched for two decades, or that every old website deserves preserving. It does show that age alone tells you very little about commercial effectiveness. When I mention this to a client who has assumed that an older-looking website must be the reason for falling enquiries, it can create a genuine light-bulb moment. A good website does not become commercially useless simply because current design fashions have moved on.
The important question is what needs to happen to regain performance.
Sometimes there is a clear answer. In other cases, a proposed rebuild is little more than a reaction to a visible symptom, with no evidence that replacing the website will solve the underlying problem.
When rebuilding makes commercial sense
There are several perfectly good reasons to replace a website. The most obvious is obsolete technology, where an old platform may be difficult to secure, expensive to maintain or dependent on software that is no longer supported. In theory, almost anything can be repaired or upgraded, but for a smaller business, untangling years of outdated themes, plugins, and custom code may cost more than replacing them with a clean, supported system. It's important to remember that technical possibility is not the same as commercial viability.
A website may also have stopped representing the business accurately. A brochure site is, in many ways, a record of what the company offered when the content was written. Businesses evolve, services change, and priorities shift. A website built around the old business may eventually become a poor fit for the new one. That may call for a complete rebuild, although it may equally require new content, a different structure or a redesigned public-facing site while retaining useful technology behind it.
There are also occasions when the owners simply want something new. A rebrand, a change of management or a new marketing direction may create a perfectly legitimate desire to replace the current site. No business has to wait until its website collapses before commissioning another one. The distinction is that choice should not be confused with evidence of failure. A business may decide that a fresh start is worth the cost, provided it understands what it is buying and what it expects to gain.
Whatever is driving the project, the business should be able to explain what the new website will do better than the one it replaces.
Poor performance needs investigating
When a client tells me the website is no longer converting, or that traffic has fallen, my first response is still to ask why.
The answer may well relate to the website, but it might not, and we should investigate rather than assume.
A website may present an unclear proposition, the navigation may be confusing, or an important call to action may be difficult to find on a mobile phone. Those are genuine website problems, although a redesign would be a radical choice for some.
There are other possibilities. Demand may have changed, or a service that once attracted steady interest may no longer have the same market. Search engines may present results differently, reducing the number of visits even where visibility remains strong. Competitors may have improved, customer expectations may have changed, or the business may be targeting the wrong audience. Replacing the website will not restore demand that no longer exists. Nor will a new design necessarily reverse a fall in clicks caused by changes in search behaviour.
Before spending money, the business needs to investigate what has happened. That may involve reviewing analytics, search data, enquiries, conversion patterns, customer questions and changes in the market. A business with the right skills may be able to do this internally. Where the cause remains unclear, it is sensible to pay someone to investigate it.
The scale of that work should reflect the size of the decision. Nobody needs a six-month research programme before changing a few pages, but a substantial rebuild deserves more than an assumption that the existing site looks tired.
Once you understand the cause of the poor performance, you can decide whether to tune what you have, replace part of it or start again.
Keep the parts that still work
Businesses sometimes treat a website as though it were one indivisible object. In practice, the parts customers see, and the systems the business relies on behind them, can have very different lifespans.
A booking platform, ecommerce system or customer database may contain years of useful optimisations, data and integrations. Replacing all of that because the design needs refreshing could be unnecessarily expensive and introduce risks that have nothing to do with the original problem.
The weakness may be in the visible website. The navigation could be improved, the customer journey simplified, or the main calls to action made clearer. A key button may be too far down the page on a mobile device. Those changes could have a meaningful effect without disturbing the systems that already do their job. If the required improvements can be made cleanly and economically on the existing platform, preserving it will often be the better commercial decision.
There are limits. A platform that once suited a small business may become awkward as the company grows. A simple website may struggle when it is expected to manage a large product catalogue, regular publishing, bookings or connections to other systems. Staff may be unable to make routine changes without paying a developer, and every new requirement may involve another workaround. At that point, the problem is no longer confined to what customers see; the technology itself is holding the business back.
There is no universal formula for deciding when another round of improvement becomes false economy. It depends on the condition of the website, what the business needs, and how long the proposed improvements will extend the site's life.
A modest investment may be excellent value if it solves the problem and leaves the site easier to manage for several more years. The same amount would be difficult to justify if it merely keeps an unsuitable platform alive until the next change is required.
The judgement comes down to what the business will be left with when the work is finished.
Two schools, two very different decisions
I have worked with two independent schools that illustrate the point well.
The first had a basic website created internally. It was a DIY job that no longer reflected the standing of a fee-paying school, and the organisation came to me with clear objectives for a new site, including updated branding and better content management. A rebuild was reasonable; in fact, it was essential if the established goals were to be met. Even then, the original plans were scaled back after we discussed the amount of staff time required to manage a more ambitious website. The final result was less complex than the first specification, but it represented the school well and remained practical for the people expected to run it.
The second school already had a sophisticated platform built specifically for education. It supported useful services for pupils, parents and teachers, but the public-facing website needed updating. In that case, replacing the whole system would have made little sense. We refreshed the design, improved the structure and updated the framework while retaining the specialist platform behind it. The school received a much better website without discarding systems that were already doing a valuable job.
A later change in management led to a different decision. The specialist platform was replaced with a conventional WordPress website, and several of the connected services were lost or moved into separate third-party systems. The school spent many thousands of pounds on the replacement and continued paying substantial annual maintenance costs, despite making little use of WordPress as a content management system. Several years later, the organisation came back to me looking for a way to reconnect the learning platform it had previously used and reduce its dependence on expensive maintenance.
By then, another complete rebuild was difficult to recommend. Too much money had already been spent, and the governors were understandably reluctant to approve another major website project. The pragmatic answer was to retain the usable parts of the WordPress site, restore the specialist learning system where possible and find a more cost-effective maintenance arrangement.
The best solution at that stage was not the one I would have chosen with a blank sheet of paper. It was the one that made commercial sense from the position the school had been left in. The lesson was not that WordPress was unsuitable or that an older system should always be retained. The mistake was replacing useful functionality without establishing what the new website needed to improve and what the organisation would lose in the process.
Decide what needs fixing before approaching suppliers
A business considering a new website should begin by thinking carefully about what it is asking for.
If performance has fallen, establish why. If the technology is becoming expensive or insecure, work out whether it remains worth preserving. If the business has changed, identify which parts of the content, structure and design no longer reflect it. Where the answer is unclear, engage someone who can help investigate it before asking suppliers to price the solution.
Until you understand the problem and what the replacement needs to achieve, you cannot prepare a useful brief. Each supplier will be left to interpret the requirement, and each may define a different project based on the services and technology it provides. A rebuild may ultimately prove to be the right answer. It may be overdue, and a clean start may offer better value than continuing to repair a website that no longer suits the business.
The investigation may also show that a focused redesign, revised content or a relatively modest improvement will solve the problem without replacing everything.
A business is ready to commission a new website when it can explain what's actually changed and what the replacement is expected to improve.