What Revisions Really Cost: The Price of Rework at an Agency

Revisions feel like small stuff: "the client asked for a few tweaks — no big deal." But every round of revisions is team hours nobody pays for. They don't show up on your bank statement, they're not in the contract, and all the while they quietly eat into the project's margin. An agency that doesn't track the cost of rework routinely hands the client free work and then wonders why a project that looked profitable ended up at zero.

Let's break down what revisions actually cost and how to stop working on them at a loss.

Why revisions are a hidden hole in your profit

The trouble with revisions is that they don't register as an expense. You see the payment for the project, but you don't see the hours spent on a third round of revisions. Yet they add to the project's cost just as much as the core work does. A project sold at a fixed price based on 100 hours can easily swallow 140 after a few rounds of revisions — and that whole difference comes straight out of your margin. For how overspent hours push a project into the red, see Project margin: how to avoid working at a loss.

What a revision really costs

To see the price of revisions, convert them into money through your cost per hour. If a team hour costs you 600 UAH and a round of revisions took 12 hours, that's 7.2k of your profit given away for free. On a project with several rounds it easily adds up to 20–30k. How to calculate your cost per hour is in Cost per hour at an agency.

Why clients don't value "free" revisions

When revisions are free and unlimited, the client has no reason to be precise in the brief — it's easier to just "look at a few options." People don't value what's free. The moment revisions beyond the limit become chargeable, the client sharpens the request right away — and the number of rounds drops on its own. That's a win for both sides: you don't work at a loss, and the client gets the result faster.

How to cap revisions

The answer isn't to ban revisions but to fix their scope. In the contract or offer, spell out the number of rounds included in the price (say, two), with anything beyond that billed separately at your hourly rate. This isn't greed — it's normal practice: you're selling a result within an agreed scope, not endless iterations.

Example: how 3 rounds of revisions ate the margin

An 80k project, planned cost 60k (100 hours × 600 UAH), built-in margin of 20k. The client ordered 3 rounds of revisions beyond what was agreed — 12 hours each, 36 hours total × 600 = 21.6k of extra cost. Bottom line: cost of 81.6k against a price of 80 — the project went into the red by 1.6k instead of +20. Revisions turned a profitable project into a losing one, and without hour tracking no one would have noticed.

Where to start counting

Start logging hours spent on revisions separately, at least on your current projects. You'll immediately see how much profit is going to rework. Next — cap the scope of revisions in the contract. You can check which projects are actually profitable after all the revisions in 15 minutes — like this.

In Finmap, hours and project costs roll up into margin, so the cost of revisions is visible in real numbers rather than "by gut feel." Try it free for 7 days.