The Case for Smaller Teams

Accenture bought Droga5. Deloitte built a design arm. Everything in this industry is getting bigger. And for a certain kind of project, that's exactly wrong. Smaller teams with builders in the room produce better work, faster, for less. We'd know. We are one.
Bigger Isn't Always Better
Major professional services firms have recently consolidated dozens of acquired creative agencies into single practices numbering 7,000 or more people. The largest consulting-owned creative business now exceeds $19 billion in annual revenue (Fiscal Year 2023 Results). WPP, Publicis, Omnicom. The holding companies keep merging and acquiring. The direction is unmistakable. Bigger.
The logic is sound on paper. Scale provides geographic reach, multi-disciplinary capability, and the ability to staff massive global programs. For a Fortune 100 company rolling out a rebrand across 50 markets simultaneously, a 7,000-person organization makes sense. That's the pitch, and it isn't dishonest.
But most work isn't that. Most work (brand building, design systems, digital products, strategic websites, AI integration) doesn't require scale. It requires judgment. And judgment doesn't improve with headcount.
When you look at how creative work gets made, the advantages of scale thin out fast for the vast majority of engagements that land on agency desks every quarter.
What Gets Lost at Scale
The talent inside major consulting-owned creative practices and the big holding companies is often excellent. That's not the issue. The issue is structure. And structure shapes outcomes whether anyone intends it to or not.
Layers of Intermediation
In a large agency, the person who understands the client's business is rarely the person building the work. Between the strategist who heard the brief and the designer or developer who executes it sit account directors, project managers, creative directors, and sometimes entire teams dedicated to workflow coordination.
Each layer is well-intentioned. Each one introduces interpretation. By the time the brief reaches the maker, it's been filtered through multiple perspectives. The original intent gets diluted. Not through malice, but through the basic physics of organizational communication. Anyone who's played the telephone game as a kid understands the dynamic. It doesn't get better when you add more players.
The client said "confident but approachable." The account director wrote "bold yet friendly." The creative director briefed the team on "strong with warmth." The designer interpreted "bright colors and rounded type." Four translations in, and nobody made an error.
The cumulative drift is the error.
Creative by Committee
Large organizations require consensus. Consensus requires meetings. Meetings require compromise. The output of compromise is, by definition, the version that offended the fewest people. Not the version that would've been most effective.
Research by Les Binet and Peter Field, analyzing thousands of IPA advertising effectiveness cases, shows that creativity amplifies marketing impact by approximately 11x (IPA DataBank, "The Long and the Short of It"). That multiplier doesn't come from safe work. It comes from distinctive, sometimes uncomfortable creative choices that solve the sameness problem plaguing most brand work. Committee processes are structurally hostile to the kind of creative risk that produces that multiplier.
Look at the work that wins effectiveness awards. D&AD Impact, IPA Effectiveness, Effies at the highest tiers. Then look at how many layers of approval those campaigns survived. The correlation between organizational flatness and creative bravery isn't a coincidence.
Institutional Overhead
Large agencies carry costs that have nothing to do with the quality of the work. Real estate in expensive cities, middle management, global coordination infrastructure, back-office systems, enterprise software licenses, and partner profit margins. These costs are real. They're significant. And they're passed to clients.
When a client pays a large agency's blended day rate, a meaningful portion of that rate funds infrastructure that doesn't improve outcomes. The client is subsidizing the agency's complexity. Sometimes that's a rational choice. But it should be a conscious one, not an invisible tax.
The Distance Between Decision-Maker and Maker
In a boutique, the founder or senior partner is often in the room with the client and doing the work. The feedback loop is direct. A question gets asked and answered in the same conversation. A direction change happens in real time.
In a large agency, feedback traverses an organizational chart. The client says "I want it bolder" to the account manager. The account manager tells the creative director. The creative director tells the designer. "Bolder" has been interpreted three times before anyone opens a design file. And the designer, who might've asked a clarifying question that would've saved two rounds of revision, never had the chance to ask it.
This distance isn't laziness. It's architecture. Large organizations are built to manage complexity through hierarchy. But hierarchy is a lossy compression algorithm when applied to creative intent.
What Are the Structural Advantages of Small Teams?
Design-to-launch timelines among leading innovators have accelerated by over 20% in recent years, according to a 2025 innovation report. Speed isn't a luxury anymore. It's a competitive requirement. And small teams are built for it in ways that large organizations structurally can't replicate without significant reinvention.
Direct Access to the Builder
The person who understands the strategy is the person building the work. No intermediaries, no telephone game, no drift. When a client explains what they need, the person listening is the person who will execute. This eliminates an entire category of communication failure.
It also changes the quality of the conversation. A maker asks different questions than an account manager. They ask about edge cases, technical constraints, and implementation details that shape the final product. Those questions, asked early, prevent costly revisions later.
Faster Decisions
When the decision-maker and the maker are the same person (or sit three feet apart) decisions happen in hours, not weeks. No routing through approval chains. No waiting for the next status meeting. No scheduling a sync to align stakeholders before a direction can be confirmed.
This speed compounds. A project that involves 50 decisions over its lifecycle, each resolved in hours instead of days, finishes weeks earlier. Not because anyone worked faster, but because no one waited.
Deeper Context
A small agency works with fewer clients simultaneously. That's sometimes framed as a limitation. It's a feature. Each client gets more attention, more senior thinking, more continuity. The team remembers the conversation from three months ago. They don't need a re-briefing before every phase.
Context is expensive to rebuild. Every time a new team member joins a project or a handoff occurs between strategy and execution, institutional knowledge leaks. Small teams with stable rosters avoid this cost entirely. The people who started the engagement are the people who finish it.
Genuine Accountability
The founder's name is on it. There's no hiding behind process or organizational structure. If the work isn't good, the person responsible is visible and reachable. This creates a level of quality pressure that organizational hierarchies diffuse.
In a large agency, accountability is distributed. When something goes wrong, it's a "process failure" or a "communication gap." In a small shop, it's a person. And that person has every incentive to prevent it from happening in the first place.
Speed as a Structural Reality
That same 2025 innovation research found that 89% of top innovators prioritize understanding customer needs over shortcuts. Deep customer understanding scales down better than it scales up. A five-person team can immerse itself in a client's world in ways a 50-person team simply can't coordinate.
Small teams are structurally faster because they have fewer coordination costs, fewer approvals, and less organizational inertia. The speed isn't about working harder or cutting corners. It's about removing the friction that large organizations create by existing.
When Do Big Firms Make Sense?
Honesty matters here. Not every project is right for a boutique, and pretending otherwise would undermine the argument. There are engagements where scale is necessary.
Global Rollouts
When a company needs simultaneous execution in 50 or more markets, a global network provides something a small team can't. Bodies on the ground with local knowledge, local language capability, and local regulatory understanding. A five-person agency in one city isn't going to staff a simultaneous launch in Jakarta, Munich, and Sao Paulo.
Regulatory Compliance at Enterprise Scale
Some industries (financial services, pharmaceuticals, healthcare) require compliance review by hundreds of specialized consultants across jurisdictions. This is volume work that demands volume infrastructure.
Massive Media Buying
Volume discounts and platform relationships in media buying are real. A holding company spending billions annually across platforms negotiates rates that a boutique never will. If media efficiency is the primary objective, scale wins.
Full-Spectrum Consulting
When the engagement spans audit, tax, technology, and creative simultaneously, a large professional services firm offers integration that would require a boutique to coordinate across multiple independent partners. The convenience has value.
The point isn't that large firms are bad. Their structural advantages apply to a specific type of work. And most companies are hiring them for work where those advantages are irrelevant or counterproductive. When someone hires a 7,000-person organization to build a strategic website, they're paying for capabilities they'll never use.
Where Do Small Teams Win?
Top-quartile design performers outperformed industry benchmarks in revenue growth by up to two to one, according to a 2024 study on design-led companies (Design Value Index, 2024). That performance gap is driven by design quality, not design volume. And quality is where small teams hold a persistent edge.
Brand Building
Distinctiveness matters more than scale in brand work. A brand isn't an assembly line product. It's a point of view, expressed consistently. Small teams maintain that consistency because the same minds shepherd the work from strategy through execution.
Design Systems
A good design system requires craft, not headcount. It requires someone who understands both the visual language and the technical implementation. And can hold both in their head simultaneously. That person is more commonly found in a small, senior team than in a large organization where those disciplines are siloed.
Digital Products and Experiences
Iteration speed determines quality in digital work and creative production alike. The team that can prototype, test, and refine in a single week will outperform the team that takes three weeks to route a concept through approvals. Harvard Business Review research indicates that agile teams with fewer than ten members consistently deliver higher productivity and faster cycle times (Harvard Business Review, 2016).
Strategic Websites
Every page needs to earn its place. A strategic website isn't a template exercise. It requires someone who understands business goals, user behavior, content strategy, and technical performance. And can make trade-offs across all four simultaneously. Small teams make those trade-offs in conversation. Large teams make them in documents that get reviewed in meetings.
AI Integration
Specific context matters more than a large bench. AI implementation isn't a commodity service yet. It requires deep understanding of a client's specific workflows, data, and objectives. A small team that spends weeks inside a client's operation will build something more useful than a large team that applies a standardized methodology.
Content Strategy
Voice and point of view can't be produced at scale without losing what makes them distinctive. Content that sounds like it was written by a committee reads like it was written by a committee. Audiences can tell. They've always been able to tell.
How Should You Choose the Right Model?
Mid-market brands increasingly split engagements between specialized boutiques and large firms based on project type, rather than awarding everything to a single partner, according to a 2024 agency workforce report. That's a rational approach. And a telling one.
Match the Model to the Work
If your project requires global coordination across dozens of markets, hire for scale. If it requires judgment and craft (a rebrand, a digital product, a strategic website) hire for talent density. The worst outcomes happen when companies default to scale for work that needs precision.
Ask Who Will Do the Work
Not who will present in the pitch. Who will open the design file, write the code, develop the strategy. If those people aren't in the room during the sales process, they won't be in the room during the project.
This is the single most important question you can ask. The answer tells you everything about the engagement model.
Evaluate Speed and Accountability
How many layers exist between you and the person building? How quickly can a decision be made and acted on? Ask for a specific example. "If I send feedback at 2 PM on a Tuesday, when does the maker see it, and when do I see a revision?" The answer reveals the organizational architecture more honestly than any capabilities deck.
Consider Continuity
Will the same team be with you from start to finish, or will there be handoffs? Handoffs cost more than they save. Every transition loses context. Every new team member needs ramp-up time. The cheapest, fastest, highest-quality path is the one where the people who started the work are the people who finish it.
Calculate the Real Cost
A large agency's day rate includes overhead you may not need. Office space you'll never visit. Management layers you'll never interact with. A smaller team's rate may be higher per person, but the total cost is often lower per outcome because there are fewer people and less waste. Compare total project cost and timeline, not hourly rates.
The Structural Reality
The industry is consolidating because consolidation serves the firms doing it. More revenue, more capability on paper, more bargaining power. These firms didn't build 7,000-person creative practices because clients were asking for it. They built them because consolidation makes strategic sense for the firms themselves.
That's fine. It's how business works. But clients should understand that the incentives driving consolidation are the agency's incentives, not necessarily theirs.
For the kind of work that requires judgment, craft, and direct accountability (which is most of the work) smaller teams aren't a compromise. They're a structural advantage. The person who heard your brief is the person building your product. The feedback loop is measured in hours, not weeks. The quality pressure is personal, not procedural.
Small teams aren't right for everything. They're right for more than the industry wants you to believe.

