Scope creep starts in the thread, not the invoice

The landing page was scoped at two rounds. Since then the client has asked for a social resize on Slack, a new pricing section on a call, and "a few last comments" by email. None of these felt large enough to discuss.

Seeing new asks pile up in a thread? Nori can flag what falls outside scope and draft the change note for you to approve.

What agency scope creep costs

Scope rarely breaks in a meeting or on an invoice. It bends in chats and emails, a little each week, until the project you are delivering is not the project you priced.

In Ignition's 2025 agency report, 57% of agencies said they lose $1,000 to $5,000 a month to unbilled scope creep. As reported by The Drum, another 30% lose more than $5,000, and only 1% bill for all of their out-of-scope work.

What scope creep looks like in practice

It rarely looks like a new project. It looks like a favor.

• The extra round. The contract says two rounds. Round three arrives as "a few last comments."

• The adjacent deliverable. You are building the landing page. Could you also resize the hero for social?

• The new stakeholder. Someone senior joins late and asks to revisit an approved direction.

• The piecemeal feedback. Comments arrive across email, Slack and WhatsApp over ten days. It is called one round. It is ten interruptions.

• The one-hour task. Sometimes accurate. Often not, once you add the context switch, the export and the follow-up.

Feedback loops are also getting longer. Research from the IPA, reported by Marketing Week, found that revision rounds before approval rose from three in 2007 to five, and only 23% of agencies said the approval process works well. More rounds mean more openings for unscoped work. For how to keep approvals to one consolidated round, see what to send while you wait on client approval.

In most cases the client is not acting in bad faith. They do not know where the scope ends. If nobody states the boundary, nobody can respect it.

How to prevent scope creep with clients

Prevention is mostly attention.

1. Check each new ask against the scope. Before replying, confirm whether it is in the statement of work and within the agreed rounds.

2. Count rounds in writing. "Here is round two of two" in the delivery email sets expectations without sounding defensive.

3. Watch the informal channels. Formal requests come by email. Scope creep tends to come by chat, voice note and file comment.

4. Log it the same day. An ask you meant to handle later becomes work you already did.

5. Ask one clarifying question. "Is this replacing something, or in addition to it?" often settles whether it is a change.

How to tell a client something is out of scope

Agree to the idea, state the cost, and offer a choice. The best moment is right after the request, before anyone starts the work.

For a new deliverable:

Happy to do this. It is outside what we scoped for this phase, so here is what it adds: about 6 hours and one extra day before launch. I can send a short change request with the cost, or we can swap it for something already on the list. Which do you prefer?

For a revision round past the limit:

Thanks for these notes. We have used the two rounds in our agreement, so this would be a third. I can quote it as an additional round, or, if we collect everyone's comments into one list by Thursday, we can treat it as a single final pass.

For work you choose to give away:

Done, at no charge. I'm noting that it sits outside the original scope, so we stay aligned if similar requests come up.

The last message matters. Giving work away is a reasonable choice. Giving it away without saying so teaches everyone that it was always included.

What a change request should include

A change request does not need to be a formal document. It needs four things in writing.

• What is new or different, in one or two sentences.

• What it adds: hours, cost, and the effect on dates.

• What it replaces, if anything.

• What you need from the client: a yes, a no, or a choice, by a date.

Send it in the channel where the client usually approves things, and save the reply where your team can find it. A "looks good" in a chat counts as approval only if someone can find it next month.

Keep one list: agreed scope and new asks

The most useful tool here is a plain list with both sides: what was agreed, and what has been asked since. A spreadsheet, your project tool or a shared doc will do, as long as it lives in one place.

Review it weekly. Share it with the client at natural moments, such as the end of a phase. It turns a vague sense that the client keeps adding work into a record both sides can see.

Best for: retainers and multi-phase projects, where small asks are easiest to lose.

How to keep the relationship intact

Scope conversations feel like money conversations. They are mostly about trust.

• Raise it early. The longer an ask sits, the harder it is to discuss.

• Offer choices. Pay for it, swap it, or move it to the next phase.

• Be consistent. If one person on your team absorbs extras and another flags them, the client learns whom to ask.

• Write down what was agreed. Memories of an agreement tend to differ.

Most clients prefer an agency that is clear. It helps them explain the budget internally.

How Nori helps

• I watch email and Slack (WhatsApp and text are coming) for new requests, including the small ones in chats and voice notes.

• I notice when an ask falls outside what was agreed and draft the scope note or change request for that exact item.

• You review and approve each message before it reaches the client.

• I keep the running list of agreed scope, new asks, and what the client decided.

Nori is in early access, by invitation, at heynori.ai.