Key takeaways

  • White-label IT is work carried out by a partner’s engineers but delivered under your name, to your process, with reporting that comes back to you.
  • It suits providers whose customers’ kit sits in places their own engineers cannot reach quickly, or whose workload outruns their headcount.
  • It covers physical, on-site work. It does not hand your customer relationship, your service commitments or your design decisions to someone else.
  • Agree the exclusions as carefully as the inclusions.

If you run an MSP, a hosting business or a larger IT services company, your customers do not care who tightens the cable. They care that it was done, that it was done properly, and that they heard about it from you. Much of the physical work behind a managed service happens in a data centre your team may not be near, on a day your team is already fully booked. White-label IT is the arrangement that fills that gap.

A working definition

White-label IT is on-site work delivered by a subcontractor on your behalf, under your name. The partner’s engineer attends, follows your instructions and reports to you. Your customer deals with you before, during and after. The partner is part of how you deliver, not a second supplier your customer has to learn about.

The same idea is sometimes called subcontracted field engineering, channel delivery or partner delivery. The words differ; the shape is the same. You own the relationship and the outcome. The partner supplies skilled hands.

Who uses it

Three kinds of provider reach for it most often:

  1. MSPs with customers across several sites. Your service desk is remote, but a failed drive or a new switch needs a person in the room.
  2. Hosting and colocation-adjacent providers. Kit arrives in bursts, and racking it quickly matters more than keeping a full-time floor team.
  3. Larger IT services providers and integrators. A project needs extra field capacity for a few weeks, or a site needs covering where you have no one.

The common thread is that the work is physical, scoped and repeatable, and that hiring for it permanently would not make sense.

What the work looks like

In a data centre environment, white-label work is mostly the physical layer of infrastructure:

  • Smart hands: component swaps, re-seating cables, physical diagnostics and fault finding on site, carried out to your runbook.
  • Rack and stack and deployment: racking, powering, cabling and labelling new equipment as a planned, documented job.
  • Migrations: moving equipment between cabinets or sites, in the sequence you set.
  • Physical decommissioning: powering down and removing equipment on site.
  • Multi-vendor work: equipment from different manufacturers handled in the same visit, to each vendor’s instructions.

DACPROS offers all of this to other providers through its white-label IT service.

What white-label does not include

White-label field engineering is not warranty-backed break/fix, and it is not hardware maintenance that needs the partner to source parts. Where parts are involved, they come from you or the vendor. Recycling, disposal and certified data destruction are normally handled by specialist partners rather than by the engineer on site. Check what each of these means in practice before you promise your customer anything.

What “under your name” means in practice

It helps to be precise about this, because it is where arrangements go wrong.

  • Your process. The engineer follows your change procedure, your runbook and your checklist, not the partner’s.
  • Your point of contact. Questions from the customer go to you. Questions from the engineer on the day go to the person you name.
  • Your reporting. The visit report comes back in a format you can pass on, ready for you to send as your own.
  • Your voice. You decide what your customer is told about who attended.

What it does not change is the facility’s rules. A data centre will normally need each visitor’s real name, employer and identification for its access process, so the engineer cannot be anonymous at the door. Plan for that with the customer and the facility in advance, rather than discovering it on the morning of the job.

What to ask a partner before you start

Before the first job, put these questions to any white-label partner:

  1. Which tasks do you take on, and which do you decline? Get both lists in writing.
  2. What are your working hours? Ask about out-of-hours work and how it is arranged. Do not assume round-the-clock availability, and do not promise your customer a response time that your partner has not agreed to give you.
  3. Where do you operate from, and how is attendance scheduled? Location, scope and engineer availability all affect when someone can be on site.
  4. How will you report? Ask to see a sample, and agree what evidence comes with each visit. Some facilities restrict photography, so ask how that is handled.
  5. How is confidentiality handled? Agree the terms up front, in the contract, before any customer details are shared.
  6. Who is accountable on the day? One named owner for each job is better than a shared inbox.

DACPROS works from a hub in Hammersmith, London, Monday to Friday, 09:00 to 17:00. Out-of-hours attendance is possible only when arranged in advance, and there is no guaranteed response time. We would rather you hear that now than discover it during an incident.

Is it right for you?

White-label IT works well when the work is defined, the instructions are clear and you want to keep control of the customer relationship. It works badly if you expect a partner to absorb accountability for outcomes they cannot control, or to make design decisions without the context you hold.

The next question is practical: which parts of a job should you hand over, and which should you keep? We cover that in subcontracting field engineering: what to hand off and what to keep. If you want to talk through a specific site, tell us about it or see how our white-label IT service is set up.