Is It Out of Scope? — Web design
Is building a component library for future use out of scope for a web design project?
Usually yes. A reusable component library is a distinct system-design deliverable beyond the specific pages quoted.
The project is quoted against a specific page list, but a client with plans to expand the site later sometimes asks for a proper design system — documented, reusable components — rather than just the pages they're paying for now.
Is it out of scope?
Usually yes. A component library means designing components as generalized, documented, reusable pieces — real additional thinking beyond styling the specific pages in the quoted list.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The quote covers the specific page designs listed; a documented, reusable component library for future use is a separate, unquoted deliverable.
Example contract wording
Example contract wording (illustrative, not legal advice)
The scope covers the page designs listed — turning that into a documented, reusable component library for future pages is a bigger system-design effort, which I'd quote as its own project.
How MarginFlow flags it
MarginFlow flags component-library requests outside_scope on design contracts, distinguishing a documented reusable system from page-specific design work.