A redesign is the most expensive way to fix a website, and frequently the least targeted. It is also the first thing anyone suggests, because a site that looks dated is the most visible problem a business has, even when it is not the most costly one.

Before committing, it is worth separating the reasons that justify a rebuild from the ones that only feel urgent.

The reasons that genuinely justify it

• The business changed and the site did not. You sell something different, to someone different, or you have added a line the current structure cannot hold. No amount of tidying fixes an information architecture built for a company you are no longer running.
• Nobody can maintain it. The person who built it has gone, the CMS fights every change, and publishing a page requires a developer. This compounds: the harder it is to change, the more out of date it gets, the more the business routes around it.
• It is measurably failing. Not "it feels clunky" — actual evidence. Drop-off at a specific step, a mobile experience that loses people, a search nobody uses successfully. If you can point at where it fails, you can fix it, and you may not need a redesign at all.

The reason that is not good enough

Somebody senior has got bored of it.

This is real, it is common, and it is worth naming rather than pretending. Leadership looks at the homepage far more often than customers do, and familiarity breeds contempt long before the design actually stops working. A site that feels tired to the person who sees it daily may be performing perfectly well for someone seeing it once.

That is not an argument for never refreshing. It is an argument for checking whether the problem is the site or your relationship with it.

What a redesign costs beyond the invoice

The fee is the visible cost. The others are not:

• Search performance. URL changes, content consolidation and structural changes all carry ranking risk. Done carelessly, a redesign can cost more in lost traffic than it gains in conversion.
• Content. Somebody has to rewrite, re-photograph and re-enter it. This is almost always the part that overruns, and it usually falls on people with day jobs.
• Institutional memory. Every workaround and edge case the current site handles quietly gets rediscovered the hard way.

None of these are reasons not to redesign. They are reasons to know what you are taking on.

The cheaper thing to try first

An audit costs a fraction of a rebuild and frequently finds that the problem is three specific things rather than the whole site. A checkout step that loses people, a navigation label nobody understands, a mobile layout that breaks on the most-visited page.

Fixing those targets is faster, cheaper, and measurable in a way a redesign rarely is — because when you change everything at once, you cannot tell which change helped.

We have written elsewhere about the hidden cost of skipping a UX audit, and our own product audit is fixed scope and fixed cost for exactly this reason: it is the cheapest way to find out whether you need the expensive thing.

How to decide

Ask three questions honestly.

• Can you name where it fails, specifically? If yes, fix those. If no, you are guessing, and a redesign is an expensive guess.
• Could your team publish a new page today without a developer? If not, that is a structural problem, and it is a legitimate reason to rebuild.
• Has the business changed since the site was built? If yes, the structure is probably wrong, not the styling.

If you answer no, yes, no — you want a refresh, not a redesign, and you should spend a tenth of the budget.

If the honest answer is that the structure no longer fits the business, then rebuild, and go in knowing what it costs beyond the fee. A thirty-minute call is usually enough for us to tell you which of the two you are looking at, including when the answer is that you do not need us.