Why "Redesign the Whole Site" Is Usually the Wrong Brief
"We need to redesign the whole site" is one of the most expensive sentences a founder can say, and nine times out of ten, it's not actually true. What's usually true is that a specific page isn't converting, the brand feels dated in a way nobody's articulated precisely, or a competitor's new site made the team anxious. All three of those are real problems. None of them require starting over.
The question we ask before agreeing to a full redesign
What, specifically, is not working? Not "it feels old" — which page, which metric, compared to what. If the answer is "our homepage bounce rate is high" or "nobody completes the signup form," that's a targeted, measurable problem with a targeted, measurable fix. A full redesign to solve a one-page problem is like renovating a whole house because one faucet drips.
What a full redesign actually risks
- Throwing away whatever is currently working, including SEO rankings built up over years, because a fresh URL structure or content rewrite resets signals Google had already trusted.
- A multi-month project with no visible progress for stakeholders, versus incremental changes that ship and get measured every few weeks.
- Replacing a known set of problems with an unknown set of new ones — a new design has its own untested friction points that only show up after launch.
- Losing institutional knowledge about why certain decisions were made the first time, and quietly repeating old mistakes with a new coat of paint.
What we do instead, most of the time
An audit first — the same instinct behind diagnosing a slow website before rebuilding it: look at real analytics, real user recordings if available, and real feedback, and find the specific two or three things actually costing conversions or credibility. Fix those, measure the impact, and let the data tell you whether there's still a case for something bigger.
A redesign is a hypothesis, not a guarantee. If you can't say what specifically will get better and how you'll know, you're not ready to start one yet.
When a full redesign is actually the right call
It's rarer than people think, but real: a brand repositioning that the current site actively contradicts, a business model change the current information architecture can't represent, or a site so old its underlying technology is a genuine liability. Even then, a clear brief that names the specific problems being solved will get you a better result than "make it feel more modern."
Talk to us
Have a project in mind? Tell us about it.
Four quick questions and we'll reply within one business day with an honest view on the fastest way to ship it, whether that's our own products, a custom build or an integration.
Start your project
Let’s build something great
Which industry does your business belong to?
Pick the closest match — we'll tailor the rest for you.
Keep reading
How to Brief a Dev Agency So You Actually Get What You Want
The best projects we've ever shipped had one thing in common, and it wasn't a bigger budget — it was a client who could clearly say what "done" looked like.
Web DevelopmentThe Real Cost of a Slow Website (and How to Fix It Without a Rebuild)
A one-second delay doesn't sound like much until you translate it into how many people quietly closed the tab before your page finished loading.
ProcessQA Testing Isn't Optional: What Actually Breaks When You Skip It
Every 'we'll skip QA to hit the deadline' decision we've seen has produced the same outcome: the bugs still get found, just later, more publicly, and more expensively.