Stop the third free revision: how to charge for "can we just add…"

The third free revision isn't generosity. It's an unofficial second job you don't get paid for.

Every freelancer and studio has lived this: you scoped the project honestly, the client signed, and then the work quietly drifted past the line you both agreed on, one "can we just..." at a time. You did not decide to work for free. You backed into it, because nothing connected the agreement you signed to the work you were actually doing. This guide is about the structural reason scope creep happens, why "just be firmer" does not fix it, and the one change that does, plus a free template you can use on your very next project.

The pattern, named

You quote three concepts and two rounds. The client signs. Then the requests arrive framed as tiny favors: one more direction, move it back to version two, add a square crop, "last thing, I promise." Each one is small. None is in the contract. And because saying "that’ll be extra" feels like starting a fight over $200, you absorb it. By delivery, the invoice matches your quote, but the work matches something twice as big.

What "just one more" actually costs (do your own math)

For a solo doing around twenty projects a year, that is roughly $4,500 to 6,000 in revision time and swallowed scope you never billed, call it two unpaid rounds a month. It's not a scare number; it is your own rate times the rounds you gave away. Run it against your numbers with the worksheet in the template below.

Why "just set boundaries" fails

The advice is always willpower: say no, be firmer. It misses the real problem, which is structural:

• The agreement is invisible exactly when you need it. When the request lands, your contract is a PDF in a folder you will not reopen mid-chat. So you wing it, and winging it always rounds down to free.
• Charging feels like a confrontation. Without a system, billing for a change means you personally choosing to be the bad guy, in the moment, over a small ask. Most people eat it.
• You have nothing to point at. "That’s out of scope" is your opinion. A signed change order with a price and a timestamp is a fact. One starts an argument; the other ends it.

The fix: make charging the easy path

You do not need a stronger spine. You need the billable path to be the frictionless path, so the awkward decision moves off you and onto the system: a scope agreement that stays a live reference (not a filed PDF), a one-click way to turn an extra ask into a priced change order, and a clean place for the client to confirm it, on the record, before the work happens.

How Tideway's Scope Shield does it

In Tideway, an accepted proposal automatically becomes a scope agreement: deliverables, your revision policy (say, "3 rounds included"), and terms in one place. When the next "can we just add..." arrives, you turn it into a one-click billable change order: add the extra round or deliverable, set the price, send it. Your client opens your white-label portal on a single link (no signup, no per-client fee), sees exactly what changed, and confirms it. Tideway logs a green confirmed badge and a timestamp. The extra work is now agreed, on the record, and billable before you start it. (Scope Shield is on the Pro plan, $23/mo annual, 14-day trial, no card.)

Get the template (use it on your next project)

A copy-paste scope agreement with a fill-in revision policy, a ready-to-send change-order script for the exact "can we just add..." moment, and a one-page worksheet that computes what free revisions are costing you. Free, no tool required.