You know the exact moment it happens. The project is done — delivered, approved, invoiced — and then the message arrives: "just one more revision." Then another. Then a "quick call" to discuss a feature that was never in the brief.
Nothing in that exchange is a negotiation. It is a leak, and it runs in one direction: your hours out, their scope up, your fee exactly where it started.
Here is the part most freelancers never price in: the revision itself is the cheap part. The expensive part is everything around it. The context-switch back into a finished project. The evening you lose re-opening files you had already closed. The next project that starts a day late because this one never actually ended. One free revision is never one hour. It is the hour, plus the recovery, plus the delay it causes downstream — and you charge for none of it.
Why "being flexible" costs more than saying no
Flexibility feels like good client service, so it is hard to see as a cost. But look at it from the client's side of the table: every free revision teaches them that the scope is a suggestion, not an agreement. The second free revision is easier to ask for than the first, and the third easier still. By the fourth, the client is not being unreasonable — they are behaving exactly as the arrangement trained them to.
That is the real price of working without a written scope. Not one awkward conversation. A pattern, repeated on every project, with every client, until "just one more" becomes the normal way your work ends.
The fix is one sentence, written before the work starts
The sentence is not clever. It does not need to be. It needs to exist in writing, before the first deliverable, where both sides can point at it:
"Revisions beyond [two] rounds, and any work outside the scope listed above, are billed as a change order at [your rate]."
That is it. No legal theatre, no hostility. Three things make it work:
- A number, not a feeling. "Two rounds" can be counted. "Reasonable revisions" cannot — and whatever cannot be counted will be argued about later, at your expense.
- A price attached to the boundary. A scope limit without a price is a wish. The moment the extra work has a rate, the client can make a real decision: pay for it, or drop it. Either outcome is better than you absorbing it.
- It is agreed before the work, not during the argument. A boundary introduced mid-project sounds like a complaint. The same boundary in the proposal sounds like professionalism — because it is.
The same leak, in the invoice
Late payment is the same leak wearing different clothes. The work is done, the invoice is sent, and then the waiting starts — a week, then two, then a "just checking in" message that you write, not them. Every week an invoice sits unpaid, you are lending the client money interest-free, out of your own pocket, while your own bills arrive on schedule.
The fix follows the same rule: the consequence is written down before the work starts, and the follow-up is a sequence, not a mood. A friendly reminder first, then a firm one that names a date, then a formal notice that states the late fee and pauses further work, then a final notice with a real deadline. Each step is calmer to write when it is decided in advance — and much harder for a client to ignore than a single apologetic nudge sent whenever you finally snap.
What to put in writing before the next client signs
If you take one thing from this, make it a checklist you run before every project:
- Scope, written as a list — what is included, in words the client can read back to you. If it is not on the list, it is a change order.
- A revision number — how many rounds are included, and the rate for anything beyond.
- A kill fee — what you are paid if the project is cancelled after work has started.
- When the IP transfers — on final payment, not on delivery. Work delivered unpaid is work given away.
- Payment terms with a date, not a hope — due on a named day, with a named late fee, and a named sequence if it slips.
- An intake step — twenty honest questions before you quote, so the scope you agree to is the scope that actually exists, not the one you discover in week three.
None of that is paperwork for its own sake. It is the difference between a project that ends when you say it ends, and a project that ends when the client runs out of "just one more."
The checklist above is the working core of the Freelancer Client OS kit — a plain-language contract template (scope, revisions, kill fee, IP transfer), a proposal template, a 19-question client intake questionnaire, five word-for-word scope-creep scripts, a four-email late-payment escalation sequence, and an Excel pricing calculator for your real hourly rate. $19 one-time, 30-day refund:
https://www.getly.store/product/freelancer-client-os-contracts-proposals-payment-protection
Templates are general business documents, not legal advice — have a local professional review the contract for large projects.
Top comments (0)