Broadcast teleprompter systems
CRM and licence management for a teleprompter manufacturer, plus a custom API so hardware can activate and validate licences in the field.
Delivered through an agency partnerExplore the case studyService
White-label web development, under your brand
You have sold the work. We build it. Everything we produce ships under your name, to your process, on the dates you have already promised your client.
01Definition
What white-label means here
“White-label” gets used loosely. Here is the operating definition, so there is nothing to interpret.
We are contracted by your agency. Our agreement is with you. We have no agreement, no invoice and no relationship with your client.
Everything we build ships under your brand. No Felix Web Solutions logo in a footer, no credit link, no attribution in the theme header, no badge in the admin. We follow your repository conventions, your branch names and your documentation format, so the work reads as though it came from your team — because as far as your client is concerned, it did.
You keep the client relationship, the scope conversation and the presentation. We keep the build.
- Contracted by
- Your agency. Never your client.
- Ships under
- Your brand. No credit link, no footer mark, no admin badge.
- Briefed by
- You, in whatever format you already use.
- Presented by
- You. We do not join a client call unless you put us in it.
02Scope
What we build
The range below is what we take on as an agency’s build team. If your project sits between two of these, it is still a project we can scope.
WordPress and custom themes
Custom themes built from your designs, block editor work, ACF-driven templates, plugin development where an off-the-shelf plugin does not fit, and multisite. We build to your designs rather than adapting a purchased theme, and we hand over a codebase your team can pick up.
Shopify and WooCommerce
Shopify and WooCommerce store builds, with payment, shipping and business-system integrations scoped around your client’s requirements. We can help choose the platform or work with the one already agreed.
Next.js, React, Vue and Nuxt
Next.js, React, Vue and Nuxt front ends, Tailwind design-system implementation, headless builds against WordPress or a commerce backend, and static prerendered marketing sites. If your designer works in Figma and your client wants a WordPress editor behind a decoupled front end, that is a normal engagement for us.
Migrations and replatforming
Content and CMS migrations, moving a site between hosts or platforms, and rebuilding a legacy site without losing its URLs. Redirect mapping, canonical handling and metadata parity are part of the build, not an afterthought your client’s SEO consultant raises three weeks later.
Rescue, performance and security work
Core Web Vitals work, hack recovery and clean-up, and inherited codebases that need to be made maintainable before anything new can be added. This is often how an agency first works with us: something is broken, the deadline has not moved, and the person who built it is gone.
03The services
The white-label services in detail
Three of the areas above have a page of their own. Start here if you already know which one the work is.
01WordPress developmentCustom themes built from your designs, block editor and ACF work, plugin development, multisite, and migrations onto or off WordPress. Handed over documented, so your team can take it over.Where it fitsYou have won a WordPress project and the build capacity is somewhere else. Read the detail 02WooCommerce developmentStore builds, payments and shipping logic, subscriptions, complex catalogues, and ERP or stock integrations. Including the WooCommerce project that turned out to be larger than the quote.Where it fitsYour client sells things, and the store turned out to be bigger than the quote. Read the detail 03Website support and maintenanceUpdates, monitoring, backups, fixes, rescue and performance work — run under your brand and resold as your care plan. Operating to a published SLA.Where it fitsYou sold a care plan and would rather not run the rota yourself. Read the detail
04Invisibility
How the invisibility actually works
Three things make the difference between a white-label partner and a subcontractor your client eventually finds out about.
Nothing we build carries our name.No credit link, no footer logo, no comment block in the source with our URL in it. If you want a humans.txt, it says what you tell it to say.
Communication goes through you.You brief us, we report to you, and progress reaches your client in your words on your schedule. If you want us on a client call — a technical scoping session, an escalation, a handover walkthrough — we join as your team, introduced however you choose to introduce us.
We do not approach your client.We do not contact them, pitch them, or take work from them, and the only time we speak to them is when you have put us in the room.
05Engagement
How an engagement starts
- 01
You send the brief. Whatever you already have. A Figma file, a client scope document, a Slack thread, a bug list. You do not need to rewrite it for us.
- 02
We scope it. You get a written breakdown: what we will build, what we have assumed, what we need from you, and what is explicitly not included. If something in the brief will not work, you hear it here, before you have committed to a date with your client.
- 03
We build. Work lands in your repository or ours, your call. You get a fixed check-in rhythm and one named point of contact, so nobody on your side has to chase for status.
- 04
We hand over. Documented, deployed and demonstrated to your team, so you can present it as your own.
06Handover
What you get at handover
Handover is a deliverable, not an email. Every project ends with:
- The full repository, with readable commit history and a README that tells your team how to run it.
- Deployment and build instructions, and the environment variables the site needs.
- A short written guide for whoever edits the content — written for your client, in neutral language you can rebrand.
- A walkthrough call with your team, so the person who takes it over has spoken to the person who built it.
- A list of anything we deliberately left out of scope, so it does not surface as a surprise later.
After that the code is yours. You are not locked into us to change it, and if you would rather we kept running it, support and maintenance is a separate, optional agreement.
07Proof
Work we have shipped for agencies
Swiss life-sciences company
A complete website build for a Swiss life-sciences company, connecting product orders and business systems alongside events, blogs and a resource library.
Delivered through an agency partnerExplore the case study
UK restaurant chain website
Full build and ongoing maintenance for a multi-location quick-service brand, connecting store geolocation with live opening-hours information across the estate.
Delivered through an agency partnerExplore the case study
Skincare product finder
An interactive product finder for a UK skincare brand, letting customers follow a questionnaire or upload a selfie to receive a personalised skin report and product recommendations.
Lead development within an agency teamExplore the case study08Why a partner
Why agencies bring in a build partner
Instead of hiring in
Permanent hiring creates a fixed cost, even between projects. We are capacity when the work is there and nothing when it is not. No recruitment, no notice period, no bench.
Instead of an offshore marketplace
We do not compete on price and we will not pretend otherwise. What you get instead is that you brief once and do not project-manage the build. The work comes back done, in your timezone, in your working hours, having already had the questions asked that a marketplace developer would have silently guessed at.
Instead of a freelancer
A good freelancer is excellent until they take a full-time role or go quiet in week six. You are buying continuity: a team, a defined response commitment and a published SLA, rather than one person’s calendar.
Instead of another white-label shop
The question every agency owner is actually asking is whether we will end up talking to your client. Our answer is written down, on this page, in the terms we operate under — not implied.
We also build and run our own software products. That is not a side business; it is the reason our handovers look the way they do. Code we have to maintain ourselves for years teaches you quickly what a codebase is like to inherit.
09FAQ
Questions agencies ask before they brief us
Can you sign an NDA?
Absolutely. Send yours over and we’ll arrange it.
Will our client know you exist?
Not from anything we produce. Nothing we build carries our name, and we do not contact your client. Whether you tell them you use a build partner is entirely your decision — some agencies do, most do not, and it changes nothing about how we work.
Do we have to change how we run projects?
No. We work to your process, your tools and your terminology. If your team lives in Jira, we are in Jira. If your client’s approvals happen in a weekly call you run, we build around it.
Who owns the code?
You do, on handover. The full repository, with no licence conditions of ours attached to it.
What happens if something breaks after handover?
If you hold a support agreement with us, it is covered under our SLA. If you do not, you can still send it to us — it goes into the queue as new work rather than as an incident. Agencies that resell care plans to their clients usually take the support agreement so the escalation path exists before it is needed.
How do you handle scope changes mid-project?
The same way you would want your own developers to. Anything outside the written scope comes back to you as a short note with the cost and the schedule impact before we build it, so you can decide whether to absorb it, bill your client, or drop it.
Can you work directly with our client if we want you to?
Yes, when you put us in the room. Some agencies want us on technical scoping calls or handover sessions because it is faster than relaying. That happens at your invitation, under your introduction, and it stops when you say it stops.
How quickly can you start?
It depends on what is already in the schedule, which is why the first call is short and specific. If we cannot hit the date you have promised, you will hear that on the call rather than in week three.
Next step
Book a partner call
Thirty minutes, about a real project. Bring the brief, the deadline and the part you are unsure about.
Not an agency? See what we build direct
Two ways in
Email it insteadStep 1 of 2
Step 1 of 2. What brings you here?