Improve the current website when it can support the change you need and someone can maintain it safely. Consider a rebuild when a specific constraint prevents that. The age of the design, on its own, does not settle the decision.
Start with the job your visitor cannot complete. A failed booking, an unclear service page and a slow product search need different investigations. This guide gives you a way to compare the options before requesting a quote.
Describe the problem before the solution
Write one sentence about the problem, then collect evidence. “Customers on a phone cannot finish the booking” is useful. Include the affected page, device, steps and what should have happened. “The website needs to be modern” gives a developer little to test.
For content and navigation problems, watch someone try the task without coaching them. For failures, save the error message and reproduction steps. For speed, measure the affected journey on representative devices. A single performance score cannot explain every delay.
Compare three possible scopes
A feature or fix
Use a focused change when the problem is bounded: a broken form, an inaccessible menu, a missing filter or a checkout validation error. Check whether the existing platform supports the change, who can deploy it and what adjacent behaviour could break.
A redesign on the existing platform
Consider new layouts, navigation and copy when people cannot find or understand the offer, but the underlying system is maintainable. A redesigned service page can keep the same address, content tools and integrations. Agree which of those parts stay before treating the work as visual.
A rebuild or platform move
Ask for evidence of the blocking constraint: an unsupported dependency, a required integration the platform cannot accommodate, or changes that cannot be tested and released reliably. Also price the work around replacement: content transfer, accounts, search URLs, analytics, training and support.
The decision can be staged. Fix the immediate failure while investigating a larger replacement, provided the temporary work has a clear boundary and will not be mistaken for the finished system.
Test the smallest uncertain part
Imagine a booking website that looks dated and loses enquiries on phones. This is an illustrative scenario, not a client result. First reproduce the failure. If a form field blocks submission, repair it and retest the whole booking path. That answers the immediate problem without assuming that every page needs replacing.
If the booking provider cannot support a required workflow, test a small integration or prototype before committing to a new platform. Ask what the test will prove, what it will leave unknown and which work can be reused.
Ask for comparable proposals
Send each supplier the same information:
- The affected URLs or screens, the task and the evidence of failure.
- Required changes, things that must keep working and explicit exclusions.
- The platform, integrations and access available for inspection.
- Who approves content and design, and who will maintain the result.
- Acceptance checks on phone and desktop, a release plan and a way back if the change fails.
- A breakdown of investigation, implementation, migration and ongoing costs.
Ask each proposal to explain its assumptions. A lower total may omit content entry, redirects or handover that another quote includes. Compare those responsibilities before comparing price.
Protect the parts that already work
Keep an inventory of existing pages and their destinations if addresses change. Test forms, search, account access and important integrations before switching traffic. Confirm that someone can restore the previous version and reconcile any new data collected during a failed release.
For changes to search URLs, Google’s site-move guidance covers URL mapping and redirects. A redesign that keeps its URLs still needs checks for accidentally blocked pages and missing content.
Drevhe’s Web & App Improvements service covers focused changes and new builds. Bring the problem and the current system; the scope follows the evidence.