“Unlimited revisions” almost always means unlimited small changes within the agreed design, not unlimited chances to change direction — and because nobody defines it, it becomes the most common source of friction late in a project. A defined number of rounds usually serves you better than an undefined promise.
Buyers ask about revisions early, often before price. It’s a sensible instinct: you know you’ll want changes and you don’t know how they’ll be treated.
The moment it happens
“Unlimited revisions” — does any web company actually mean it? You find out at the point where changes stop being welcomed and start being answered slowly.
Nothing is refused outright. The replies just get longer, then vaguer. Somewhere in round four, the tone shifts, and a promise that felt generous at signing has become the thing you’re both quietly arguing about.
Why the promise breaks down
Two definitions of “revision” are in play. Moving a section, changing a colour, swapping a photo — small, bounded, cheap. Redesigning the homepage layout after approving it, or restructuring the page order — a different scale of work wearing the same word. Buyers reasonably use one meaning; vendors budget for the other.
Nobody logged what was approved. Without a record of “design approved on the 12th”, every later request is arguably a revision of something already settled, or arguably part of the original scope. Both readings are available, which is why it turns into a dispute.
The design committee arrives late. A spouse, a business partner, a friend who “knows computers” sees the site at 80% and has genuinely useful opinions. Those opinions are also a second design brief, delivered after the first one was built.
And sometimes the buyer can’t stop. Projects sit unlaunched for months because the owner keeps finding one more thing. That isn’t the vendor’s fault, and the promise of unlimited revisions actively enables it.
What to ask for instead
A number is more useful than “unlimited”, because a number implies both sides know what’s being counted.
| Ask this | Why it’s better |
|---|---|
| “How many revision rounds are included, and what’s a round?” | Turns an argument into arithmetic |
| “What’s the rate for changes after that?” | Makes extra changes a purchase, not a favour |
| “What counts as a change vs a redesign?” | Names the boundary before you’re standing on it |
| “When does design get formally approved?” | Creates the reference point everything else depends on |
| “Who on my side can say ‘final’?” | Prevents the late committee |
Two or three rounds of consolidated feedback is normal for a small site and enough for most projects, provided the rounds are used properly.
How to use your rounds well
- Collect feedback in one pass. Ten separate messages over four days is one round burned inefficiently and a developer switching context repeatedly. Look at everything, list everything, send once.
- Bring your reviewers early. Show the first design to whoever will comment eventually — spouse, partner, the family member with opinions. Their input costs nothing at that point and is expensive at 80%.
- Be specific about outcomes, not solutions. “The phone number is hard to find on mobile” is more useful than “make the header blue”. Vendors can solve stated problems; guessing at intent produces another round.
- Separate must-fix from preference. A wrong phone number is a defect. Preferring a different shade is taste. Treating both as equally urgent is what exhausts the goodwill you’ll want later.
- Know when to stop. A live site earning enquiries with two imperfections beats a perfect one that isn’t launched.
What to do this week
- Ask your vendor the five questions above, in writing, before design work starts.
- Name your own approver — one person who can say final.
- Get anyone who’ll have an opinion to look at the first draft, not the last.
- Keep a single running list instead of sending changes as you notice them.
- Mark your list: defects first, preferences second. Send in that order.
If you want it done the certain way
We state the number of rounds and what happens after them, so nobody is relying on an undefined promise. If your project mainly needs a clear approval process rather than a new vendor, we’ll say that. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- What counts as a “small change” and what doesn’t
- The final-payment standoff
- When the whole family reviews your website design
- Did they put your deadline in writing?
FAQ
How many revisions should a website project include?
Two or three rounds of consolidated feedback is normal for a small business site. What matters more than the number is a written definition of what a round includes and when design is formally approved.
Is it fair for a developer to charge for extra changes?
Yes, once the agreed rounds are used and the request goes beyond the approved design. It stops being fair when the “extra” work is fixing something that was wrong in the first place.
What if I want to change the design completely after approving it?
Expect that to be quoted as new work rather than a revision, at any price level. If you’re unsure about direction, resolve it at the first draft stage when changes are cheap.
