"The site feels old, we should redesign it" is one of the most expensive sentences in business. A full rebuild costs thousands, takes months, and carries real risk — you can lose search rankings, break things that worked, and end up somewhere that isn't actually better.
Sometimes it's the right call. Often it isn't. Here's how to work out which.
First, name the actual problem
"It feels dated" is not a problem you can fix, because it's not specific. Push until you have a concrete list:
- Is it slow? → measurable, often fixable without a rebuild
- Does it look broken on phones? → usually a CSS problem, not a foundation problem
- Is a specific flow broken or confusing — the contact form, the booking step, the checkout? → fix that flow
- Is the content wrong or thin? → a content project, not a design project
- Does it genuinely look a decade behind competitors and cost you credibility in sales? → this is the one that can justify a redesign
- Can nobody on your team update it? → a platform problem worth solving
Half the time, the honest list is "it's slow and the mobile layout is rough and the copy is stale" — and none of those need you to start over.
When a targeted fix is enough
Repair rather than rebuild when:
- The foundation is sound. It's on a reasonable platform, the code isn't a mess, and it's not so old that every change fights the last one.
- The problems are specific and bounded. Three things are wrong, and you can describe all three.
- It's ranking. If the site brings in search traffic, a rebuild risks that. A careful fix doesn't.
- The structure works. People can find what they need; the pages that matter exist. It's the surface that's tired, not the plan.
A focused engagement — a performance pass, a mobile rebuild of the templates, a rewrite of the key pages, a fix to the one flow that's losing you leads — is often a few weeks and a fraction of a full project.
When a rebuild is justified
Start over when:
- The platform is the problem. It's on something you can't get off, or something so outdated that maintaining it costs more than replacing it. Or it's a proprietary builder you don't control.
- The structure is wrong, not just the styling. The site is organised around how your company is structured internally rather than what customers are looking for, and no amount of restyling fixes that.
- It's genuinely hurting sales. You're pitching clients who look at the site and quietly downgrade their impression of you. For a B2B firm chasing bigger contracts, this is real money.
- You've outgrown it. The business does things now the site can't represent, and bolting them on has made a mess.
- Performance can't be fixed from the outside — you've compressed the images and cut the plugins and it's still slow, because the platform ships too much.
The middle path most people miss
You don't have to choose "limp along" or "spend £15k now." A sensible sequence: fix the urgent, measurable problems first — speed, mobile, the broken flow — for a small budget. Live with it for six months. If the structural problems are still holding the business back after that, then you have a clear, evidence-based case for a rebuild, and you'll scope it better for having waited.
If you want an honest read on which side of this line your site is on, send us the URL — we'll tell you what a fix would cover and whether it's worth it, before anyone talks about a rebuild. See how we approach web development for how we scope this kind of work.