Scope Creep Examples — Web development
A rebuild requested after the client's own mid-project pivot
The client changes their core business model mid-build, invalidating a chunk of already-built functionality, and expects it reworked at no extra cost.
The application was built around a subscription pricing model the client specified at the start, with billing logic, plan tiers, and account flows all built against it. Midway through the build, the client decides to switch to a usage-based pricing model instead — a legitimate business decision, made for reasons unrelated to the development work, that nonetheless invalidates a meaningful chunk of the billing and account logic already built.
Clause typically implicated
Clause typically implicated
Change order clause→ — A client-side business model change mid-build is squarely what triggers a formal change order — the rework needed depends heavily on how much existing logic can be adapted versus rebuilt.
Suggested change-order wording
Suggested change-order wording (illustrative, not legal advice)
The billing and account logic built so far assumes the subscription model from our original spec. Moving to usage-based pricing means reworking that logic — some of the account structure should carry over, but billing calculation and plan management will need significant changes. I'll need a few days to assess exactly how much carries over before sending an estimate for the rework.
How this usually resolves
Taking the time to actually assess what's reusable before quoting (rather than guessing) protects both sides — it avoids underquoting a rebuild that turns out bigger than expected, and gives the client a number they can trust is based on real analysis rather than a defensive estimate.
Related reading