If your website looks dated, rebuilding it may seem the obvious answer. Whether you need to do that depends on what has to change: confusing design, missing service information and a function the system cannot support each require different work.
You may be able to add a missing service explanation in the existing CMS without replacing the system. A customer portal with individual case records, however, could need functions the current website was never designed to provide. Establishing those differences helps you weigh an adaptation against a rebuild.
Identify what can stay
An inventory by page type and function makes the decision concrete: what works, what needs changing and what remains unknown? Including content, image files, existing page URLs and editing in the CMS also reveals work that goes beyond the new design.
An old design tells you little about whether the technical foundations remain useful. Conversely, a recently redesigned site may run on a system nobody maintains. Have these questions checked against the actual site rather than using age as the deciding factor.
A small trial can help. Can a representative service page be improved using real content? Do navigation, mobile layouts and editing remain workable? This is particularly useful when the limits of the current system are not yet understood.
Where a focused change may be enough
If the main problems lie in a few repeated components, scope the work around them. Examples include an offer overview that is hard to compare or feedback that visitors do not understand. Record which other areas should remain unchanged.
Two services with different prerequisites make useful trial content. They let you see whether the existing template explains the differences and whether your editors can maintain the revised pages themselves. The changes required also provide a basis for estimating the work.
The trial also reveals side effects. Longer service names or additional images may put different demands on the template from the old content.
When to investigate a rebuild
A rebuild deserves consideration when required flows cannot reasonably be implemented in the current system, operation is unresolved, or many connected areas would need replacing anyway. Compare adaptation and rebuilding against the same intended outcome.
The GOV.UK description of the alpha phase recommends testing risky assumptions with limited prototypes. For your decision, that might be an early technical trial: can the necessary integration actually work? An attractive design cannot answer that question.
A rebuild estimate therefore also needs to cover content migration, redirects, training and future operation. The current site still needs attention until the changeover. If that transitional work is missing, you cannot compare the rebuild fairly with an adaptation.
Compare adaptation and rebuilding against the same goal
The inventory and trials give you something concrete to compare: which parts stay, what work is required and which limitations you would still have afterwards. Estimates that depend on an untested technical assumption should remain visibly unresolved rather than appearing to be dependable costs.
Frontend modernisation and a new website or shop are different commissions. For a web design project, we establish which parts you need. If the immediate question concerns a difficult buying journey, start with the checks before a shop redesign.
