White label MSA, NDA, and IP: what agencies must get in writing

Your client hired your agency, not a network of subcontractors. When a launch slips, a staging URL leaks, or ownership of a plugin is disputed, the conversation lands in your inbox. Paper is how you decide in advance who can speak, who owns the files, and who pays to fix a defect after go-live. Agencies delay it because the pipeline is hot. That is exactly when it matters: a pilot still exposes names, brand files, and credentials.

If you cannot point to a signed assignment of IP and a written change process, you do not have a white label model. You have a freelancer with extra steps.

Agencies often ask a partner to “send a contract.” That request is too vague. You want three instruments that do different jobs. Mixing them into one messy PDF is how SOW scope fights become MSA fights, and how IP language gets leftover in a statement of work that expires.

Keep the MSA stable. Put the variable commercial terms in the SOW. If you change IP assignment per project, you will forget which client’s work is actually yours. If you put unlimited liability in every SOW, you will stall every kickoff while someone “checks with legal.”

A capabilities call does not need an NDA. A conversation that includes a client’s industry, pipeline, or a confidential Figma file does. The operational rule is simple: if you would be embarrassed to see the information in the partner’s public case studies, do not send it until a mutual NDA is signed.

What the NDA must actually cover

One-way NDAs that only protect the partner are a tell. You are the party introducing client relationships. If they will not protect those names, they are not a white label partner. They are a vendor shopping for logos.

If how white label development works is the operating manual, the MSA is the permission structure. Process without paper still leaks: a helpful developer joins the client Slack “just this once,” and now your partner has a relationship you do not control.

Clauses agencies should insist on seeing

Non-solicit language should be specific. A ban on ever hiring anyone who touched a ticket is often unenforceable and always hostile. A term about not soliciting named end clients for overlapping delivery, for a reasonable tail, is a business point counsel can draft. If a partner will only sign their paper, read it as if you were the client: refuse unlimited liability, a claim on your internal tools, or a right to publicize the work.

This is the clause agencies skip and then panic about at handoff. Your client contract almost certainly says they own custom work they paid for, or that you assign it on payment. If your partner never assigned it to you, you may be selling rights you do not have. Operational target: upon full payment for a SOW, custom deliverables are assigned to your agency (or onward to the client—counsel picks the chain). The partner keeps pre-existing tools. Third-party software stays under its own licenses. That split is normal. Keeping custom client code after you pay is not.

The U.S. Copyright Office circular on works made for hire is a public primer on a US-specific phrase—not advice, and not a worldwide magic spell. Have counsel write the assignment that matches where the work is actually performed.

IP on paper is worthless if the partner’s personal GitHub owns the repo and the hosting invoice is in a freelancer’s Gmail. White label operations need a credential policy that matches the MSA.

1. 01

   Agency-owned accounts by default

   Hosting, domain, CMS, app stores, analytics, and error tracking live in accounts your agency (or the client, via you) controls. The partner gets least-privilege access.

2. 02

   Repositories under your org

   Create the repo in your GitHub/GitLab org. Invite the partner. Do not accept “we’ll transfer it at the end.” Transfers fail when people quit.

3. 03

   A written handoff at close

   SOW close includes: access removed, passwords rotated where they were shared, env vars documented, and a list of third-party apps still connected.

4. 04

   No shared personal logins

   If someone is using a personal Figma or a personal OpenAI key on a client project, you do not control continuity. That is an ops defect, not a personality quirk.

Put the credential standard in the MSA or an operations exhibit. Then enforce it in the first sprint, not at launch week. The process we run with agencies assumes staging and production access are visible to the account team from the start—because invisible access is how agencies get held hostage.

You vetted a company. They may still use specialists. That is not automatically bad. Undisclosed subcontracting is. Your client may have asked you not to use unnamed third parties. Your insurance and confidentiality promises may assume you know who touched the files.

Get in writing: whether the partner may subcontract, whether you must approve named subs, and that every sub is bound to confidentiality and IP terms at least as tight as the partner’s. If your client’s MSA forbids subcontracting, your partner MSA must match—or you cannot put that client on that partner.

Legal paper cannot invent a brief you never wrote. It can stop a fight about whether a late CRM field is “a small tweak.” The MSA should point to a change-order process. The SOW should define revision rounds, what a round is, and how extra work is priced. That commercial detail belongs next to how to run revision rounds without killing margin—and it belongs in writing, not in a kickoff anecdote.

Liability caps belong in the MSA, sized to the relationship. Counsel sets the numbers; you insist numbers exist. Delay is usually a stack of dependencies: content, APIs, approvals. The SOW should say what happens when the client (through you) is late. If the partner’s date is fixed and assets are not, you will pay for idle time or a crash at the end.

Launch is not a disappearing act. If you sell the client a 30-day bug window, buy a 30-day bug window. Mismatch here is how agencies donate senior time. The MSA should allow SOWs for both build and care so you are not inventing terms on a Friday night.

Partnership paper is a negotiation. Walking away is allowed. So is not asking for fantasy terms that no competent studio will sign.

If a candidate pushes back on NDA, IP assignment, or white-label communication, stop. That is not a “legal personality.” It is a business model that needs your clients as their marketing. Compare that signal with the red flags in how to vet a white label partner. Diligence without paper is a vibe. Paper without diligence is a well-documented accident.

The goal is not to spend six weeks in redlines while the client waits. The goal is to never put client files in a channel that is not covered. Run paper in parallel with scoping.

1. 01

   Mutual NDA before the real brief

   Capabilities call can happen first. Named client, files, and credentials cannot.

2. 02

   MSA redlines while the SOW is estimated

   Do not wait for a perfect SOW to start MSA review. The relationship terms rarely depend on page count.

3. 03

   SOW with rounds and acceptance

   Price, dates, deliverables, change process. Attach the brief. No production until both sides sign.

4. 04

   Pilot, then retainer addendum

   Move to monthly capacity with a retainer SOW. Do not rewrite the MSA unless the relationship actually changed. Store executed files where account managers can see the revision cap.

When you are ready to see how Tretanz handles agency paper and delivery together, book a partnership discovery call. Bring your template or your open questions. The useful conversation is whether the operating model and the documents describe the same company.

Contracts do not make a weak partner strong. They make a strong partner safe to scale. Stay in the vetting checklist until they can deliver. Use white label pricing models to decide how to buy capacity. Use when white label is the wrong model if the model itself is the issue. Paper is the last mile of a commercial decision—not the first slide of a sales deck.