Is It Out of Scope? — Web development
Is building a custom plugin or module out of scope for a web development project?
Yes, if it wasn't named in the original deliverables. It's native dev work, but a custom plugin is substantial, unquoted effort.
This lands squarely in dev's wheelhouse, which is exactly why it's easy to wave through — but a custom plugin or module is a substantial build with its own architecture, testing, and maintenance surface, not a quick add to an existing feature.
Is it out of scope?
Yes, if it wasn't listed as a deliverable in the original quote. A one-off custom feature is meaningfully more effort than working within what was already scoped.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The original quote listed specific deliverables; a custom plugin or module not named in that list is new, unscoped work.
Example contract wording
Example contract wording (illustrative, not legal advice)
A custom [plugin/module] wasn't part of the deliverables we quoted — it's real build work with its own architecture and testing. I can scope it out as an addition once we've nailed down what it needs to do.
How MarginFlow flags it
MarginFlow checks custom-build requests against the deliverables list in the contract and flags anything not named there as outside_scope, treating it as new build work rather than a bug fix or minor addition.