When a website becomes frustrating to work with, a rebuild can look like the clean solution. New design, new platform, no history. Sometimes that is exactly right. Often the frustration comes from something smaller: nobody owns the site, changes are hard to make, or one broken part colours the whole picture.
A rebuild costs time, money and attention, and it brings its own risks. Before committing, it is worth checking whether the website you have can be maintained and improved instead.
Separate the problem from the platform.
Write down what is actually wrong. “The site is old” is not specific enough. Useful answers look like this:
- We can’t add a new service page without a developer.
- The contact form sometimes doesn’t arrive.
- It is slow on mobile.
- Nobody knows how it was built or who can change it.
- It no longer reflects what we sell.
Some of these are platform problems. Many are maintenance, content or ownership problems that a new website would inherit unless they are addressed separately.
Four questions a review should answer.
- Can it be accessed? Does the business control the accounts, and can a developer get appropriate access to the platform or code?
- Can it be changed safely? Is there a way to test a change and reverse it if needed?
- Can it be kept current? Are the platform, extensions or dependencies still supported, and is updating them realistic?
- Can it do what the business needs next? Given the plans for the next year or two, can the current setup be extended without fighting it?
If the answers are mostly yes, maintenance and gradual improvement are usually the better investment.
Three outcomes, not two.
The choice is rarely “keep everything” or “start again”. A review usually lands on one of three outcomes:
- Maintain and improve. The setup is sound. Ongoing care plus a development allowance covers what the business needs.
- Repair, then maintain. There are specific problems — outdated components, a broken integration, no recovery route — that need a defined, one-off repair before regular care makes sense.
- Replace part or all of it. The platform can’t be accessed, kept current or extended in the way the business needs. Then a rebuild, or replacing a section, is justified.
What about AI-built websites?
A website made with an AI tool is not automatically disposable, and it is not automatically fine either. The same four questions apply. Look at where the project lives, whether you can export it or connect your own domain, and whether someone other than the original author can make changes safely.
If the answers are good, keep it and give it an owner. If they aren’t, a review will show whether the fix is a handover, a repair or a move to something more maintainable.
Get a second opinion before you commit.
A short review of the current setup costs far less than a rebuild, and it makes the rebuild better if you still need one. Tell us about your website and what isn’t working. We’ll tell you honestly which of the three outcomes looks most likely.
