You keep the relationship. We take the build.
White-label is not a billing arrangement here — it is how the engagement is structured. Below is exactly what happens, including the parts most partners want in writing before they start.
Five steps, and none of them involve us meeting your client.
We work with a limited number of agencies at a time.
- 01
You scope it with your client
You run the conversation, set the price and sign the contract. We are not on the call. If you want a second opinion on feasibility before you quote, ask — that part is free and it is usually where we are most useful.
- 02
We agree the brief together
You hand over the requirement in whatever shape it arrives: a Figma file, a call recording, three paragraphs. We come back with what we understood, what we would build, and where we think the estimate is soft.
- 03
It enters your workstream
Work happens in your Slack, your ClickUp, your Jira. You see commits as they land rather than a status report on Friday. Nothing is a black box you have to defend to a client without information.
- 04
You review before your client does
Every delivery reaches you first. You decide what goes on to your client and in what words. If something needs changing, it goes back into the same workstream rather than becoming a change request.
- 05
You ship it as your own
Source, documentation and handover notes land with you, written in your conventions. Copyright transfers on delivery. Your client sees one agency, and it is yours.
What the first four days look like.
A retainer that spends its first fortnight on discovery is a retainer you are paying to get organised. This is the shape we aim for instead.
- Day 1
- Kickoff call, access to your tools, NDA signed
- Day 2
- We restate the brief and flag the soft edges
- Day 3
- Architecture sketch and delivery sequence agreed
- Day 4
- First commits in your repository
The mechanics, not the reassurance.
Every partner asks some version of “what stops you from taking my client?” It deserves a structural answer.
- We never contact your client
- We are not introduced to them, never join a call under our own name, and never reach out. Where the work itself exposes us to their data, an NDA covers it and we touch nothing the build does not require.
- Your accounts are not a prospect list
- We will never approach your client, accept work from them behind you, or let them find out we exist. Your accounts are closed to us for as long as you are a partner, and afterwards.
- The work is yours on delivery
- Automatic copyright transfer, an NDA in every engagement, and editable source files handed over with each build.
- Delivered under your name
- Commits, documentation and handover notes carry your conventions, not ours. Everything reaches your client as work from your team.
Three things that decide how well this goes.
A named decision maker
One person on your side who can answer a question the same day. Projects stall on unanswered questions far more often than on hard problems.
Access, not permission chains
Repository, staging environment, and the third-party accounts the build touches. We work under your NDA, so treat us like the in-house team you did not hire.
The real constraint
Fixed launch date, a budget you already quoted, a stack decision you cannot revisit. Tell us early. We would rather design around a constraint than discover it in review.
Bring us the brief you were about to turn down.
Thirty minutes, no deck. Tell us what your client needs and we will tell you plainly whether we are the right team to build it behind your name.