What to do when your agency relationship isn't working

Three months into a six-month engagement, the agency that felt electric in the pitch has become difficult to reach. Deliverables arrive late or miss the agreed standard. Internal conversations end with “give it another few weeks”.

Delay consumes budget, evidence and trust. An aggressive conversation without diagnosis can also end a recoverable relationship or extend one that lacks the capability to improve.

The source's strongest advice is to identify the primary failure and the client's contribution before choosing recovery or exit.

Four failure patterns

Communication

The work may be competent while the client cannot see progress, risk or decisions. Updates are ceremonial, issues appear late and the sponsor chases information that should arrive through the agreed route.

Define what was promised and show examples. The source's steering-committee quotation, “I genuinely have no idea whether this project is on track”, needs verification before publication. It captures the consequence: client experience of delivery includes intelligibility.

Capability

The assigned team lacks an essential technical, research, design or delivery skill. Rework repeats and senior agency leaders enter day-to-day work to compensate.

Senior involvement can be legitimate assurance, so do not treat it automatically as evidence of a weak bench. Ask whether the original team and skill commitment match the sale.

The source's financial-services portal case, including four months and £80,000 overrun, needs project records, attribution and client permission.

Commitment

The pitch team disappears, response degrades or the live team lacks the promised context. Compare named roles, time, senior oversight and substitutions with the proposal and contract.

Avoid calling every staffing change bait-and-switch. People leave and availability changes. The test is whether the agency handled substitution transparently and preserved capability.

Working-model fit

One party expects fast iteration while the other needs documentation and formal approval. Informal communication, committee dates, risk tolerance or feedback style may conflict.

Neither side has to be wrong for the cost to become unsustainable. Some differences can be designed around; others should have been identified during selection.

These patterns overlap. A hidden capability gap can produce poor communication. Slow client decisions can look like weak agency commitment. State evidence and confidence before assigning cause.

Audit the client side

Ask:

• Was the brief and acceptance evidence clear?
• Did authorised people make decisions on time?
• Was client content, data and access available?
• Did stakeholders route changes through governance?
• Did priorities or outcomes move?
• Did the client respond to early agency warnings?
• Does the commercial model still fit the work?

This is not a way to excuse supplier performance. It prevents a recovery plan from correcting only half of the system.

Hold a diagnostic conversation

Bring a small set of observed examples:

• Deliverable and agreed expectation
• Decision or update that arrived late
• Rework and consequence
• Repeated concern across periods
• Effect on outcome, budget, risk or team

Describe the observation without attributing motive. Ask the agency for its diagnosis before prescribing the repair. Differences between the two accounts are evidence the plan must resolve.

Agree whether immediate protection is needed for security, legal, data, client or operational risk. Route serious matters through the contract and qualified owners.

Set a review date and evidence of improvement. “Try harder” cannot be assessed.

A bounded recovery

Recovery needs a temporary operating model.

Written commitments. Define deliverable quality, owners, review, communication, decisions and escalation. This may require a contractual change; involve commercial or legal owners where appropriate.

Short feedback loops. Increase cadence enough to expose problems early without moving all effort into reporting. Weekly can suit a short recovery period; risk and work determine frequency.

A few observable improvements. Examples might include a dated written update, named senior review before submission, resolution of an aged decision and delivery of one accepted artefact. Choose evidence connected to the primary failure.

Client commitments. Reserve decision-maker and reviewer capacity, freeze or govern priorities and provide required access.

A decision gate. On the agreed date, continue, change terms or exit based on evidence. Avoid moving the gate because the latest conversation felt positive.

Recovery can feel like a performance plan because it is designed to test whether the relationship can perform. It should remain fair, time-bound and focused on the work.

Recognise when exit is proportionate

Exit becomes more likely when:

• The agency offers reassurance without a credible cause or change
• Required capability cannot be supplied
• Commitments fail during recovery
• Trust is too damaged for evidence to be evaluated fairly
• Relationship management consumes the delivery capacity
• Continuing creates unacceptable risk or cost

One sign alone may be resolvable. The decision should consider contract, delivery state, alternatives, transition risk and the value still recoverable.

Do not prolong a relationship solely to avoid admitting the original selection failed. Equally, do not start a new procurement to escape a difficult conversation about client-side governance.

Exit with control and legal clarity

Review the contract before announcing or executing an exit. Confirm ownership, licences, payment, termination, notice, data, confidentiality, access and transition obligations with qualified advisers.

Create an asset and access inventory:

• Source code and repositories
• Design and research files
• Documentation and decision records
• Domains, hosting and deployment
• Analytics and supplier accounts
• Data, exports and deletion
• Work in progress and known defects
• Credentials through secure firm-owned routes

The source advises obtaining assets before the conversation because leverage changes. Do not take or copy material outside contractual rights. Preserve business continuity lawfully and negotiate missing handover obligations.

A managed transition can reduce risk when both parties can cooperate. The source's two-to-four-week range is illustrative; complexity and contract determine duration. Control incoming-partner access and protect confidential client information.

Learn before the next appointment

Record which selection, contracting or governance evidence would have exposed the problem earlier.

Did the pitch team differ from delivery? Were references relevant to the actual team and technology? Were acceptance criteria vague? Did the client test working style? Did the contract define documentation, access and substitution? Did early concerns wait too long?

The source argues that respected managing partners engage at the first sign of trouble. Prompt attention is useful, although every early issue is not a relationship failure. Establish a route where concerns can be raised without turning them immediately into escalation theatre.

An agency relationship is recoverable when both sides can name the cause, change the operating conditions and produce evidence within a bounded period. If they cannot, a controlled exit protects more value than another month of hopeful ambiguity.

If you want an independent view on whether your agency relationship is recoverable before committing to either a recovery or an exit, we offer a project recovery assessment. We've also built a relationship diagnosis checklist covering the four failure categories with observable symptoms for each, a go/recovery/exit decision guide, and the recovery plan structure I've described here. It's free and takes about ten minutes. Most people find it gives them a clearer picture than another internal conversation about whether things might get better on their own.