Is It Out of Scope? — Web development
Is building a component library for future use out of scope for a web development project?
Usually yes. A generalized, reusable code component library is more work than building the components a specific site needs.
Building components tightly coupled to one site is standard build work. Making them generalized — configurable props, documented usage, decoupled from this specific site's needs — is a different, larger engineering effort.
Is it out of scope?
Usually yes. Generalizing components for reuse across future projects takes real additional engineering beyond what a single-site build needs, unless that reusability was quoted upfront.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The quote covers building the components this site needs; a generalized, documented library for future reuse is a new, unquoted deliverable.
Example contract wording
Example contract wording (illustrative, not legal advice)
The build covers the components this site uses. Turning those into a generalized, documented library for future projects is separate engineering work, which I'd scope on its own.
How MarginFlow flags it
MarginFlow flags generalized-component-library requests outside_scope on development contracts, distinguishing them from building the components the current site needs.