Precedent does the damage here, not greed. The opening request is trivial, and refusing it would cost more goodwill than doing it costs you in minutes, so you absorb it and feel reasonable. What you have established is that requests of that kind travel free, and each subsequent one is now harder to price than the last, because pricing the fourth means implicitly querying the three you waved through. By the time the total is visible, raising it sounds like an accusation. That is why the only cheap moment to speak is the first one, and why freelancers who lose money to this are rarely the ones with difficult clients; they are the ones with excellent manners. Two other sources deserve naming, since both come from your side of the table. The first is your own improving: the extra state nobody asked for, the refactor, the second option produced to be helpful. It is unpaid work you chose, and it teaches the client that polish is free. The second is the silence in the paperwork. Where the agreement never listed what sits outside the job, both parties fill that space with whatever they each assumed, and their assumption is invariably more generous than yours. None of that is fixed by being firmer in conversation. It is fixed by writing exclusions while everybody is still friendly, and by having one short reply ready for each of the shapes a request tends to arrive in.
| What you hear | What it is | The truthful answer |
|---|---|---|
| While you are in there, could you also… | A second small job with no price, no deadline and no end | Yes, and it adds time. I will send a change note with what it costs and what it moves |
| One more round, it is nearly right | Revisions past the agreed count, usually because a fresh opinion arrived late | Rounds are counted in the agreement. The next one is chargeable, at a stated figure |
| The new head of marketing has thoughts | A settled decision reopened by somebody who never signed the brief | Happy to walk them through the approved brief. Changing it is new work and priced as such |
| This is a bug, not a change | Either a genuine defect or a requirement nobody wrote down | Check it against the acceptance criteria. Inside them, fix it fast and free; outside them, say so calmly and price it |
| Quick question, weeks after handover | Unpaid support hardening into a permanent part-time job | Answer the first one generously, then offer support terms or a block of paid time |
| Can it be seen in blue as well? | Exploration billed to you, because asking costs the client nothing | One cheap alternative is goodwill. A second is a decision the client should pay to take |
The instrument that stops all six is the same, and it is deliberately small. A change note is three lines sent the same day: what is being added, what it does to price and delivery, and a request to confirm before you touch it. It is not a confrontation and should not be written like one, because its purpose is to hand the client a decision rather than a verdict. Clients accept these far more readily than freelancers expect. What they refuse is an invoice at the end containing work they never knowingly bought. If you are already four absorbed requests deep, do not try to back-charge them; that conversation cannot be won and the money is gone. Reset at the next natural boundary instead. Send a short note listing what has been added so far, state that it has been absorbed, and say that from here anything outside the original agreement gets priced before it gets done. Then hold it on the very next request, because a boundary announced and not enforced does more damage than none at all. And when the same item keeps arriving from the same kind of client, stop treating it as creep and put it in the next agreement's exclusions, where it becomes an upsell rather than a leak.