Scope Creep Examples — Web development
A new third-party API integration, requested after go-live
The application launched as scoped. The client asks for a new CRM integration to be built post-launch — never discussed or estimated beforehand.
The application launched with the feature set and integrations specified in the SOW — no CRM connection was part of that scope. Weeks after launch, the client's sales team adopts a new CRM platform and asks for lead form submissions to sync automatically into it. It's a legitimate, useful request, but it's new integration work — API authentication, field mapping, error handling for failed syncs — on a project that already shipped and closed.
Clause typically implicated
Clause typically implicated
Out-of-scope clause→ — A new integration requested post-launch falls outside the delivered scope by definition — this is the reference point for scoping and pricing it as new work.
Suggested change-order wording
Suggested change-order wording (illustrative, not legal advice)
We can build the CRM integration — since the app's already live, this is new scope beyond the original SOW. I'll need to review the CRM's API docs to scope it properly (auth, field mapping, error handling for failed syncs), then send over an estimate. Should have that to you within a couple of days.
How this usually resolves
Taking the time to review the third-party API's actual documentation before quoting (rather than estimating blind) matters here — CRM and third-party integrations vary a lot in how well-documented and reliable their APIs are, and that materially affects how much the integration actually costs to build well.
Related reading