Nick QuirkEvery agency has one. The account that generates 40% of your Slack notifications and 8% of your revenue. The client who sends feedback at 11pm on Sunday, changes the strategy three weeks into a six-month roadmap, and CCs their CEO on an email about a missing comma in a meta description.
Here's the uncomfortable truth: the "client from hell" is almost never a personality problem. It's a process problem that got personal. Somewhere in the first 30 days, a boundary went unset, a precedent got established, and now you're running an unpaid on-call service for a retainer that priced in 25 hours a month.
This guide is about client boundary setting that actually holds — the contract language, the scripts, the escalation paths, and the operational systems that make boundaries self-enforcing instead of something you have to defend in every email.
Diagnose the problem before you treat it
Not all difficult clients are the same, and the fix depends entirely on the type. Before you draft a stern email, work out which of these you're dealing with.
The Scope Creeper
Every request arrives as "just a quick thing." A quick landing page. A quick competitor analysis. A quick look at their Google Ads account, even though you were hired for SEO. Individually each ask is 30 minutes. Collectively they're 11 hours a month you're not invoicing.
The Anxious Micromanager
They want daily updates, they question the strategy weekly, and they forward you every SEO newsletter they read. This client is usually scared, not malicious — often because they sold your engagement internally and their own job is riding on the results. They typically respond very well to structure.
The Ghost-then-Emergency
Silent for three weeks, then demands a deliverable review in 24 hours because their board meeting moved. Your production schedule bends around their calendar chaos, and blown deadlines get attributed to you.
The Boundary Tester
Emails your team members directly to bypass the PM. Calls your mobile on a Saturday. Asks for "a favour" that's clearly a change order. This is the only type where the behaviour is genuinely about power, and it's the only one that requires firmness rather than empathy.
Write down which one you have. The Anxious Micromanager needs more communication; the Boundary Tester needs less. Applying the wrong remedy makes things worse.
Boundaries are set at kickoff, not at breaking point
The single biggest predictor of a painful client relationship is what happened in the first two weeks. If the first "quick favour" went unbilled and unremarked, you taught them the rules. Retrofitting boundaries after month four is possible, but it costs goodwill you wouldn't have had to spend.
Build a Rules of Engagement document — two pages, signed alongside the contract, covered verbally in the kickoff call. It should specify:
- Channels. Where work requests live. One place. "Requests made in Slack DMs, text messages or hallway conversations aren't tracked and won't be actioned."
- Response SLAs, both directions. "We respond to requests within one business day. Urgent items flagged as such get a response within four working hours. In return, we need feedback on deliverables within three business days."
- The default-approve clause. This one changes everything: "Deliverables not reviewed within five business days are considered approved and move to the next stage." It removes the incentive to sit on drafts.
- Revision rounds. One consolidated round per deliverable, submitted as a single set of comments. Not seven emails over nine days.
- Named decision-makers. Who signs off. When a fourth stakeholder appears in month three with new opinions, you have something to point at.
- What "urgent" means. Define it. Site down, indexation collapse, penalty notice. A blog post that needs to go live Thursday instead of Friday is not urgent.
Read this aloud on the kickoff call. Clients rarely object — most are relieved that someone has a system. The ones who push back on reasonable process terms are showing you exactly who they'll be in month six.
Make the work visible so boundaries don't need defending
The hardest boundary conversations happen when it's your word against theirs. "We've done loads of extra work for you" is an opinion. "You've approved 42 hours against a 25-hour retainer, here's the breakdown" is a fact.
Visibility does three things at once: it kills scope arguments, it justifies rate increases, and it makes the client self-regulate. When someone can see that their "quick question" thread consumed 90 minutes of a senior strategist's time, the questions get better.
Practically, this means every request — no matter how small — becomes a tracked task with an estimate before anyone touches it. Time gets logged against phases, not floated in a general bucket. The retainer burn rate is visible to the client, not buried in a spreadsheet you update the night before the QBR.
This is where tooling matters more than people expect. Generic PM tools are built for internal teams; agency work needs retainer burn, per-client time tracking and client-facing views that don't leak your internal chatter. If you're evaluating options, the agency PM tool roundup covers what to look for, and the comparison hub breaks down how the major platforms handle client access specifically.
Scripts that hold the line without burning the relationship
Boundaries fail in the moment of delivery. Here's language that works.
For the out-of-scope request
Never say no. Say "yes, and here's the trade-off."
"Happy to take that on. It's roughly 6 hours, which is about a quarter of this month's retainer. We can either add it as a change order at £X, or swap it for the internal linking audit that's currently scheduled for week three. Which would you prefer?"
This converts a confrontation into a choice. In my experience about 60% of casual requests evaporate the moment a number and a trade-off appear.
For the 11pm Sunday email
Don't reply. Replying at 11:04pm sets the expectation permanently. Reply at 9:15am Monday with: "Picked this up first thing — here's where we are." No apology for the delay. Apologising confirms that a delay occurred.
For the client who bypasses the PM
Brief your team on a single response: "Great question — let me loop in Sarah so it gets prioritised properly against the sprint." Then the PM answers. Three repetitions of this and the direct emails stop, without anyone having to be told off.
For the missed feedback deadline
"We haven't had comments on the four articles from the 9th. Per our process they'll be published Thursday as-is so we don't lose the publishing slot. If you'd like changes, we'd need them by Wednesday midday."
For the strategy re-litigation
"That's a reasonable question, and it's worth a proper conversation rather than an email thread. Let's put 30 minutes on the calendar for Thursday. In the meantime the team will continue with the agreed roadmap so we don't lose the momentum on the technical fixes."
Handle escalation in three graded steps
When patterns don't break after scripts, escalate deliberately rather than emotionally.
- The written pattern summary. Not a complaint — a data email. "In the last 60 days we've received 14 requests outside the agreed scope totalling 31 hours against a 25-hour monthly retainer. Here's the list." Facts, no adjectives.
- The reset call. Owner to owner, 30 minutes, agenda sent in advance. Three outcomes on the table: adjust the scope, adjust the fee, or adjust the working process. Come with a recommendation, not a grievance.
- The exit. 30 days' notice, full handover, no drama. Offer a referral to another agency if you can do so honestly.
Run the numbers before step three. A £4,000/month client consuming 55 hours is billing at £72/hour. If your target is £120, that account is costing you roughly £2,600 a month in opportunity. Also apply the human test: if a team member has quietly asked not to be staffed on an account, you have a retention problem disguised as a client problem.
Prevention: systems that stop the pattern forming
The agencies that rarely have a "client from hell" aren't luckier — they've made boundaries structural rather than interpersonal.
- Templated projects. When every engagement starts from a standard phase structure, scope deviation is visible immediately. A reusable setup template means nobody has to negotiate what's included from scratch.
- Sprint-based delivery. Fixed-length cycles with a locked scope give you a natural, non-personal answer to mid-cycle requests: "That goes into the next sprint." This works particularly well for technical SEO work, where client-side dev dependencies create most of the friction.
- Scheduled reporting rhythm.
