The $9,400 Sentence
In May 2025 I wrote two words on a proposal: "unlimited revisions."
It was a brand identity project. The client was a founder I liked, the brief felt clear, the budget was reasonable ($4,800), and I figured "unlimited" was a generous gesture that would close the deal. It closed the deal.
By August I had delivered the project 27 times.
Twenty-seven full revision rounds. Logo color shifted in eleven of them. Typography swapped three times and came back to the original twice. The founder's co-founder joined in round 14 with a complete redirection. The founder's spouse weighed in around round 19. By round 23 we were comparing the latest version to round 6, which the founder now said was "actually closer to what we wanted."
The project finally signed off in late August. I had logged 94 additional hours beyond the original scope. At my $100/hr target rate, that's $9,400 of free work on a $4,800 project. Effective hourly rate for the whole engagement: $32/hr. I would have made more money working at a coffee shop for the same calendar time.
I never wrote "unlimited" on a proposal again. This post is what I wrote instead.
Why "Unlimited Revisions" Attracts the Worst Clients
The instinct to offer unlimited revisions comes from a generous place. You want the client to feel cared for. You want to compete with the freelancer down the road who's offering the same. You assume your work will be good enough that the revisions won't materialize.
What actually happens, structurally:
- Clients with internal alignment problems self-select toward "unlimited." A founder who can't get their team aligned on a brand direction will absolutely shop for the freelancer who will iterate forever for one price. You become the unpaid alignment therapist.
- You signal that your time has no economic weight. A client who pays a freelancer who values their own time will treat that time carefully. A client who pays a freelancer who doesn't, won't.
- The Norman Odeh case (the freelancer who wrote about his "$12,000 revision clause" on Medium in late 2025, which made the rounds) makes the same point with different numbers. The pattern is consistent across every freelancer who's been burned by this.
The mistake isn't generosity. The mistake is confusing generosity to clients with self-erasure.
The 3-Round Policy (the Actual Structure)
The replacement is a 3-round revision policy with each round having a defined purpose. The number isn't sacred — some people do 2, some do 4 — but the structure matters more than the count.
Each round has a name and a scope:
Round 1: Structural feedback. The client responds to the first delivery with structural changes. Layout, page structure, IA, major direction. They don't pick at headlines or icon colors. If they do, you note that the feedback is being pulled forward into round 2 and they should hold structural questions.
Round 2: Design and content feedback. Visual decisions, copy, component-level changes. Specific colors, fonts, imagery, button labels. By the end of round 2 the document is approximately what will ship.
Round 3: Polish. Microcopy, alignment, spacing, animation timing, final QA. Round 3 should not introduce new ideas. If it does, it gets a change order.
Anything past round 3, or anything that introduces new scope inside a round, is billed at your hourly rate.
The structure does two things at once. It teaches the client how to give feedback (the framing changes their behavior) and it gives you a defensible reference point when round 4 shows up ("we agreed round 3 is polish, this is direction, so it's a change order").
The Contract Clause (Copy-Paste, Adapt to Local Law)
Revisions
The deliverables include up to three (3) rounds of revision feedback from the Client. Each round consists of a single consolidated feedback document or call, returned to the Contractor within seven (7) calendar days of delivery.
Rounds are scoped as follows:
- Round 1: structural feedback (layout, structure, direction).
- Round 2: design and content feedback (visual decisions, copy, component-level changes).
- Round 3: polish (microcopy, alignment, final QA).
Feedback introducing scope outside the agreed deliverables (new pages, new components, new functionality, or new directions) will be handled as a change order per Section [X] and is not counted toward the included rounds.
Revisions requested beyond the three included rounds, or feedback returned later than seven (7) calendar days after delivery, will be billed at the Contractor's hourly rate of $[rate]/hour, with an estimate provided before work begins.
Three things this clause does that "you get 3 revisions" doesn't:
- It defines what each round is for. Without this, "round 2" turns into a second round 1 because the client didn't know rounds were scoped.
- It puts a clock on the feedback. A 7-day window prevents the project from sitting in client-side limbo for 4 months while you can't bill anything.
- It explicitly separates new scope from revisions. "This is not a revision, this is a change order" needs to live in the contract, not in an awkward email.
Have a local lawyer adjust the language for your jurisdiction. The structure transfers; the wording shouldn't be lifted blindly.
The Visible Counter (the Operational Half)
The clause is necessary. It's not sufficient. The operational piece that actually keeps clients inside the structure is visible status.
After each delivery, send a one-line note. Verbatim:
After round 1 delivery: "Round 1 delivered. Awaiting structural feedback — 2 of 3 included rounds remaining."
After round 2 delivery: "Round 2 delivered. 1 of 3 included rounds remaining."
After round 3 delivery: "Round 3 delivered. This is the final included round per the contract. Any further revisions will be handled as additional billed time — happy to estimate if needed."
This feels uncomfortable to send the first few times. It is also the single most reliable behavior-change mechanism I have ever introduced into a client relationship. Clients adjust their feedback patterns within one project once they see the counter.
Briefance bakes this counter into the project view because of exactly this dynamic — most freelancers have the contract clause but never enforce it operationally, and the contract on its own doesn't change client behavior.
When the Client Pushes for Round 4
This happens. Here's the script.
The friendly push (most common):
"Hey [Name] — thanks for round 3, looks great. Just a few small tweaks I'd love to see, can you do one more pass?"
Your reply:
"Happy to take that on. We're past the 3 included rounds, so this one will be a change order — based on what you've described, I'd estimate 2 hours at $125/hr = $250. Want me to send the formal change order to sign before I start?"
Three things to notice:
- No apology. Apology signals the contract is negotiable.
- A specific number. "Some additional hours at our hourly rate" gives them an opening to negotiate. "$250" doesn't.
- The change order is formal. Not "I'll just add it to the next invoice." A signed change order. This is what trains them that the boundary is real.
The harder push (less common but worth preparing for):
"I think when we signed this we both understood it would take whatever it took to get it right."
Your reply:
"I hear you. The contract has 3 rounds because that's what's economically viable for a project at this price — anything beyond that needs to be billed, otherwise I'm working at a loss. I'm not trying to nickel-and-dime; I'm trying to keep the math honest so we can both finish this project happy. $250 for the round, let me know."
You don't have to apologize and you don't have to capitulate. The economic reality is on your side. Speak it plainly.
What If You're Already Trapped Mid-Project?
Worst case. You're 6 rounds in on an unlimited-revisions project, the client thinks you're going forever, and you can feel the resentment building.
Two scripts depending on how the project is going.
If the relationship is healthy enough to renegotiate:
"Hey [Name] — I want to be straight with you because the project's been great. We're at round 6 now and I want to make sure we land it without burning either of us out. Can we agree round 8 is the cap, with anything after being a small additional fee? I'd rather have that conversation now than at round 10."
If the relationship is already strained:
Don't renegotiate. Set a hard floor with one final round.
"I want to scope round 7 carefully so we can wrap this. Can you send all remaining feedback in one consolidated doc by [date]? I'll address it in one final pass and we'll ship after that."
Then ship it, regardless of what comes back. Take the lesson and never write "unlimited" again.
The Filtering Effect (the Hidden Win)
Switching from "unlimited" to 3 rounds will cost you some leads. The leads it costs you are the leads that would have cost you 80 hours of unbilled work.
A founder who walks away because you have a revision cap is telling you that they intended to make you iterate until they figured out what they wanted. That's a project, not a discovery process, and you shouldn't be funding their discovery process at $32/hr.
In the 11 months since I switched, my close rate dropped about 12%. My average effective hourly rate went up roughly 38%. The math is not subtle.
TL;DR
- "Unlimited revisions" attracts clients with internal alignment problems and signals your time has no economic weight.
- Replace it with a defined-round policy (3 rounds is the working default for design; 2 for dev; 2 for copy). Name what each round is for.
- Use the contract clause above as a starting point. Get local-law review.
- Operationalize with a visible counter after every delivery. The counter changes client behavior more than the clause does.
- When round 4 happens, send a specific dollar number and a formal change order. No apology.
- If you're trapped on an existing project, scope a hard final round and ship.
You are not less generous than the freelancer who offered unlimited. You are still in business in twelve months.