No client sets out to take more than they paid for. Scope creep happens one reasonable request at a time. Can you just resize this for stories. Can you just add Arabic subtitles. Can you just pop into the launch on Thursday. Each one is small, each one is easier to do than to discuss, and after six months the account is running at twice the effort it was priced for.
The problem is not the client asking. Clients should ask. The problem is that the agency has no calm, repeatable way to answer, so every request becomes a judgment call made by whoever happens to receive it.
Scope creep starts in the contract
Most creep can be traced back to a scope that was never specific enough to be exceeded. Social media management is not a scope. Twelve feed posts a month, in English and Arabic, with two rounds of revisions and consolidated feedback within two working days, is a scope.
The difference is that the second version has edges. When a request falls outside it, both sides can see that it does, without anyone having to argue about it. A vague scope turns every extra into a debate about what was meant, and the agency almost always loses that debate because it wants to keep the account.
The statement of work template on this site is built around those edges: deliverables with quantities and formats, a list of what is not included, revision rounds, feedback deadlines and a change process. The section most agencies skip, and most need, is the one that says what is not included.
Name the small things before they happen
Certain requests turn up on almost every account, and they are far easier to address at the start than in month four. Put them in the scope, either as included or as priced extras.
- Resizing and reformatting. One asset in five formats is five pieces of work.
- Translation and transcreation. Arabic copy is not a quick pass over the English, and clients who assume it is will be surprised by the time it takes.
- Attendance. Shoots, launches and events are days out of the studio.
- Extra revision rounds. Say how many are included and what happens after that.
- Urgent turnarounds. Work needed tomorrow costs capacity that was promised to someone else.
Give every change the same path
A change process only works if it is boring. When a request falls outside scope, the response is always the same: acknowledge it, say it is outside the current scope, and send a short note with the time, cost and effect on the timeline. The client approves it in writing, and then the work starts.
That last part matters most. Work that starts before the change is approved is work the client will reasonably assume was included. Once it has been done for free once, it is very hard to charge for the second time.
The goal is not to refuse extra work. It is to make sure extra work is always a decision, never an accident.
How to say it without sounding difficult
Account managers avoid the scope conversation because it feels like confrontation. It does not have to. The words that work are neutral and specific, and they offer a way forward rather than a wall.
Something like: happy to do this, it sits outside what we agreed for this month, so here is what it would take and what it would cost. Or, if the budget is fixed: we can do this instead of one of the planned posts, which would you rather drop. Either answer respects the client's request and the agency's capacity at the same time.
Trading rather than adding is often the better offer. It keeps the price stable, it makes the client prioritise, and it shows that the scope is a real plan rather than a minimum the agency is trying to protect.
Keep a log of the favours you do grant
Sometimes the right decision is to absorb a small extra, because the relationship is new, or the request is genuinely trivial, or the client has been generous in other ways. That is fine, as long as it is recorded.
Keep a simple list against the client of anything done outside scope, with the date and the rough time it took. It costs a minute per entry. At the quarterly review it turns a vague feeling that the account has grown into a specific list, and a specific list is something a client can actually respond to.
Review the scope on a schedule
Some creep is not creep at all. It is the account genuinely changing: a new market, a new product line, a client who now wants reels where they used to want statics. Treating that as a string of one-off extras frustrates everyone.
Set a quarterly scope review with the client and bring the log. If the extras have become the normal work, rewrite the scope to match and price it properly. If they were one-offs, the review is a chance to say so and reset expectations. Either way, the conversation happens on a date both sides expected, which makes it a planning meeting rather than a complaint.
The client you keep by holding the line
Agencies worry that pushing back on scope will cost them the client. In practice, the accounts that end badly are more often the ones where the agency said yes to everything, quietly resented it, and let the quality slip as the workload grew. Clients notice the slip long before they notice the resentment.
A clear scope, a predictable change process and a regular review protect the work as much as the margin. Keeping each client's projects, tasks and budget in one place makes that log far easier to keep, which is part of why Wiro holds them together. Whatever you use, start with the statement of work, because every other step depends on it.
