Do not rebuild a website just because someone dislikes the platform. Start by identifying the actual problem. A confusing menu, outdated content or an oversized image may call for a focused repair rather than a new website.
The right decision depends on what is working, what needs to change and the limits of the current setup. A clear diagnosis should come before the sales pitch.
Write down the friction
Walk through the website as a customer. Can you find the service, read comfortably on a phone and complete the main action? Record the specific places where that journey becomes difficult.
Separate usability concerns from technical problems and content gaps. Request measurements where performance is the concern. Do not assume every site on a platform performs the same way.
Improve what already has a sound foundation
A focused update is worth considering when the structure and platform still suit the business. That could mean replacing confusing copy, reorganising products, simplifying navigation or reviewing an enquiry form.
Ask for a small, prioritised scope and a way to check the result. Preserve pages and content that are already useful rather than discarding them simply to make the project feel new.
Rebuild when the requirements have genuinely changed
A fresh build may be justified when the business needs a substantially different customer journey, catalogue or integration setup. Make the case in terms of those requirements rather than a promise that a new platform fixes everything.
Plan the move carefully. Inventory the existing content, account access and important URLs. Agree redirects, testing and handover responsibilities before launch. A considered migration protects the useful parts of the old website while making room for the next version.