How to Structure NDA and IP Agreements with a White-Label Partner

The legal structure of a white-label partnership determines what happens when things go wrong. A good contract protects your clients, your brand, and your business. A bad contract — or no contract — leaves you exposed.

Disclaimer

This article provides general guidance on white-label contract structures. It is not legal advice. Have your attorney review all agreements before signing.

Agreement 1: Mutual NDA

The NDA should be the first document signed — before any project details, client names, or business information is shared.

Scope of Confidential Information

Define broadly:

• Client names, project details, and business requirements
• Your agency's business processes, pricing, and client lists
• Technical information, source code, and architecture details
• Employee and contractor information
• Any information marked as confidential
• The existence of the partnership itself (for white-label purposes)

White-Label Specific Clauses

Non-disclosure of relationship: The partner agrees not to disclose that they work with your agency. They will not mention your agency name, your clients' names, or the nature of the work in any marketing, portfolio, or public communication.

Portfolio restriction: The partner may not use work created under the white-label arrangement in their portfolio or case studies without your written consent. If consent is given, attribution must follow your specifications (e.g., "developed for [your agency name]" — never referencing the end client).

Duration

• Active confidentiality obligations: Duration of the partnership + 3-5 years after termination
• Non-disclosure of client names: Perpetual (client names should never be disclosed)
• Trade secrets: Perpetual protection under applicable law

Agreement 2: IP Assignment

This is the most important agreement for protecting your client relationships and business value.

Core Principle

All intellectual property created during the engagement belongs to you (or your client, as defined in your client agreement). The white-label partner retains NO rights to any code, design, documentation, or other work product.

Key Clauses

Work made for hire: All work is created as work made for hire. If work-for-hire doctrine does not apply (varies by jurisdiction), the partner irrevocably assigns all rights to you.

Immediate transfer: IP transfers at the moment of creation, not upon payment or project completion. This protects you if a payment dispute arises.

Comprehensive scope: The assignment covers:

• Source code and compiled code
• Database schemas and data structures
• Technical documentation and specifications
• Design assets created during development
• Any inventions, methods, or processes developed for the project

No retained rights: The partner does not retain any license, right, or interest in the work product. They cannot reuse code, patterns, or approaches that were developed specifically for your project.

Exception for pre-existing tools: If the partner uses their own pre-existing frameworks, libraries, or tools, these should be explicitly listed. The partner grants you a perpetual, royalty-free license to use these components in the delivered product. This is reasonable — you should not own the partner's general-purpose tools, but you need the right to continue using them.

Pre-existing IP schedule: Maintain a list of partner's pre-existing components used in your projects. This prevents disputes about what was created for you (your IP) vs. what existed before (licensed to you).

What to Watch For

• Clauses that transfer IP "upon payment" — This means the partner owns your code until you pay. Unacceptable. IP should transfer at creation.
• Retained license clauses — Some partners want a license to reuse code they wrote for you. For white-label, this should be restricted to general patterns (not client-specific code).
• Vague assignment language — "All relevant IP" is too vague. Be specific about what is included.

Agreement 3: Non-Solicitation

This protects your client relationships from direct approach by the partner.

What It Should Cover

Client non-solicitation: The partner will not directly or indirectly solicit, contact, or provide services to your clients for 12-24 months after the engagement ends. "Your clients" should be defined specifically (named in a schedule) or functionally (any client whose project the partner worked on).

Employee non-solicitation: The partner will not recruit or hire your employees for 12-24 months. You similarly agree not to directly hire the partner's developers (you can negotiate an exit fee structure if both parties agree to a direct hire).

Incoming contact protocol: If your client contacts the partner independently, the partner must:

1. Inform you immediately
2. Redirect the client to you
3. Not engage in business discussions without your written consent

Making It Enforceable

Non-solicitation clauses must be reasonable to be enforceable:

• Duration: 12-24 months (courts rarely enforce longer periods)
• Scope: Specific to clients the partner actually worked with (not all your clients)
• Geography: Not usually relevant for services, but include if applicable
• Remedy: Specify liquidated damages (e.g., 12 months of fees) to make enforcement practical

Agreement 4: Service Agreement (MSA)

The Master Service Agreement governs the ongoing relationship:

Essential Terms

Service description: What the partner provides (development services, specific technologies, team composition).

Service levels:

• Response time during overlap hours (e.g., 2 hours for urgent, 4 hours for standard)
• Sprint completion targets (e.g., 85%+ commitment delivery)
• Code quality standards (code review, testing, documentation)
• Replacement timeline for underperforming developers (e.g., 2 weeks)

Pricing and payment:

• Monthly retainer amount or hourly rates
• Payment terms (Net 15 or Net 30)
• Rate change notice period (60-90 days)
• Currency and payment method

Communication requirements:

• Daily standups (async or sync)
• Weekly progress reports
• Sprint demos
• Escalation path for issues

Change management:

• How scope changes are handled (change orders)
• How team composition changes are communicated
• How pricing adjustments are proposed and agreed

Agreement 5: Termination and Transition

What happens when the partnership ends (for any reason) is critical. Without clear termination terms, you risk losing access to code, documentation, and knowledge.

Termination Triggers

• Either party with 30-day written notice (no-cause termination)
• Immediately for material breach (after cure period, typically 15 days)
• Immediately for confidentiality breach
• Immediately for insolvency

Transition Obligations

Upon termination, the partner must:

Code and access:

• Ensure all code is committed and pushed to your repository
• Transfer any credentials or access they manage
• Delete their copies of your code and client data
• Confirm deletion in writing

Documentation:

• Deliver all documentation created during the engagement
• Provide architecture notes for in-progress work
• Document any known issues or pending decisions

Knowledge transfer:

• 2-week overlap period (paid) for knowledge transfer to your new team
• Availability for questions during 30-day transition period
• Written summary of current project state, upcoming decisions, and known risks

Data handling:

• All client data returned or certified destroyed
• No copies retained (with written certification)
• Compliance with applicable data protection regulations

What to Watch For

• No transition period — If the partner can walk away without transition support, you lose critical knowledge
• IP contingent on termination — Some contracts restrict IP transfer if YOU terminate. Unacceptable. IP is yours regardless of who terminates.
• Penalty clauses for early termination — Reasonable if you committed to a minimum term. Unreasonable if applied to no-cause termination.

Putting It All Together

Before signing with a white-label partner, ensure you have:

1. Mutual NDA — Signed before first conversation
2. IP assignment — Unconditional, immediate, comprehensive
3. Non-solicitation — 12-24 months, specific to worked-on clients
4. MSA — Service levels, pricing, communication, change management
5. Termination clause — 30-day notice, transition obligations, data handling

These five agreements protect your agency's most valuable assets: your client relationships, your brand reputation, and the software you pay to have built.

At Kwiqwork, we provide all five agreements as standard. NDA before first conversation. IP assignment from moment of creation. Non-solicitation included in every partnership agreement. Because white-label only works when both sides are protected.