When a website starts causing problems - slow performance, a clunky user experience, a platform that's making everything harder than it should be - the instinct is to jump straight to a solution. In almost every initial conversation we have with a new client, the path has already been decided before we're in the room. It's usually a redesign, because that's the most familiar option. Sometimes it's a full rebuild, because someone senior has decided the whole thing needs to go.
What's rarely happened before that conversation is a proper diagnosis. And that gap is where expensive mistakes are made. A redesign won't fix a platform that can't scale. A rebuild won't help if the real issue is strategic misalignment. A replatform won't deliver results if the underlying experience hasn't been thought through.
So before anything else, the question isn't which path - it's what's actually broken.
These three terms get used loosely, and often interchangeably, which is part of the problem.
Redesign means changing how a site looks, feels, and flows - the visual design, the information architecture, the user journey. The platform underneath stays the same. This is the right path when the technology is working well but the experience isn't converting, or when a brand refresh needs to be carried through to the digital presence.
Replatform means moving your existing site to a different technology platform - for example, migrating from one CMS to another. The content and core functionality largely stay the same, but the infrastructure changes. This is typically the right call when the current platform has hit its ceiling: it can't support the integrations you need, it's becoming difficult to manage, and internal processes (updating content, creating new pages) are very time-consuming.
Rebuild means starting from scratch - new platform, new design, new architecture. This is the most resource intensive. A rebuild makes sense when the current site is so structurally compromised, both from a technical perspective and UX/UI standpoint, that working around its limitations costs more than replacing it entirely.
One thing we tell every client: you shouldn't have to rebuild everything to grow. The right answer is the one that fixes what's actually broken, the one that will return the highest ROI for you.
Before choosing, a team needs honest answers to a few fundamental questions.
Is the problem with the platform or the experience?
If your team is regularly hitting walls - content that's painful to update, integrations that won't connect, performance that can't be optimised - the problem is likely the technology underneath. If the platform is largely fine but your conversion rates are poor and users are bouncing, the problem is more likely the experience sitting on top of it. These are different problems with different solutions, and confusing one for the other leads to expensive missteps.
Can your content and data be easily migrated?
Replatforming works cleanly when the content architecture on the current platform is well structured or you site runs on headless. If years of ad hoc additions have left your content and data in a mess, and replatforming means rebuilding both your frontend and backend, then a replatform can become far more complex than you had budgeted for. Sometimes a rebuild gives you the opportunity to get that structure right from the start - and ends up being the faster path.
How much is the current platform costing you?
Not just the licensing fee but the time your team spends working around its limitations, the integrations that have to be built manually, the features that simply aren't available. We often find that organisations are significantly underestimating this number, because the cost is distributed across people and time rather than sitting on one invoice.
What does your team need to do with this site in the next three years?
A path that solves today's problem but closes off tomorrow's options isn't really a solution. If your roadmap includes significant personalisation, A/B testing, or omnichannel content delivery, that needs to factor into which platform you land on - not as an afterthought, but as a starting constraint.
Path | Good fit when... | Watch out if... |
|---|
Redesign | Platform is solid but the experience has aged, conversion rates are underperforming, or a rebrand needs to be reflected digitally | The real frustration is with the platform - a new look won't fix a broken engine |
Replatform | The platform is the primary bottleneck - performance, integrations, content management tasks within the CMS, or cost | The content model is a mess - migration will be far harder and more expensive than expected |
Rebuild | The architecture is so tangled that meaningful change requires disproportionate effort, or the business has fundamentally changed | The team is simply frustrated - rebuilding for the wrong reasons can be very expensive |
There's a step that gets missed in most website transformation projects: the diagnostic conversation before any work is scoped.
It's not just a website or digital journey audit. It's a structured look at what the site needs to do for the business, what's preventing it from doing that today, and what the team has the capacity to execute and maintain.
At Paved Digital, we call this our Discovery Phase - typically four to six weeks where we audit the current technology, processes, customer journeys, and performance data to get a clear picture of what's working, what's blocking growth, and what the smartest path forward actually looks like.
The goal isn't to recommend the most impressive solution. It's to recommend the right one, and sometimes that means improving what's already there rather than replacing it.
When Gibraltar Strategic Advisory came to us, their existing one-page site couldn't scale with their growth - it was difficult to add new content, there was no CRM integration, and the team had no way to manage it independently without outside help. A redesign would have made it look better but left every underlying problem intact. The right path was a rebuild: a new architecture built around templates their team could use, with HubSpot integrated for lead management and GA4 for performance tracking. The result was a site that the GSA team now runs largely on their own, without needing to call anyone every time they want to publish something new.
Read our work for GSA here
That's exactly the conversation we have before any project begins. If your website is causing friction for your customers, your team, or both, get in touch and we'll help you figure out what's worth doing, and why.
Talk to Paved Digital →