Ask a bank what a branch costs to equip and you will usually get a hardware number: so many workstations, a server, some switches, a few printers. It is a clean figure and it is almost always wrong, not because the prices are off, but because the hardware is the smallest part of what actually keeps a branch trading.
In the Nigerian operating environment, branch infrastructure is a resilience budget far more than an equipment budget. The question is not "what does the kit cost" but "what does an hour of downtime cost, and what are we spending to prevent it." Reframe the budget that way and the line items change.
The hardware is the easy part
Workstations, a branch server or edge appliance, switches, an access layer for Wi-Fi, printers, scanners, and the counter peripherals that front-line staff use, this is the visible layer, and it is genuinely the most predictable to cost. Specifications are well understood, warranties are standard, and refresh cycles are roughly four years for endpoints and longer for network gear.
The mistake is stopping here. A branch full of new workstations with unstable power and a single connectivity link is not a resilient branch. It is an expensive one that still cannot transact when the grid drops.
A bank branch does not fail because its computers are old. It fails because the power, the link, or the cabling underneath them was the cheapest line in the budget.
Power is the line that decides everything
Nigeria's power reality means a branch budget that does not treat power as a first-class system is not a serious budget. Plan for layered protection, and cost each layer honestly:
- Conditioning and protection. Voltage stabilisation and surge protection to keep equipment from dying early, this is preventive spend that quietly saves the hardware budget.
- Battery runtime (UPS). Enough to ride through short outages and switchover gaps without dropping transactions mid-flight. Size it to the branch's actual critical load, not a round number.
- Generator and changeover. Automatic transfer that brings the branch back without a member of staff walking to a switch. The cost here is the changeover discipline as much as the generator itself.
The reason power belongs near the top of the budget is sequencing: every other investment depends on it. A new server protected by an undersized UPS is a new server you will replace early.
Connectivity needs a plan B that is actually separate
A branch on a single link is one fibre cut away from being closed. Resilient connectivity means a primary link and a genuinely diverse secondary, different medium or different carrier, with failover that happens automatically and fast enough that staff barely notice. Budget for the second link as a running cost, not an optional extra, and budget for the edge device that manages the failover.
This is also where branches quietly overspend or underspend depending on honesty about traffic. A branch that mostly runs a thin core-banking client and some back-office traffic has a very different need from one running heavy document workflows. Size to the work.
The infrastructure underneath: cabling and the comms room
Structured cabling is the least glamorous line in any infrastructure budget and the one that causes the most expensive problems when it is skimped. Poorly terminated cabling and an unventilated, disorganised comms room produce intermittent faults that are maddening to diagnose and that erode trust in everything else.
Budget for proper structured cabling, a ventilated and physically secure comms room, labelling, and patch management. Done once and done well, this layer outlives several hardware refreshes. Done badly, it is a recurring tax on every support visit.
Don't forget physical and environmental factors
Cooling, physical access control to the comms room, and basic environmental monitoring belong in the budget. In branch environments these are small numbers that prevent large incidents, a failed cooling fan that bakes a switch is a cheap problem to prevent and an expensive one to discover at 2pm on a busy day.
The lifecycle cost no one puts on the slide
The largest under-budgeted figure is the cost of keeping the branch running after go-live. Hardware is capital; uptime is operational. A defensible branch budget includes:
- Warranties and spares sized to your geography. A branch in a city with same-day parts is a different risk from one a day's drive from the nearest spare.
- A support and SLA model with a defined response time, because the question is never whether something fails but how fast you are back.
- Monitoring so problems are seen centrally before a branch manager phones to say the network is down.
This ongoing layer is precisely what a managed services arrangement exists to make predictable: turning a series of unbudgeted emergencies into a known monthly cost. For banks and other financial services operators, that predictability is itself a compliance and risk asset.
A budget that survives contact with reality
The branches that stay open through outages, fibre cuts, and busy afternoons are not the ones that bought the most expensive computers. They are the ones whose budgets treated power, connectivity, cabling, and support as the infrastructure and the workstations as the part you can always replace.
If you take one thing from this into your next branch budget, make it this: spend less time perfecting the hardware spreadsheet and more time pricing the hour of downtime you are trying to prevent. The first number is easy and flattering. The second is the one your customers will actually feel.
