Insights / Bank Transformation
BANK TRANSFORMATION
September 29, 2026
A bank can enter January with an approved transformation budget and still be months away from making a meaningful change. The funding may be agreed while the practical questions remain open: which opportunities should come first, what will implementation require, who will do the work, and when will the bank receive the benefit?
Across banking and capital markets, those questions consume part of the same year in which leadership expects results. Whether the objective is to grow revenue, reduce operating costs, improve service, or strengthen the bank's capabilities, the time spent answering them matters. Some initiatives can generate enough additional financial contribution, through growth, savings, or both, to cover their costs. Others serve important purposes without paying for themselves in the same year.
My view is that fourth-quarter planning should leave the bank ready to begin specific, worthwhile work on the first business day in January. Reaching that point requires enough advance investigation to make sound decisions, together with a clear understanding of what remains uncertain.
A January start date can mean several different things. It might mean the first assessment meeting, the beginning of implementation, or the point at which a changed process starts operating. Those are different positions from which to promise a year's results.
Work backward from the benefit. If a change is intended to generate additional revenue, establish what must happen before customers begin using the service and the bank earns that revenue. If the objective is to reduce avoidable expense, establish when that expense can actually leave the cost base. A completed system release may still need new procedures, staff preparation, control testing, or customer transition before either benefit appears.
Three illustrative examples show how the preparation and timing can differ.
A trading desk may see an opportunity to increase revenue by offering an existing product to additional institutional clients. Realizing that opportunity requires more than an available trading capability. The team needs to establish client demand and pricing, complete counterparty onboarding, confirm credit capacity and risk limits, and ensure that trade processing and supporting technology are ready. The business case should assess the expected incremental contribution after the relevant execution, servicing, funding, and risk costs, with capital needs also considered. The useful start in January could be an agreed phase of client rollout, supported by the work completed before year-end.
A bank improving its commercial customer onboarding process may enable customers to begin using cash-management services sooner and bring fee revenue forward. A simpler process may also reduce the number of prospective customers who abandon onboarding. Those benefits depend on actual demand, customer adoption, pricing, and the bank's ability to deliver the service with effective controls. Business and operations need to agree the customer journey, risk needs to challenge the controls, and technology needs to support a process that works from beginning to end. Faster onboarding alone does not establish how much additional revenue the change will produce.
A bank may plan to move work from a legacy application into an existing platform and retire the old application. The potential savings include licensing and support costs, but they will depend on a successful transition, effective controls, and the ability to end the relevant contracts. Running both systems for longer than planned can delay savings and add expense. The preparation should establish what must be migrated, how the replacement process will be tested, and when the old system and its associated costs can actually be removed.
In all three examples, the financial benefit follows operational readiness and the actions needed to realize it. If the benefit begins in September, the bank may receive only a few months of financial contribution that year. An annualized estimate describes a different result. The distinction belongs in the business case before leadership commits to a financial target.
Earlier planning can create more room for implementation and benefit realization. It does not remove the need to test assumptions or account for costs incurred during planning itself.
A useful assessment should produce a ranked set of opportunities with reasons for the ranking. Strategic relevance, operational constraints, customer impact, risk, implementation effort, and the timing of benefits all matter.
Some changes can support growth by improving customer acquisition, retention, or access to services. Others can reduce operating costs or combine growth and efficiency benefits. An attractive return may still depend on resources already committed elsewhere or assumptions that need further testing.
There are also initiatives whose primary purpose is resilience, better customer outcomes, stronger controls, or a strategic capability the bank needs. They may merit investment without same-year payback. Those differences need to be visible in the decision.
Required regulatory remediation also needs its own treatment. Financial return can inform how the work is sequenced and delivered, but a weak financial return is not a reason to disregard an obligation. The bank needs to understand the concern it must resolve and the comprehensive response required.
For each candidate, I would want a short business case that explains the problem, the intended outcome, the scope of change, the likely cost, the dependencies, and the evidence supporting the benefit estimate. Where the evidence is weak, identify the work needed to improve it before making a commitment.
Business, operations, risk, and technology should help shape the proposed change before its scope hardens into a delivery promise. Finance should challenge the financial assumptions and how results will be measured. Procurement or other functions may also be essential where supplier terms or specialist dependencies affect the timetable.
Each group needs to understand the benefit to the bank and the contribution expected from it. That does not mean every function receives an identical benefit. A growth initiative may require business leaders to establish customer demand, operations to prepare for additional volume, technology to enable the service, and risk to challenge the proposed controls. Finance needs to assess the contribution remaining after the associated costs. Those responsibilities belong in one coherent business case.
If a group sees only an unexplained burden, its apparent agreement may not survive the first difficult tradeoff. Resolve those questions while leadership still has choices about scope, sequence, and capacity.
A delivery owner is accountable for producing an agreed result. A benefit owner is accountable for assessing whether that result creates the intended value. Sometimes those responsibilities sit with the same person. They should still be explicit.
Record the starting position, intended measure, expected timing, and review points for each material benefit. Identify where the evidence will come from and who will challenge the interpretation.
For a revenue benefit, agree the starting position and how the bank will distinguish the contribution of the initiative from growth it would otherwise have achieved. Track the relevant customer activity, realized revenue, and associated costs. Account for revenue shifted from another product or channel rather than counting all activity as new business.
A process that saves staff time may release capacity without reducing expenditure. Leadership needs to decide how that capacity will be used. A financial forecast should distinguish incremental revenue contribution, cash savings, avoided future costs, improved service, and reduced exposure to risk instead of adding them together as though they were interchangeable.
That discipline also prevents the same benefit from being claimed by several programs. The bank needs one accountable view of what changed and what value it received.
An initiative may be able to cover its costs through incremental revenue contribution, operating cost savings, or a combination of both. Self-funding through growth is just as relevant to assess as self-funding through efficiency. Neither should be assumed before the business case is tested.
For a revenue-led initiative, assess the financial contribution remaining after the costs of acquiring customers and delivering and supporting the additional business. Where relevant, include funding costs, expected credit losses, and capital requirements. Gross revenue alone is not the amount available to recover the investment.
Include the relevant assessment and implementation costs, internal capacity, transition effort, recurring expenses, and the time required for benefits to build. Count each cost once and use a consistent basis for comparing the alternatives. Consider the effects of delays, slower adoption, and lower-than-expected benefits.
A payback calculation also does not establish that the bank can fund the work as it proceeds. Costs may arrive well before additional revenue is collected or savings are realized. Finance should distinguish the projected financial return from the cash needed to support delivery.
A useful business case should make those timing differences visible. Leadership can then compare an earlier, smaller benefit with a larger opportunity that takes longer, alongside the risks and strategic value of each. Same-year payback is one consideration in that decision; it is not a universal test of whether an initiative should proceed.
The output of fourth-quarter work should be usable by the people expected to deliver. I would look for:
The plan should also identify what would cause leadership to revisit the decision. A changed market opportunity, material cost increase, or unresolved dependency can alter the case for discretionary work. The plan must be disciplined enough to support delivery and open enough to respond to evidence.
In my article on program drift, I discussed the need to keep business, operations, risk, and technology invested in the same outcome throughout delivery. That work begins before the program is underway.
At AntePartners, we help leadership assess growth and efficiency opportunities alongside operational, strategic, and regulatory needs, develop practical business cases, and connect those decisions to accountable execution. We work with the functions that will have to operate the change and establish measurable progress along the way.
If your bank is preparing its 2027 change agenda, contact AntePartners to discuss which initiatives are ready to begin in January, which assumptions still need investigation, and how delivery and value realization will be measured.
