Is It Out of Scope? — Web development
Is adding real-time chat support integration out of scope for a web development project?
Yes, if it wasn't in the original deliverables. It's native dev work, but a live chat integration is a new feature with its own setup and testing.
Chat integration is real dev work — API keys, routing rules, notification hooks, testing across devices — not a quick embed-and-done task, even for well-documented third-party platforms.
Is it out of scope?
Yes, if it wasn't named in the original deliverables. Even a well-supported platform needs configuration, testing, and integration work specific to the site.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The original quote listed specific deliverables; a chat integration not named there is a new feature.
Example contract wording
Example contract wording (illustrative, not legal advice)
Live chat wasn't part of the original deliverables — even with a well-documented platform, it needs real setup and testing on our end. I can scope it as an addition.
How MarginFlow flags it
MarginFlow flags chat-integration requests outside_scope when not named in the contract's deliverables list, treating them as a new feature rather than a configuration change.