More circuit capacity was only one of the options
The team compared a conventional hardware and circuit-capacity refresh with Cisco Intelligent WAN. It selected the software-defined approach, supported by laboratory preparation and an onsite proof of concept brought into operation in about a week.
The comparison addressed how the network used connectivity, rather than only how much it purchased. An acquired estate can inherit several different ways of delivering the same business service. A common architecture offers a way to reduce that variation. The proof of concept gave internal stakeholders something operational to assess before the design became the basis for the wider migration.
Application requirements shaped the path selection
The design carried critical voice and video over MPLS while using less expensive links for lower-priority traffic. The program also included Cisco switching, wireless, security, implementation support and training. Central management gave the IT team a shared view of wired and wireless infrastructure.
This architecture connected cost control to the treatment of different applications. It did not assume that every packet needed the same transport characteristics. The technical change was a more deliberate relationship between business traffic and the available paths. That distinction explains the reported avoided cost more accurately than suggesting the bank simply bought less connectivity.
The financial result was an avoided increase
The case reports avoidance of a greater-than-60-percent increase in network expense for redundant links. It does not report a 60 percent reduction in the bank’s existing total network bill. The bank also described improved continuity and fewer user complaints after implementation.
Avoided expenditure compares the chosen design with an alternative that was being considered. It is a meaningful project measure, but it has a different baseline from a reduction in historical spending. Preserving that baseline makes the outcome interpretable and avoids turning an architecture comparison into an unsupported savings claim.
The operating model accelerated subsequent branches
Huntington reported that deployment tools brought new branches online in days instead of weeks or months. That statement describes network deployment, not every construction and business-readiness task required to open a branch.
Cartennas’s assessment is that the acquisition provided the scale and urgency for a common design, while the pilot provided evidence for the decision. The resulting network connected application-aware path selection with shared management and a faster deployment process. The case’s lasting value is that relationship between consolidation and repeatability. It records how the bank made a varied estate easier to operate and extend, using the technology available during that program.