Why agencies use a white-label partner
The usual reason is capacity, not capability. A client project needs more senior engineering than the team has free that month, or it needs something the team does not do every week: a headless CMS, an integration, a web app rather than a marketing site. Hiring for one project is slow, and turning the project down hands the client to someone else.
A white-label partner fills that gap without changing the client relationship. You keep the strategy, the design direction and the account; the partner builds. For that to work, the partner has to fit your process rather than ask you to fit theirs.
How a project runs, step by step
This is how a white-label project runs with us. The steps are worth comparing with any partner you speak to:
- Brief: your client’s goals and constraints, from you, in one call. Your client does not need to be on it.
- Written proposal, within a few days: scope, deliverables, timeline and a fixed price wherever the scope allows.
- Build: weekly preview links you can show your client. Small sites take one to two weeks.
- Handover, on the final invoice: the GitHub repository with its full history, the Vercel project moved to your team or your client’s, CMS admin seats, docs and a runbook, and analytics accounts in the client’s name.
- Optional retainer: fixes and upgrades after launch, billed monthly, with a three-month minimum.
Whose name is on it
By default the client sees one name: yours. We work inside your process and under your brand, and stay behind the scenes unless you want us in the room, in which case we join calls as part of your team. Work done under your brand is not listed in our portfolio, and an NDA is available if your client requires one.
Ask any partner the same three things: will they ever contact your client directly, will the work appear in their portfolio, and what happens if your client later asks who built it. The answers should be in writing before the project starts, not assumed.
Who owns the code and the accounts
Ownership is where white-label arrangements most often go wrong, usually late, when a client wants to move hosting or hire their own developer. With us, project-specific code and assets belong to you once invoices are paid, so you can hand them to your client or to your own team. We keep general know-how and reusable patterns, not the client’s project.
Accounts matter as much as code. The repository, the hosting project, the CMS and the analytics should end up in your name or your client’s, not the partner’s. A handover that is a zip file and a password is not a handover.
How it is priced
Each project gets a short written proposal with a fixed price wherever the scope allows. Projects under €5,000 are paid 50% to start and 50% on delivery; larger fixed-scope projects are split across milestones. Invoices are in euros, typically on 14-day terms, and EU business clients with a valid VAT ID are invoiced under the reverse charge.
Fixed price only works with a written scope, which is why the proposal comes before the build. If the client changes the scope halfway, the change is written down and priced before it is built, so you are never the one explaining a surprise invoice.
The stack, and why it matters to you
We build in Next.js and TypeScript by default and deploy on Vercel when it fits. For a quick marketing site we occasionally use Webflow, if it is the better tool, and we say so. Libraries are chosen for accessibility, performance and maintainability, because your team, or the next developer your client hires, may inherit the code.
You can check that on work we have shipped. Modo Deco is a brand concept and Next.js site we built for the BrandableWorks portfolio; on our agencies page it is shown with its name replaced by a placeholder, which is what a white-label site looks like from the outside. Aria Deco and Envision Deco show the editorial end: a journal-led interiors brand and a catalogue of Style × Room idea pages. This site scores 98 to 99 in Lighthouse with a layout shift of 0 on the pages we measure.
White-label Next.js developmentAria Deco case studyEnvision Deco case study
What to ask a partner before you sign
Whoever you choose, get clear answers to these before your client’s name goes on the work:
- Who will the client see, and will you ever contact them without us?
- Will this project appear in your portfolio or case studies?
- Who owns the code and the assets, and from when?
- Whose accounts will the repository, hosting, CMS and analytics be in at the end?
- What exactly is in the handover: docs, a runbook, admin access?
- Is the price fixed, and what happens when the scope changes?
- How often will we see working output, and can we show it to the client?
- Who does the work, and what have they shipped that is still in production?
- What happens after launch: retainer, blocks of time, or nothing?
- Will you sign an NDA if our client asks?
Beyond the build
Agencies also bring a partner in for work around the build. With us that is SEO and AI-search work you resell, video capacity for a client campaign (shoots, edits and social cut-downs credited to your agency), a hands-on team workshop on AI workflows in your own codebase (two to three hours, remote, up to 15 engineers; single session from €1,400, tailored team workshop typically €2,500–3,500), and co-pitch support, where we join a sales call when a client asks about AI or video.