Is It Out of Scope? — Web development
Is adding a second environment (staging/QA) out of scope for a web development project?
Usually yes, unless the original quote already specified a staging environment as a deliverable.
Most small-site builds ship to a single production environment by default, priced that way. A staging/QA environment — its own hosting, its own deploy pipeline, its own data — is a real added setup, even though it sounds like "just a copy."
Is it out of scope?
Yes, if it wasn't in the original quote. A second environment means separate hosting, config, and a process for promoting changes between the two — a concrete deliverable the single-environment build didn't include.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The quote specified a single production environment; a separate staging/QA setup with its own hosting and deploy flow is a new, unquoted deliverable.
Example contract wording
Example contract wording (illustrative, not legal advice)
The build was quoted against a single environment — adding a staging/QA copy means separate hosting and a deploy pipeline between them, which I'd scope as an add-on.
How MarginFlow flags it
MarginFlow flags staging-environment requests outside_scope on development contracts unless the original SOW explicitly listed a multi-environment setup.