How are revisions and scope changes handled?
In-scope polish is separated from new work; boundaries are discussed up front without absolute guarantees.
Revision usually means improvement inside the agreed scope; a scope change means new pages, roles, integrations, or features that were not included. If that line is blurry, every request feels “included” and budgets break.
We typically define revision and change boundaries in the proposal or contract: feedback rounds, what kinds of edits are included, what becomes a separate estimate. Numbers and rules vary by project type—we do not promise one free-revision count for every engagement on this page.
When scope grows, the healthy move is to pause and assess impact on time, cost, and priority. “Unlimited revisions forever” sounds friendly and usually damages quality.
The aim is transparency: what is included is clear early; if it changes, we update the plan together.
