Keep what works and replace what prevents progress. A redesign can improve presentation and customer journeys while retaining the current platform. A rebuild changes the foundation. The right investment depends on the cause of the problem, not the age of the website alone.
Diagnose before choosing a solution
Identify where the journey breaks. Visitors may not understand the offer, find the right service or complete the contact form. Those problems can sometimes be solved with clearer copy, simpler navigation and tested forms. Changing technology will not automatically repair an unclear commercial message.
Check the technical foundation separately. Can the team edit content safely? Are integrations supported? Does the mobile experience function correctly? If every useful change requires a workaround, a rebuild may remove continuing operational costs rather than merely change the appearance.
What can stay?
Inventory pages bringing relevant traffic, useful images, customer questions and existing integrations. A redesign should preserve valuable URLs and improve weak sections. A rebuild should also retain valuable content unless there is a clear reason to replace it.
For example, a contractor may have service pages attracting enquiries but an awkward mobile quotation form. Replacing the form and strengthening those pages can be more appropriate than discarding the whole site. A platform that cannot support required languages or secure editing presents a different problem.
Compare risk and effort
Request separate proposals for targeted improvements and a full rebuild where both are feasible. Include content migration, redirects, measurement and staff training. A rebuild with no migration plan can lose the benefit of years of content, even if the new design looks better.
Ask the provider to explain what cannot reasonably be repaired. That explanation should refer to observed limits, dependencies and maintenance costs. A generic claim that newer technology is always better is not a project justification.
Make the scope measurable
- List the pages and journeys being changed.
- Agree what stays, what moves and what is retired.
- Define mobile, editing, form and tracking checks.
- Budget for launch support and a post-launch review.
Judge the result against the problem: fewer blocked enquiries, easier editing or clearer service discovery. Establish a baseline before work starts so you can evaluate the change rather than simply approve a new visual style.
A brief you can use to compare proposals
Use the following as an illustrative procurement check, not a promise of results or a fixed package. Ask the provider to turn it into named deliverables, exclusions and a test you can witness before accepting the work.
Inventory reusable content, integrations and URLs before deciding whether to repair the current site or replace it.
A published example to inspect
A website for building insulation and renovation of the building envelope, presenting services and guiding homeowners towards a quotation. The navigation connects insulation, façades, roofing and windows with guides and quotation entry points, letting visitors start with their own renovation needs.
This published example illustrates presentation and visitor flow. It is not evidence of a conversion uplift, a ranking position or a price for your own project. Compare the scope you need with the capabilities actually demonstrated, then ask what would be different for your business.
Primary reference
Next.js documentation. Use the reference to check terminology and platform requirements when briefing a provider; the proposal still needs to define your own implementation and responsibilities.
Continue your comparison
A Website That Gets Traffic but No Enquiries: Conversion Audit or Full Redesign?
Discuss your project
Website design and development · See our website and service pricing
Send your current website, target customers and the problem you want to solve. We will discuss the appropriate scope, responsibilities and next step before you commit.