How to deal with difficult clients as an agency

Key takeaways

• Learning how to manage difficult clients mostly means fixing the work around them: unclear scope, disputed sign-off, lost versions, files they can’t open, and requests for old work.
• Write down scope, revision rounds, and signoff requirements before kickoff, and establish a record of every approval, including who said yes to which version.
• Clients should be given one clean place to receive finished work, and freelancer access ends when the project does.
• Old client work stays searchable in an archive, so you can answer a request to dig up a two-year-old file in minutes instead of days.
• Some clients cost more than they pay, and a clear walk-away point protects the rest of your roster.

‍

Learning how to deal with difficult clients as an agency starts with sorting the friction into two piles: what you can plan for and what you can’t.

Some clients are simply impossible. They change direction at midnight, go silent for two weeks, and reply-all with a new idea after launch, and no process will change their temperament. 

A surprising share of the pain is avoidable, though: the client who swears they never approved the cut, the one who can’t open the file you sent, the one asking for a spot you delivered two years ago. 

Each of those traces back to something that was never written down, recorded, or findable. 

This post covers both piles: how to prevent the moments you can plan for, how to handle the ones you can’t, and when to walk away.

What makes an agency client difficult?

Dealing with difficult clients gets easier once you can identify the moment things go wrong. Some clients are demanding by temperament, but most agency friction is structural, and it repeats. Scope grows without a conversation, feedback rounds continue without end, nobody can verify approvals or find files, and so on. 

The table below maps each common behavior to a likely cause and ways to prevent it. For the features that matter once client volume climbs, see “7 high-utility MAM features for high-volume agencies.”

Difficult client behavior, its usual cause, and what prevents it

Remember: Some clients are just impossible…and no process fixes that

Process can’t fix every client. A few arrive with a temperament that no scope document will soften, and it helps to recognize the type before you spend a month trying to engineer around it. 

Four show up in nearly every agency:

• The midnight rewriter sends a brand-new direction at 11:48 p.m. on delivery day. You can’t stop the email, but a written change-order step turns “just one small thing” into a priced decision.
• The vanishing approver goes silent for two weeks, then expects the original deadline to hold. Turnaround commitments in the scope mean their silence moves your delivery date instead of making you the late one.
• The committee has eleven opinions and one signature. You can’t shrink it, but naming one person who consolidates feedback and signs off keeps eleven opinions from becoming eleven rounds.
• The “I made my own cut” client arrives with a rough edit and strong feelings about it. Ask what problem it’s solving, then bring the conversation back to the agreed brief.

A quick test for sorting the two piles: if a written record would have settled the argument, it’s a process problem, and the fixes in this post apply. 

If the argument would have happened anyway, it’s a temperament problem, and the moves in the next sections are your toolkit. 

You can’t change the client, but you can change what the record looks like the next time they do it.

Set scope, revision rounds, and sign-off rules before kickoff

Most scope arguments are decided before the first frame is shot, because the scope document either leaves space for a new idea to slip in or it doesn’t. Write it specifically enough that an out-of-scope request is visibly outside it. 

At minimum, the scope document should cover:

• The deliverables, formats, and runtimes the client is paying for
• The number of revision rounds included, and what an extra round costs
• The one person who gives final sign-off and who consolidates everyone else’s feedback before it reaches you
• The turnaround the client commits to at each stage, so a late response moves your delivery date instead of making you the late one
• The change-order step that applies when a request lands outside scope

Pick the round count and put it in the contract, because a number you both agree to is much easier to point to than a norm you both assumed. The same goes for sign-off: Decide where approval happens before the first draft goes out, because an approval given on a phone call is hard to point to three weeks later. A content approval workflow that records who approved which version, and when, means that conversation never depends on anyone’s memory.

Fix the process behind the difficult client

Each of the following nine issues has the same shape: A client says something you can’t immediately disprove, and the fix is to establish a simple upfront process that documents the actual answer so you can provide it down the line. 

1. When the client says they never approved it

An approval given on a call, in a reply-all, or in a chat message holds until someone disputes it, and then it comes down to whose memory wins. Running approval through the asset itself takes that argument off the table. 

In Iconik, a reviewer opens a secure link, comments on the video, and sets an approval status of approved or rejected. The Approval Status panel lists every reviewer and shows whether each one approved, rejected, or hasn’t chosen yet.

You can require every assigned reviewer to approve before the asset counts as approved, so one “yes” from a single contact doesn’t stand in for the whole client team. When reviewers give conflicting answers, the status shows as mixed, which tells you the disagreement sits on the client’s side before you start another round. 

Reviewers don’t need an Iconik account, and Iconik users completed 185,000 approvals in 2025 through this kind of video review and approval workflow.

2. When nobody knows which version is final

Version confusion usually starts with feedback scattered across email threads, chat messages, and a link to a cut that’s two versions old. If your team still collects notes by email, here’s insight into why email review breaks down and what it costs in rework. 

In Iconik, each asset version stays within the same record, so comments and approval history remain attached, and you can still open comments on older versions. Playlist shares can include the latest version, all versions, or specific versions, which means you can show a client exactly which cut they signed off on. 

This checklist on simplifying video feedback is a quick way to audit your current process.

3. When the client can’t find or open what you sent

Large files bounce, links expire, and the client forwards your message to someone in IT. Delivering finished work from one place fixes most of these issues. 

Brand Portals in Iconik give you a branded presentation space for a curated set of finished assets, with your logo, cover image, theme, and fonts, and one link that recipients can open without an Iconik account. Brand Portals are available on Professional and Enterprise plans, and the Brand Portals documentation covers setup.

Standard share links add expiry dates, passwords, and download restrictions, and each recipient gets a unique link so you can see how often it’s been opened. 

4. When the approved cut has to go live on the client’s channels

Approval isn’t the end of the job, and the gap between “approved” and “published” is often where agencies get burned. A stale version gets uploaded, metadata gets retyped from memory, and the client emails to ask whether it went out. 

The Iconik Publish Panel closes that gap from the finished asset. A team picks a publishing template, chooses one or more connected destinations, reviews the published metadata, selects a thumbnail, and publishes without downloading and re-uploading the file. Publishing can also be triggered by Iconik’s automation engine when you want it to run without someone clicking.

The Posts page answers the “Did it go live?” question directly. It lists every post from your domain with the platform, status, when it went live, and who published it, plus performance data — and one click takes you back to the source asset. The Publish Panel is available as an add-on.

Discover how agencies run approval and delivery from one place: Explore the Iconik demo.

5. When a freelancer leaves and their access stays

Scaling an agency usually means growing the contractor roster, and every freelancer who keeps a login after the project ends is an exposure across every client they touched. The fix is to scope access when you invite someone and end it when the work ends. 

In Iconik, an invite link can preset a new user’s teams and role groups, so a contractor arrives with access to the assets for one campaign and nothing else. Invite links expire after seven days, which limits how long an unused one stays live. Because several people can use a single link, send individual freelancers a direct email invite and keep invite links for team onboarding.

When the engagement ends, a domain owner can delete the user. For clients that need ongoing access to finished work, shares carry their own expiry dates, so access ends on a date you set when you hand over the work

6. When nobody can find last quarter’s files

Files go missing on an agency’s server in a predictable pattern. The person who named everything leaves, the naming convention leaves with them, and the library turns into a guessing game. 

Two habits keep files findable: 

• Organizing work into collections by client and project: An asset can sit in more than one collection without being copied, so the same clip lives under the client and the campaign without a duplicate to keep track of. 
• Searching by footage content instead of file name: With media asset search, you can search for spoken words from transcripts and recognized faces and objects, so “the interview where the founder mentions the launch” returns the correct clip without anyone having to remember a file name.

7. When the client asks for files from two years ago

Requests for old work arrive with no warning and a short deadline, and the answer determines whether the client sees you as organized or as a risk. An archive only helps if retrieval stays quick. 

Using Iconik, archive rules can move content off production storage on a set schedule, keeping the archived asset searchable through search filters. When the client request arrives, you can find it, restore it, and deliver it.

Ginkgo Agency, a South African content agency, moved a 270TB archive to the cloud so people can browse it from anywhere and request either an edit-ready proxy or the hi-res original through the portal. This case study notes the archive has a high reuse rate, which is the point of keeping it findable. Once you can find old work in minutes, you can offer retrieval and reuse as a service to clients. 

For the full picture, see this guide to media archive management.

8. When the client’s own DAM gets in the way

Some clients want deliveries to land in their own digital asset management (DAM) system, under their naming rules and their metadata fields. Settle it at kickoff: Agree on delivery formats, naming conventions, and final file ownership. Then, keep your working library on your side and hand over the approved versions. 

If the client is weighing a new system, the difference between DAM vs. MAM is a useful frame. A DAM is built for finished brand assets and a MAM for the production work before them. 

Psst — the “Digital asset management checklist” is a quick way to compare client system needs with what you are delivering.

9. When the RFP asks how you protect client assets

Larger clients ask for this in writing, and a clear answer wins work. 

In Iconik, access control lists define what each user, team, or group can see and do, gatekeeping access to every asset. Admins can switch off external sharing, and Iconik supports single sign-on through SAML 2.0, so a departing employee loses access when the client’s identity provider does. Iconik is also SOC 2 Type II compliant, and the report is available under NDA.

For the full list, see Iconik’s security and access controls.

How to handle difficult clients in the moment

Wondering how to handle difficult clients in the moment? Slow down the exchange, and bring it back to verifiable proof. 

These five moves work in most situations:

• Wait before replying to an angry email. A reply sent an hour later is almost always better than one sent in the first ten minutes.
• Get on a call to listen. Ask what would make the situation feel resolved, so you are solving the real concern instead of the loudest sentence.
• Go to the record: the scope document, the approval status on the version in question, or the share history that shows when the file was delivered.
• Offer options instead of a flat “no.” “We can add a third round for this fee, or swap it for the revision you asked about last week” keeps the conversation about choices.
• Confirm what was agreed — in writing, on the same day. The next conversation will start from this summary instead of from memory.

When to walk away from a client

How to fire a client is mostly about doing it cleanly. 

Some clients simply cost more than they pay. Bills run late, every change order becomes an argument, or your team dreads the account. When the pattern repeats after you have implemented a clearer scope and tighter sign-off, it’s reasonable to end the relationship.

Take the following steps when it’s time to let a client go:

• Start with your contract’s termination clause and the notice it requires, and ask a lawyer if the wording is unclear. 
• Give the client notice in writing.
• Finish or hand off work in progress, and deliver every final file from one place, so nothing gets lost in the exit. 
• End client and freelancer access when the handoff is complete.
• Keep the archive intact, in case they come back or a dispute needs the record. 

A client that leaves with organized files and a clear paper trail is far less likely to cause trouble on the way out, and your team gets its time back.

Frequently Asked Questions

What is the best way to handle a difficult client?

The best way to handle a difficult client is to stay calm, listen to their actual concern, and bring the conversation back to a written record: the scope, approval status, and delivery history. Offering options instead of a flat “no” keeps the discussion about choices.

How do agencies stop scope creep?

Agencies stop scope creep by writing deliverables, revision rounds, and sign-off owners into the scope before kickoff, and by requiring a change order for requests that fall outside it. A specific enough scope will make an outside request visible and do most of the work in stopping creep.

How do you prove a client approved the work?

You confirm a client approved the work by running approval through the asset itself, so the status shows each reviewer and whether they approved or rejected that version. In Iconik, you can require every assigned reviewer to approve before the asset counts as approved.

How many rounds of revisions should an agency include?

The number of revision rounds an agency should include depends on the project. Clearly scope the number before kickoff, and price any extra rounds separately. A number the client agreed to upfront is easier to point to than an assumption made on either side.

How can an agency share files with clients that have no Iconik account?

An agency can share files with clients that have no Iconik account through share links with expiry dates, passwords, and download controls, all of which external reviewers can open without signing up. Brand Portals add a branded single link for finished work on Professional and Enterprise plans.

When should an agency fire a client?

An agency should fire a client when late payments, constant disputes, or a drained team keep recurring after you have clarified scope and tightened the sign-off process. Check your contract’s termination clause first, give written notice, and hand over final files from one place.

Fix your process so clients are easier to work with

Most friction that makes a client difficult shows up as a missing record: an approval nobody can prove, a version nobody can identify, a file nobody can find. When approval, delivery, access, and archive run through one system, those arguments get shorter and a lot less personal. 

Get an Iconik demo to see exactly how to deal with difficult clients as an agency. 

‍