More insights.
Subscribe to our newsletter.
Deep dives into design thinking, creative process, and the intersection of business and aesthetics.
A rebuild is often the most expensive way to fix a structural mistake.
A new website launches and everyone's pleased with it. Six months on, the marketing team finds it awkward to update. By twelve months they've started to resent it, and at around eighteen months someone proposes scrapping it and paying for a rebuild.
A site that's awkward to update starts to feel out of date even when the design holds up, and tearing it down feels decisive. The old agency goes, a new one comes in. But if nobody fixes whatever made the first site hard to work with, the new one starts on the same eighteen-month clock.
The problem is usually the content model
When a site gets scrapped, the reason is more often rigidity than looks. The team wants to run a webinar series, but the CMS only has a template for blog posts. They want a location page for Cork, but the footer is hard-coded and every change means a developer.
When the structure can't change, every update turns into a small project with a quote attached, and people stop asking. The site freezes on launch day while the business moves on, until a rebuild looks like the only way out.
Build a library of sections the team can rearrange
Modularity breaks the cycle. We design the system first and the pages second: a library of reusable sections, testimonial blocks and feature grids for example, that can be stacked in whatever order a page needs.
A new landing page is then assembled from existing blocks, usually without a developer, and it matches the rest because it's made from the same parts.
Someone has to say no to the one-off
A modular site still degrades if nobody looks after it. It happens through exceptions: a manager wants a font that isn't in the brand guidelines, or a plugin goes in to handle one small feature. A year or two later the site is a patchwork of quick fixes and the system underneath means nothing.
Governance is the set of approvals and technical rules that stops that happening. The useful question for any change is whether it helps the people using the site or just settles an internal preference. Give one person the job of asking it, and the standing to say no to a senior colleague.
When a rebuild is the right call
There are good reasons to rebuild, and they're ones you can write down in a sentence. "It feels tired" isn't one of them.
The first is a real repositioning, say from selling to consumers to selling to businesses, where the site's structure no longer matches what you do. The second is technical debt you can't work around, such as code that's become a security risk or won't pass Core Web Vitals however much it's tuned. Outgrowing the platform counts too, as when a business needs to move off Wix to a headless setup.
If you can't write your reason down, try this. List the updates the team wanted to make in the past year and couldn't, and why. If the answers are templates, hard-coded sections and waiting on a developer, a new site built the same way will end up in the same place.
Improve it in stages instead
If none of those reasons apply, drop the idea of one big launch day and work through the site in order of importance:
Sort out the hosting and security.
Move to a modular content model.
Bring the case studies and testimonials up to date.
Refine the animation and small interactions last.
The site stays live throughout. Put the first two stages on this year's plan, and leave the polish until the structure can carry it.
Related Brainstorm services and work
Website redesign and support services · Web design in Ireland · Plan a staged website improvement
Updated 24 September 2026. Dave Curtin, founder and Creative Director of Brainstorm, leads website strategy, brand direction and technical delivery for Brainstorm clients.
A rebuild is often the most expensive way to fix a structural mistake.
A new website launches and everyone's pleased with it. Six months on, the marketing team finds it awkward to update. By twelve months they've started to resent it, and at around eighteen months someone proposes scrapping it and paying for a rebuild.
A site that's awkward to update starts to feel out of date even when the design holds up, and tearing it down feels decisive. The old agency goes, a new one comes in. But if nobody fixes whatever made the first site hard to work with, the new one starts on the same eighteen-month clock.
The problem is usually the content model
When a site gets scrapped, the reason is more often rigidity than looks. The team wants to run a webinar series, but the CMS only has a template for blog posts. They want a location page for Cork, but the footer is hard-coded and every change means a developer.
When the structure can't change, every update turns into a small project with a quote attached, and people stop asking. The site freezes on launch day while the business moves on, until a rebuild looks like the only way out.
Build a library of sections the team can rearrange
Modularity breaks the cycle. We design the system first and the pages second: a library of reusable sections, testimonial blocks and feature grids for example, that can be stacked in whatever order a page needs.
A new landing page is then assembled from existing blocks, usually without a developer, and it matches the rest because it's made from the same parts.
Someone has to say no to the one-off
A modular site still degrades if nobody looks after it. It happens through exceptions: a manager wants a font that isn't in the brand guidelines, or a plugin goes in to handle one small feature. A year or two later the site is a patchwork of quick fixes and the system underneath means nothing.
Governance is the set of approvals and technical rules that stops that happening. The useful question for any change is whether it helps the people using the site or just settles an internal preference. Give one person the job of asking it, and the standing to say no to a senior colleague.
When a rebuild is the right call
There are good reasons to rebuild, and they're ones you can write down in a sentence. "It feels tired" isn't one of them.
The first is a real repositioning, say from selling to consumers to selling to businesses, where the site's structure no longer matches what you do. The second is technical debt you can't work around, such as code that's become a security risk or won't pass Core Web Vitals however much it's tuned. Outgrowing the platform counts too, as when a business needs to move off Wix to a headless setup.
If you can't write your reason down, try this. List the updates the team wanted to make in the past year and couldn't, and why. If the answers are templates, hard-coded sections and waiting on a developer, a new site built the same way will end up in the same place.
Improve it in stages instead
If none of those reasons apply, drop the idea of one big launch day and work through the site in order of importance:
Sort out the hosting and security.
Move to a modular content model.
Bring the case studies and testimonials up to date.
Refine the animation and small interactions last.
The site stays live throughout. Put the first two stages on this year's plan, and leave the polish until the structure can carry it.
Related Brainstorm services and work
Website redesign and support services · Web design in Ireland · Plan a staged website improvement
Updated 24 September 2026. Dave Curtin, founder and Creative Director of Brainstorm, leads website strategy, brand direction and technical delivery for Brainstorm clients.