DEV Community

xiaoxin
xiaoxin

Posted on

How I stopped losing money on client revisions — a system that works for any freelance project

I'm a freelancer. Last year I sat down and actually calculated how much time I'd spent on revision rounds beyond what I'd originally scoped. The number made me sick — roughly $8,000 in unbilled hours across a dozen fixed-price projects.

The worst part? Most of the extra rounds weren't even meaningful changes. They were:

  • "Can we try a different font?" → switched back to the original
  • "The CEO wants to see a blue version" → CEO never looked at it
  • 11 separate emails over 4 days instead of one organized batch

I built a system to stop this. Here it is — every step is free to implement.

Step 1: State revision limits in the proposal, not the contract

Don't bury this in legal text. In my proposal email I literally write:

"This project includes 3 rounds of revisions. Each round = one consolidated batch of feedback from your team. Additional rounds: $X each."

Clients skim contracts. They read proposals. Put the limit where they'll actually see it.

Step 2: Acknowledge the round number every single time

Client sends changes? My reply template:

"Received — incorporating these as revision round 2 of 3. One round remaining after this."

This does three things: reminds them the counter exists, incentivizes consolidated feedback, and eliminates the "I didn't know" conversation later.

Step 3: Give options, not ultimatums

Bad: "You've used all your revisions. Pay me."

Good: "We've completed the 3 included rounds. The current version is final-ready. If you'd like additional changes, I can do those at my hourly rate — or we can wrap here. Your call."

Step 4: Make the counter visible to both sides

If you track revisions in your head, the client doesn't feel the cost. When they see "2/3 rounds used" — whether on a shared doc or a tool — their behavior changes instantly. Feedback becomes focused because every round is finite.

Why this works

Unlimited revisions feel free. A visible counter changes the psychology. Same reason buffets have more waste than à la carte.

Results after ~20 projects

  • Average revision rounds: from ~5 to exactly 3
  • Zero "can we just try one more thing?" after the final round
  • I stopped dreading my inbox

The tool I ended up building

I eventually built Revision Desk to automate this — project pages with visible counters, client share links, file uploads, and a separate client revision log. 14-day free trial if you want to try it.

But a shared Google Sheet works too. The system matters more than the software.

What's your revision policy? Drop it in the comments — I'm curious how other freelancers handle this.
freelance webdev design productivity tutorial

Top comments (0)