For agenciesUpdated 5 min read
How white-label development works for agencies
A white-label developer builds the work your agency sells, and the work ships under your name. Your client sees your team, your process and your invoice, and never sees me.
I work white label for agencies that need senior dev capacity without hiring for it. This page is how I run it, in the order agency principals usually ask.
Who stays invisible, and how?
NDA-backed. Your name on the deliverable, always.
Two rules make the invisibility real. An NDA is signed before any work starts, and your name goes on everything that leaves my hands: the repository, the staging links, the documentation, the build itself. There is no credit line, no watermark, no "built by" in a footer or a commit.
That is the whole reason to buy white label rather than refer the work out. A referral sends your client to someone else. White label keeps the client, the brand and the margin with you, and adds the capacity you were missing.
Who talks to the client?
I never contact your clients. The relationship stays yours.
You do. Not during the project, not after it, not if they ask. If a question needs the client, it goes through you, in your words. If you want me in a call as one of your team, that is your decision and your introduction.
In practice most agencies keep me out of the room entirely and relay. It works because the builds speak for themselves: you are never in the position of describing progress you have not seen.
How is it priced?
Fixed milestones, no hourly surprises.
We scope the project into milestones with a fixed price each, agreed before the first one starts. Hourly billing moves the risk of my estimates onto you; fixed milestones keep that risk with me, where it belongs.
A change in scope is priced as a new milestone, in writing, before the work is done. It is never discovered on an invoice.
How do I see progress?
You see working builds early and often, not a reveal at the end.
Each milestone ends with a deployed build you can click through, and there are usually several along the way. The staging link carries your name, so you can walk your client through it yourself, on your schedule.
Early builds are how problems surface while they are still cheap. A reveal at the end is how they surface when they are not.
What do I get at the end?
The design ships the way it was drawn, and the code stays clean after I leave.
Fidelity to the approved design is the deliverable, not an approximation of it. The code is documented and structured so that your next developer, in-house or not, can pick it up without me. Handover is part of the last milestone, not a favour asked afterwards.
I work in English and French, and so does the documentation.
Who do I contract with?
Contracting and invoicing run through 36N Group LLC (Wyoming). You pay a US company.
The contract, the NDA and the invoices are all with a US company. Your accounting sees a domestic vendor, and your client, if they ever look, sees nothing at all.
What kind of work fits?
Production SaaS, and the browser work most developers turn down: real-time video, WebGL, Canvas engines, and rescues of half-shipped platforms. A full build, one hard feature inside your build, or the project another developer left at eighty percent.
Is there a way to try it without committing?
If a client asks you mid-pitch whether something is feasible, forward me the question: answer the same day, you sign it. Costs you nothing, and it shows you how I work.
A mandate that is overflowing? Write to me, or book 25 minutes.