There is a test you can run on any agency relationship. Ask yourself: do I understand more about my digital investment now than I did before we started working together?
If the answer is no, something has gone wrong.
The dependency model
Most agencies do not set out to create dependency. But the structure pulls them there.
Revenue is tied to hours. More hours means more revenue. Building client capability reduces hours. The model punishes efficiency.
The result looks like this: the CMS stays opaque. Analytics are presented in dashboards the client cannot interpret without the agency's narration. Decisions about the website pass through the agency because nobody else knows how anything works.
It feels like service. It is extraction.
The client pays more over time but learns nothing. Eventually they plateau, resent the spend, and leave — without referrals, often telling the next agency exactly what went wrong.
What capability building looks like
An agency that builds capability does three things:
It teaches content management. The client learns to edit, publish, and manage their own content. They can update a page, publish a blog post, and adjust messaging without making a phone call. The CMS is their tool.
It explains strategy. The client learns to read their analytics, understand what is working, and make informed decisions about where to invest. Every recommendation comes with reasoning. If the client cannot articulate why something is being done, the agency has not done its job.
It protects ownership. The client owns their design system, their content, their data, their domain. Nothing is locked behind proprietary tools. If they leave, everything goes with them.
Where the agency still earns
Capability does not mean the client does everything. It means the line between "what the client handles" and "what the agency handles" is visible and deliberate.
The agency handles infrastructure: security patching, performance monitoring, SSL management, CDN configuration, plugin updates, compatibility testing, backups, disaster recovery. These are specialist operations with real downside if neglected or done wrong.
A business owner who patches their own WordPress plugins is not building capability. They are misallocating their time and accepting risk they are not qualified to manage.
The principle: clients should own anything that makes their business smarter. They should delegate anything that carries downside risk if neglected.
Teach them to fish for content and strategy. Handle the plumbing and electricity.
Why it works commercially
The instinct is to worry: if clients can do things themselves, why would they keep paying?
The data suggests the opposite. Deloitte's research on digital maturity found that higher-maturity organisations are roughly three times more likely to report revenue growth above their industry average. They invest more — because they understand what they are investing in.
Capability building moves clients up the maturity model. A Stage 1 client who learns to manage content becomes Stage 2. A Stage 2 client who understands data becomes Stage 3. Each transition increases willingness to invest.
Dependency does the opposite. It keeps clients stuck at whatever stage they entered. They pay more but get no smarter.
The retention paradox
Clients who feel capable and free to leave are the clients who stay longest.
The decision to stay becomes a genuine choice — not a hostage situation. Trust reduces churn more reliably than contracts or complexity.
A capable client is also a better referral source. They can articulate what they got, why it worked, and what the money bought. A dependent client cannot — they just know they pay a monthly fee and things mostly work.
The quality of the referral is a direct function of the client's understanding of the value they received.
The AI accelerant
AI makes commodity execution cheap. Any business can get a website built for near-zero cost by a model.
What AI cannot replicate is the judgement and pattern recognition that comes from hundreds of real engagements. An agency that hoards execution as its value proposition is competing with a machine.
An agency that builds client capability — teaching them to think about digital as a business function — is providing something AI accelerates rather than replaces. Digital leaders already outperform laggards by two to six times on shareholder returns. The gap will widen as AI amplifies the advantage of understanding.
How to tell which model you are in
Ask your agency three questions:
- Can I edit my own website without calling you?
- Can you explain — in plain language — why we are doing what we are doing?
- If I left tomorrow, would everything come with me?
If the answer to any of these is no, you are paying for dependency, not service.
That does not mean your agency is malicious. It probably means their revenue model rewards the wrong things. But the cost is yours either way.
This article applies develop-capability-not-dependency.
Sources
- Uncovering the connection between digital maturity and financial performance — Deloitte Insights, 2020
- Rewired and running ahead: Digital and AI leaders are leaving the rest behind — McKinsey & Company, 2024
- It's Time for Agencies to Stop Using Billable Hours to Prove Value — Adweek, 2018