Big Logo, Small Fit: Rethinking Who You Actually Hire

Ask a room of marketing leads how they chose their agency and you'll hear the same three answers: they came recommended, they were on the framework, or they were the only ones who replied in August. Very rarely does anyone say 'because the shape of their team matched the shape of our problem'.

That's the gap worth closing. Freelancers, boutique agencies and network agencies are not better or worse than each other — they're different instruments. The trouble starts when you use a sledgehammer to hang a picture, or a picture hook to knock down a wall.

How the default roster choice happens

Most UK brands end up with a roster that was assembled by accident. A big network agency wins because it looks safe to a finance director. A freelancer wins because they're a fifth of the price and available on Monday. A boutique wins because the founder is charming and the deck was excellent.

None of those are terrible reasons. They're just not the reasons that predict whether the work gets delivered well six months later. And the things that actually predict it — scope clarity, handover discipline, whether your account lead survives the year — rarely feature in the pitch.

Three shapes of team, three kinds of risk

The freelancer

You're buying a person, not a capability. That's a feature when the work is well-defined and the person is senior: a GA4 migration, a landing page system, a paid search rebuild. It's a bug when the work needs three specialisms at once, or when the freelancer gets ill, or when they take a six-month contract elsewhere and your project is the thing that gets deprioritised.

The real risk isn't quality. It's continuity and coverage. Ask yourself honestly: if this person disappeared next month, could anyone else pick up the work from what's documented?

The boutique agency

Typically 10 to 40 people, senior-heavy, and often excellent value because you're paying for delivery rather than a global brand's property portfolio. Boutiques are strongest where strategy and craft need to sit close together — a website rebuild, a martech clean-up, a repositioning that has to land in the actual copy.

The risk here is capacity and concentration. One big client can quietly become 40% of their revenue, and suddenly your roadmap moves at their pace. It's also worth knowing how many of the people in the pitch will still be on your account in a year.

The network agency

You're buying process, breadth and a name that reassures the board. For genuinely complex, multi-market or heavily regulated programmes, that scaffolding has real value — particularly in financial services and healthcare, where compliance review can sink a smaller team.

The cost is distance. Layers of account management, change request culture, and a creative team that may be three time zones away. And when the account lead who sold you the vision moves on — which they will — the relationship often resets to whatever the contract says.

The costs that don't appear on the quote

Headline price is the least interesting number in the comparison. These matter more:

• Scope gaps. The cheapest proposal is often cheap because it excludes things you'll definitely need: analytics, QA, accessibility, copywriting, or the migration of 400 old URLs.
• Handover quality. Ask to see the handover pack from their last three projects. If it's a Loom video and a shared password, you've learned something useful.
• Account churn. Average tenure of an account lead is a fair question, and the answer tells you how much of your relationship is likely to survive.
• Seniority drift. The pitch team is rarely the delivery team. Get names, roles and time commitments in writing.
• Procurement overhead. Some brands spend more internal hours managing a large supplier than they would have spent doing the work with a smaller one.

A simple way to sort the options

Plot the work on two axes: how ambiguous it is, and how long you need the capability for.

High ambiguity, short duration — a repositioning sprint, a new market launch — usually suits a boutique or a senior freelancer with a specialist partner. You want judgement close to the work.

Low ambiguity, short duration — a platform migration, a tracking implementation — suits a specialist freelancer or a small technical shop. Clear brief, clear price.

High ambiguity, long duration — an ongoing growth programme across web, content and paid — is where a boutique with a genuine account structure earns its keep, or a network if you need multi-market coverage.

Low ambiguity, long duration — retainers for maintenance, hosting, support — suits almost anyone competent, so choose on responsiveness and cost, not reputation.

Most roster failures happen because the brief was ambiguous and the team was assembled for scale.

Questions to ask before you sign

Not the generic procurement list. These are the ones that surface the things that actually bite.

1. Who does the work day to day, and can I meet them before signature?
2. What's your average tenure for an account lead on clients like us?
3. Show me a recent handover document. Not a case study — the actual document.
4. What's explicitly out of scope, and what's the rate if we need it?
5. Who owns the code, the ad accounts, the licence keys and the data at the end?
6. What happens if the lead on our project leaves — notice period, knowledge transfer, replacement?
7. What have you said no to recently, and why?
8. Which of your current clients would you describe as a tricky relationship, and what did you do about it?

That last one is deliberately uncomfortable. The answer tells you more about how they behave when things go wrong than any credentials deck.

The honest answer is usually blended

Few ambitious UK brands need a single agency to do everything, and fewer still are well served by an all-freelancer patchwork with no one holding the thread. The pragmatic roster is a small senior core — a boutique or a lead consultant who owns the strategy and the roadmap — supplemented with specialists for defined pieces of work.

The thing to protect is accountability. Someone has to own the whole picture, and that someone shouldn't be you by default just because you're the client.