When Your Retainer Client Keeps Adding Work
When a client's requests outgrow their retainer, most agency owners absorb the extra work and say nothing. Here's what to do instead — document scope, present explicit options, and have the pricing conversation before resentment sets in.
An agency owner I work with has been running influencer activations for a food brand client at roughly double the rate her retainer covers. Not because the client is unreasonable — because nobody documented how many were included.
This happens in almost every agency I've talked to. A retainer gets signed, the work starts, the client gets excited, and the requests multiply. Nobody wants to have the awkward conversation, so the team absorbs it. Six months later the account is quietly unprofitable and everyone is burned out.
How does scope creep actually start?
It usually starts with a yes that seemed fine at the time. The client asks for one more activation, one more deliverable, one more revision. You say yes because the relationship is good and you want to keep it that way. Then that yes becomes the new baseline, and before long the new baseline gets its own set of extras.
In this case, the client had budget for more influencer content — they were genuinely interested in expanding — and that made it easy to keep saying yes. But intent and scope are two different things. Wanting to grow the account isn't the same as agreeing to pay for the additional work.
Why most agencies don't catch it early
The people doing the work rarely have visibility into what was originally agreed. The account manager knows, maybe. The person managing the influencers probably doesn't. So the team just keeps executing, nobody flags the discrepancy, and by the time someone runs a profitability check the gap is substantial.
There's also a relational pull at play. Most agency owners got into this business because they like their clients and they like doing good work. Protecting scope feels adversarial. It's not.
What to do when you're already over scope
The conversation needs to happen before the resentment sets in — on either side. Once you're doing significantly more work than you're charging for, you're not doing the client a favor. You're building toward a situation where you'll eventually have to raise your rates dramatically, drop the account, or tell them you can't sustain the current service level. None of those are clean options.
What works better is presenting two explicit choices: reduce the monthly deliverables to what the retainer covers, or renegotiate pricing to reflect the actual work being done. Neither option is "I've been doing you a favor and now I'm charging you for it." The framing is cleaner — here's what we agreed to, here's what we've been doing, here's how we want to move forward.
In this case, the client actually has budget for the expanded work. The friction point was never the money — it was that no one had documented the scope clearly enough to make the conversation possible.
Who should have the pricing conversation?
Not always the agency owner. This is counterintuitive for founders who default to handling everything client-facing themselves.
In this situation, the agency owner held the client relationship and controlled the narrative, but had her account lead run the pricing conversation directly. That separation keeps the relationship intact. The agency owner is still the person the client trusts; the account lead handles the mechanics of renegotiation. Mixing those roles can make clients feel managed rather than supported.
One thing that matters: whoever isn't involved in the pricing conversation should be kept out of that meeting. Don't bring someone with a warm relationship to the client contact into a discussion about money — it muddies the dynamic and creates loyalty conflicts neither party knows how to resolve.
The scope document you should have had from the start
The fix going forward is simple to describe and slightly tedious to actually do: define the number of activations, deliverables, and revision rounds in writing before the work starts. Tie each line item to a unit. "Influencer management" is not a scope. "Six influencer activations per month with one round of revisions each" is a scope.
When scope is vague, clients aren't necessarily trying to extract more than they're paying for. They're operating on whatever mental model they built from the sales conversation. If your pitch implied more than your contract specified, that's a contract problem.
For retainer clients you already have, treat the scope conversation as a reset. Review what's been delivered against what was agreed and use that as the opening for a clean renegotiation. Do it before the account gets to a place where you're quietly resentful or they're suddenly surprised.
The operational signal nobody's watching
The scope problem wasn't the only thing that surfaced. When an account grows faster than the team executing it, the execution gaps compound. A scheduler stretched past capacity missed a meeting and made two approval errors in the same week. The fix wasn't to reprimand her — the role required two people and had been running with one.
The tell is usually a rash of small errors. Not catastrophic failures, just slippages that show up more frequently than they used to. That's the signal that the current structure isn't keeping pace with the account load.
The agency owner is posting a backup scheduler on Upwork this week. The assignment she's using to evaluate candidates specifically tests for manual community engagement — no AI shortcuts — because the role requires authentic interaction that bots replicate badly. That one sentence in the job post will filter out about 80% of the applicants, which is exactly the point.
