The agency pitch is appealing on its face. "We do brand and web in one team — one project plan, one point of contact, no handover gaps, one invoice." The argument writes itself. Hiring two specialists creates coordination overhead, the brand and the website end up disjointed, and the founder ends up project-managing two agencies who don't quite talk to each other.

The counter-argument is depth. A studio that does both rarely does either at the level a specialist does. Brand strategy is its own craft; web architecture is its own craft. The studio that promises both is averaging across two disciplines, and the averaging usually shows.

Both arguments are right depending on the project. My position is that for Australian small-to-mid business projects under about $60k total, the integrated approach is usually fine and sometimes better. Above that threshold, the specialist-on-each-side approach produces a better outcome, even with the coordination cost.

But there are signals — six of them — that distinguish a legitimate integrated studio from one that's claiming capability they don't have. If you're being pitched by a "one studio for both" outfit, these are the things to look for.

The case for the integrated approach

Real reasons to use a single studio for brand and web:

Smaller projects don't have the budget for coordination overhead

If your total brand-and-web budget is $40k, paying a $4k handover line item is 10 percent of the project. The integrated studio absorbs that cost into general overhead, which means more of your money goes to the actual work. For projects under $60k, this is genuinely a material difference.

The brand and web work share infrastructure

When the same studio does both, the brand strategy informs the website structure, and the website design constraints inform the brand decisions. Photography commissioned for the brand can be the same photography rendered on the website. The voice document and the web copy are written by people who attended the same brand strategy session. The integration isn't a coordination problem to solve; it's a default state.

Iteration is faster within a single team

When the founder asks for a small change — "can we soften the navy slightly in the dark mode version of the logo?" — it propagates through brand and web simultaneously without an inter-agency conversation. The studio's internal Slack handles in a day what would be a three-email thread between two agencies.

Smaller businesses often need a generalist's instinct

A brand strategist who's done 200 brand projects but never built a website thinks about brand differently than one who's done 80 brand projects and 80 websites. For a small business where the brand work has to be commercially functional from day one — not just strategically clean — the studio that has built websites tends to make brand decisions that translate better.

The case against

Real reasons to use specialists on each side:

Strategic positioning is its own discipline

If the rebrand is genuinely strategic — repositioning a business, naming a new entity, defining how the company differentiates in a competitive market — that work benefits from a dedicated brand strategist who's done that specific work hundreds of times. The integrated studio's "brand strategist" is often a designer with strategy adjacent skills, not a positioning specialist.

For projects where the strategic component is the value being purchased, the specialist is worth the premium.

Technical web architecture is its own discipline

A senior web architect making decisions about CMS structure, performance budget, accessibility, SEO migration, and component system design is bringing depth that an integrated studio's web team often doesn't have. If the website is going to be a serious commercial asset — high traffic, complex content, deep integrations — the specialist web studio is going to produce a more durable result.

Larger projects have the budget for coordination

A $120k brand-and-web project can afford $8k of coordination overhead. The trade-off shifts. Above $60k or so, the depth of specialist work outweighs the coordination friction, and the result is a better outcome that justifies the additional cost.

Six signals that distinguish a good integrated studio from a bad one

If you're being pitched by a studio that claims to do both, these are the diagnostic questions to ask. Good answers look one way; not-good answers look the other way.

1. Show me three projects where you did brand and web together. What was the brand strategy work specifically?

The good answer talks about positioning, audience research, competitor analysis, naming decisions if relevant, voice and messaging framework. There are documents (positioning briefs, brand strategy decks, naming exploration) the studio can show.

The bad answer talks about logo design, colour palette decisions, and visual moodboards. The brand work was essentially visual identity work with no real strategic foundation.

2. Who specifically does the brand strategy work in your team?

The good answer names a person, that person has 5+ years of brand strategy experience specifically, and they're not the same person who's running the web design or build.

The bad answer is that the senior designer or the studio principal does brand strategy "when the project needs it" — meaning brand strategy isn't a discipline within the studio, it's an occasional add-on that happens at the discretion of the most senior person available.

3. What's your performance budget on the websites you build?

The good answer has a number. LCP under 2 seconds, INP under 200ms, total page weight under 800KB, Lighthouse mobile score above 90. They can show you the PageSpeed Insights results on their past projects.

The bad answer is that they build "fast" websites without specifying what fast means. Or worse, the past projects they show land in the 60s to 70s on Lighthouse mobile, which suggests "fast" is aspirational rather than measured.

4. What CMS do you build on and why?

The good answer either has a specific opinion (we build on Sanity for content-heavy sites and Payload for sites that need an admin UI for editors, here's why) or has a context-aware framework for choosing between options.

The bad answer is that they build on whatever the client wants, or they only build on one platform (usually WordPress or Webflow) without acknowledging the trade-offs of that platform.

5. What does your accessibility approach look like?

The good answer mentions WCAG 2.2 AA as a baseline, talks about automated testing tools, manual keyboard navigation, screen reader testing on at least one assistive technology, and explicit accessibility audits as a deliverable. They can show you a past project's accessibility report.

The bad answer is that accessibility is "designed in from the start" without specific evidence, or that accessibility is treated as a compliance add-on rather than a design discipline.

6. How do you handle the SEO migration when the website's getting rebuilt?

The good answer talks about URL audits, 301 redirect maps, metadata preservation, Search Console handover, post-launch monitoring. There's a specific process and it's a costed line item in the proposal.

The bad answer is that "SEO is included" without specifying what that means, or that SEO is treated as a post-launch concern rather than a migration concern.

The "we'll subcontract" red flag

A specific failure mode worth flagging: the integrated studio that wins the project on the strength of an integrated pitch and then subcontracts the web build to a developer they don't work with regularly.

This is worse than either pure-integrated or pure-specialist because you're getting integrated communication overhead (one studio managing the relationship) and specialist execution friction (the developer the studio hired this month isn't deeply familiar with the studio's brand work).

Ask directly: who is going to build the website, are they employees of your studio or contractors, how long have they been working with you, and can I meet them before signing? If the answer is a contractor the studio met on Upwork last quarter, that's worse than going specialist on both sides.

When integrated is genuinely right

The scenarios where I unambiguously recommend the integrated approach to Australian small businesses:

Total budget under $40k. The coordination overhead matters more than the depth gap at this scale.
Single-person service businesses. A solicitor, a financial advisor, a consultant doing a brand and website together as a launch package. The integration matters and the strategic depth required is modest.
Time-pressed projects. A business needs to ship in 10 weeks, doesn't have time for two-agency coordination, and the brand work is relatively contained.
First-time rebrand for a young business. The business hasn't matured into a clear strategic position yet, so the brand work is exploratory and benefits from being tightly coupled with the commercial implementation.

When integrated is the wrong call

The scenarios where I'd push back on the integrated pitch:

Total budget over $80k. The depth gap on either side matters too much to absorb.
Genuinely strategic brand work. Repositioning, naming, multi-brand systems, brand architecture decisions. These benefit from dedicated brand strategists.
High-traffic websites where performance and SEO are commercial drivers. The technical depth required argues for specialist web.
Sophisticated content operations. Newsrooms, content marketing operations, sites with complex publishing workflows. The CMS implementation is its own engineering discipline.

How to test the integrated studio's actual depth

Beyond the six diagnostic questions, three practical tests separate genuinely capable integrated studios from generalists overselling their range.

Ask to see the brand strategy work, not just the visual. Most integrated studios will show you logos, websites, and brand books. Ask specifically for a positioning brief or strategy deck from a recent project — the document that defined who the client is for, what they stand for, and how they differ from competitors. If the studio has these documents, brand strategy is a real discipline within the team. If they don't, the brand work is essentially visual identity work without strategic depth.

Ask to walk through a recent website build technically. Get the studio to show you the GitHub repository, the deployment setup, the CMS configuration, and the performance audit for a recent project. A studio with real engineering depth will walk you through these comfortably. A studio that relies on subcontractors or low-code builders will struggle to show you the underlying technical work because they don't manage it directly.

Ask for a 30-minute call with a recent client. Not the contact at the agency's most successful project — the second-best project from 12 months ago. Talk to that client about how the brand and web work integrated, where the gaps showed up, and how the studio handled them. Real client conversations surface what testimonials hide.

If the integrated studio passes all three tests, the integrated approach is probably the right call for your project. If they pass one or two and struggle with one, you're looking at a studio that's strong on one side and weaker on the other — which is fine if the strong side matches your priority, less fine if the weak side is the priority.

The honest bottom line

The "one studio for both" pitch isn't a scam and isn't a misdirection. For the right projects it produces better outcomes than two specialists working in coordination. For other projects it produces a watered-down version of both disciplines.

The question isn't whether integrated studios are good or bad in general. It's whether the studio in front of you, on the project in front of you, is the right answer. The six signals above are how you tell, and the budget threshold is the rough cut.

If you're being pitched by an integrated studio and you want a second pair of eyes on the proposal before you sign, book a free audit. I'll look at the studio's past work, the proposal, and the project scope, and tell you honestly whether integrated is the right call or whether specialists on each side would produce a better outcome.

One Studio for Brand and Web? 6 Signals to Decide (2026)