How agencies should evaluate white-label development pricing, protect margin and choose between fixed-scope, hourly, retainer and dedicated-capacity models.
White-label development pricing is easy to misunderstand because agencies often compare the supplier rate with the price they plan to quote the client and call the difference “margin.”
That is only the starting point.
Your real margin has to absorb account management, scoping, design coordination, QA, revisions, sales cost, risk and the time your team spends translating between the client and the delivery partner.
A healthier pricing question is:
What fulfilment model gives us enough room to deliver the client promise reliably and still leave worthwhile gross profit after agency effort?
The four common pricing models
1. Fixed-scope project pricing
The partner quotes a defined project for a fixed amount.
This works well when requirements are reasonably clear: a marketing website, Shopify redesign, migration or a contained feature set.
Advantages:
- easier for the agency to mark up and quote;
- clear commercial boundary;
- less exposure to small implementation inefficiencies;
- useful for a first project with a new partner.
Risks:
- vague scope creates change-order disputes;
- agencies sometimes promise unlimited revisions while the supplier priced a finite scope;
- hidden client dependencies can delay delivery without changing the quoted price.
The protection is not a longer contract. It is a better scope.
2. Hourly or time-and-materials
You pay for actual delivery time.
This is useful when scope is intentionally fluid — ongoing development, debugging, technical discovery or a product that will evolve through feedback.
Advantages: flexible and transparent when the work cannot be predicted accurately.
Risks: your agency carries more estimation risk and needs strong visibility into time usage.
If your client is on a fixed price while your fulfilment partner is hourly, you need a contingency buffer and a clear approval process for scope growth.
3. Monthly retainer or capacity bucket
The agency buys an agreed amount of recurring capacity.
This fits agencies with a steady stream of client requests but not enough predictability to hire every skill internally.
A good retainer should define:
- what skills are included;
- approximate capacity or service level;
- how priorities are queued;
- what happens to unused capacity;
- response expectations;
- what counts as out-of-scope specialist work.
4. Dedicated team or pod
The agency effectively reserves a recurring group of specialists.
This can suit larger agencies with consistent volume across multiple clients or a long-running product engagement.
The economics can become attractive at high utilisation, but it only works if the agency has enough work to keep the pod productively occupied.
Calculate gross margin after agency effort
A simple starting formula is:
Project gross profit = client revenue − fulfilment cost − direct project-management cost − project-specific tools/expenses − expected rework allowance
Then:
Gross margin % = project gross profit ÷ client revenue × 100
Do not treat your account manager’s time as free simply because they are salaried. If the white-label model requires six hours a week of coordination that another partner would not require, that difference affects the economics.
Price uncertainty, not just build hours
Two projects with the same estimated development hours can deserve different agency markups.
Risk rises when:
- the client has not approved designs;
- third-party APIs are undocumented;
- the site must migrate without losing existing SEO traffic;
- the client has many stakeholders;
- requirements change frequently;
- the deadline is tied to an event or campaign;
- data migration is incomplete;
- the agency is responsible for post-launch support.
Your price needs room for the uncertainty you are accepting.
Keep your client price separate from your partner cost
One of the benefits of a white-label development partner is that your agency controls the commercial relationship.
That does not mean the markup should be arbitrary.
Your client is paying for more than coding. Depending on the engagement, your agency may own:
- discovery;
- strategy;
- UX/design;
- account management;
- quality control;
- project risk;
- client communication;
- launch planning;
- post-launch support.
The client price should reflect the complete value and responsibility your agency is providing.
Do not win the project by removing the safety margin
Underpricing creates a predictable chain reaction:
- the agency removes contingency to make the proposal attractive;
- the client makes normal requests that were never scoped;
- the agency avoids charging for changes because the relationship feels delicate;
- the supplier quite reasonably treats them as additional work;
- the agency’s margin disappears;
- everyone starts rushing.
It is better to make scope boundaries visible in the proposal than to hide them and hope the project behaves perfectly.
A simple quotation structure
For a fixed-scope white-label build, an agency proposal can separate:
Discovery / technical planning
What has to be clarified before implementation.
Design
Whether the agency, client or delivery partner owns it.
Development
Templates, functionality, integrations and CMS/ecommerce scope.
QA & launch
Devices, browsers, analytics, migration checks and deployment.
Post-launch support
Duration, response expectations and what counts as a new feature.
This makes it easier to compare the client promise with the partner scope before signing.
How to compare two white-label quotes
Do not compare only the totals. Compare what each quote actually includes.
Ask:
- Is project management included?
- Is QA included?
- Are responsive states included?
- Are integrations fully included or only setup?
- Are migrations and redirects included?
- Who owns deployment?
- How many review rounds are assumed?
- Is post-launch support included?
- Is documentation included?
- Are meetings included?
- What is the change-request rate or process?
The cheaper quote can easily become the more expensive project if core delivery responsibilities are missing.
The best model for a first partnership
For most agencies testing a new partner, a contained fixed-scope pilot is easier to evaluate than immediately reserving monthly capacity.
You learn how the team scopes, communicates, builds, tests and responds to ambiguity. If the working relationship is strong and volume becomes predictable, a retainer or dedicated-capacity model can then reduce repeated setup overhead.
For Shopify-specific client work, see our white-label Shopify development model. For custom products and applications, see white-label software development.
Get a free growth audit
Just drop your email — we’ll do the rest. No forms, no phone call required.
Turn the insight into an operating decision.