The first favor is cheap. The second identical one is where the price gets set.
A client asks for something just outside the agreed work. It is small. It is reasonable. It takes twenty minutes. You do it, say nothing, and move on, because making a thing out of twenty minutes feels petty.
Three weeks later the same ask arrives again.
Nothing about the second request is bigger than the first. What changed is what it means. Your first answer taught them this work is included, and now there are two data points saying so. The boundary you never wrote down is being written for you, one quiet yes at a time.
This is how scope creep actually works in small teams. Not as one big ask that forces a negotiation. As a drip of small ones that never trigger anything, because each arrives looking exactly like the last favor you were happy to do.
The reason good operators still miss it is that the signal does not live in any single message. It only exists when someone compares this week's asks with last month's. If nobody is doing that comparison, every request gets answered by whoever reads it first, and every answer is a fresh judgment call with no memory behind it.
Three signals are worth writing down, because they mean the scope conversation is due while it is still cheap.
The same out of scope request appearing for the second time.
A milestone's remaining effort jumping past the plan, even when the deadline still looks fine.
Someone on the team saying, in any wording, this is taking longer than it should.
Any one of the three is enough. You do not need proof of a trend. Proof is what you get after the boundary has already moved.
The conversation itself is smaller than people fear. It is not a change order and not an invoice line, not yet. It is one written sentence: this is outside what we agreed, we are happy to do it, and here is how we handle that. Then a name, the one person on your side who can say yes to extra work, so the answer stops depending on whoever happens to open the email.
Said early, that sentence reads as professionalism. The exact same words at invoice time read as a bill for something your client thought was included. The content is identical. The timing is the entire difference, and the timing is decided by whether anyone wrote the first request down.
Two habits carry most of the weight. Log the small asks somewhere visible, not to bill for them but so the second one is recognizable as the second one. And decide in advance who owns the yes, because an unanswered boundary question defaults to yes, and a default yes is still a yes.
Open your last month of client threads and find the ask that appeared twice. That is where the sentence is missing. It takes five minutes to write, and it is the cheapest five minutes in the whole engagement.
Top comments (0)