Why I Stopped Giving Unlimited Revisions

Why I Stopped Giving Unlimited Revisions

Offering unlimited revisions felt generous — until it quietly became the thing that was draining my time, my income, and honestly, my will to keep freelancing. If you've ever said "sure, I'll fix that" for the fifth time on a project that should've been done weeks ago, this is for you. I'm going to tell you exactly what went wrong, how bad it got, and the system I built to make sure it never happens again.

Key Takeaways (TL;DR)

  • Unlimited revisions sound client-friendly but are a direct threat to your income and mental health
  • Scope creep compounds fast — one uncapped revision policy can cost you dozens of billable hours monthly
  • A structured revision policy, paired with AI tools, can protect your time without damaging client relationships
  • Free and paid tools exist to help you write, enforce, and automate your revision boundaries
  • The shift from "yes to everything" to "yes within structure" is where sustainable freelancing actually begins

The Promise That Slowly Broke Me

I added "unlimited revisions" to my freelance packages back when I was trying to stand out.

It worked — clients loved it, and bookings picked up fast. What I didn't see coming was that a handful of those clients would treat that policy like an all-you-can-eat buffet with no closing time.

One client in New York — a startup founder I genuinely liked — sent me 11 rounds of revision requests on a single landing page. Eleven. Each one reframed the entire direction of the copy.

That project paid a flat rate. I'd already spent three times the estimated hours on it. And because I'd written "unlimited revisions" in my contract, I had zero ground to stand on.

When One Bad Policy Multiplies

Here's what most freelancers don't realize until it's too late:

One uncapped revision policy doesn't just cost you hours on one project. It sets a precedent across your entire client roster.

The client who got 11 rounds told a colleague. That colleague hired me expecting the same. Meanwhile, I was so deep in revision loops that I started missing deadlines for other clients — good clients, who had been respectful the whole time.

Here's where it spirals:

Missed deadlines erode trust. Eroded trust triggers more micro-management. More micro-management means more revision requests. More revision requests on uncapped projects means your calendar turns into a hostage situation.

I did the math one Sunday afternoon in New York last year. Roughly 30% of my working hours that month had gone to unpaid revision work. That's nearly one and a half days a week I was working completely for free.

If you scale that over a year, that's over two months of your life handed over at no charge.

The risk isn't just financial either. Chronic scope creep quietly reshapes how you see your work. You stop feeling like a skilled professional and start feeling like a vending machine that keeps giving even when no money was inserted.

The System I Built to Fix It

I didn't just remove "unlimited revisions" from my contracts. I replaced it with something better — a revision framework that clients actually respect, backed by clear communication and a few smart tools.

Start With a Revision Policy That Has Teeth

A vague policy is as bad as no policy. Here's the structure I now use:

  • Round 1: Minor copy or design tweaks based on the original brief
  • Round 2: One round of consolidated feedback (all notes in one document, not drip-fed over email)
  • Additional rounds: Billed at my hourly rate, communicated upfront

The key word there is consolidated. Clients who have to gather all their notes into one document before sending them stop nitpicking. It forces intentional feedback instead of reactive feedback.

Use AI to Write Your Policy Language (Free)

If writing your own contract language feels awkward, this is exactly where AI earns its keep.

Here's the prompt I used in ChatGPT:

"Act as a freelance contract specialist. Write a professional but friendly revision policy clause for a freelance copywriter. It should include: 2 rounds of revisions, a definition of what counts as a revision vs. a new request, and a clear rate for additional rounds. Keep it under 150 words and avoid legal jargon."

ChatGPT (free tier at chat.openai.com) will generate clean, usable policy language in under 30 seconds. Refine it to match your voice, paste it into your contract, and you're done.

Tools to Document, Send, and Enforce Your Policy

Worth knowing:

You don't need expensive software to protect your boundaries. Here's what I actually use:

Free Options

  • ChatGPT (Free tier) — Drafting policy language, revision request response templates, and client communication scripts. chat.openai.com
  • Google Docs — Storing and sharing your revision policy as a linked document clients sign off on before work begins
  • Notion (Free tier) — Tracking revision rounds per project so you always know exactly where you stand. notion.so
  • HelloSign (Free tier — up to 3 documents/month) — Getting client signatures on your updated contracts. hellosign.com

Paid Options

Tool What It Does Cost
ChatGPT Plus Faster, smarter contract and email drafting $20/month
HoneyBook Starter Client contracts, invoicing, and project tracking in one place $19/month
Dubsado Starter Automated client onboarding with built-in contract workflows $20/month
Notion AI Summarizes revision threads and drafts response emails $10/month
DocuSign Personal Unlimited document signing with audit trails $15/month

Start free. Upgrade only when volume genuinely demands it.

How to Handle the Conversation Without Losing the Client

Here's the part most freelancers dread:

Telling an existing client — especially a good one — that the rules are changing.

I used this exact ChatGPT prompt to draft my transition email:

"Write a warm but professional email to an existing freelance client explaining that I'm updating my revision policy going forward. I now offer 2 rounds of revisions. Emphasize the benefit to them — faster turnarounds and more focused feedback. Keep it friendly, under 120 words, and don't sound apologetic."

Not a single client left. Two of them actually replied saying they respected the clarity.

The honest truth:

Clients don't leave because you set boundaries. They leave because you set them badly. AI helps you set them well.

The Friday That Changed My Mind About All of It

Last week, I wrapped a full brand copywriting project in New York — three deliverables, two revision rounds, done.

The client sent one consolidated round of feedback. I addressed everything in an afternoon. We signed off by Friday.

I had the entire weekend free.

No lingering emails. No "just one more small thing." No guilt about a project still technically open three weeks past its due date.

That Friday felt like something I hadn't felt in a long time: like my work had a beginning, a middle, and an actual end.

Before vs. After: The Real Shift

Before the Revision Policy

  • Calendar constantly hijacked by old projects
  • Income unpredictable because hours were uncapped
  • Clients trained to expect unlimited access
  • Resentment quietly building toward work I used to love
  • Every "done" project felt hypothetically undone

After the Revision Policy

  • Projects close on schedule, every time
  • Income reflects actual hours worked
  • Clients give better, more intentional feedback
  • Creative energy preserved for new work
  • "Done" actually means done

Your Work Deserves a Finish Line

Unlimited revisions feel like kindness. But kindness without structure isn't sustainable — it's just delayed resentment.

The moment you define what's included in your fee, what falls outside of it, and how you'll handle the difference, you stop being a vendor and start being a professional. And that shift changes not just your calendar, but how clients see you — and how you see yourself.

What's Your Revision Story?

If you're stuck in a revision loop right now, or you're not sure how to word your policy, drop a comment below. Tell me where you're at — I read every single one and I'll help you figure out the next step.

Frequently Asked Questions

Won't capping revisions scare clients away?
The clients worth keeping actually appreciate clear policies — it signals professionalism. The clients who push back hardest on revision limits are usually the same ones who would've exhausted your time anyway. A clear policy is a natural filter.
What counts as a "revision" versus a "new request"?
A revision adjusts existing work based on the original brief — changing a headline, tweaking tone, fixing a factual error. A new request changes the direction, scope, or core concept of the deliverable. I define both explicitly in my contract so there's no grey area.
What if a client insists on more revisions mid-project?
Have a pre-written response ready. Something like: "I'd love to keep refining this — additional rounds are billed at [rate]. Want me to send over a quick add-on invoice so we can keep moving?" Keep it warm, keep it matter-of-fact, and don't apologize for it.
Can I use AI to handle the actual revision feedback process too?
Yes. I paste client revision notes into ChatGPT and ask it to identify which requests are within scope and which represent new directions. It saves me from having to make that judgment call in the heat of the moment when I'm already frustrated.
How do I implement this for clients I've already promised unlimited revisions to?
Introduce the new policy at the start of your next project together — not mid-project. A simple line like "I've updated how I structure revisions to keep projects moving faster for both of us" is enough. Frame it as a benefit to them, because honestly, it is.
« Newer Post Next Workflow Older Post » Previous Guide

Comments