Agency operations

Scope creep

Work that grows beyond what was agreed, without the fee following.

The gradual accumulation of small extra requests, each reasonable on its own, until the account consumes far more time than it is priced for. It is the most common way a profitable account becomes unprofitable.

Key takeaways

  • Every individual instance is cheap and refusing looks petty. The cost only exists in aggregate.
  • The first symptom is not financial. It is a delivery team that has started to dread a particular client.
  • It needs a change order process light enough to actually use, or nobody will use it.
  • Absorbing the work silently and resenting the client for it is the worst available outcome, and the most common.
  • Raise it weekly in small amounts. Six months raised at renewal reads as an ambush.

Why it is structurally difficult to stop

Scope creep is not a failure of firmness. It is the predictable result of a situation where every individual request is cheap, reasonable and urgent, and the cost of it only exists somewhere nobody is looking.

Consider the position of the person asked. A client they like needs a small thing by Thursday. It will take an hour. Saying no requires explaining a commercial principle in a conversation that was about a banner. Saying yes takes an hour. Anybody would say yes, and the agency would want them to.

The forty-first time is identical to the first, and by then the account is consuming half again what it is priced for. No individual decision was wrong; the aggregate is badly wrong.

Which means the answer cannot be to ask people to refuse more often. It has to be structural: make the aggregate visible to somebody whose job is to look at it, early enough that the correction is a conversation rather than a confrontation.

The first symptom is not in the numbers

Margin reviews are quarterly and lagging. The people delivering the work know months earlier, and they express it in ways that do not look like commercial information.

The tells are consistent across agencies: a particular client name produces a reaction in a stand-up. Somebody quietly stops volunteering for that account. Work for it drifts into evenings. The account manager starts pre-apologising for requests when passing them on.

Those are all reports of scope creep, filed in the only format available to the person filing them. An agency that treats them as morale issues is throwing away its earliest and best data.

The practical version is to ask directly and routinely. Which accounts are heavier than they should be is a question with a reliable answer if somebody asks it monthly, and a question nobody can answer once it has become a resignation.

A change order process light enough to be used

Most agencies have a change order process and most of them do not use it, for a simple reason: it costs more to invoke than the work costs to absorb. If logging an out-of-scope request means a form, an approval and an awkward email, nobody will do it for an hour of work.

So the process has to be cheaper than the thing it is protecting. A line in a shared sheet with the request, the account and an hours estimate is enough. It takes thirty seconds, it requires no confrontation at the moment of the request, and it accumulates into evidence.

The conversation then happens on a schedule rather than in the moment, which is the important shift. At the weekly or monthly review there is a figure: this account has taken eleven hours of unscoped work this month. That is a discussion about capacity, not a refusal aimed at a person who asked for something.

It also gives the account manager something to say in the moment that is neither yes nor no: I will log that and we will look at it Friday. That sentence is the whole mechanism, and it is available to everybody once the sheet exists.

How to raise it without it becoming a fight

There is a right size and a right frequency, and both are smaller and more often than instinct suggests.

Raised as it happens, in small amounts, it is administrative. We did three extra assets this month, they took six hours, here is where that sits against the retainer. A client hearing that monthly is being kept informed, and usually finds it reasonable, because it is.

Accumulated and raised at renewal, the same information is an ambush. Six months of unbilled work presented at once looks like either an invoice nobody agreed to or a complaint that was never made, and the client is entitled to ask why nobody mentioned it in month two.

The worst version is absorbing it silently and letting it show up as resentment: slower responses, a colder tone, a team that has decided this client is difficult. The client never made the decision that caused it and cannot correct a problem nobody told them about.

Not every instance needs billing. Absorbing small things is part of a relationship, and saying so explicitly is stronger than doing it silently. We did this one, it took four hours, we are not billing it, we are telling you because the pattern matters, is a sentence that builds a relationship rather than spending one.

What it means for an agency

Track hours against the account even on a deliverables retainer. Without that, the first hard evidence of a problem arrives when someone resigns or the margin review lands.

Where it goes wrong

  • Absorbing extra work to protect the relationship, then resenting the client for a decision they never knew you made.
  • Raising six months of accumulated scope in one renewal conversation, which reads as an ambush.
  • A change order process that costs more to invoke than the work costs to absorb, so nobody invokes it.
  • Reading team reluctance about an account as a morale problem rather than as the earliest commercial signal available.

In short

Scope creep is an accounting failure dressed as a relationship problem. Nobody decided to give away a month of work; the mechanism for noticing was missing, and by the time the number appeared it was large enough to be a fight.

Frequently asked questions

How do you prevent scope creep?

Not by refusing more often, which asks the wrong person to hold the line at the wrong moment. Make the aggregate visible: log out-of-scope requests with an hours estimate, in something that takes thirty seconds, and review the total monthly. The conversation then happens on a schedule with a number attached, rather than as a refusal aimed at somebody who asked for a small favour.

What are the early signs of scope creep?

They show up in the team before they show up in the margin. A client name that produces a reaction in stand-up, somebody quietly avoiding an account, work drifting into evenings, an account manager pre-apologising when passing on requests. Those are reports of scope creep filed in the only format the person has available, and they arrive months before a quarterly margin review.

Should I bill for every out-of-scope request?

No, and pretending otherwise makes the process unusable. Absorbing small things is part of a working relationship. What matters is that it is a decision somebody made and told the client about, rather than one that happened silently. Saying we did this, it took four hours, we are not billing it is stronger than doing it quietly and resenting it.

When should I raise scope with a client?

Monthly, in small amounts, while each instance is still recent and uncontroversial. Six months raised at renewal is an ambush regardless of being accurate, and the client can reasonably ask why nobody mentioned it in month two. Small and frequent is administrative; large and late is a negotiation you start from behind.

Related terms

Last reviewed

Keplent keeps track of these for you.

It holds what each client agreed to, watches what their campaigns actually did, and tells you in plain sentences what needs you this week.

Join the waitlist