A particular moment happens in maybe half of the rebrand projects I see. The brand agency is six weeks in, they've nailed the positioning, the visual direction's coming together, the founder is excited. Then someone — usually the brand strategist, sometimes the web designer who's been pulled in to start scoping the site — looks at the existing website properly and the mood changes.

The problem they're realising: the new brand is going to look great on a website that doesn't work. The architecture is wrong. The page hierarchy doesn't match how the business actually sells. The conversion paths don't exist. The site is slow. The CMS is so constrained that even building the new visual identity into it is going to fight the platform.

This is the conversation where rebrand budgets accidentally double, and where founders feel ambushed by an agency that was supposed to be doing one job and is now telling them they need a different one.

My position: the situation is actually fine, but it needs to be diagnosed honestly and early, not surfaced as a surprise at the end. The brand agency should be looking at the website during the strategy phase, not the visual phase, and the conversation about whether the site needs rebuilding should happen before the new logo is finalised.

Why this happens so often

Brand agencies and web studios specialise. A brand agency that's good at positioning and visual identity is rarely good at technical web architecture, performance, or conversion design. That's fine — they're different disciplines.

The problem is the sequencing. The brand agency wins the project on the strength of the rebrand pitch, scopes the project around brand deliverables, and gets to the part where the brand book hands off to "implementation" — at which point they discover that implementation isn't a small step. The website that's supposed to receive the new brand isn't capable of doing it justice, and the cost of the website rebuild they're now recommending wasn't in the original budget conversation.

The founder feels surprised. The brand agency feels like they're doing the right thing by flagging it. The web studio they bring in to quote the rebuild feels like the bad guy because they're delivering an extra $40k of bad news.

None of these parties did anything wrong. The process was wrong.

The signs the website has bigger problems than the logo

When a brand agency starts a rebrand, there's a quick diagnostic they can run on the existing website that takes about an hour and predicts whether the website rebuild is going to surface. The signals:

The information architecture doesn't match how the business sells

This is the strategic one. The brand strategist has just spent two weeks understanding the business's actual value proposition, target audiences, and decision-making process. Then they look at the website. The navigation has five top-level items. The services are split into eight sub-pages that each describe one micro-service. The "About" page is buried. The contact form is on a separate page with no context.

If the website's structure has nothing to do with how the brand strategist now understands the business, the website needs rebuilding. A new logo on top of the wrong structure produces a prettier broken thing.

Performance is genuinely bad

Run PageSpeed Insights on the homepage and the most important service page. If LCP is over 4 seconds on mobile, INP is over 300ms, or the Lighthouse score is under 60, performance is a problem the rebrand can't fix. A rebrand can change what visitors see; it can't change how fast they see it.

The Core Web Vitals thresholds — LCP under 2.5 seconds, INP under 200ms, CLS under 0.1 — aren't aspirational. They're the line Google uses to differentiate page experience. A site failing all three is going to underperform regardless of how good the visual identity is.

The CMS can't render the new brand without compromise

The new brand book specifies a specific typography pairing — a display sans for headlines, a humanist serif for body text. The existing Squarespace site supports the body font but not the display font. The brand book specifies a colour system with eight defined uses (primary, secondary, accent, error, success, warning, neutrals). The existing WordPress site uses Elementor and the page builder doesn't have a coherent way to manage those tokens.

If implementing the brand on the existing platform requires constant compromise — close enough fonts, manually applied colours, custom CSS hacks — the platform is going to fight the rebrand for as long as the platform exists. Either the rebrand gets watered down or the site needs rebuilding on something that can render the brand faithfully.

The conversion paths don't exist

Most rebrands include a strategic component about who the brand is for and what action you want them to take. The website should be the primary surface for those actions. If the existing site's primary CTA is "Contact Us" buried in a top navigation, and there's no service-specific enquiry path, no qualifying form, no nurture content — the rebrand can't fix that. The website needs structural work that's not a brand exercise.

The CMS is making content updates painful

The brand book is going to include a tone of voice and messaging framework. The team is going to want to update existing content to match. If the existing CMS is painful enough to update that the team will avoid doing it — clunky page builders, no draft and preview, no version history — the content rewrites won't happen and the site will continue to sound off-brand for years.

How the conversation should go

The honest version of the conversation, said in week 2 of the brand project, not week 12:

"We've looked at the existing website while we've been working on the strategic positioning. Three things stood out: the architecture doesn't match how you're now describing the business, the performance is failing Core Web Vitals which is hurting search performance, and the CMS isn't going to be able to render the typography and colour system we're proposing without significant compromise.

We can complete the brand work as scoped and you'll have a great brand book. But to actually see the brand live, the website is going to need rebuilding. We can either rescope this project to include the web build, recommend a web studio to do that work separately, or you can decide the rebrand isn't the right priority right now and we can pause."

That conversation is uncomfortable. It's much less uncomfortable than the same conversation in week 12, when the brand work is done and the founder has committed the budget and now is being told there's another $40k needed.

What it costs when you do both together

The honest range for an Australian business doing a brand-and-web project together:

| Component | Low | High | |-----------|-----|------| | Brand strategy and positioning | $8,000 | $25,000 | | Visual identity (logo, palette, typography, brand book) | $12,000 | $40,000 | | Website strategy and content design | $5,000 | $15,000 | | Website design and build (custom code) | $15,000 | $60,000 | | Content writing | $4,000 | $20,000 | | Photography and asset production | $3,000 | $15,000 | | Total | $47,000 | $175,000 |

The lower end is a small services business doing a sensible rebrand on a sensibly-scoped website. The higher end is a mid-market business with multiple service lines, photography production, custom illustration, and a complex CMS implementation.

The number that surprises founders is the website strategy and content design line. That's the part that takes the brand work and translates it into site architecture, page hierarchy, and content structure. It's invisible work but it's the bridge between the brand book and the built site.

When it's actually right to do the website later

The case for not doing them together: some businesses are genuinely better served by rebranding now and rebuilding the website in 12 months once the rebrand has settled. This applies when:

The current website is technically fine and just visually off-brand. A skilled web designer can apply the new visual identity to the existing site in a week or two as an interim step. Real rebuild waits until the budget recovers.
The rebrand is partly experimental. If there's any uncertainty about whether the new direction is going to land — new market, new audience, new positioning — getting the visual identity out into the world via cheaper channels first (social, email, sales collateral) lets you stress-test before committing to the more expensive website rebuild.
The business genuinely can't afford both. A bad rebrand done well is better than a partial rebrand done badly. If the choice is a great rebrand and an unchanged website, that's a reasonable position to take and revisit the website in the next financial year.

The case against: in every other situation, doing them together is the better economic decision because the strategic alignment is built in, the team and timeline overlap, and the launched outcome is cohesive instead of disjointed.

The role of the website audit in the rebrand brief

The structural fix to the surprise-rebuild conversation is to include a website audit in the rebrand brief from day one. Before the brand agency even starts strategic work, an honest two-day audit of the existing site — by either the brand agency's web partner or a separate consultant — produces a clear assessment.

The audit answers: is the existing site capable of rendering the new brand, is it performing well enough technically, and is the architecture going to need restructuring? With that answer in hand, the rebrand budget gets scoped honestly, the timeline includes (or doesn't include) the web rebuild, and there are no surprises in week 12.

The audit costs $1,500 to $3,000. It saves projects from surprise scope blowouts that routinely run $30,000 or more.

The honest bottom line

When the rebrand reveals the website needs rebuilding, that's not a failure of the brand agency or a problem with the rebrand. It's the natural consequence of the brand work being done properly — when you understand the business clearly, the gap between the strategy and the current implementation becomes obvious.

The fix is to anticipate this. Audit the website at the start of the rebrand. Have the conversation about whether the website needs rebuilding before the brand work is finalised. Plan and budget for both as a coordinated programme, not as sequential surprises.

If you're in the middle of a rebrand and starting to suspect the website is going to need more than a visual refresh, book a free audit. I'll look at the existing site, the brand direction, and tell you honestly whether the platform you're on can carry the new brand or whether you're going to need to plan a proper rebuild alongside the rebrand.

When a Rebrand Reveals the Website Is the Real Problem (2026)