A cost center view treats the branch as overhead to minimize, while a relationship channel view treats it as part of customer acquisition, retention, and lending. The article’s central claim is that branches still matter because they support trust, in-person service, and local business activity. Practitioners should judge branches by customer outcomes and revenue contribution, not by occupancy and maintenance expense alone.
How the Two Views Change the Branch Decision
A cost center lens asks whether the branch is expensive to run relative to the transactions it processes. That view tends to prioritise occupancy, staffing, maintenance, and footprint reduction. A relationship channel lens asks what the branch enables that a digital-only model may not, including trust-building, complex sales conversations, retention work, and local visibility that can influence deposit growth and lending.
The practical difference is that the same branch can look inefficient on a pure cost basis yet still be economically useful when it supports higher-value relationships. This is why branch performance should be judged with a wider set of signals, such as customer acquisition, product penetration, referral quality, and the branch’s role in serving small-business and community needs.
Where the Cost Center Model Misleads
The cost center model often overweights what is easiest to count and underweights what is hardest to attribute. Foot traffic, teller volume, and space utilisation are visible; trust creation, retention, and relationship deepening are slower-moving and less obvious. That can lead firms to close or shrink branches that still contribute to revenue through advice, cross-sell, and local credibility.
This does not mean every branch deserves to stay open. It means the decision should distinguish between a branch that only processes routine transactions and a branch that supports broader customer economics. The right question is not just “How much does this branch cost?” but “What business outcomes disappear if this branch goes away?”
For reference, the article’s branch logic aligns with the broader NHI governance lesson that visibility matters more than assumptions: only 5.7% of organisations have full visibility into their service accounts, a reminder that what is easy to measure is not always what is most important to manage. Ultimate Guide to NHIs — What are Non-Human Identities
What Practitioners Should Measure Instead
If the branch is treated as a relationship channel, the scorecard should include measures that capture revenue contribution and customer behaviour, not just expense control. Useful indicators include new-account conversion, retention of higher-value households, loan origination influenced by branch staff, local business development, appointment conversion, and the share of customers who still prefer face-to-face help for complex decisions.
Branches also need to be evaluated by segment. A location in a dense digital market may justify a lighter footprint, while a branch in a community-led or small-business market may generate disproportionate trust and lending opportunities. That means the same branch format can be wrong in one geography and right in another.
Where digital service is strong, the branch should be positioned as an escalation and advisory point rather than a default transaction site. That helps banks preserve the relationship value of the branch while reducing the cost of low-value routine activity.
Risk and Threat Considerations
Branch strategy carries operational and competitive risk when management treats every location as interchangeable overhead. Closing or thinning a branch without understanding the customer relationships attached to it can erode trust, weaken local deposit stability, and push borrowers or business clients to competitors. The risk is not just service inconvenience, it is relationship attrition and revenue leakage.
Failure mechanism: The institution optimises for measurable expense reduction, but misses the less visible role the branch plays in acquisition, retention, and lending. Once customers lose a trusted local touchpoint, the damage often appears later as lower conversion, weaker loyalty, and reduced product depth.
Impact: Short-term savings can be offset by slower growth, weaker local market presence, and reduced ability to originate or defend profitable relationships. In banking, that can turn a cost decision into a franchise decision.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.OV — Oversight | Branch decisions need oversight of business outcomes, not just operating expense. |
| ID.BE — Asset Management and Business Environment | The branch must be evaluated in its business context and role in customer activity. | |
| GV.RM — Risk Management Strategy | Closing or shrinking branches changes customer, revenue, and franchise risk. | |
| Recommendation — Use oversight metrics to judge branch value by customer and revenue impact. Map each branch to the business outcomes it supports before changing the footprint. Include branch relationship loss in the organisation’s risk strategy. | ||
| CIS Controls v8 | 14 — Security Awareness and Skills Training | Branch staff capability affects relationship quality and customer trust. |
| Recommendation — Train branch staff for advisory and escalation roles, not only transactions. | ||
Practitioner Guidance
What to prioritise: Separate routine transaction activity from relationship-bearing activity. If the branch mainly handles cash, simple payments, or service requests, cost pressure matters more. If it supports advisory sales, lending conversations, or community trust, treat it as a revenue enabler and measure it accordingly.
What to verify: Before closing, downsizing, or redesigning a branch, verify which customer segments, products, and local business relationships depend on it. A branch can look underused while still being strategically important to a specific high-value population.
Practitioner takeaway: The core mistake is to manage branches as real estate before you manage them as customer infrastructure; once that framing is fixed, the economics become more accurate and the strategy becomes less brittle.
Related resources from NHI Mgmt Group
- What is the difference between attack surface management and NHI governance?
- What is the difference between reviewing human access and reviewing NHIs?
- What is the difference between role-based access and API key governance for NHI security?
- What is the difference between human IAM controls and NHI governance?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 18, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
