Start with the business problem and technical foundation. If the site is stable and the problems are targeted, maintenance may be enough; if the platform repeatedly blocks the business or makes changes expensive, a rebuild may make more sense.
Not every website problem requires a new website.
A site can look old, feel difficult to manage or have a collection of technical problems without automatically needing to be rebuilt. The right decision starts with understanding what is actually wrong.
1. Look at the business problem first
Is the website failing to generate enquiries, difficult for the team to update, technically unstable or simply visually dated? Different problems require different solutions.
2. Check the technical foundation
Review the hosting, CMS, code, integrations, forms, analytics, SSL, backups and domain configuration. A clean technical foundation may make targeted maintenance the sensible route.
3. Identify what is expensive to keep fixing
If small changes repeatedly cause new problems, important integrations are unsupported, or the existing platform prevents the business from moving forward, a rebuild may make more sense.
4. Compare the two paths before deciding
Write down what maintenance would cost and what it would achieve. Then compare that with the scope, migration work and ongoing ownership requirements of a rebuild. The goal is not a newer website for its own sake; it is a technology setup that the business can actually operate.