Operations
In-house engineers vs a smart hands provider
· 8 min read
Employing engineers directly gives you people who know your estate intimately and are available without coordination, which is hard to beat on a single site during business hours. A smart hands provider gives you coverage in many cities and outside business hours without carrying headcount in each one. Most organisations end up with both: in-house for the site where the team already sits, a provider everywhere else and overnight.
This is usually framed as a cost question, and cost is the least interesting part of it. The useful questions are how many sites you have, how often something needs hands on it, and what happens at three in the morning.
What in-house engineers are genuinely better at
An employed engineer who works in your estate every day accumulates knowledge no briefing transfers. They know which cabinet has the awkward rail kit, which switch was replaced last spring, and which cable nobody labelled in 2019. That context turns a two-hour investigation into a five-minute fix, and it is the strongest argument for having people of your own.
- Deep familiarity with your specific estate, its history and its quirks
- No coordination overhead: you ask, and someone walks downstairs
- Available for work too small or too vague to raise as a ticket
- Present for the incidental things nobody would ever dispatch an engineer for
- Institutional memory that survives between projects
If your infrastructure sits in one facility and someone is on that campus daily, employing them directly is very likely the right answer. A provider adds coordination overhead you do not need.
Where that model runs out
The difficulty is that data centre work is spiky. An estate might need nobody for three weeks and then need two people for a weekend. Employment is a fixed cost against a demand pattern that is anything but fixed, and the mismatch gets worse as you add sites.
- One engineer cannot cover a second city, let alone a second country
- Out-of-hours cover means a rota, and a rota means several people
- Holiday, sickness and turnover all need a second person to be viable
- Specialist work such as fibre splicing may come up too rarely to justify the skill in-house
- Idle capacity is paid for whether or not it is used
What a provider actually buys you
A smart hands provider converts a fixed cost into a variable one and gives you reach you would otherwise have to hire for. The trade is that the engineer arriving does not know your estate, which is why documentation and build standards matter far more when you work this way.
| Feature | In-house | Provider |
|---|---|---|
| Knowledge of your estate | Deep and accumulated | Only what you document |
| Coverage across cities | One site per person | Wherever the provider operates |
| Out-of-hours | Needs a rota, so several people | Included in the model |
| Cost shape | Fixed, paid whether used or not | Variable, paid per engagement |
| Specialist skills | Whatever you hired for | Drawn from a wider pool |
| Response for small tasks | Immediate during hours | Raised as a request |
| Scaling to a new city | Recruit before you can serve it | Usually already covered |
How most organisations actually resolve it
The common pattern is not a choice at all. Teams keep in-house people at the site where the team already sits, and use a provider for the other cities and for out-of-hours everywhere. That keeps the deep knowledge where it pays off most, without hiring a second engineer in a country to cover work that arrives a few times a quarter.
- Count your sites. One site with staff on the campus points to in-house.
- Count your out-of-hours incidents. A real rota needs several people to be sustainable.
- Ask which specialist skills you need rarely. Those are the ones to buy rather than hire.
- Look at what happens when your engineer is on holiday. If the answer is 'we hope nothing breaks', you have a single point of failure regardless of cost.
Whichever way you go, the thing that makes either model work is documentation. In-house teams can survive without it for a while because the knowledge sits in someone's head. That is also why losing that person hurts so much.