Is It Out of Scope? — Web development
Is adding a chatbot widget out of scope for a web development project?
Depends on the depth requested — a drop-in script embed is minor; connecting the chatbot to backend data (order status, account info) is a real integration outside a typical build's scope.
"Add a chatbot" covers a wide range. At the simple end, it's a script tag from a third-party provider — a few minutes of work. At the other end, the client wants the bot to answer questions using their live data (order status, account details, inventory), which means a real backend integration: API access to internal systems, data mapping, and ongoing maintenance as those systems change. The two versions of this request are barely related in effort.
Is it out of scope?
The script-embed version is minor and often reasonable to include informally. A data-connected chatbot is a genuine integration project outside the scope of most builds, and should be scoped and quoted like any other backend integration — the request needs to be clarified before answering either way.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — A backend-connected chatbot is functionally a new integration — outside the deliverables list unless explicitly named.
Example contract wording
Example contract wording (illustrative, not legal advice)
If this is the drop-in [tool] widget, that's a quick add, happy to do it. If you want it pulling from your order/account data to answer questions, that's a real backend integration — different scope entirely. Which version did you have in mind? I can quote accordingly once I know.
How MarginFlow flags it
MarginFlow keeps confidence low on ambiguous "add a chatbot" requests until the thread clarifies which version is meant, rather than confidently classifying either way on a request this bimodal — the explanation flags the ambiguity itself as the useful information for the account manager, prompting a clarifying question back to the client before quoting anything.