Get 25 battle-tested prompts
Turn real client conversations into Linkedin content that builds authority and attracts the right clients.
Turn real client conversations into Linkedin content that builds authority and attracts the right clients.
Agency scope creep is the extra work a client gets that nobody priced, approved or wrote down. It rarely arrives as one big request. It shows up as a string of small yeses, most of them said by someone on your team who had no way to check what the client actually bought.
That second part is what most advice skips. Founders already know they need a tighter statement of work. The harder problem is the moment a client asks for "one small thing" in Slack and the person answering has no idea whether it's in scope.
I went through a few hundred comments on Reddit this week from agency owners arguing about exactly this. The useful answers had less to do with contracts than I expected, and a lot more to do with where the scope actually lives inside the agency.
Scope creep is any growth in a project's deliverables after it starts, without a matching change to budget, timeline or staffing. In an agency it usually looks like extra revision rounds, a "quick" landing page, a report nobody asked for in the proposal, or a founder who keeps joining calls that were supposed to be run by the team.
It's common. PMI's Pulse of the Profession research, as reported in PM Network, found that 52 percent of projects completed in the prior 12 months experienced scope creep, up from 43 percent five years earlier. That data covers project teams broadly, but agency founders will recognize the trend.
The most upvoted thread I read was a post in r/marketingagency asking how owners deal with clients who want more than they paid for. The replies were full of good rules. Give 10 to 20 percent out of scope as goodwill and stop there. Say out loud when something is a freebie so the client doesn't start expecting it. Have a change order ready on day one.
The original poster kept coming back with the same follow-up question. How do you enforce that with employees? How do you spot it without the founder being dragged into every request?
That question is the whole problem. A 10 to 20 percent rule only works if someone knows where the line is. In most small agencies, the real scope is spread across a signed SOW, a sales call nobody recorded, a few promises the founder made on a kickoff, and whatever the account manager remembers. The person replying to the client at 4 PM on a Thursday can see maybe a third of that.
One commenter in a thread in r/agencynewbies put it plainly: the process advice works in theory, but scope creep survives because saying no feels like it risks the relationship, and for a four person shop one client can be a quarter of the month's revenue. When the team can't tell what's in scope, saying yes is always the safer call for them personally.
A post in r/consulting titled "The scope creep I didn't see coming was my own" described a founder offering to make an introduction during a strategy session and leaving the call committed to outreach and follow-up nobody had scoped. Plenty of agency founders do this. We volunteer help because we like the client and it feels good, and then the team inherits a promise they never heard.
The fix suggested in that thread was simple. Say the boundary out loud ("happy to make the intro, and if you want me to run the follow-up we can scope that separately"), then repeat it in the written recap so nobody has to remember the call.
Here is the approach I'd take, pulled from the answers that held up best and from what I've seen work with the agency founders I talk to.
A list of deliverables invites interpretation. Write what "done" means for each deliverable and add a short section on what isn't included: number of revision rounds, channels not covered, copy not included. Several commenters said the exclusions section did more than anything else to cut arguments later, because the client signed it.
One agency in the r/agencynewbies thread goes further. At kickoff they ask the client to describe each deliverable in their own words, then compare that to the agency's version and write down the agreed one. Misreadings surface in week one instead of month three.
Accelo's guide to change order management frames it well: treat a new request as a proposal, log it, assess what it does to fee, timeline and staffing, and get written approval before the work starts. Their line that good project managers prevent undocumented change, as opposed to change itself, is a good one to put in front of your team.
The script can be short. "Happy to do that. It's outside what we scoped, so I'll send a quick estimate today." Or give the client a trade: "We can fit that in free when the schedule opens in two weeks, or rush it now for an added fee. Which works better?" One commenter used that second version and said it turned scope talks into a prioritization choice, which clients take far better than a no.
My favorite reply in the whole r/marketingagency thread was about measurement. Most owners don't know if they are at 10 percent out of scope or 40, because creep never shows up as a decision. The commenter's fix: one line in a note per client every time someone says yes to something outside the SOW. After a couple of months you have a count, and it's usually concentrated in one or two clients. "This client asked for 11 extra things in March" is a sentence you can bring to a renewal conversation without it sounding like a complaint.
Another owner shares a simple tracker with the client showing the original SOW next to everything requested since. They said most clients don't realize they're creeping and adjust once they can see the list grow.
This is the step most agencies skip, and it's the one that answers the "how do I enforce this with employees" question. If the only complete picture of what a client bought lives in the founder's head, the founder becomes the scope police for every account, which defeats the point of hiring a team.
So capture the full context in one place your team actually uses: the SOW, the exclusions, notes from the sales calls, what was promised on kickoff, every approved change order and every freebie you've already given. Then a junior account manager can answer "is this in scope?" in a minute without pinging you. This is a big part of what we think of as a company brain for a consulting or agency business: the knowledge that lets your team make the call you would have made.
A few commenters build a buffer into the fee that they won't negotiate away, so small out of scope favors don't hurt. Others argued the opposite: if a client or project looks risky, bill hourly or break the work into smaller milestones. Both are fine. What doesn't work is pricing tight, promising flexibility and hoping it evens out.
The thread split on this, and the client side made the sharpest point. One in-house marketer who used to work agency side described being told at a monthly check-in that the agency was "spending way too much time" on their account, when they thought they were working inside the scope the agency itself had written. Another time the agency complained after launch that a website was bigger than planned, even though the client accepted the agency's own proposal without changes.
That's the version of scope creep that costs you the client. If your team underscoped, the honest move is to fix your estimating and either absorb the miss or have a direct conversation early. Raising it as a grievance at the end of the project makes it the client's problem when it started as yours.
Most of the time, though, nobody is acting in bad faith. As one reply put it, if scope reads like a wish list, clients will treat it like one.
Some owners cap it at 10 to 20 percent of a project as goodwill. The cap matters less than tracking it and telling the client each time something is a freebie, so it builds goodwill and doesn't quietly become the new baseline.
A reference to the original agreement, a plain description of the change, the fee and billing impact, the timeline and staffing impact, acceptance criteria and who approved it. Keep the template short so your team actually sends it.
Give them a script and give them access to the full scope. People say yes when they can't check what was sold and don't want to risk the relationship. When they can see the SOW, exclusions and past promises in one place, saying "let me send an estimate" stops feeling risky.
Hourly billing moves the risk to the client, and it can make sense for vague or risky work. Many agencies prefer fixed fees for predictability. With fixed fees, the protection comes from tight acceptance criteria, an exclusions list and a change order process the team uses every time.
In most agencies I talk to, scope creep comes from a team making dozens of small calls without the information to make them well. Give them that information and the contract you already have starts doing its job.
