Tend, Don't Rebuild: The British Websites Being Pruned Rather Than Redesigned

Every few years, like a badly timed comet, it arrives: the Big Website Project. A brief goes out, an agency pitches, a budget is quietly doubled, and six months later the whole thing launches to a brief round of applause before everyone stops looking at it again until 2028.

A small but growing band of British studios and in-house teams have decided this ritual is, frankly, a bit mad. Their argument is simple: a website isn't a building you construct once — it's a garden, and gardens die when nobody tends them.

The Relaunch Trap

The traditional model has a familiar rhythm. A site launches, everyone's delighted, then attention drifts elsewhere. Content decays. The design slowly dates. Analytics go unread. Eventually the site becomes an embarrassment, and the only solution anyone can imagine is a dramatic, expensive rebuild.

It's the digital equivalent of leaving the garden to become a jungle, then paying a landscape firm to pour concrete over the lot and start again.

The costs are rarely just financial. Big rebuilds mean months of internal meetings, a hard freeze on improvements elsewhere, and — almost inevitably — a launch that breaks things regular customers had learned to rely on. Anyone who's watched a beloved checkout flow vanish overnight knows the feeling.

The Gardeners of the Web

Across the UK, a different approach is taking root. Small studios in places like Sheffield, Cardiff and Glasgow are quietly dropping the phrase "redesign" from their vocabulary altogether. In its place: fortnightly sprints, a rolling backlog of improvements, and a standing rule that nothing sits untouched for more than a few weeks.

In-house teams are doing the same. Rather than a two-year rebuild cycle, they run their sites like product teams — shipping small changes, watching the numbers, keeping what works and pruning what doesn't. A button gets moved. A page gets rewritten. A clunky form gets cut from nine fields to four. None of it makes headlines, and that's precisely the point.

The results, when teams talk about them openly, tend to be unglamorous but compelling: conversion rates creeping upward, fewer panicked support calls, and — crucially — no terrifying relaunch to budget for.

Why Small Beats Big

There's a deeper logic here than simple tidiness. Big rebuilds are high-stakes gambles: you bet months of work on a set of assumptions, and you only find out if you were right after launch, when it's too late to do much about it. Small, constant fixes are the opposite — a stream of low-stakes experiments where you learn something every fortnight.

Modern tooling has quietly made this easier. Composable platforms, component libraries and sensible deployment pipelines mean a two-person team can ship a meaningful improvement on a Tuesday afternoon without anyone holding their breath. The technical excuse for the mega-project is wearing thin.

There's a cultural shift, too. The Big Launch rewards agencies who bill for drama. Continuous improvement rewards people who actually know the site — which usually means the business itself. It shifts power, in a small way, back in-house.

The Honest Downsides

It would be rose-tinted to pretend the gardening model is effortless. Continuous improvement requires someone to own it, and in many UK SMEs that someone already has three other jobs. It needs a budget line that survives the quarterly cull — easier said than done when a rebuild can be capitalised and a maintenance retainer cannot. And it demands a degree of discipline: a backlog nobody prioritises becomes a guilt list, not a strategy.

There's also a genuine case for occasional bigger swings. Sometimes a brand genuinely changes, or the underlying platform is beyond saving. The gardeners aren't against all big moves — they're against big moves as a substitute for looking after the place.

A Fit for the Times

There's something rather British about this shift, too. It suits a business culture that's grown sceptical of grand pronouncements and wary of big-ticket spending — a preference for the sensible over the spectacular. It's the corporate equivalent of repairing a jumper rather than buying a new coat.

For the next generation of British firms, the question is changing. It's less "when do we rebuild the website?" and more "who's looking after it this month?" The firms asking the second question are, quietly, pulling ahead.

The relaunch party was always fun. But gardens beat construction sites in the long run — and the teams tending them are finding the view is better, too.