A marketing agency wins a client who wants a website. The agency does SEO and paid media, not design and development. It has three options: turn the work down, hire a developer for one project, or find a partner who builds it quietly under the agency's name. That third option is white label. It is common, it is unglamorous, and when it goes wrong it goes wrong in predictable ways. Here is how the model actually works, what the margins look like, and where the traps are.
White label web design is when one agency builds websites that another agency sells under its own brand. The production partner stays invisible to the end client. Common models are per project, dedicated resource and monthly retainer. The reselling agency typically marks work up 40 to 100 percent and owns the client relationship, scope and quality control.
What white label web design actually means
A white label arrangement has three parties. The end client, who thinks they are buying from one agency. The reselling agency, who signs the contract, owns the relationship and handles the money. And the production partner, who does the design and development work but never appears on an invoice, a proposal or a call unless invited.
The distinction people confuse is white label versus subcontracting versus referral. Subcontracting is the same delivery structure but the client usually knows a third party is involved. A referral means you hand the client to someone else and take a commission, giving up the relationship entirely. White label means the client's experience is entirely with you, and the partner works behind your brand.
Nothing about this is deceptive when it is done properly. Almost every large agency uses specialist production partners somewhere in its stack. What matters is that the reselling agency takes genuine responsibility for the work rather than just passing files along.
Why agencies use a production partner
The usual reason is capacity gaps. An SEO or paid media agency gets asked for a site build roughly once a month. That is not enough volume to justify a salaried designer and developer, but it is too much revenue to keep declining. A partner turns a fixed cost into a variable one.
The second reason is skill gaps. A shop that lives in WordPress gets a Shopify request. A branding studio gets asked for a headless build. Hiring for a one off need takes months and rarely pays back.
The third is overflow. Three projects land in the same fortnight, the in-house team is booked, and the choice is to delay the client or push a build outward. Delays cost more relationships than partners do.
The reason that usually fails is trying to build a whole business on reselling with no delivery competence at all. If nobody at the reselling agency can review a build critically, the partner's worst week becomes your reputation.
The three common engagement models
Per project. You scope a site, get a fixed quote, pay a deposit, receive the build. Best for irregular work and for testing a new partner. Costs more per hour in exchange for zero commitment. Watch the change request pricing, since fixed quotes tend to be tight and revisions are where the partner recovers margin.
Dedicated resource. You buy a designer or developer for a set number of hours per month, usually full time or half time. They learn your standards, your stack and your clients. Better economics than per project once you have three or more builds a month, and continuity you cannot get from ticket based work. The risk is paying for idle capacity in a slow month.
Monthly retainer or block of hours. A pooled bucket of hours across design, development and maintenance. Good for agencies with a base of client sites needing ongoing edits rather than large builds. Ask whether unused hours roll over, because most agreements quietly let them expire.
How does the margin actually work?
The commercial logic is simple: you buy production at a wholesale rate and sell at a retail rate, and the gap pays for sales, project management, quality review and the risk you carry on the contract. Here are illustrative market ranges for a US reselling agency in 2026. Treat them as a planning model, not a quote.
| Project type | Typical partner cost | Typical client price | Gross margin | Your workload |
|---|---|---|---|---|
| 5 page brochure site | $800 to $2,000 | $2,500 to $6,000 | 55% to 70% | Scoping, copy review, 2 client calls |
| 15 to 25 page custom site | $3,000 to $7,000 | $8,000 to $18,000 | 50% to 65% | Discovery, content plan, weekly reviews |
| Shopify store build | $2,500 to $8,000 | $7,000 to $20,000 | 50% to 65% | Product data, app decisions, launch QA |
| Landing page, single | $300 to $900 | $1,000 to $2,500 | 50% to 65% | Brief plus one review round |
| Monthly maintenance | $200 to $600 per site | $500 to $1,500 per site | 55% to 65% | Ticket triage, monthly report |
| Dedicated developer, full time | $3,000 to $7,000 per month | Billed into multiple projects | Depends on utilization | Daily direction, sprint planning |
Gross margin is not profit. Subtract your own project management time, which on a mid sized build runs eight to twenty hours, plus sales cost and the cost of any rework you absorb. A 60 percent gross margin on paper often nets closer to 30 to 40 percent once your team's hours are counted honestly. Agencies that forget this end up busy and broke.
Price your first two white label projects as if you will spend twenty percent more of your own time than you expect, because you will. Once you have run three builds with the same partner and know their rhythm, tighten the number. Discounting early to win the deal is how agencies end up subsidizing their own clients.
Where white label projects go wrong
The failures are operational, not technical. Four patterns cover most of them.
The telephone game. Client tells account manager, account manager writes a summary, partner's project manager interprets it, developer builds something adjacent to the original request. Every hop loses detail. The fix is written specs the partner reads directly, annotated screenshots instead of prose, and a single named person on each side who owns the thread.
No quality gate. Work goes from partner to client without anyone at the reselling agency actually reviewing it. Then the client finds the broken mobile menu. Whoever sold the project has to own the last look, on a real device, before anything is shared.
Timeline arithmetic. The partner quotes four weeks. You promise the client four weeks. You have left no room for your own review cycles, client content delays or a revision round. Add 25 to 40 percent to any partner timeline before it reaches the client.
Brand leakage. The partner's name appears in a staging URL, a commit message, a footer credit, a PDF file property or an email signature. Usually harmless, occasionally awkward. Handle it in the agreement and check before every client facing share.
The contract terms that matter
An NDA is the floor, not the ceiling. The agreement between you and a production partner should be explicit about several things.
- Non solicitation in both directions, covering the partner approaching your clients and you approaching their staff, with a defined term.
- Ownership of deliverables. Design files, code and assets transfer to you on payment so you can pass full ownership to the client.
- Confidentiality that survives the engagement, covering client names, project details and anything you share about your own pricing.
- Anonymity terms: no portfolio use of the work without your written permission, and no client facing branding anywhere in the deliverables.
- Revision policy. How many rounds are included, what counts as a revision versus a new request, and the rate for extra work.
- Response and turnaround commitments, especially for post launch bugs. Define what counts as urgent and how fast it gets a fix.
- Escalation and exit. What happens if quality slips, who you contact, and how you retrieve everything if you part ways mid project.
How do you vet a white label partner?
Most of this is standard vendor diligence, done more carefully because your client's opinion of you rides on it.
Start with a paid pilot. One small project, one landing page or a five page site, at full price. Free tests attract partners who cut corners and tell you nothing about how they behave under a real deadline.
Ask to see work in the specific platform you sell. A partner who is excellent in WordPress may be mediocre in Shopify, and portfolio pages rarely make the distinction clear.
Meet the actual project manager, not just the sales contact. That person's clarity is the single best predictor of how the engagement will feel week to week.
Establish the timezone reality. A partner working ten hours ahead can be an advantage, since work lands overnight, but only with a defined daily overlap window and clear async documentation. Without both, you lose a day per question.
Confirm capacity honestly. Ask how many active projects each developer carries and what happens if two of your builds start in the same week.
Check the maintenance story. Sites break after launch. If the partner treats post launch fixes as a separate paid engagement, your margin on retainers evaporates.
Run two partners rather than one. Give the second a smaller share of volume so they stay warm. Single partner dependency is the most common reason an agency has to tell a client bad news, and the second relationship costs nothing to maintain beyond an occasional project.
When you should not white label
Skip it when the work is core to what you sell. If clients hire you because of your design thinking, outsourcing design hollows out the reason they chose you. Skip it when the project needs constant iteration with a client stakeholder in the room, since every loop through a partner adds a day. Skip it when the margin is already thin, because a discounted project plus a partner fee plus your management hours is a project you will resent by week three.
Also skip it if nobody on your team can judge the output. Reselling work you cannot evaluate is a bet on someone else's worst week.
The model works best when it is deliberate: a defined set of project types, one or two trusted partners, a scoping process you control, and a quality gate you never skip. Agencies that treat it that way expand what they can sell without expanding payroll. Agencies that treat it as a way to avoid learning delivery tend to find out the hard way.
If you are weighing this against building capacity in house, the honest comparison is not partner cost versus salary. It is partner cost versus salary plus recruiting, benefits, management time, and the months where the pipeline is thin and the developer is idle. For most agencies doing fewer than four builds a month, a partner wins on arithmetic alone. Past that, in house starts to make sense, and many agencies end up running both, keeping website builds in house and pushing Shopify work or overflow outward.
Frequently asked questions
What is white label web design?
It is an arrangement where one company builds websites that another agency sells under its own name. The end client only ever deals with the reselling agency, which owns the contract, the pricing and the relationship. The production partner does the design and development work but does not appear on proposals, invoices or calls.
How much margin do agencies make reselling web design?
Gross margin typically runs 50 to 70 percent, so a build bought at $2,000 often sells for $5,000 to $6,000. That figure is misleading on its own. Once you subtract your project management hours, sales cost and any rework you absorb, a 60 percent gross margin frequently nets closer to 30 to 40 percent.
Is white label web design ethical to sell as your own?
Yes, provided the reselling agency genuinely owns the outcome: scoping the project, reviewing the build, standing behind fixes and honoring the contract. Clients are buying accountability. It becomes questionable when an agency forwards deliverables untouched, cannot explain how the site was built, and disappears when something breaks after launch.
What should a white label agreement include?
Mutual non solicitation, ownership of design files and code transferring to you on payment, confidentiality that outlasts the engagement, no portfolio use of the work without written permission, a defined revision policy with rates for extra rounds, response times for post launch bugs, and an exit clause for retrieving assets mid project.
How do you keep a white label partner invisible to the client?
Host staging on your own domain, keep every client email and call in your accounts, and check deliverables before sharing. Leaks almost always come from small places: PDF file properties, footer credits, commit messages and stray email signatures. Put the anonymity requirement in writing, then verify it as part of your pre share review.
When should an agency hire in house instead of using a partner?
Once you are consistently shipping four or more builds a month, or when design and development are the actual reason clients hire you. Below that, a partner is usually cheaper, because the real comparison is not partner fees versus a salary but partner fees versus salary plus recruiting, benefits, management time and idle months.
The takeaway
White label works when it is a deliberate operating decision rather than a way to avoid saying no. Define the project types you will resell, keep two partners so one bad month does not become a client conversation, price with your own management hours counted, and never let a build reach a client without someone on your side reviewing it on a real device first.