Scope Creep Examples — Web design
A new third-party integration, requested after go-live
The site launched as scoped. The client asks for a live chat widget from a specific vendor to be integrated — never discussed before launch.
The site launched with the pages and functionality specified in the proposal — no live chat or third-party widgets were part of that scope. A month after launch, the client signs up for a live chat platform independently and asks the design team to integrate it into the site, including matching its appearance to the brand and positioning it correctly across pages. It's a small technical task in isolation, but it's new work on a project that was already delivered and closed.
Clause typically implicated
Clause typically implicated
Out-of-scope clause→ — Post-launch, any new integration is by definition outside the delivered scope — this clause is the reference point for treating it as new work rather than a leftover task.
Suggested change-order wording
Suggested change-order wording (illustrative, not legal advice)
Happy to add the live chat integration — since the site's already launched and this wasn't part of the original scope, I'll send over a quick estimate for the integration and any styling to match the brand. Should take about [X] hours; let me know if you'd like to move forward.
How this usually resolves
Post-launch integration requests like this are usually easy, low-friction billable work — most clients expect to pay for it once framed as a new addition rather than a forgotten piece of the original project, and it's often a good opportunity to mention the maintenance retainer if one isn't already in place.
Related reading