Anyone who gives you a single percentage for this is guessing. Margin on white label web development varies by market, by project type, by how well you scope, and mostly by what your clients will pay — which has more to do with your positioning than with your costs.
What can be described usefully is the structure: where the margin comes from, what erodes it, and which decisions move it. The worked figures below are illustrative round numbers, not our rates and not drawn from any real engagement.
The basic shape
White label margin is the gap between what you price the project at and what the build costs you, with no recruitment, onboarding, bench time or payroll in between. That last part is what makes it different from margin on in-house delivery, where the cost accrues whether or not the work sells.
An illustrative example. You sell a website build for $12,000. Delivered by a partner it costs you $7,000; built in-house at an effective $97 per productive hour it takes 70 hours and costs about $6,800. On paper the two are close.
| Via a partner | Built in-house | |
|---|---|---|
| Price to your client | $12,000 | $12,000 |
| Cost of delivery | $7,000 | ~$6,800 (70 hrs at $97) |
| Gross margin | $5,000 (~42%) | ~$5,200 (~43%) |
| Cost in a month with no sales | $0 | Unchanged — salary continues |
| Cost before the first project sells | $0 | Recruitment plus onboarding |
The difference is what happens in the month when nothing sells. The partner cost disappears. The salary does not.
What actually erodes it
Almost never the partner's price. In practice margin leaks in four places, all of them on the agency's side of the arrangement.
- Scope you absorbed rather than raised as a change order, usually to avoid an awkward conversation
- Your own unbilled time: scoping, briefing, reviewing, and relaying feedback between client and partner
- Rework caused by a brief that was incomplete when it was handed over
- Discounting at the point of sale to win work you were probably going to win anyway
The second one is the most consistently underestimated. Managing a white label project is real work — often five to ten hours across a mid-sized build, spent on briefing, review and client communication. If your pricing assumes that time is free, your actual margin is several points below the number on your spreadsheet.
The decisions that move it most
Three things move margin far more than negotiating your partner down.
First, brief quality. A complete brief — final content, signed-off designs, named integrations, agreed acceptance criteria — is the single cheapest thing you can do to protect margin. Rework caused by an incomplete brief is paid for by you, whichever way the contract is worded.
Second, pricing on value rather than cost-plus. If you quote by marking up the build cost, you have anchored your price to your supplier and capped your upside. A website that will generate meaningful revenue for a client is worth what it is worth, and that number rarely relates to how many hours it took.
Third, knowing the cost before you quote. If you get a fixed figure from your partner before you price the project, your margin is decided at the point of sale rather than discovered at the end. Agencies working the other way round are effectively hoping.
Where agencies leave the most money
Not on the build. On everything after it.
A website project is a one-off with a defined end. Maintenance, hosting management, ongoing changes and iterative improvement are recurring, and recurring revenue is worth considerably more to an agency than the same amount earned once. It is also the part most agencies decline to sell, because a retainer implies someone is available when a client's site breaks on a Friday — and that someone usually has to be a permanent hire.
Delivering that through a partner removes the constraint: you sell the retainer, set the price and keep the relationship, while the cost scales with the number of retainers you actually hold rather than with headcount. Because our own maintenance plans are published with their prices and included hours, you can work out that margin exactly rather than estimating it.
The second commonly missed piece is the work adjacent to the build — integrations, automation, performance work, analytics implementation. Clients who have just approved a website budget are unusually receptive to it, and it is frequently higher-margin than the site itself because it is scoped narrowly and valued by outcome.
A sanity check on your own numbers
Take your last three technical projects and work out, honestly:
- What you invoiced, and what the delivery actually cost you
- How many of your own hours went into scoping, briefing, review and client communication, at your own charge-out rate
- How much scope you absorbed without raising a change order
- What recurring revenue, if any, followed the project
The gap between the margin you thought you made and the margin that survives that exercise is usually instructive, and it is nearly always about the middle two lines rather than the first.
If you want the cost side of that calculation to be a known quantity before you quote, that is how our white label service is structured — a fixed figure for the build before you commit a price to your client, so the margin is a decision rather than an outcome.
