Short answer: A white-label agency agreement should settle eight things before work starts: scope, branding, client contact, confidentiality, account access, ownership, review rounds, and payment plus exit terms. Put them in writing, usually as one master agreement and a short statement of work for each project. This is a checklist for discussion, not legal advice.
Imagine this. Your partner's designer is halfway through a landing page for your client. The client, who has found the designer's email in a shared file, writes to ask whether the page can launch a week early. The designer, trying to be helpful, says yes.
Nobody did anything malicious. But you've just lost control of the timeline, the client now knows you have someone else building their page, and you found out from a forwarded email.
One sentence in a written agreement would have prevented all of it. That's what this checklist is for.
A white-label agency agreement is the written set of terms between an agency and its delivery partner. It covers what work gets delivered, under whose brand, who speaks to the client, how information is protected, who owns what, and how the arrangement ends. Many agencies use two documents: a master agreement that stays in place, and a statement of work for each project.
A note on what this is. This is a practical checklist to help you decide what to raise, written by a marketing company, not a law firm. Contract law and data-protection rules vary by country and sometimes by state. Have a qualified lawyer review the final wording.
Why do handshake white-label deals fail?
Because the first few projects go well, and good projects don't test an agreement. Problems show up at the edges: a client contacts the wrong person, a file needs to be reused, a payment is late, someone leaves. Those are the moments a verbal understanding turns into two different memories of what was said.
What should a white-label agency agreement cover?
1. Scope and deliverables
List what you are buying in terms you can check. "SEO" is not a deliverable. "One technical audit, one keyword map and four optimised pages per month" is. Say what is excluded, and add the sentence that anything not listed is a change request.
2. Branding on deliverables and reports
State whose brand appears on files, reports and dashboards, and in what format. Add one clause people forget: portfolio rights. Can the partner mention the work in its own case studies? In most white-label arrangements the answer is no, and it's better to write that down.
3. Client communication and escalation
Decide who speaks to the client. The usual default is nobody except you, unless you ask. Add what the partner does if the client contacts them anyway (politely redirect to you, don't answer on substance) and how urgent problems reach you, with expected response times.
4. Confidentiality
An NDA should cover both your information and your clients'. Check that it matches what you promised in your own client contracts, because a promise you made to a client doesn't automatically bind the people you hire. Say who is bound (staff and any subcontractors), how long the duty lasts, and what happens to data when the work ends.
5. Access and account permissions
The client should own the ad accounts, analytics, website and social profiles. The partner should be invited as a user with the lowest level of access that lets them work. No shared passwords. Name the people who have access, and agree that it will be removed at the end.
6. Ownership of files and work product
Say who owns the finished deliverables, the source files and the accounts, and when ownership passes (often when payment is complete). Partners usually keep ownership of their own tools and templates. Also cover third-party items such as fonts, stock images and plugins: who buys the licence, and who holds it.
7. Review rounds and approvals
Agree how many revision rounds are included, what counts as a round, how fast each side responds, and who signs off. Without this, "just one more tweak" becomes unpaid work for someone.
8. Payment, change requests and exit
Set the payment schedule, how changes in scope are quoted (priced and approved before work begins), the minimum term if any, and the notice period. Then write the exit: a handover list, removal of access, and what happens to work in progress. Some agreements also include a clause about the partner not approaching your clients directly. Whether and how that is enforceable depends on where you are, so ask a lawyer.
Two quick tests for any draft
The two-sentence test
Can you explain, in two sentences, who talks to the client and who owns the finished work? If you can't, there's a gap.
The Tuesday test
If your main contact at the partner were unavailable on Tuesday, could someone else pick up the work from what's documented? If not, you depend on one person's memory.
What does a simple statement of work look like?
You don't need a long document for each project. One page is often enough.
One-page statement of work outline
Section | What goes in it |
Project and objective | One or two sentences on what the work is for |
Deliverables | Numbered list, with quantities |
Out of scope | What isn't included |
Timeline | Start date, milestones, delivery dates |
Review rounds | How many, and the response time on each side |
Contacts | Named people and roles on both sides |
Access needed | Which accounts, at which permission level |
Fees and payment | Amounts, dates, how changes are priced |
Handover | What you receive at the end |
What mistakes show up most often?
- Writing the agreement after the first project has started.
- Describing scope in adjectives ("comprehensive", "ongoing") instead of items.
- Forgetting that client contracts may require the same confidentiality terms from anyone who touches the work.
- Giving admin access "just for now" and never taking it back.
- Having no exit plan because nobody wants to talk about the end at the start.
If you take one habit from this list, write the exit first. It's the least pleasant section and the one you'll be glad of.
How do you bring this up with a prospective partner?
A script you can use
Do it early and plainly. Something like: "Before we start, I'd like us to agree scope, review rounds, who contacts the client, and what happens if we stop. Can you send what you usually use, or shall I draft a one-page statement of work?"
A good partner will be relieved. A partner who treats it as an insult has told you how they handle disagreement. If you're still choosing someone, our guide on how to choose a white-label partner covers what else to ask.
How Highbav handles it
On our side, this is built into how we work. Our
agency partnership process has us agree scope, pricing, review rounds, communication and confidentiality and client-contact expectations before access is shared.
The short version
Agree it in writing, keep client control with your agency, and plan the exit as carefully as the start. If you want to see how we'd set out scope, review stages and handover before any access is shared,
share a brief or
contact us.
Frequently Asked Questions
What should a white-label agreement include?
At minimum: scope and deliverables, branding rules, who communicates with the client, confidentiality, account access, ownership of the work, review rounds, and payment, change and exit terms. Have a lawyer check the wording for your location.
Can a white-label partner contact my client directly?
Only if you agree to it. Most agencies write that the partner does not contact the client unless the agency asks, and that any client contact is passed back to the agency.
Who owns the deliverables in a white-label arrangement?
That is set by the agreement. A common approach is that ownership of finished work passes to the agency when payment is complete, while the partner keeps its own pre-existing tools and templates. Write the rule down rather than assuming.
What happens to client work when the partnership ends?
It depends on what you wrote. Good agreements list what gets handed over (files, documentation, account details), require access to be removed, and say how work in progress is paid for and transferred.
Do we need both an NDA and a service agreement?
Often yes, or an agreement that contains confidentiality terms. A standalone NDA covers information; the service agreement covers the working arrangement. Ask a lawyer which structure suits you.