When to Rebuild Your Website vs. When to Fix What You Have

"We need a new website" is something we hear a lot. Sometimes it's true. But sometimes what looks like a case for a full rebuild is actually a few specific problems that could be fixed without starting from scratch.

A full rebuild is a significant investment of time and money. Before committing to one, it's worth understanding whether a more targeted approach would solve your actual problems. Here's how we think about it.

Signs you probably need a rebuild

The technology is holding you back

If your site is built on a platform that can't do what you need it to do, no amount of patching will fix that. Maybe it's a legacy CMS that hasn't been updated in years. Maybe it was built with technology that's no longer supported. Maybe the code is so tangled that every small change risks breaking something else.

We've inherited sites where the cost of making even minor updates exceeds the cost of rebuilding the relevant section from scratch. At that point, you're throwing good money after bad.

The design is fundamentally wrong for your audience

If your site was designed for a different audience, a different era, or a different version of your organisation, surface-level changes won't fix the underlying problem. When the information architecture, the visual language, and the content strategy all need rethinking, it's usually cleaner to start fresh.

You've outgrown the original scope

A site that was built for a five-person startup looks and feels different from what a fifty-person organisation needs. If you've added features, pages, and functionality over the years without a cohesive plan, the result is often a Frankenstein site that nobody's happy with.

Signs you can probably fix what you have

The structure is sound but the content is stale

If the site's architecture and design still work but the content hasn't been updated in years, a content refresh is far cheaper and faster than a rebuild. Update the copy, refresh the imagery, review the SEO fundamentals, and you might be surprised at the difference.

Performance is the main issue

Slow sites aren't always broken sites. Sometimes the problem is unoptimised images, too many plugins, poor hosting, or render-blocking scripts. A performance audit and targeted fixes can dramatically improve load times without touching the underlying site.

You need a few new features

If the site works well overall but you need to add a blog, improve the contact form, or integrate a booking system, that's an enhancement, not a rebuild. Build the new features within the existing framework.

The middle ground: phased approach

Sometimes the honest answer is somewhere between "fix it" and "rebuild it." We've worked on projects where we rebuilt the public-facing site while keeping the back-end systems intact, or where we migrated to a new CMS in phases rather than all at once.

A phased approach manages risk and spreads cost over time. You get the most impactful improvements first and can adjust the plan as you go based on what you learn.

How to decide

Ask yourself these questions:

• Can the current site be updated by your team, or do you need a developer for every change?
• Does the site reflect who your organisation is today, or who it was three years ago?
• Are your users able to find what they need and complete the tasks you want them to?
• Is the site fast, secure, and accessible?
• Are you spending more on maintaining the current site than you would on building something new?

If you answered "no" to most of these, a rebuild is probably the right call. If the issues are more targeted, a fix might be all you need.

Either way, we're happy to take a look and give you an honest assessment. We'd rather recommend a $5,000 fix than sell you a $50,000 rebuild you don't need.