A pricing model is likely failing when deposits are leaking to higher-rate competitors, customer loyalty weakens, and the bank cannot react quickly enough to market changes. If rates are treated as static, customers notice the gap between the bank’s offer and the market. That usually signals the need for more flexible pricing tied to customer relationship value.
How to tell when deposit pricing is no longer tracking the market
The clearest sign is not a single rate-sheet miss, but a pattern: deposits start moving to competitors that are paying up faster, promo balances stop converting into sticky balances, and relationship depth no longer offsets price. In a rising-rate environment, that usually means the pricing engine is reacting to the market too slowly or treating all balances as if they behave the same.
Once that happens, the bank is no longer managing price as a portfolio decision. It is quoting a generic rate and hoping customer inertia will cover the gap, which works only until competitors make the spread visible.
Operational signals that the model has broken
Failure shows up in the balance mix before it shows up in the P&L. Non-maturity deposits can reprice away, promotional accounts can roll off with weak renewal, and high-value customers may remain only where relationship services, convenience, or bundled products still outweigh the yield gap. If those segments are decaying at the same time, the bank is losing control of price elasticity.
Another warning is that internal teams cannot answer a simple question quickly: which customer groups deserve higher pricing, which can be held, and which are most likely to leave? If pricing decisions depend on manual exceptions or lagging committee review, the model is probably too rigid for a fast-moving rate cycle.
- Watch for rising runoff in rate-sensitive balances and weaker renewal on maturing deposits.
- Compare realized pricing to peer offers by segment, not just to a headline market rate.
- Check whether relationship value is actually changing customer behaviour or only explaining it after the fact.
Why rigidity becomes dangerous in a rising-rate market
A static model fails because rate competition is dynamic. When market yields move up, customers test whether their bank is still competitive, especially on balances that are easy to move. If the bank prices too slowly, it gives away volume; if it reprices too broadly, it protects volume at the cost of margin.
The real problem is usually not that the bank lacks data, but that it lacks segmentation discipline. Different customers have different retention thresholds, and a model that ignores relationship strength, product usage, or balance behaviour will misprice both loyalty and mobility.
That is why a failing model often creates a false sense of stability. Balances may appear stable for a period, but they are becoming more rate-sensitive underneath, so the bank is effectively paying more for less loyalty.
Risk and Threat Considerations
A failing pricing model creates earnings pressure, funding instability, and franchise risk at the same time. In a rising-rate market, the institution can lose core balances faster than its pricing governance can react, which forces a costly scramble to replace funding or compresses margin to defend volume.
Failure mechanism: The model assumes static customer behaviour, so it underestimates rate sensitivity, missegments relationship value, and applies pricing changes too slowly to prevent attrition.
Impact: The bank can suffer balance runoff, weaker retention, higher funding cost, and poorer margin protection, especially when competitors reprice more aggressively and customers can switch with little friction.
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 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.RM-01 — Risk Management Strategy | Deposit repricing failure is a funding and margin risk that needs formal risk appetite and response thresholds. |
| Recommendation — Define rate-sensitive deposit risk tolerances and trigger segment repricing when runoff exceeds appetite. | ||
| ISO/IEC 27001:2022 | A.5.4 — Management Responsibilities | Pricing governance failure is an ownership and accountability issue requiring clear decision responsibility. |
| A.5.29 — Information security during disruption | Rapid rate changes can disrupt funding stability, making response planning and resilience relevant. | |
| Recommendation — Assign clear ownership for deposit pricing decisions and escalation when market conditions shift. Prepare contingency pricing actions for rapid balance leakage and funding stress. | ||
Practitioner Guidance
What to prioritise: Focus first on the balances that are both most rate-sensitive and most valuable to retain. If a segment is leaving despite strong relationship depth, the issue is likely not service quality but a pricing threshold problem that needs segment-specific action.
What to verify: Confirm that pricing decisions are based on observed customer behaviour, not only on policy bands or treasury assumptions. The model should be able to show which balances are defended, which are allowed to roll off, and why the bank believes each outcome is acceptable.
Practitioner takeaway: In a rising-rate market, a pricing model fails when it can no longer distinguish between balances that are truly sticky and balances that are merely untested by competition.
Related resources from NHI Mgmt Group
- What are the signs that an IT stack is failing under its current operating model?
- What are the signs that a click-through rate model is failing because of data quality problems?
- How does the consumer-secret-entitlement model help with governance at scale?
- What are the signs that an authorization model is failing in a polling or collaboration app?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 26, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
