Introduction
“Can you just tweak this one more time?” — said for the 15th time. Unlimited revisions are the #2 profit killer for freelancers (after scope creep). The client keeps asking for changes, you keep making them, and you’ve done 3x the work for the same price.
This post shows you how to set revision limits, handle excessive revision requests, and protect your time.
Why unlimited revisions are a problem
- Time: Each revision takes 30-60 minutes. 10 revisions = 5-10 hours of unpaid work.
- Quality: After too many revisions, the work gets worse, not better. Design by committee produces mediocre results.
- Resentment: You start resenting the client and the project.
- Precedent: If you allow unlimited revisions once, the client expects it always.
The solution: define “revision”
What IS a revision:
- Changing the color of a button
- Adjusting font sizes
- Swapping an image
- Minor text edits
- Reordering sections
What is NOT a revision (new scope):
- Adding a new page
- Changing the entire design direction
- Adding new features or functionality
- Rewriting all the copy
- “Make it look like [competitor’s site]”
Rule of thumb: If it takes more than 30 minutes, it’s not a revision — it’s new scope.
Setting revision limits in your proposal
Standard approach
Revisions: 2 rounds included
Additional revisions: ₹1,500/round
Tiered approach
Basic package: 1 revision round
Standard package: 2 revision rounds
Premium package: 3 revision rounds
Time-based approach
Revisions: Unlimited within 14 days of delivery
After 14 days: ₹1,500/round
How to handle excessive revision requests
Script 1: Gentle reminder (revision 3+)
“I’m happy to make this change! Just a heads up — we’ve used [X] of your [Y] included revision rounds. After [Y] rounds, additional revisions are billed at ₹[rate]/round. Would you like me to proceed with this change?”
Script 2: Out of revisions
“I’ve made the changes you requested! We’ve now used all [Y] included revision rounds. Any further changes will be billed at ₹[rate]/round. Let me know if you’d like me to proceed with additional revisions.”
Script 3: “Just one more small thing”
“I can definitely make that change. Since we’ve used all included revisions, this would be billed as an additional revision round (₹[rate]). Shall I go ahead?”
Script 4: Scope change disguised as revision
“That’s a great idea, but adding [feature/page/section] is beyond the scope of revisions — it’s essentially a new feature. I can add it for ₹[amount] with an additional [X] days. Would you like me to include it as an add-on?”
The “consolidate feedback” technique
Clients often send revisions one at a time (“change the color,” then “make the text bigger,” then “move this section”). This is inefficient.
Solution: Ask for all feedback at once.
“I want to make sure I capture all your feedback. Could you compile all changes into one document or email? I’ll implement them all in the next revision round. This way we use one round instead of multiple.”
This reduces revision rounds and saves time.
The “approval checkpoint” technique
Instead of one final review, use checkpoints:
- Wireframe approval — “Does the layout work before I design it?”
- Design approval — “Does the design match your vision before I build it?”
- Content approval — “Is the copy correct before I finalize?”
- Final review — “Any last tweaks before launch?”
This catches issues early (when they’re cheap to fix) instead of late (when they’re expensive).
When to say “enough”
If a client has used all revisions and keeps asking for more:
- Acknowledge: “I understand you want it perfect.”
- State the boundary: “We’ve used all [Y] included revisions.”
- Offer options: “I can do additional revisions at ₹[rate]/round, or we can launch and make tweaks post-launch.”
- Stand firm: “I want to make sure we launch on time. Let’s finalize and go live.”
Common mistakes
- Not setting a revision limit — “unlimited revisions” is a trap
- Not defining “revision” — clients and freelancers have different definitions
- Doing free revisions — once you do one free revision, they expect more
- Not tracking revisions — if you don’t count, you can’t enforce the limit
- Being too flexible — “just this once” becomes “every time”
Key Concepts
- Revision = changes to existing work within scope
- New scope = additional features or pages (billed separately)
- Revision round = one batch of changes (not one individual change)
- Consolidated feedback = all changes in one document
- Approval checkpoint = review at each project phase
What to Try Next
- Handle scope creep professionally
- Write a scope of work that prevents scope creep
- Say no to extra work without losing clients
- Price your services with a proven framework
FAQ
What if the client says “I thought revisions were unlimited”?
“I understand the confusion! Our agreement includes [X] rounds of revisions. Additional rounds are billed at ₹[rate]. I’d be happy to make these changes — shall I proceed with the additional revision round?”
How many revision rounds should I include?
2-3 rounds is standard. More than 3 and you’re giving away too much. Fewer than 2 and clients feel constrained. Adjust based on project complexity and client type.
What if the client keeps asking for “just one more small thing”?
Set a threshold: “Changes under 15 minutes are included as courtesy. Changes over 15 minutes are billed as a revision round.” This filters out trivial requests while protecting your time. See Handle Scope Creep.