Key takeaways
- 60% of CTOs plan to buy new storage; 55% are planning a hardware refresh — but staffing is almost never included in these business cases.
- Expanding your storage estate multiplies ongoing operational demands — more systems require proportionally more engineering oversight.
- Data centres already operate with lean teams. Adding infrastructure without adding capability creates a dangerous understaffing scenario.
- Three solutions: full outsourcing, a hybrid model, or a short-term assessment period. All are cheaper than the cost of the first major incident.
As Big Data initiatives gain mission-critical importance, organisations face mounting pressure to expand storage infrastructure. Cloud solutions offer supplementary capacity, but latency constraints mean that many real-time operations must maintain local data repositories. Beyond Big Data, standard business growth puts continuous strain on storage systems — file sizes grow, databases expand, email archives accumulate, compliance requirements extend retention periods. The infrastructure answer is relatively straightforward: buy more storage. The operational answer is where most strategies fall short.
The numbers driving the decision
Industry data puts 60% of CTOs in the market for new storage solutions in the near term, with 55% intending to manage capacity demands through a hardware refresh rather than net-new procurement. These are significant capital commitments. The business cases supporting them will typically include hardware costs, licensing fees, implementation services, and a support contract from the OEM.
What they will almost never include is a staffing line item for the ongoing operational requirements that the expanded estate creates. This is not an oversight unique to any one organisation — it is a structural gap in how infrastructure projects are budgeted and approved. Capital expenditure gets a business case. Operational expenditure follows later, often reactively.
A hardware refresh that doubles your storage system count requires roughly proportional growth in monitoring coverage, maintenance cycles, and incident response capacity. That cost belongs in the business case — not in the emergency headcount request six months later.
The missing variable: staffing
New storage deployments create two distinct staffing demands that are easy to conflate and dangerous to overlook.
The first is the deployment-phase demand: the temporary uplift in engineering capacity required to install, rack, cable, and commission the new systems. This is typically recognised and planned for — it appears as a project cost, often covered by a temporary engagement or an OEM professional services team. It ends when the systems go live.
The second is the ongoing operational demand: the sustained increase in engineering capacity required to monitor, maintain, and respond to incidents across a larger estate. This is the demand that organisations consistently underestimate or fail to budget for entirely. It does not end when the systems go live — it begins there.
The fundamental logic is simple: additional systems require additional oversight. Drive replacements, firmware patching, connectivity troubleshooting, capacity monitoring, and emergency callouts are all functions of system count. Double the systems, and — broadly — you double the operational load on your engineering team.
Business efficiency principles dictate that data centres operate with lean teams. That is a reasonable approach when the estate is stable. When the estate is growing, lean becomes dangerously thin. The question organisations must answer honestly before an infrastructure expansion is: do we have the engineering capacity to operate the estate we are about to create?
The fundamental question: have we factored human resourcing needs into our long-term data strategy? — Gergely Kiss, DACPROS
Three practical solutions
Option 1: In-house expansion
The most direct approach is to hire additional technicians proportional to the estate expansion. This provides maximum control and deepest institutional knowledge. It also requires a budget that has typically already been exhausted on hardware procurement. In-house expansion is the right answer for organisations with sufficient scale to justify dedicated headcount — and the wrong answer for everyone else, because the budget usually is not there.
Option 2: Outsource to a smart hands vendor
Engaging a specialist smart hands vendor for on-site technical support converts a fixed staffing cost into a variable service cost. Smart hands vendors specialise in providing these additional resources — qualified engineers who can handle physical storage operations (drive replacements, firmware updates, cabling, rack expansion) at colocation and data centre sites without the overhead of direct employment.
This approach costs less than full-time hiring, scales flexibly with demand, and transfers the recruitment and retention risk to a provider whose business depends on managing it. For organisations with infrastructure at colocation facilities, where maintaining your own on-site team is impractical anyway, it is often the only economically rational option.
Option 3: Short-term assessment contract
If the scale of the ongoing operational requirement is genuinely uncertain, a short-term engagement — typically 30 days — with a smart hands vendor allows the organisation to measure actual demand before committing to a longer-term arrangement. This is a sensible approach for first-time outsourcers or for estates with unusual operational profiles. It is cheaper than guessing wrong in either direction.
DACPROS provides on-site engineering support for storage estate maintenance and expansion — drive replacements, firmware cycles, cabling, commissioning, and emergency callouts — at colocation and data centre sites across the UK. Contact us to discuss your operational requirements.
A note on OEM tools
Some organisations assume that improvements in OEM management tooling will offset the need for additional engineering capacity — that better monitoring dashboards, smarter alerting, or more capable remote management will allow the same team to manage a larger estate. This reasoning is appealing and wrong. Monitoring tools generate alerts; engineers resolve them. Automation can optimise workflows; it cannot physically replace drives, run cables, or respond to a facility event. The assumption that tooling improvements will compensate for insufficient headcount is wishful thinking, not sound strategy.
The bottom line
A storage capacity plan without a staffing plan is half a plan. The hardware decision and the human resourcing decision are not sequential — they are parallel. Organisations that separate them, approving the capital expenditure first and figuring out the operational headcount later, create a predictable gap between the estate they build and their ability to operate it reliably.
Management must address staffing requirements proactively, before the hardware order is placed, not reactively, after the first incident that a stretched team failed to prevent. The cost of planning correctly is modest. The cost of not planning is not.
