Scope Creep Examples — Web development
White-label reseller rights the agreement doesn't cover
The client, an agency reselling development services, asks to remove all code comments and attribution and present the build as their own in-house work.
A digital agency subcontracted this team to build a client project, intending to present it to their own end client as in-house work. When the build ships, they ask for all code comments and commit history referencing the subcontracting agency to be scrubbed, and want written confirmation they can represent it as entirely their own team's work — reasonable for a white-label subcontracting arrangement, but the current SOW never actually granted or defined those rights.
Clause typically implicated
Clause typically implicated
Confidentiality clause→ — The natural place to formalize white-label terms — that the subcontracting relationship itself, and the agency's involvement, stays confidential.
Suggested change-order wording
Suggested change-order wording (illustrative, not legal advice)
Happy to operate as a white-label partner on this — I'd just like to get the terms written down as an amendment so it's formalized rather than assumed. That would cover confidentiality of our involvement, removal of any identifying references in the deliverable, and confirmation you can represent the work as your own to your client. I'll draft language for us to review.
How this usually resolves
Subcontracting agencies that use white-label partners regularly usually have their own standard language for this — worth asking if they do before drafting from scratch, since it may already match what they need and save both sides time.
Related reading