When to Redesign vs. Refresh: A Framework for Business Owners
A full redesign is expensive. A surface refresh often misses the point. This decision framework helps you pick the right path.
At some point, every business owner looks at their website and thinks: "We need to do something about this." The next question โ whether to do a full redesign or a targeted refresh โ is where significant money gets spent wisely or wasted.
We've guided dozens of Australian businesses through this decision. Here's the framework we use.
First: diagnose the actual problem
Before discussing solutions, get clear on what's broken. Pull your analytics. Look at bounce rate, time on site, pages per session, and โ most importantly โ conversion rate. If traffic is healthy but conversions are low, the problem is likely messaging or UX. If traffic is low, the problem is likely SEO or discoverability. If the site loads slowly, it's a performance problem. Each of these has a different solution.
The worst reason to trigger a redesign is aesthetic boredom. "It's looking a bit dated" is almost never worth $15,000โ$40,000. Start with data.
The case for a refresh
A refresh is the right call when your underlying site structure is sound but specific elements have degraded. Signs you need a refresh rather than a rebuild:
- Your conversion rate was once good but has declined โ the structure works, but the messaging is stale
- Your brand has evolved and the site no longer reflects it, but the information architecture is still logical
- The site is technically healthy (fast, mobile-friendly) but visually feels behind competitors
- You need new service pages or a content refresh, not a structural overhaul
A refresh might involve new copywriting, updated photography, revised colour application, and tweaks to key pages. Done well, it can be completed in 2โ4 weeks and costs a fraction of a full rebuild.
The case for a full redesign
A redesign is justified when the problems are structural. Signs you genuinely need a rebuild:
- The site is built on an outdated platform that can't support modern performance standards
- The information architecture is confusing โ users can't find what they're looking for
- Your business has pivoted significantly and the current site reflects who you used to be
- Core Web Vitals are poor and the underlying code or CMS can't be optimised without a rebuild
- You're scaling and need integrations the current platform can't support
The decision test
When a client is on the fence, we ask them two questions:
1. If you fixed only the visual layer โ new photography, updated colours, refreshed copy โ would the site still frustrate users? If yes, you need a redesign. The problem isn't cosmetic.
2. If you kept the current visual design but fixed the speed, structure, and messaging โ would you be embarrassed to send someone to it? If no, a refresh might be enough.
One more thing: don't let perfect block progress
We've seen businesses spend six months planning the perfect redesign while their current site costs them clients every week. If you're confident a refresh won't solve the core problem, start the redesign. But if you're uncertain, do the refresh first โ it's faster, cheaper, and the data you get from an improved version of the current site often clarifies what the full rebuild should focus on.
If you'd like to talk through your situation, book a strategy call. We'll give you a straight answer on which path makes sense.

