White-label development pricing: fixed price, day rate or retainer?

When an agency brings in a white-label developer, the pricing model matters as much as the rate. Get it right and you can quote your client with confidence and keep a healthy margin. Get it wrong and you absorb every overrun yourself.

There are three common models. Each suits a different kind of project.

Fixed price

You agree a scope and a price up front. The developer carries the risk of the work taking longer than expected.

Best for: projects with settled designs and clear requirements, such as building a marketing site from finished Figma files.

Pros:

• You know your cost before you quote your client
• Easy to add a predictable margin
• The developer is motivated to be efficient

Cons:

• Changes mean change requests, which can slow things down
• Developers price in risk, so vague scopes get expensive quotes
• Someone has to own the scope document, and it needs to be precise

Protecting your margin: make sure the scope lists assumptions explicitly (number of templates, integrations, browsers, content entry) and agree how changes will be priced before you start.

Day rate

You pay for time, usually by the day or in blocks of days.

Best for: evolving projects, discovery work, joining your team mid-build, or when your client is still working out what they want.

Pros:

• Flexible: priorities can change without renegotiating
• No padding for risk, so you pay for the work actually done
• Works well alongside your own developers

Cons:

• The final cost isn’t fixed, which is harder to sell to some clients
• You need visibility of progress to manage the budget

Protecting your margin: agree an estimate range and a cap for each phase, ask for weekly updates on days used, and bill your client on a similar basis where you can.

Monthly retainer

A reserved block of time each month, for a fixed monthly fee.

Best for: ongoing support, maintenance and improvements for sites you’ve already launched, or agencies with a steady flow of smaller jobs.

Pros:

• Guaranteed capacity when you need it
• Predictable cost that fits neatly into your own client retainers
• The developer builds deep knowledge of your clients’ sites

Cons:

• Unused time is usually lost, so size it carefully
• Less suited to large one-off builds

Protecting your margin: start with a smaller retainer than you think you need and increase it, rather than paying for capacity you don’t use.

Mixing models

Many agency partnerships use more than one. A common pattern is a day-rate discovery phase to pin down the scope, a fixed-price build, then a retainer for support after launch. Each phase uses the model that best fits its level of uncertainty.

What to ask a white-label partner about pricing

1. Which models do you offer, and which would you recommend for this project?
2. What assumptions sit behind this estimate?
3. How do you handle and price changes?
4. How will I see progress against budget?
5. What happens if the work takes longer than estimated?

A partner who answers these clearly is one you can price your own work around. For the wider picture, see what to look for in a white-label development partner.

We offer all three models to agencies and will recommend whichever protects your margin best. Here’s how we work with agencies.