Remote hands vs. in-house hiring (insourcing): when to have your own technician on staff
Your operations director asks whether 40 racks and two power circuits already mean you need a facility technician on staff. That question is almost never answered with racks. It is answered with how many real hours of work your operation generates every month.
Why data center size misleads the decision
Size measures square meters, not workload. A 200-rack room with a new UPS and remote monitoring can ask for ten hours a month. A 20-rack room with cooling at its limit and ten-year-old piping can ask for sixty.
Racks describe the inventory of your room, not the wear on your distribution panels, the condition of your emergency generator or the complexity of the cabling. An assessment that starts with “we just have a lot of racks” ends in a payroll nobody would defend in the budget.
The number that decides: hours, not square meters
Before comparing prices, measure the volume. Review twelve months of tickets: how many were opened, how many were resolved by hand and how many were repeated for lack of a procedure. That total is your real workload, and it is the only input that should rule.
The threshold I use is simple: more than 40 to 50 hours a month of manual work, averaged over six months or more, is no longer a set of loose tasks. It is a part-time position. Past 60 hours, it is a full-time position disguised as support.
If your hours concentrate in two weeks a year, the average will lie to you. Ask for the peaks, not the average, and calculate on the worst quarter.
Count the hours nobody logs too. A technician who replaces parts or restarts equipment without opening a ticket is still consuming hours. If your record is incomplete, the real number is higher than the one you see, and the decision you make with it falls short too.
When a technician on staff DOES make sense
There are three signals that, together, say remote is going to fall short. Each one has a threshold you can audit.
When all three are met, the technician stops being an expense and becomes risk control. In Mexico, a facility technician with benefits costs between $25,000 and $45,000 MXN a month: salary, benefits, training and tools. That is between $300,000 and $540,000 a year.
When it does NOT make sense and remote hands are enough
The opposite signals are just as clear, and they are the ones most often ignored out of pride at “having everything in-house”.
There, remote hands win without discussion. They are charged per closed ticket, between $500 and $3,000 MXN, or per hour with a four-hour minimum. No benefits, no replacements and no staff rotation to plan.
The full account: why TCO is not the payroll
The most expensive mistake is comparing the salary against the ticket and stopping there. The total cost of a technician on staff is not just the salary: it is the replacement time when they leave, the training of whoever comes in, and the learning-curve period during which they perform at 60%.
There is one more cost that almost never gets quantified: the decisions taken without them. An available technician does not only put out fires, they also decide fast. And the hour of lost decision-making does not show up on any payroll, but it is paid for in the SLA.
With remote hands that cost is mitigated by two people who know the procedure, instead of one who knows it out of habit. That is the strongest financial argument for the model, and it has nothing to do with the hourly rate.
And the bottom-line math comes out fast. A technician at $25,000 MXN a month ($300,000 MXN a year) delivers around 1,750 effective hours a year, which works out to roughly $171 MXN per available hour; but if your operation only needs 20 hours a month, every hour actually worked costs you $1,250 MXN.
Against that, a $500 to $3,000 MXN ticket is cheap if a two-hour intervention settles once and for all what in-house takes two visits to solve.
That is the hybrid that almost always wins: a base remote-hands agreement with hours, plus a fixed retainer for the facility technician. You pay for window coverage with the remote SLA and you keep the technical judgment on site for what cannot be delegated.
The practical rule is simple: if your load drops below 20 hours a month for half the months of the year, the fixed position is not justified. If it never drops, it is not justified either. Hybrid contracts bill on hours consumed with a minimum, and that minimum ends up deciding your real budget, not the hourly rate.
How to decide it in an afternoon
Pull the last twelve months of tickets, estimate the hours per intervention type and apply the threshold. Do not follow the intuition that the data center is “big”, nor the one that it is “small”. Follow the load, because the load is what gets paid for.
And ask yourself one question before signing: what happens on the day the only person who knows how to swap a starter does not show up? If that question does not keep you up at night, you probably do not need the full payroll. If it stops you dead, you already have your answer.
Sources
Want to master this?
Noxtel Academy →