Written by
Jonny Stuart
The client did not ask for extra work. We just said yes. Every time.
In this post
"Can we see another version?" Sure. "Can you make it work on mobile too?" Of course. "Can we just adjust the copy?" No problem.
None of these felt significant in the moment. Cumulatively, they added around 30% to the project hours with zero additional revenue. We called it scope creep and told ourselves the client was difficult. But the client never forced our hand. We had written a proposal vague enough to make every one of those requests feel reasonable.
Scope creep is not a client management problem. It starts at the proposal stage.
What Is Scope Creep?
Scope creep is the gradual expansion of a project beyond its originally agreed boundaries, typically without a corresponding increase in budget or timeline. In agencies, it manifests as additional revision rounds, expanded deliverables, extended timelines, and absorbed requests that were not included in the original fee.
The reason it feels like a client problem is that clients are the ones making the requests. But the reason agencies absorb those requests rather than pricing them appropriately is almost always a scoping and pricing issue at the start of the engagement.
Why Scope Creep Is a Pricing Problem
Vague deliverables create ambiguity. A proposal that says "website design" is a promise with no defined boundaries. How many pages? How many revision rounds? Does it include copywriting? What happens if they want to add a blog? Every undefined variable is a potential request the client can make and the agency will struggle to decline.
Underpricing creates psychological debt. When an agency prices a project lower than it should to win the work, the team knows it. There is an implicit sense that the agency owes the client something for the lower rate. This makes it much harder to push back when requests come in, because internally it feels like the requests are fair compensation for the discount.
Fixed-fee projects absorb all overruns. A fixed fee that is set too low creates a situation where every extra hour is a margin loss. The agency bears all the risk. The client bears none. This is backwards. Scope should define the fixed element, with clear processes for anything outside it.
Saying no damages relationships (or feels like it does). Agency founders often absorb scope rather than risk damaging the client relationship. This is understandable. It is also the most expensive relationship preservation strategy available.
What Happens to Margin
A project priced at a 35% margin can hit 10% or below with three unplanned revision rounds. The math is brutal.
If a project is quoted at £10,000 with 50 hours of work estimated, that is £200 per hour effective rate. If the project runs to 65 hours because of scope additions the agency did not charge for, the effective rate drops to £154 per hour. Against a cost base of, say, £120 per hour, that is a margin of roughly 22% - versus the 40% originally planned.
This is not unusual. It is what happens on projects without clear scope definition and without a process for charging for changes.
How to Fix It
Scope deliverables, not effort. Instead of "logo design" write "three initial logo concepts, two rounds of revision, final files in specified formats." The client knows exactly what they are buying. You know exactly what you are selling. Requests outside that scope are easy to identify and easy to price.
Define revision rounds explicitly. Every proposal should state the number of revision rounds included. Two rounds is common. Three rounds is generous. Anything beyond that is a change request with an associated fee. This is not adversarial - it is clear.
Price with a risk buffer. If your honest estimate for a project is 40 hours, price for 48. The buffer absorbs the inevitable small additions that do not warrant a change order. If the project runs clean, your margin is higher. If it runs long, you are protected. Either outcome is better than pricing for best-case and absorbing worst-case.
Build a change request process. When a request comes in that is outside scope, the response is not "yes" or "no" - it is "that is outside the current scope, here is what it would cost to add it." This is a professional process, not a confrontation. Most clients accept it when it is presented that way.
Charge for discovery. Many scope issues originate in an incomplete brief. The less the agency understands the project before starting, the more likely the scope will shift as the brief becomes clearer. Paid discovery - even a small engagement to define the brief properly - dramatically reduces scope creep on the main project.
Frequently Asked Questions
What causes scope creep in agencies?
Scope creep is primarily caused by vague deliverable definitions in the original proposal, underpricing that creates psychological reluctance to push back, and the absence of a formal change request process. Difficult clients contribute, but they are the exception rather than the rule.
How do you prevent scope creep on agency projects?
Define deliverables specifically in every proposal (number of concepts, revision rounds, formats, exclusions), price with a buffer for the inevitable small additions, and build a formal change request process so that out-of-scope requests are priced rather than absorbed.
Should agencies charge for revisions?
Agencies should include a defined number of revision rounds in every project fee, then charge for additional rounds beyond that. The number of included rounds should be specified in the proposal. This is standard professional practice and most clients accept it when it is communicated clearly upfront.
Scope creep feels like a problem that happens to you. The truth is it usually starts with a proposal that left too much undefined.
The fix is upstream - in how you scope, how you price, and how you respond when requests come in. Get those three things right and the difficult conversation at revision four rarely happens.
AgencyFlo tracks scope changes against original estimates so you can see the moment a project starts running over - and act on it before the margin is gone.
