Start with one customer task
A website that looks dated does not automatically need a rebuild. If visitors can understand your offer, read the page on a phone and send an enquiry, a focused redesign may solve the remaining problems. A rebuild becomes more useful when the platform prevents essential changes or when maintaining the existing site costs more effort than replacing it.
Choose one task to test first: requesting a quote, checking a service or viewing a relevant project. Ask someone unfamiliar with the business to complete it on a phone. Avoid explaining where to click. Write down the point where they hesitate, the information they cannot find and any step that fails. This gives you a concrete problem list instead of a vague instruction to make the site more modern.
Separate presentation problems from platform problems
Common findings and the first change to consider| Finding | First option to investigate |
|---|
| Text is cramped or buttons are hard to use on phones | Improve responsive layout and spacing |
| Visitors cannot tell what the business offers | Rewrite and reorganise service content |
| Useful projects exist but are difficult to find | Improve portfolio organisation and links |
| The platform cannot support an essential workflow | Compare a supported integration with a rebuild |
| Routine changes repeatedly break unrelated pages | Investigate the underlying implementation before choosing a solution |
These are starting points, not automatic verdicts. A broken enquiry form, for example, may be a small configuration issue. Rebuilding every page before diagnosing it can spend the budget without addressing the actual cause.
Make a short inventory before requesting a quote
Create a list with four columns: page URL, purpose, what works and what needs attention. Include service pages, enquiry pages and portfolio pages. Note which pages already bring relevant visitors or enquiries if you have reliable analytics. Keep a separate list of integrations such as email notifications, appointment booking and customer management.
Mark each item as keep, improve, replace or investigate. For example, a strong service page might need only clearer spacing and a shorter form. An unused feature might not belong in the next version at all. Give the designer the inventory and the customer task from the first step. Both help define scope more accurately than sending a collection of attractive reference sites.
Protect pages that already work
During a redesign, preserve existing page addresses whenever practical. Record page titles, descriptions, canonical URLs, important headings and internal links before work starts. If an address genuinely must change, plan where its visitors should go rather than leaving the old link broken.
Do not treat a redesign as a reason to rewrite every useful paragraph. Keep accurate service information and real examples. Test enquiry forms, confirmation messages, mobile navigation and contact links in a separate preview. A design can look complete while the customer journey still fails at the final step.
Example: a small consultancy website
Imagine a consultancy with six pages, a working enquiry form and useful case studies. Customers complain that the phone layout is crowded and that the main service is unclear. A focused redesign could improve the service introduction, simplify the mobile menu and make case studies easier to scan while retaining the existing URLs.
If that same consultancy needs a client portal that its current platform cannot support safely or maintainably, compare the cost of an integration with a rebuild. Write down the required portal tasks before selecting a platform. The decision should follow the workflow, not a preference for a particular tool.
Record the decision and what would change it
Prepare a short decision record before approving a redesign or rebuild. List the observed customer problem, what already works, platform limitations that have been demonstrated, how the proposed option solves the problem, and the cost or disruption that still needs an estimate.
Illustrative redesign-versus-rebuild comparison| Observed problem | Initial option | Evidence that could change the decision |
|---|
| Headings and spacing are hard to read on phones | Improve the existing design | The current template cannot be updated accessibly or maintainably |
| Enquiries fail because notifications are misconfigured | Test and repair the form flow | The platform cannot reliably deliver the required workflow |
| An essential client portal cannot be supported | Evaluate extensions and platform alternatives | Documented security, support and maintenance constraints |
These scenarios are hypothetical. Do not promise savings or conversion gains without a real estimate and reliable evidence. Preserve useful page content and existing URLs unless a separately approved migration is necessary.
Use this brief to agree the next step
- Our main customer task is: ___.
- The three problems we observed are: ___.
- Pages and integrations we must keep are: ___.
- Required new functionality is: ___.
- Our budget range, deadline and approval contact are: ___.
- We will accept the work when these tasks pass on desktop and mobile: ___.
Ask for a recommendation with reasons, a clear list of included work and a separate list of assumptions. If the evidence supports incremental improvements, start there. If it supports a rebuild, use the inventory as the migration checklist. You can review our website design service when you need help defining that scope.