Unlimited revisions · Web development
Unlimited revisions in web development: what is normal
Scope creep is the defining web-dev risk; healthy contracts define the scope and bill change requests, rather than promising unlimited revisions.
Typical range
A defined scope with 1 to 2 revision rounds per milestone. Anything outside the agreed scope, or a further round, is a billed change request.
Off-market
"Revisions until the client is satisfied" or an open scope where any new feature counts as a 'revision', turning a fixed bid into unbounded development.
One-line fix
"The fee covers the scope in [the spec] with 1 revision round per milestone. New features or scope changes are handled as billed change requests."
What we see
Scope creep is to web development what unlimited retouching is to photography: the single most common way a fixed-price build turns into unpaid overtime. The defense is a written scope and a clear rule that anything outside it is a change request, not a free revision.
The healthy structure separates two things: revisions (refining what was agreed) and changes (adding or altering what was agreed). A round or two of revisions per milestone is normal; a new page, a new integration, or a redesigned flow is new work, billed as such.
'Unlimited revisions' in a build contract is especially dangerous because software has no natural finish line and every 'small tweak' can cascade. Anchoring the fee to a defined spec, with change requests priced, is how developers keep a fixed bid from becoming an open-ended commitment.
Paste your actual contract into our free scanner and see exactly how its unlimited revisions compares.
Check a contract freeNo signup. Results in under 15 seconds.