There is a type of client who takes more of your time than they paid for, and usually without meaning to. The design comes back a second time, then a third, then there is one last small change that is not last. You make the changes while quietly resenting it, and you finish the job feeling like you worked a month for a week's fee.
The standard advice is to cap the number of revisions in the contract. That is right and incomplete, because most revision problems are not caused by the number of revisions. They are caused by there being no agreement on what counts as a revision in the first place.
So let us separate it out: why it happens, the difference between a revision and new work, and the conversation that belongs before the job rather than after you are already tired.
Too many revisions is a symptom, not the disease
When a client asks for a fifth round, it does not necessarily mean they are difficult. It means one of three things happened: you misread the brief at the start, they did not actually know what they wanted and are discovering it now, or there is a third person in the picture you never spoke to who is the real approver.
All three are solved before the work starts, not halfway through. The third one is the most expensive: you are talking to the marketing coordinator while they present your work to a director, so every round of feedback arrives from someone you have never spoken to, stripped of the reasoning behind it. The question that prevents this is one line, asked before anything begins: who gives the final sign off on this?
And if the problem is that the client has not identified their own problem, that is a different failure with a different fix. I wrote about the questions that surface it in how to find the client's real problem, and they remove a good half of this kind of feedback before it is ever written.
This is not a freelancer problem, it is a documented one everywhere
Something that should take a little of the sting out of it: this is not you, and it is not peculiar to small projects or to this market. It is measured, at scale, across project management globally.
The Project Management Institute's 2018 Pulse of the Profession, from a survey conducted online in October 2017, reported that "on average, around half (52 percent) of projects experience scope creep and roughly half (48 percent) are not delivered on time". The same release puts 43 percent of projects outside their budget. The figures are in PMI's press release on the report.
Notice the order of that sentence. Scope creep and late delivery are named together, because they are the same problem seen from two sides. Organisations with certified project managers, written contracts and legal teams hit it on roughly half their projects.
What separates them from you is not fewer change requests. It is that they have a written procedure for handling one. You need a small version of that, which is the rest of this piece.
The difference between a revision and new work
A revision improves something you produced as agreed. New work is something that was not in the agreement at all.
- Revision: change the colour, increase the font size, swap this photo for that one, rewrite this line.
- New work: the same ad in another size, the same post in English as well, an extra page nobody mentioned, or changing the concept after it was approved.
Most people conflate the two, deliver the new work as though it were a revision, and then resent the client for asking. The client, meanwhile, does not feel they asked for anything extra, because nobody told them it was extra.
The sentence that fixes it is not "that is not in scope". It is: "That works well, and it is outside what we agreed. I can add it as a separate item for X, or we can finish what is agreed first and look at it after." You have not refused, and you have established that it has a price.
What to write down before you start, in four lines
You do not need a two page contract. You need four lines in the message that carries your price, sent before any work begins:
- Deliverables as a number: three designs, not "designs".
- Rounds of revision, with the round defined: two rounds per deliverable, where a round means all feedback collected and sent at once.
- Who approves: one named person.
- Anything outside that is quoted separately and agreed before it is done.
The second line is the one almost nobody writes properly. "Two rounds of revisions" with no definition of a round invites ten separate messages that the client reasonably counts as ten notes rather than ten rounds. Write explicitly that feedback is collected and sent in one go.
This is not pedantry, and it is better for both sides. A client sending a note every hour is not only costing you time, they are getting worse work, because you are revising something they have not finished forming an opinion about.
What to do when it has already gone wrong
If you are mid project, the revisions have run away, and nothing was written down, the right move is neither to carry on silently resenting it nor to stop work.
Do two things. First, send one message listing what has been produced so far, as a count, in neutral language rather than as a complaint: "So far we have produced five versions of the design, and what remains from the original agreement is X." In about half of cases the situation calms down at that point on its own, because the client genuinely had not been counting.
Second, draw the line forward, not backward. "I will finish this round, and after that any further changes would be at an hourly rate of X." Applying a new rule retroactively damages the relationship. Applying it from here is fair and easy to accept.
If the same client is also slow to pay, that is a pattern rather than an incident, and the prevention side of it is in dealing with a client who does not pay.
If your projects are getting bigger
Once the work is projects rather than small deliverables, the same logic grows into something called scoping. The principle does not change: the difficult conversation belongs before anyone starts building, not after.
The engineering version of this is worth reading even if you never write code. Rivl set it out in how to scope a software project before anyone writes code, and the part about defining what is being delivered before delivery starts applies to any work handed to a client.
The honest limits
No contract wording prevents a difficult client. What the wording does is let you raise the subject without becoming the person who is being awkward, because it was agreed in writing at the start and you are only pointing at it.
And there is a case that has to be said out loud: sometimes the endless revisions are because what you delivered was not good. If a client is asking for a fifth round on the same thing, ask yourself honestly before you start counting their requests: are they being unreasonable, or did I hand over something that was not close to the brief? Both happen, and the first is far easier on the ego than the second.
One last thing, and it is not in any contract. Revision counts drop when you change how you present work. Do not send the finished thing as a surprise. Show the direction first, get agreement on it, then build. Half of the revisions that exhaust people are a return to a direction that should have been settled in the first five minutes.
Underneath, this is an analysis question: where you stand, who you sell to, and who you are being compared with. In my book Growth Engine that is the first part of the whole growth system, because a strategy built on the wrong diagnosis is just an opinion. The three questions are in Part 1, Analysis: where are you. The book is free, and it is in Arabic.