Write down the problem in business terms
Examples include too few qualified enquiries, a slow publishing process, an unreliable booking journey or a platform that cannot support an essential integration. “The website looks old” is a preference that may matter, but it is not yet an explanation of lost business.
Collect evidence from customers, staff, analytics and actual task tests. Establish whether the problem affects the whole site, one important journey or only a small number of pages.
Compare the available routes
| Route | Appropriate when | What to establish |
|---|---|---|
| Focused improvement | The platform works and the problem is bounded | Specific changes, baseline and validation |
| Design refresh | Presentation and usability need attention but core functionality fits | Reusable content, templates and conversion requirements |
| Rebuild or replatform | Existing constraints prevent the required capability or reliable operation | Migration, integrations, data, ownership and support |
A visually different website can still preserve the same operational limitations. Conversely, an unattractive form may be corrected without a full rebuild.
Test whether the proposed investment addresses the cause
If relevant traffic is scarce, the website may need better service coverage and acquisition. If people arrive but misunderstand the offer, content and page structure may be the priority. If enquiries are submitted but lost, investigate the operational workflow.
Ask the proposed supplier to explain which problem each major part of the rebuild solves. A new platform should have a reason beyond familiarity or fashion, including the costs and responsibilities it introduces.
Include the cost of changing
Budget for content decisions, URL mapping, redirects, data transfer, integrations, tracking, training and support—not just new screens. Identify existing pages that customers use and organic search already finds. Those assets need deliberate treatment.
Define how representative tasks will be tested and who approves launch. Also establish how the old and new systems will be handled during the change and what a practical rollback or contingency would involve.
Make a proportionate decision
Compare the expected outcome, delivery effort, dependencies and ongoing cost of each credible option. If a focused improvement can test the main hypothesis, it may provide useful evidence before a larger commitment.
A Digital Growth Review looks across search, conversion, analytics and customer journeys to help prioritise this decision. Where a rebuild is justified, use a clear brief and a reviewable migration plan rather than assuming the design process will discover every requirement.
Common questions
Can an older website still perform well?
Yes. Age alone does not determine usefulness or commercial performance. The relevant question is whether it meets current customer and operating needs.
Should all old content be carried into the new site?
No automatic rule works. Assess usefulness, evidence, existing demand and business relevance, while preserving valuable URLs and planning changes deliberately.
What should we do first?
State the problem, test important customer tasks and reconcile the tracking with real enquiries or sales.