Is It Out of Scope? — Web development
Is setting up A/B testing infrastructure out of scope for a web development project?
Usually yes, unless it was quoted. A testing platform, traffic-split logic, and results tracking is a distinct technical build.
A/B testing sounds like a small addition — "just show half the visitors a different version" — but doing it properly means a testing platform integration, traffic-split logic that doesn't hurt performance, and results tracking wired to real conversion events.
Is it out of scope?
Yes, unless it was quoted. Integrating a testing platform and building reliable traffic-split logic is its own technical deliverable, not implied by a standard site build.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The quote covers the site as built; A/B testing platform integration and traffic-split logic is a new, unquoted deliverable.
Example contract wording
Example contract wording (illustrative, not legal advice)
The build didn't include A/B testing infrastructure — that's a platform integration and traffic-split logic on top of the site, which I'd scope and quote separately.
How MarginFlow flags it
MarginFlow flags A/B testing infrastructure requests outside_scope on development contracts unless the SOW explicitly listed it as a deliverable.