The Client Who Paid Per Revision, Not Per Hour

The project started clean. A fixed number of deliverables, a clear rate, a reasonable timeline. Then around week three, the client said something that should have alarmed me immediately.

"We just pay per revision round, not per hour. That's how we work with everyone."

I had not agreed to that. It was not in the contract. But I also had no hourly data ready to push back with, because I had been estimating loosely and trusting my gut. That was the mistake.

When the Structure Changes, the Power Shifts

Revision-based billing sounds fair until you realize what it does. It removes time from the equation entirely. The client stops caring how long something takes. They care only that they get another round of changes for the same flat fee.

A one-hour revision and a six-hour revision cost them the same. Which means they have zero incentive to give clear feedback the first time. And you have no way to show them why that matters unless you have the hours logged.

Without tracked time, you cannot say "round two took four hours because the brief changed." You can only feel it.

The Number They Do Not Expect You to Have

Halfway through the third revision cycle on that project, I started tracking. Not for the invoice, just to understand what was happening. The data was brutal. Each round was running longer than the last. The first revision took ninety minutes. The third took nearly five hours because the client had looped in a new stakeholder who had different opinions on everything.

When I brought that up in our next call, I had actual numbers. I was not complaining. I was reporting. There is a difference, and clients feel it.

Tracked time turns a frustration into a fact. That changes the conversation.

What You Learn When You Watch the Pattern

Revision creep follows a pattern almost every time. The first round is fast because the client is engaged and the work is fresh. The second round slows down because they have had time to second-guess things. The third round often involves someone new who was not in the original brief.

If you can see that pattern in your time logs, you can price for it. You can build a revision cap into your next contract and back it up with real data from past projects. You stop guessing at what "a revision round" costs you and start knowing.

Time-Trak's floating timer makes this easy to keep running even when revision work bleeds into email threads and Slack messages. You can log it all without interrupting the work itself. That matters because revision hours are sneaky. They hide in small interactions that feel too minor to track. They are not minor. They are where your rate goes to die.

The Contract Clause I Now Have

After that project, I added a single line to every contract: revision rounds are capped at two hours each. Additional time is billed at my standard rate and supported by time logs provided on request.

No client has ever pushed back on that clause. What they do push back on is vague revision language that leaves them feeling like you can charge anything, anytime, without explanation. The clause is not about limiting their access to changes. It is about making the cost of changes visible before they happen.

That visibility only works if you actually have the data to show. Which means you need to be tracking before the revision request lands, not after.

The Real Lesson

Clients who want to pay per revision are not always trying to take advantage of you. Sometimes they genuinely think it is simpler. But simple for them can mean expensive for you if you are not watching the hours.

The answer is not to argue about billing structure. The answer is to have time data that makes the real cost of any structure completely clear. Then you can have that conversation from a position of knowledge instead of anxiety.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots