Is It Out of Scope? — Web development
Is adding an extra landing page variant for A/B testing out of scope for a web development project?
Usually yes. Building and deploying a second variant — and wiring up traffic-splitting between the two — is real implementation work beyond the single page the build was scoped around.
The functional spec scoped one landing page, built and tested. A request for an A/B test variant means building a second version of that page and, usually, wiring up a way to split traffic between the two and measure results — whether through a dedicated testing tool or custom logic. Neither piece was in the original build.
Is it out of scope?
Usually yes. Building a second page variant is additional implementation work, and the traffic-splitting/measurement piece is arguably its own small feature if there's no existing A/B testing tool already wired into the site. Both fall outside a single-page build.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — Scopes the build to the specific page delivered — a second variant, plus any traffic-splitting logic needed to test it, is additional implementation work.
Example contract wording
Example contract wording (illustrative, not legal advice)
The build covered the one landing page. A test variant means building a second version and setting up a way to split traffic and measure results — real additional work, especially if there's no A/B testing tool already in place. I can scope this as an add-on; let me know if you already use a testing platform we should integrate with.
How MarginFlow flags it
MarginFlow checks the deliverables list for the single page scoped and, separately, for any mention of A/B testing infrastructure — where neither exists, a request for a test variant is flagged outside_scope with an explanation noting both pieces (the variant itself, and the mechanism to test it) so the estimate isn't scoped too narrowly.