You can dislike the way your website looks without needing to replace it. Equally, a fresh set of colours can leave the real problems untouched. The decision becomes easier when you separate presentation from the way the site is organised and maintained.
Suppliers do not always use “redesign” and “rebuild” in exactly the same way. For this discussion, a redesign means improving the visual presentation while retaining a sound underlying structure. A rebuild means revisiting that structure and implementation more substantially, while keeping whatever content and assets remain useful.
The right choice is the smallest coherent piece of work that solves the actual problem. It should leave you with a site that represents the business and can be looked after sensibly.
When a redesign can be enough
Start by asking what already works. Can a new visitor understand the offer? Are the pages logically arranged? Does the navigation use language customers recognise? Can someone read about a service and reach an appropriate enquiry route without difficulty?
If those answers are positive, the site may have a useful foundation. Perhaps the photography is dated, headings are inconsistent or spacing makes good information feel crowded. Those are genuine design problems, but they do not automatically require a new site underneath.
Check mobile before making that judgement. The desktop version may be orderly while the phone layout hides important content or makes the menu awkward. A visual refresh is easier to justify when the responsive behaviour is already sound too.
The underlying site should also be healthy enough to keep. Ask whoever maintains it whether routine updates are manageable, whether there are unresolved faults and whether the proposed design can be applied consistently. A system your team can use confidently has value worth preserving.
When the structure needs a rethink
A rebuild becomes more plausible when the site reflects decisions made at different points in the company’s history, without a clear organising idea.
For example, a business may have added a service every few years. Some now appear in the main menu, others under an old department name and another only on the homepage. A new design applied to those pages would leave the customer facing the same confusing choices.
Accumulated content can create a similar problem. Repeated introductions, obsolete services and conflicting contact instructions make it difficult to tell which information is current. Tidying a few paragraphs will not resolve a page structure that no longer matches the offer.
Read the signs that a website is underselling its business if the mismatch is difficult to describe. The useful question is where the site misrepresents the company, rather than whether it simply feels old.
Treat technical symptoms carefully
Poor mobile behaviour, slow pages and fragile forms are reasons to investigate. They are not, by themselves, proof that everything must be replaced.
A large image may be fixable without rebuilding the site. A problem limited to one form may need a targeted repair. Ask for a diagnosis that identifies the cause and distinguishes an isolated fault from a repeated limitation.
The case for a rebuild is stronger when the same weaknesses run through the implementation: layouts that need individual workarounds, changes that break other pages, or repeated patches that cannot be maintained consistently. Then improving the foundation may be more sensible than continuing to work around it.
That assessment should be explained in language you can evaluate. “The platform is old” is not a complete business case. What is difficult, what does it prevent and what would the proposed work improve?
Compare two concrete scopes
Instead of asking for a preference between two labels, ask for the work behind each option.
A redesign scope might retain the existing pages and enquiry flow, update typography and photography, standardise spacing and correct specific mobile issues. A rebuild scope might regroup the services, remove obsolete content, rewrite unclear introductions and create a consistent layout system.
For each, identify what will remain unresolved. If a redesign leaves you with a confusing menu and difficult maintenance, the lower initial scope may not address your concern. If a rebuild adds no useful improvement beyond a visual refresh, it may be more work than you need.
Also consider your own involvement. A new structure may require decisions about services, evidence and wording. Make room for that work in the plan rather than assuming the supplier can infer every detail from the old site.
A rebuild should keep what has earned its place
Starting again technically should not mean discarding useful material. Good project photography, accurate service descriptions, clear contact details and established page addresses may all deserve to stay.
Before work begins, make an inventory of the pages and assets that matter. Record any URLs that must be retained or redirected, and identify forms or integrations that need checking. If search traffic or enquiries already depend on particular pages, bring that information into the discussion.
Our review, rebuild and launch process begins with the current site for this reason. The existing work provides context, including evidence of what should be preserved.
Make the decision around the business
Write a short statement of the outcome you need: clearer service choices, a more accurate impression of your work, better mobile usability or easier maintenance. Use it to assess the proposed scope.
A focused rebuild such as our business website offer can be appropriate when the website has fallen behind the company. A redesign can be appropriate when the foundation is still doing its job. Neither label is an achievement in itself; the result should solve the problem you started with.