Start with a short diagnosis
Write down what is getting in the way. Is the site difficult to use, unreliable, slow to update or simply out of date? Separate problems with the content and design from problems with the underlying platform.
Look for improvements with a clear purpose
A focused update can be enough when the platform is sound. Clearer service pages, better project examples, a simpler menu or a repaired enquiry form may solve the immediate problem.
Recognise when the foundation is the issue
A rebuild becomes more useful when the current setup cannot support the business, creates repeated maintenance problems or makes essential changes disproportionately difficult. Compare the cost of continued repair with the cost of a planned replacement.
Treat migration as part of the project
Record existing URLs, content and important integrations. Identify email and domain dependencies. Build and test the replacement separately, then plan redirects and the live handover.
Agree how success will be assessed
Choose practical checks: whether enquiries reach the right place, pages explain the services clearly, staff can manage content and key journeys work on mobile. Set up measurement where appropriate, with suitable privacy controls.
Compare the same scope, not just the headline price
Ask what each option includes: design, copy, page templates, product data, integrations, testing, redirects and ongoing costs. A cheap rebuild can become expensive if it leaves out the content migration or the tools your team relies on. A large repair can also be poor value if the underlying system still cannot support your plans.
Choose a focused improvement when the problem is specific
If people cannot understand your services, a clearer heading and better service pages may be a more useful first step than a new platform. If enquiries are failing, repair the form and delivery process first. If the site feels slow, measure the bottleneck before assuming the whole website needs replacing. The smallest useful change is sometimes the right one.
Keep domain and email decisions separate
A website move does not automatically require a domain transfer or new email provider. Confirm registrar access, DNS records and the current email setup before making changes. Keep a record of the old configuration and a way to reverse the website change if the new site has a serious problem. Never cancel the old hosting until its remaining dependencies are understood.
Agree the handover before the work starts
Ask who supplies the content, who approves the design, how changes are handled and who manages the website after launch. Clarify access to accounts, any recurring licence costs and the practical process for updates. Write down what a completed project means so both sides can make decisions against the same brief.
Your practical checklist
- List the problems you need to solve.
- Separate content and design issues from platform limits.
- Compare repair and rebuild against the same brief.
- Record important URLs, integrations, domain and email dependencies.
- Agree approval, migration and rollback arrangements.
- Include maintenance and ownership in the handover.