“Two rounds of revisions” is on nearly every web design proposal. It is also, on its own, meaningless. Nobody has defined what a round is, so round two starts, a third email arrives a week later with “one more thing,” and round two somehow never ends. The limit was never really a limit, because it was never written down as anything other than a number.
This is not a client discipline problem. It is a process gap, and it is entirely fixable before the next contract goes out.
Why unlimited (or undefined) revisions is a pricing mistake
Margin, not goodwill. Every round of revisions costs real hours: reviewing feedback, making changes, re-presenting. A fixed-price project with no round limit has an unbounded cost against a bounded price. The agency is the only party absorbing that risk.
It removes the client's own filter. When rounds are unlimited, there is no reason for a client to consolidate their own feedback or decide what actually matters before sending it. Each small thought becomes its own message, and the project drifts instead of converging.
It makes “done” undefined. A project with a round limit has a built-in end state: once the included rounds are used, the deliverable ships as-is or the client pays for more work. Without that limit, there is no natural point where the site is finished rather than merely paused.
Step 1: Define what a round actually is
A round is one consolidated set of feedback, delivered in one place, by one date. That definition does the real work here. It means feedback that trickles in across a dozen emails over two weeks is still one round, as long as it is responding to the same deliverable, and it means the client is the one who decides when they are done sending feedback for that round, not the agency guessing.
Without this definition, every new email can be argued as its own mini-round, and the contract's round count becomes unenforceable in practice even if it is correct on paper.
Step 2: Put the number in the contract, not the kickoff call
State the included round count, per deliverable, in the signed proposal, in a sentence a client can point back to later. “Two rounds of revisions per page design” said out loud in a kickoff call is forgotten or disputed by round three. The same line in a contract they signed is simply a fact both sides already agreed to.
Two rounds is a reasonable default for most agency work: one broad pass covering layout, structure and content direction, and a second for the remaining detail-level fixes. Larger, brand-sensitive builds sometimes justify three. Fewer than two rarely gives a client room to react to something genuinely new in round one.
Step 3: Separate a fix from a new request
This is where most disputes actually live, not in the round count itself. A fix addresses something that does not match the approved brief or an earlier round's own feedback: the wrong color, a broken layout on mobile, a typo in the copy that was already approved. A new request introduces something nobody discussed: an additional page, a different layout concept, a feature that was never scoped.
Only fixes should count against the included rounds. New requests get a change order, with its own price and timeline impact, agreed before the work starts, not absorbed silently into “round two.”
Step 4: Collect every round in one place
The trickle problem
Feedback over email arrives in pieces: one thought today, another tomorrow, a screenshot forwarded from a client's phone three days later. Each piece feels like a fresh ask, so the round never visibly closes.
The batch fix
A tool the client marks the live page up on directly turns scattered comments into one visible list, with a screenshot and context attached to each. The round has a start, an end, and a count the client can see for themselves.
This is the practical reason an embedded feedback tool beats email for this specific problem: it is not just about collecting feedback well, it is about making a round look like a round, to both sides, instead of an open-ended inbox thread.
Step 5: Price the next round before you need it
Put a flat rate or hourly rate for any round beyond the included count in the same clause that states the included number. When round three actually arrives, quoting it is reading a sentence back to the client, not negotiating a new charge on the spot. That difference is most of what keeps the conversation friendly.
When to bend the rule anyway
Hold the line on scope, not on relationships. If a long-standing client is one small fix past their round limit and the fix takes four minutes, charging for a new round is a worse business decision than just doing it. Save the enforcement for requests that are genuinely new work, or for clients who treat “unlimited” as the actual expectation. The written limit exists so you have the option to say no, not an obligation to say no every time.
How to limit revision rounds, step by step
- Define what counts as one round. One consolidated set of feedback, in one place, by one date, regardless of how many messages it arrives in.
- Set the round count in the contract. State it in the signed proposal, per deliverable, not in a verbal kickoff mention.
- Separate a fix from a new request. Only feedback against the approved brief counts toward the limit; new asks get a change order.
- Collect every round in one place. Use a tool like tapko.app that lets clients mark up the live page directly, so one round is one visible batch instead of a trickle of emails.
- Price the next round upfront. Put the rate for rounds past the included count in the same clause, so it is a formality to quote later.
Frequently Asked Questions
How many revision rounds should a website project include?
Two rounds per deliverable is the most common default: one broad pass covering structure and content, one for remaining detail fixes. Smaller projects sometimes do one; larger brand-sensitive sites sometimes do three. The number matters less than writing it down and having a price for anything past it.
What counts as a revision round versus a new request?
A revision addresses something that does not match the approved brief or an earlier round's feedback: wrong color, broken layout, a typo. A new request introduces something never discussed: a new page, a different layout approach, a feature that was not scoped. Only revisions count against the included rounds; new requests get a change order.
Why do agencies offer unlimited revisions?
Usually to sound generous in a proposal, or because there was no process for saying no to round five. Unlimited revisions removes the one lever that makes a client consolidate and prioritize their own feedback, so rounds multiply instead of converging toward a finished site.
How do you tell a client they are out of included revision rounds?
Point back to the contract clause they already signed, rather than making a judgment call in the moment. “You have one round left after this one, per the proposal” lands as a reminder of something agreed, not as a new rule being invented to say no to them.
