"Unlimited revisions" reads as reassuring to a client and, from the other side, functions as an unbounded commitment with no defined endpoint. It's rarely actually meant to be exploited, but without a boundary, revision requests can drift indefinitely, each one individually reasonable, the total anything but.
The client's underlying worry, being stuck with something they don't like, can be addressed without agreeing to a genuinely open-ended commitment.
Unlimited sounds generous and behaves like an open-ended cost
A promise with no limit removes any natural point where the work is considered done, which means the project can, in practice, never fully close. What sounds like flexibility for the client is actually an unbounded liability for whoever's delivering the work.
Find the real worry behind the request
A client asking for unlimited revisions is usually worried about being stuck with an outcome they don't like, not planning to request fifty rounds of changes. Address that underlying worry directly rather than agreeing to the literal, unbounded ask.
In Stelaah, a project's revision rounds can be tracked against the scope, so both sides can see clearly how many have happened and how many remain. See how projects works.
Offer a generous, bounded number instead of unlimited
Three or four rounds, framed as genuinely generous, gives the client real room to iterate while keeping the commitment finite. Most legitimate revision needs are met well within a bounded number; it's the truly open-ended promise that creates risk.
Define what counts as a revision versus new scope
A revision refines what was already scoped; a request for something genuinely new is additional work, not a revision round. Drawing that line explicitly prevents scope from quietly expanding under the umbrella of "just a revision."
Build in a real review cycle instead of open-ended tweaking
Structured review rounds, with a defined start and end to each one, feel more collaborative to a client than an ambient sense that changes can happen whenever, indefinitely. Structure actually produces a better outcome than unlimited access does.
A simple checklist
If you do nothing else, do these five things:
- Identify the real worry behind an unlimited-revisions request.
- Offer a generous, bounded number instead of open-ended access.
- Define clearly what counts as a revision versus new scope.
- Structure review as defined rounds, not ambient ongoing tweaking.
- Track revisions used against the agreed number, visibly.
Do that, and the client's real need for confidence gets met without taking on a commitment that never actually ends.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
