The key points
- You keep the client relationship, the margin and the credit.
- Source lives in your repository as it is written.
- Weekly demo builds can be forwarded to your client without editing.
- An NDA and non-solicitation protect the relationship.
When does white-label development make sense?
When you have won a project you cannot staff, or you do not want permanent engineering headcount for work that arrives in bursts. Rather than turning the work down or hiring in a hurry, you bring in a white-label development team that works to your process and disappears behind your brand. Agree working hours across time zones at the start.
What terms matter most to an agency?
The ones agencies get burned on. An NDA covers the engagement. A non-solicitation clause means we will not approach your client during or after it. You receive the code in your own repository as it is written, not as an archive at the end, so you are never dependent on us continuing. Client change requests come through you and are requoted if they move the scope.
- NDA and non-solicitation as standard
- Work in your repository and your process
- Named point of contact, not a ticket queue
- Handover documentation in your name
What do we build with?
Next.js, React, TypeScript and Node, delivered as fixed-scope or sprint-based engagements. Specifications are best when they are explicit about who writes them and who is accountable if they are wrong, so we agree that at the start.
How a white-label engagement runs
Scoping
We estimate against your specification, flag anything underspecified and agree scope. About three days.
Design
Where design is part of the engagement, settle it before the build begins. One to two weeks.
Build
Work in sprints with weekly demo builds in your repository. Two to eight weeks.
Handover
Documentation written in your name and a post-launch support window. About three days.
Before engaging a white-label team
- Who writes the specification, and who is accountable if it is wrong?
- How much design is settled before the build starts?
- Who fields client change requests, and how are they priced?
- Who does your client call for support after handover?
- Is the work happening in your repository?
Sources
Rules and guidance this answer relies on. Policies change, so check the current version before acting on it.