A prospect calls and says "we need a redesign." Sometimes they mean a new visual layer on the existing site. Sometimes they mean a complete rebuild from scratch. Sometimes they genuinely don't know which one they mean.

These are different projects. They have different budgets (a redesign costs roughly 40% of a rebuild). They take different amounts of time (a redesign is 3–4 weeks, a rebuild is 6–8). They have different outcomes, risks, and durations of benefit. Using the words interchangeably causes real confusion about scope.

This post is the honest breakdown of both, and a diagnostic for figuring out which one your specific situation calls for.

What a redesign actually is

A redesign keeps the existing underlying site — same platform, same tech stack, same backend — and replaces the visual layer. Same HTML structure, same pages, same URLs. New colours, new typography, new layouts, new imagery, new copy.

The output looks dramatically different. The infrastructure is the same.

Typical redesign scope:

New Figma designs for every page
New CSS and styling code
New imagery and photography
Updated copywriting
Minor interaction polish
No new backend functionality
No new pages (or at most 1–2 new ones)
Same CMS, same hosting, same database

A redesign is appropriate when the site's technical foundation is sound but the visual identity is dated, off-brand, or not converting well.

What a rebuild actually is

A rebuild replaces the entire site. New code, new tech stack, new CMS, new hosting, new architecture. The URLs are preserved for SEO, but everything behind them is thrown out and written from scratch.

Typical rebuild scope:

New design (implicitly — you're rebuilding, so you're also redesigning)
New codebase in a new framework (e.g. moving from WordPress to Next.js)
New CMS (e.g. moving from Webflow's CMS to Sanity)
New hosting (e.g. moving from a shared WordPress host to Vercel)
URL redirect map from old to new structure
Migration of content from the old system
New features and functionality that weren't possible on the old stack
Often: new information architecture (pages reorganised, sections merged or split)

A rebuild is appropriate when the site's technical foundation is causing ongoing pain that a visual redesign can't fix.

The price difference

Real numbers for Australian small businesses:

Redesign: usually $4,000 – $8,000 for a small site, $8,000 – $15,000 for a larger one. Takes 3–4 weeks. Lower risk, faster, preserves SEO automatically because URLs don't change.

Rebuild: usually $10,000 – $25,000 for a small site, $20,000 – $50,000 for a larger one. Takes 6–10 weeks. Higher risk (requires careful migration), slower, needs a redirect plan to preserve SEO.

The rebuild is usually roughly 2–3× the cost and 2× the timeline of a redesign on the same site. The reason people ask for a "redesign" when they actually need a rebuild is that the redesign sounds cheaper and less scary. Unfortunately, a redesign on top of a broken foundation usually doesn't solve the real problem.

When a redesign is the right call

Tick any of these:

The site loads fast (under 3 seconds on mobile)
The underlying platform is modern and maintained (React/Next.js, or a well-maintained Webflow build, or a clean WordPress install)
The SEO is working — you're ranking for relevant keywords and getting organic traffic
The site structure and content are fundamentally correct — the right pages exist, the right information is on each page
The main issue is that the site looks dated, off-brand, or generic
You like the CMS and the people who built the site, you just want it to look different

If most of those are true, a redesign is the right call. You're fixing the visual layer without disturbing anything that's working.

When a rebuild is the right call

Tick any of these:

The site is slow on mobile (over 4 seconds LCP) and the platform makes it hard to fix
The underlying tech stack is dated (WordPress with 20+ plugins, Wix, Squarespace with hacky customisations)
The CMS is painful to use and your team avoids updating content because of it
Adding new functionality requires workarounds, plugins, or code hacks that keep breaking
The SEO has plateaued and you've hit the platform's ceiling for optimisation
The information architecture is wrong — pages are in the wrong places, the sitemap doesn't match the business, content is missing
You're paying significant ongoing platform fees that a custom build could eliminate
The site gets visibly buggy and you're paying a retainer to keep it working

If three or more of those are true, a rebuild is the honest answer. A redesign will make it look better for a few months but won't fix the underlying problems.

The middle case: rebuild the frontend, keep the backend

Occasionally the right answer is a hybrid. Your backend is fine (a modern WordPress install, a working Shopify store, a solid database) but the frontend is broken. You don't need to rebuild everything — you need to replace the frontend while keeping the backend intact.

This is called a headless rebuild. You keep the CMS and the content, replace the frontend with a modern framework (usually Next.js), and connect them via API.

Typical cost: roughly 70% of a full rebuild. Timeline: 5–7 weeks. Risk: medium, because the backend stays stable while the frontend changes.

Headless rebuilds are usually right for:

E-commerce businesses on Shopify or WooCommerce that have decent product data but a slow/generic storefront
Content businesses with a huge WordPress database of posts that they don't want to migrate
Subscription businesses with user accounts and billing in an existing backend that's working

They're overkill for most small businesses. But for the right situation, they save significant cost and risk.

The decision framework

If you're trying to figure out which one you need, run this five-question diagnostic:

Q1: How does your site perform on mobile right now?

Run PageSpeed Insights. If Performance score is under 60, you have a technical problem that a visual redesign can't fix. → Lean toward rebuild.

Q2: Is the CMS working for your team?

Ask the person who updates content: "Is it easy to update the site?" If the answer is "yes", the CMS is fine. If the answer is "no, I avoid it because it's painful", the CMS is part of the problem. → Lean toward rebuild.

Q3: Are you happy with the underlying structure?

Walk through the site yourself. Are the pages in the right places? Is the navigation logical? Is the content organised in a way that makes sense? If yes → lean toward redesign. If you'd reorganise it if you could → lean toward rebuild.

Q4: Are you paying ongoing fees you could eliminate?

Count your monthly costs for the site: platform fees, plugin licences, maintenance retainers, premium hosting, CMS subscriptions. If the total is under $100/month → redesign is fine. If it's over $250/month → a rebuild often pays for itself in year two by eliminating the monthly spend.

Q5: Have you hit the platform's ceiling?

Is there something you want the site to do that the current platform can't support? A custom booking flow, a specific integration, a performance target, a content structure that doesn't fit? If yes → rebuild.

If you answer "redesign" to 3 or more questions, a redesign is enough. If you answer "rebuild" to 3 or more, the redesign is a waste of money and you need the rebuild.

The honest warning

The most expensive outcome is a redesign that turns into a rebuild halfway through.

This happens when the project starts as "we just need a visual refresh", the agency digs into the existing site, discovers that the underlying stack is too broken to polish, and ends up rebuilding the whole thing anyway. The client pays for both — the redesign quote plus the rebuild work — and the timeline doubles.

To avoid this trap, the smart move before starting any project is a discovery audit. Spend a day or two (either your own or a paid consultant's time) auditing the technical foundation before committing to either a redesign or rebuild. The audit answers the question: is the foundation solid enough for a redesign, or does this need a rebuild?

Most good agencies include this as a discovery phase in the first week of the project. If yours doesn't, ask for it.

What we usually recommend for small businesses

Honest general rule: if your site is on Squarespace, Wix, Webflow, or a WordPress theme and it's older than 2 years, the right answer is usually a rebuild. The ongoing costs and the performance ceiling make the redesign path uneconomical.

If your site is on a modern custom stack (React, Next.js, Astro, or a well-maintained headless CMS) and less than 3 years old, a redesign is usually enough.

If you're genuinely not sure which category you're in, book a free audit. We'll check the technical foundation of your current site and tell you honestly whether you need a redesign, a rebuild, or just a few targeted fixes. No pitch, no pressure, keep the audit.