How do I push back without damaging the relationship?

Do not push back; quantify. "Happy to add that — it's about half a day, so it either extends delivery by a day or replaces the revisions round we'd planned. Which would you prefer?" This treats the client as someone making an informed trade rather than someone trying to get something for nothing, which is almost always the truth.

Is hourly billing immune to it?

It shifts the damage rather than removing it. On hourly terms the additions are paid, so margin is protected, but the deadline and the budget still drift — and an invoice that quietly grows past what the client expected damages trust just as effectively as an overrun does. Scope still needs stating; the consequence is simply different.

Scope creep — why projects grow quietly

Scope Creep

Also: requirement creep, feature creep, scope drift

Scope creep is the gradual expansion of agreed work through small additions that each seem too minor to renegotiate — and which collectively consume the margin, the timeline, and eventually the working relationship.

It is never one big request

Scope creep does not arrive as a demand for twice the work. It arrives as "while you're in there, could you just…" — each item genuinely small, each individually unreasonable to invoice for, and none of them worth the awkwardness of a conversation. The damage is cumulative and invisible until the project is materially larger than the one that was priced.

The structural cause is almost always an ambiguous agreement rather than a difficult client. Where the statement of work does not say what is excluded, both sides fill the gap with their own reasonable assumptions — and those assumptions differ. Fixed-price work makes this sharper, because every hour of drift comes directly out of the supplier's margin while costing the client nothing.

"Yes, and here's what that changes"

The effective response is neither refusal nor silent absorption. It is to accept the request and immediately state its consequence: what it adds in time or cost, and what it displaces. Clients almost never object to that framing — they object to surprises. Saying it the first time, on the first small request, is what stops the pattern forming.

Key takeaways

→The cause is usually an agreement that never said what was excluded, not a client behaving badly.
→Price and displacement stated at the moment of the request — not at the end — is what prevents accumulation.

FAQ

How do I push back without damaging the relationship?: Do not push back; quantify. "Happy to add that — it's about half a day, so it either extends delivery by a day or replaces the revisions round we'd planned. Which would you prefer?" This treats the client as someone making an informed trade rather than someone trying to get something for nothing, which is almost always the truth.
Is hourly billing immune to it?: It shifts the damage rather than removing it. On hourly terms the additions are paid, so margin is protected, but the deadline and the budget still drift — and an invoice that quietly grows past what the client expected damages trust just as effectively as an overrun does. Scope still needs stating; the consequence is simply different.