Why agencies that don't make this shift will get left behind

The digital agency model is broken. Not in a dramatic, falling-apart way, but in a slow, structural way that most people inside it haven't fully clocked yet. The work still comes in. The projects still get delivered. But the model that built these businesses, take a brief, execute it, send an invoice, repeat, is running out of road.

I know because I've lived both sides of it. I started my career as a Project Manager in a traditional agency setup. Today, I operate as a Delivery Manager and consultant, sitting on client leadership teams, challenging briefs, and shaping strategy. The shift happened gradually, driven partly by a deliberate strategic repositioning at CDS and partly by my own refusal to keep operating in a way that felt increasingly limiting.

This post is part personal reflection and part industry analysis. I want to walk through what the agency-to-consultancy shift actually looks like in practice, why it matters, and what the data says about where the market is heading. If you work in or with a digital agency, this might challenge some of the assumptions you're operating under.

The traditional agency model: what's actually wrong with it

Let me be specific about what I mean by the "agency model" because this isn't about bashing agencies. It's about being honest about where the limitations are.

In a traditional agency setup, the relationship with the client is transactional. The client has a requirement, you scope it, you build it, you deliver it, you invoice. Rinse and repeat. The work is project-based, often won through competitive pitches, and measured primarily on output: did you deliver what was asked, on time and on budget?

For a long time, this worked. But here's where it starts to crack:

The agency model is inherently reactive. You wait for the client to tell you what they need. You don't question the brief because the brief is the contract. You don't push back on scope because pushing back risks the relationship. And you definitely don't suggest work the client hasn't asked for because that's "upselling" and it feels uncomfortable.

The result? You become a pair of hands. A very skilled, very expensive pair of hands, but a pair of hands nonetheless. The client controls the strategy, you execute it. And when budget gets tight or priorities shift, you're the first cost to cut because you're a line item, not a partner.

The data backs this up. Project-based agencies see annual client churn rates of around 42%, with average client relationships lasting just 24 months. Compare that to retainer and partnership-based models where churn drops to around 18% and client lifespans nearly treble to 56 months. The maths is brutal: if you're constantly replacing nearly half your clients every year, you're spending more time and money on new business than on delivering great work.

The consultancy model: what it actually means in practice

When I talk about the "consultancy model," I'm not talking about becoming McKinsey. I'm talking about a fundamental shift in how you position yourself with clients and how that changes everything about the way you work.

At CDS, this shift has been deliberate. The Bailie Group has strategically positioned itself to allow CDS the autonomy to evolve its model, moving from a pure execution agency towards a consulting-led approach. My role has changed as part of that. I went from Project Manager, focused on timelines, budgets and task management, to Delivery Manager and consultant, focused on value, outcomes and strategic partnership.

In practice, that means:

I sit on my client's leadership team as the Account Delivery Lead. I'm not an external supplier attending a weekly status call. I'm part of the decision-making structure.

I challenge briefs rather than just accepting them. When a client sends a requirement, my first question is "why?" not "when do you need it?" Understanding the strategic objective behind the work changes what you deliver and how you deliver it.

I proactively suggest improvements and new approaches. Instead of waiting to be told what to build, we turn up with recommendations, backed by data and evidence from the work we're already doing.

I'm a subject matter expert in the client's domain, not just a generalist project manager who could be working on any account in any industry.

The difference between these two modes of operating isn't subtle. It's the difference between being replaceable and being indispensable.

The role evolution: from Project Manager to Delivery Manager

This shift isn't just happening at an organisational level. It's fundamentally changing what it means to manage delivery in a digital environment.

As a Project Manager, my world was defined by the iron triangle: scope, time, cost. Success meant delivering to spec, on time, on budget. The client relationship was managed through formal governance, change requests and status reports. I was measured on output.

As a Delivery Manager, my world is defined by outcomes. Did the work create value? Did the client's position improve? Are we solving the right problem? The relationship is collaborative, not contractual. I'm measured on impact.

This isn't just a title change. The skills required are fundamentally different:

The market is reflecting this shift. The UK consulting sector is forecasting growth of 5.7% in 2026 and 7.4% in 2027, with 78% of consultants identifying digital technology as the primary growth driver. Meanwhile, the traditional agency subsector of computer programming, consultancy and related services fell 6.7% from 2022 to 2023. The direction of travel is clear: clients want strategic partners who understand their business, not execution shops who understand their CMS.

What this means for resource and commercial models

One of the biggest practical implications of this shift is what it does to how teams are structured and how work is commercialised.

In the agency model, you staff up for projects and scale down when they end. Utilisation is king. Every hour needs to be billable. Bench time is wasted time. This creates a cycle where people are overworked during delivery and underutilised between projects, with constant pressure to sell the next thing.

In the consultancy model, the relationship is ongoing. You're embedded with the client. The revenue is more predictable, the team is more stable, and crucially, you have the time and space to actually think strategically rather than just executing at pace.

The market data supports this: retainer-based agencies achieve 2.3 times better client retention than project-based counterparts. A 5% increase in client retention can boost profits by 25 to 95%. And larger agencies that invest in dedicated account teams and comprehensive service integration achieve industry-best retention of around 12 to 15%.

The commercial argument for the shift isn't ideological. It's mathematical. Longer relationships mean more revenue per client, lower acquisition costs, more predictable forecasting, and teams that can actually develop deep domain expertise instead of context-switching between accounts every few months.

What this looks like in the real world

I can talk theory all day, but the shift only matters if it changes outcomes. Here are two examples from my own experience.

On my largest account, we had been operating in a purely transactional way for a long time. Client sends requirement, we build it, we invoice, done. The work was fine but it was limited. There was no strategic conversation happening, no proactive thinking, and no real understanding of where the client was trying to get to.

A face-to-face meeting changed everything. By sitting down with the client's leadership team and genuinely listening to their strategy, their objectives, and their challenges, we unearthed a completely different way of working together. We stopped waiting to be told what to build and started suggesting improvements, becoming subject matter experts in their space, effectively sitting on their team rather than next to it. We went from passing by one another to working as one.

On a separate account, I identified an opportunity to introduce AI agents into our Azure DevOps workflows to support the team's delivery. Rather than just accepting the existing tooling and processes as they were, I proactively explored how AI could reduce manual admin, improve board hygiene, and give us better data to work with. I built a case for it, presented it to the team, and we're now piloting it together. An agency PM wouldn't typically have the mandate or the curiosity to drive that kind of innovation. A consultancy Delivery Manager does, because the client trusts you to improve how you work together, not just deliver what's been agreed. I'll be writing more about this in a future post.

Why agencies that don't make this shift will get left behind

The market is moving. Clients are getting smarter. Budgets are getting tighter. And the organisations that will thrive are the ones that can offer more than just execution.

The consulting sector is growing at nearly 6% year on year. Digital transformation and AI are driving 78% of that growth. Meanwhile, traditional agency models are facing headwinds: clients bringing work in-house, commoditisation of execution services, and increasing pressure on day rates.

The agencies that survive will be the ones that evolve. That means:

Moving from project-based to partnership-based relationships. Moving from output measurement to outcome measurement. Investing in people who can think strategically, not just execute efficiently. Building domain expertise rather than generalist capability. Embedding with clients rather than servicing them from a distance.

This isn't a prediction. It's already happening. The only question is whether you're ahead of the curve or behind it.

Where I'm heading

I'm still relatively early in this transition. My role has changed, my approach has changed, and the results are already visible. But the cultural shift across the wider business, and across the industry, is still in progress.

What I know for certain is that I'm never going back to the old way. The transactional, brief-in-brief-out model of delivery was limiting for me personally, limiting for my teams, and limiting for the clients we work with. The consultancy approach is harder, it requires more thinking, more confidence, and more genuine expertise. But it's infinitely more rewarding and, crucially, it delivers better outcomes for everyone involved.

If you're a PM or Delivery Manager in an agency right now, I'd encourage you to start asking different questions. Don't just ask "what does the client want us to build?" Ask "why do they want to build it?" Ask "what problem are we actually solving?" Ask "where does this sit in their strategy?"

You might be surprised where those questions take you.

Find me on LinkedIn if you want to continue the conversation, or drop me a message on the contact page.