White label web services
under your brand

The default arrangement: your agency owns the client relationship completely. You handle sales, pricing, and the client-facing conversations. We do the design and build work in the background. Deliverables (designs, staging sites, documentation, release notes) carry your branding, not ours. The client sees your team. During onboarding we agree the communication model: most resellers want all client contact to route through them, some prefer us to join calls as “their team” under their brand.

Practically, you get a project manager and a working channel (Slack, email, or your project tool). You brief us the way you’d brief an internal team, we deliver in slices you can review and present, feedback comes back through you. The level of involvement scales: some agencies hand us a brief and resell the result, others stay closely involved in design direction and treat us purely as build capacity. Both work. How we work covers the collaboration model in more depth.

Our white-label rate is €60 to €65 per hour across roles, the same rate as our direct work. Projects are scoped either as a fixed-budget proposal once requirements are clear, or as time-and-materials for ongoing or evolving work. There’s no separate “reseller markup” from our side, you pay our standard rate and set your own client-facing price on top.

How you price to your client is your decision and your margin. Common reseller models: a straight markup on our hours (typically 1.5x to 2.5x depending on your market and the value you add in account management and strategy), a fixed project price where you carry the scope risk and keep the difference, or a retainer where you bill the client monthly and we deliver against an agreed capacity. The right model depends on your client relationship and how much strategic value you add beyond the build. Pricing and rates page covers our rate structure.

Not from us. The white-label arrangement means we don’t contact your client directly unless you ask us to, we don’t put Studio Ubique branding on deliverables, staging environments, or documentation, and we don’t appear in the code comments, commit history, or anywhere else the client might look. Staging sites run on your domains or neutral URLs, not ours. Release notes and documentation carry your agency name.

The honest part: white-label is about who delivers, not about deception. Many agencies are openly transparent with clients that they use specialist production partners, it’s a normal and respected model. Whether you tell your client is entirely your call. What we guarantee is that the choice stays yours, we won’t make it for you by leaving our fingerprints on the work. If you ever want us to join a client call as part of your team, under your brand, that’s available too. More on how we work.

White-label project work is scoped and delivered as a project: you bring a brief, we deliver a defined outcome (a website, a store, a web app) under your brand, against an agreed budget and timeline. You manage the client, we manage the build. It fits when you have a project to deliver and need it done without expanding your permanent team.

IT staff augmentation is different: instead of a scoped project, you add one or more of our developers to your team for a defined period, a few months, a specific project phase, a capacity gap. They work inside your processes, your stand-ups, your tooling, as if they were your staff, but without the contracts, benefits, hardware budget, or long-term commitment of a hire. It fits when you have your own technical leadership and process, and you just need more hands for a while. Many agencies use both: project work for overflow, staff augmentation for sustained capacity gaps. IT staff augmentation covers that model in detail.

Your agency owns the code, the repository, the documentation, the credentials, and the deployed infrastructure. IP transfers on payment as part of our standard terms. For white-label work this matters twice over: you own it relative to us, and you can then pass full ownership to your end client or keep it, depending on your client agreement. No proprietary frameworks that lock you in, the work is done on standard tools (WordPress, WooCommerce, Laravel, Node.js, React, Vue.js) that any competent developer can maintain.

If you stop working with us, you leave with everything: a documented codebase, a deployment runbook, architectural decision records for the non-obvious choices, and a knowledge-transfer session for whoever picks the work up next, your in-house team or another partner. Because the work was built under your brand with your client none the wiser, there’s no awkward transition visible to the client. The handover is structured so your agency stays in full control of the relationship throughout. How we work covers handover in more detail.

Studio Ubique runs a Netherlands team and a development team in India, which is a practical advantage for white-label work: the timezone spread means build progress continues across more hours of the day, and urgent issues raised late in your working day are often picked up before your next morning. You get a primary contact in your timezone for coordination, with the development team reachable through the shared working channel.

For day-to-day communication, we work in your project tool or a shared channel, with an agreed cadence for updates and reviews. For urgent issues after launch, the response model depends on the support package: automated monitoring runs continuously, and human response runs during business hours with after-hours escalation available through the Growth and Partnership tiers. We’re honest about this rather than claiming round-the-clock human support that no agency of our size genuinely staffs. Website support packages cover the response tiers.

We adapt to yours, within reason. For white-label work the goal is that the output fits cleanly into what your agency already does, so we work with your preferred stack where it’s one we know well (WordPress, WooCommerce, Laravel, Node.js, React, Vue.js, standard databases), follow your coding conventions and naming standards, and deliver into your repository structure and deployment setup. If your process uses specific tools (a particular project management system, a specific CI setup), we work within them.

The honest limit: if your stack is something genuinely outside our experience, we’ll tell you rather than learning on your client’s budget. And for greenfield white-label projects where you don’t have a strong stack preference, we’ll recommend based on what the project needs and what your team can maintain afterwards. The aim is that the work is indistinguishable from your own team’s output, which means matching your standards, not imposing ours. Custom development work covers the stack range.