White Label Agreement: What Agencies Should Put in Writing

Bojan SandićLead UI/UX at Inkyy 8 min read
Woman at a studio desk reviewing a printed contract with pen in hand, with pills reading NDA signed, Your brand, White Label Agreement and IP transferred

A white label agreement is the contract that lets your agency sell a partner’s design and development work under your own brand, without the partner ever stepping into your client relationship. Most templates online are written for SaaS resellers or private label products, so they skip the things that actually go wrong between an agency and a build team.

This guide covers the 14 clauses an agency should put in writing before the first project, what each one protects, and the red flags to watch for. It is a practical checklist, not legal advice. Have a lawyer in your country review the final version.

What a white label agreement does for an agency

In a white label setup, your client hires you. You hire the partner. The client never sees the partner’s name. The agreement makes that arrangement stick. It answers four questions before money changes hands:

  • Who owns the work, and when does ownership move to you and your client?
  • What can the partner say, show or do with your clients and their projects?
  • What exactly is being delivered, by when, and to what standard?
  • What happens when a project goes wrong or the relationship ends?

If you are still choosing who to work with, start with our guide on how to choose a white label partner. This article assumes you have a candidate and now need the paperwork.

MSA, SOW and NDA: the three documents you need

Most agencies do not need one giant contract. A simpler structure is one master agreement that covers the relationship, plus a short document for each project. Here is how the pieces fit together.

DocumentWhat it coversHow often you sign it
Master services agreement (MSA)White label rules, IP, non-solicitation, payment terms, liability, terminationOnce, at the start of the relationship
Statement of work (SOW)Scope, deliverables, timeline, price, revision rounds, acceptance criteria for one projectOnce per project
Non-disclosure agreement (NDA)Confidential information, client names, briefs, credentialsBefore you share any client details, often folded into the MSA later

Sign the NDA first, even for a quote. You will share client names, briefs and sometimes access details while scoping. That information needs protection before the MSA is ready.

The 14 clauses to put in writing

1. Scope and statement of work

The MSA should say that every project runs on a signed SOW, and that the SOW wins if the two conflict on project details. Each SOW lists pages, templates, features, integrations and what is out of scope. A clear page list removes most scope arguments. Our website sitemap template is a good starting point.

2. White label and confidentiality

This is the core clause. The partner works under your brand only. Spell out what that means in practice: no partner credits in footers, no partner names in code comments, file metadata or theme author fields, no partner email addresses in client tools, and no direct mention of the partner in any client-facing document. Confidential information should include client identities, briefs, pricing and credentials.

3. Client non-solicitation

The partner agrees not to contact, pitch or accept work from your clients directly during the relationship and for a set period after it ends. Add a rule for the reverse case: if a client contacts the partner, the partner refers them back to you. How long and how wide this can be depends on local law, so this is one clause your lawyer should check.

4. Portfolio and showcase rights

Generic templates miss this one. Many studios show past work on their site, on Dribbble or Behance, and in sales decks. Your agreement should say the partner cannot show any work made for you, or mention your clients, without your written permission. If you are happy for them to show anonymised work later, write down exactly what is allowed.

5. IP ownership and assignment on payment

Do not assume you own the work because you paid for it. Under US law, for example, work from an outside contractor only counts as a “work made for hire” if it fits one of nine specific categories and there is a written agreement, as the US Copyright Office explains in Circular 30. Websites and logos do not always fit those categories. That is why agency contracts usually add a written assignment: all rights in the deliverables move to you (or straight to your client) once the invoice is paid. Rules differ by country, so check yours.

6. Third-party assets and licences

Fonts, stock photos, icon sets, plugins and code libraries are licensed, not owned. The partner should list every paid or licensed asset in the handover, say whose name the licence is in, and avoid anything that cannot be transferred to the client. For WordPress builds, see the licence notes in our white label WordPress development guide.

7. Source files and handover

Define what “delivered” means. A good handover pack includes design source files (Figma or similar), exported assets, the full code repository or site export, a list of plugins and licences, and short notes on how the site is built. If it is not in the contract, you may only receive the live site.

8. Revisions and change requests

State how many revision rounds are included per stage, what counts as a revision versus new scope, and how change requests are quoted and approved. Match these numbers to what you promise your own client, or you will end up paying for the gap.

9. Timelines, communication and response times

Set the working channel (Slack, email, your project tool), the working hours and time zone overlap, and a response time for normal messages and for urgent issues such as a site going down. Agree on who on each side has authority to approve work.

10. Quality standards and acceptance

Write down the standard you expect: supported browsers and devices, accessibility level, performance targets and code standards. Then define acceptance. For example, you have a set number of working days to test and report issues, and the partner fixes reported bugs at no extra cost. Our website launch checklist works well as an acceptance list.

11. Pricing, invoicing and payment

Cover the pricing model (fixed price per project, hourly, or a monthly retainer), deposit and milestone payments, invoice currency, payment terms, and what happens if a client pays you late. Many agencies pay the partner on their own schedule, not when the client pays, so make that explicit. Also state any refund or satisfaction terms the partner offers.

12. Data protection and access credentials

The partner will touch hosting, CMS logins, analytics and sometimes customer data. The agreement should require a password manager or shared vault instead of email, named accounts instead of shared logins, and removal of access when a project ends. If your clients are in the EU or UK and the partner processes personal data, GDPR requires a written data processing agreement, so add one.

13. Liability and warranties

The partner should warrant that the work is original, does not infringe anyone’s rights, and will be fixed if it does not match the agreed spec within a set bug-fix window. Liability is usually capped, often tied to fees paid. Make sure the cap and any indemnity line up with what you promise your own client.

14. Term, termination and exit

Say how either side can end the agreement and with how much notice. Then describe the exit in steps: finish or hand over work in progress, deliver all files, transfer licences, remove access, and confirm in writing that confidentiality and non-solicitation still apply. A clean exit plan is what protects your clients if the partnership does not work out.

Clause checklist with red flags

ClauseWhat it protectsRed flag
White label and confidentialityYour brand and client listPartner wants a footer credit or “built by” link
Non-solicitationYour client relationshipsPartner refuses any restriction on contacting your clients
Portfolio rightsClient privacy“We may display work for marketing purposes” by default
IP assignmentYour client’s ownershipPartner keeps ownership and only grants a licence
Source filesYour ability to maintain the workSource files cost extra or are “not included”
AcceptanceQualityNo testing window, bugs billed as new work
ExitContinuity for clientsNo handover duty if the agreement ends

How to put the agreement in place in 6 steps

  1. Sign a mutual NDA before you share any client details.
  2. Ask the partner for their standard terms. Compare them against the 14 clauses above.
  3. Mark up the gaps. Non-solicitation, portfolio rights and IP assignment are the usual ones.
  4. Have a lawyer review the final MSA once. After that, each project only needs an SOW.
  5. Run a small paid pilot project under the new terms to test handover, response times and acceptance.
  6. Review the agreement after the first few projects and fix anything that caused friction.

The agreement is only one part of a working partnership. For the wider picture of what you can resell and how to package it, read white label services: what agencies can resell, and for the outsourcing models behind it, see our guide to outsourcing web development.

From the studio: ask your partner to send the handover pack for the pilot project before final payment, then try to edit the site yourself using only that pack. If you cannot find a file, a licence or a login, add that item to the SOW template for every future project. It takes an hour and it closes the gaps that contracts written in advance always miss.

Frequently asked questions

What is a white label agreement?

It is a contract that lets one business sell another business’s product or service under its own brand. For agencies, it sets the rules for reselling a partner’s design or development work without the partner being visible to clients.

Is white labeling legal?

Yes. Selling work made by a partner under your brand is a common and legal business model. The agreement simply makes sure ownership, confidentiality and responsibilities are clear.

Who owns the work in a white label partnership?

Whoever the contract says. Without a written assignment, the creator may keep the copyright, so agency agreements usually transfer all rights to the agency or its client once the work is paid for.

Is an NDA enough on its own?

No. An NDA protects information, but it does not cover IP ownership, non-solicitation, scope, payment or exit. Use it at the start, then sign a full agreement before the first project.

Can I use a free white label agreement template?

A template is a fine starting point, but most are written for software or product resellers. Add the agency clauses from this guide and have a lawyer review it.


Need a white label team for your agency?

Inkyy is a white label design and development team for agencies, working in-house from Bosnia and Herzegovina since 2015. We work under your brand, sign an NDA, and never show client work without your permission. See how our white label service works, or book a call to talk through your next project.

Written by

Bojan Sandić

Lead UI/UX at Inkyy

Bojan leads UI/UX at Inkyy and works with agencies on websites, product design and brand identity.

Meet the team