You look at your website, know something is wrong, and can't quite name it. That's the moment most business owners search for redesign versus rebuild, hoping the label will tell them what to do next. It won't, not by itself. The honest answer depends on where the problem actually lives — in how the site looks, or in what it's built on and what it's built to say. Those are different problems with different price tags, and confusing them is how projects run over budget for the wrong reasons.
The two are not points on the same scale
A redesign changes the surface: layout, visual identity, copy, imagery, the way pages are organised. The underlying structure — the content model, the tech stack, the way the site is coded — mostly stays. A rebuild changes the foundation: a new platform, a new information architecture, sometimes a new sitemap altogether, because the current one no longer matches how the business actually works. You can redesign a site that's structurally fine but visually dated. You cannot redesign your way out of a site built on the wrong platform, missing the pages your business now needs, or held together by a content management system nobody on your team can use.
Signs you need a redesign, not a rebuild
- The site loads fine, is reasonably fast, and the CMS works — you just don't like how it looks or it feels ten years out of date
- Your business hasn't fundamentally changed since the site was built: same offering, same audience, same sales process
- Content and structure are basically sound — the pages people need exist, they're just presented badly
- You get traffic and rankings you don't want to lose, and a full platform change risks breaking both
- The team can update content today, even if the process is clunky — the problem is presentation, not capability
Signs you need a rebuild
- The site can't do something the business now needs — bookings, a product catalogue, multilingual content, an integration with your CRM or ERP
- Nobody in-house can update it without calling a developer for basic changes
- It's built on a platform that's discontinued, unsupported, or that the original developer no longer maintains
- The information architecture reflects a business you no longer are — services you dropped, an org structure that changed, an audience that shifted
- Mobile performance or core web vitals are structurally bad, not just a matter of unoptimised images
- You're bolting workarounds onto workarounds just to keep the site doing what you need
Where the confusion usually starts
Most businesses ask for a redesign when the real complaint is about structure. "Make it look modern" often means "our services aren't clear," "visitors can't find pricing," or "the site doesn't explain what we actually do anymore." Those are content and architecture problems. No amount of new visual design fixes them, because the issue was never how the page looked — it was what the page was trying to say, and in what order. This is why we start every project with structure and content, not visuals. If a client comes to us wanting a redesign and the real gap is in the sitemap, in what data the site needs to hold, or in how services are grouped, we say so before any design work starts. A visual refresh over a broken structure just produces a better-looking version of the same problem.
What each option actually costs
Ranges vary a lot by scope and market, but as a rough guide for small and mid-sized business sites in the EU: a genuine redesign — new visual direction, refreshed copy, same platform and structure — tends to land somewhere between €2,500 and €8,000. A full rebuild, with new architecture, new platform, and content migration, usually runs from €6,000 to €25,000 or more, depending on how much custom functionality is involved. The gap isn't arbitrary. A rebuild involves decisions a redesign doesn't touch: what content model the site needs, how pages relate to each other, what integrations have to work, what happens to existing URLs and rankings during the move. Skipping that thinking to save time is how rebuilds go over budget — the hard questions get answered mid-project instead of before it, usually at a worse moment and a higher cost.
The middle path worth considering
Not every situation is purely one or the other. It's common for the structure to be mostly right with a few real gaps — a missing case studies section, a service that needs its own page, a navigation that grew messy over three years of ad-hoc additions. In that case, a structural refresh plus a visual redesign, done together but scoped honestly, costs less than a rebuild and fixes more than a cosmetic pass would. The mistake is treating this as a redesign with a few extra pages thrown in. If the sitemap needs real rethinking, that thinking has to happen first, on paper, before anyone touches a template or writes code. We deliver that as a presentation of the new structure and content plan, not a half-built prototype, precisely so a client can push back on the architecture before it's expensive to change.
A short way to decide
Ask three questions before requesting a quote of either kind. First, has the business itself changed since the site was built — new services, new markets, a different sales process? If yes, lean rebuild. Second, can your team update and maintain the site today, even clumsily? If no, that's a platform problem, which points to a rebuild regardless of how the site looks. Third, if you fixed nothing but the visual layer, would visitors finally understand what you do and how to buy it? If the honest answer is yes, you need a redesign, and a rebuild would be spending money to solve a problem you don't have.
The label matters less than getting the diagnosis right. A redesign done well is a fast, contained project with a predictable outcome. A rebuild done well starts with structure, not styling, and earns its higher cost by fixing things a new coat of paint never could. Getting them backwards is the expensive mistake — not choosing the more expensive option, but choosing the wrong one.
Related services