Is It Out of Scope? — Web development
Is building an internal tool for the client's team out of scope for a web development project?
Usually yes. An internal tool is a separate application build, quoted (or not) on its own terms.
This tends to land as "since you're already in the codebase" — a spreadsheet the ops team maintains by hand, framed as something that should be quick to turn into a small internal app.
Is it out of scope?
Yes. "Already in the codebase" doesn't make it the same deliverable — an internal tool has its own data model, forms, and access rules distinct from the site that was quoted.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The quote covers the site's specified functionality; a separate internal tool with its own data and forms is a new, unquoted deliverable.
Example contract wording
Example contract wording (illustrative, not legal advice)
An internal tool is a separate build from the site — its own data model and forms — so it'd need its own quote. Happy to scope it as an add-on once the current build wraps.
How MarginFlow flags it
MarginFlow flags internal-tool build requests outside_scope on development contracts, treating them as a distinct deliverable rather than a natural extension of the current build.