Legacy modernization for a UK challenger bank

Client profile

The client is a UK challenger bank with approximately £4.2 billion in assets, serving over 1.4 million retail customers across the United Kingdom and select European markets. The bank grew rapidly from 2016 to 2023 through digital-first acquisition and had built its customer-facing mobile app on modern infrastructure, but its core banking, payments processing, and regulatory reporting systems still ran on legacy technology inherited from a 2018 acquisition of a regional building society.

The challenge

By early 2025, the client's legacy core banking platform had become a material operational and regulatory risk. Deployment cycles for the platform averaged 42 days from feature specification to production release, roughly 14 times slower than the client's modern mobile application stack. Every release required overnight downtime windows, mandatory coordination with three external vendors, and rollback rehearsals for high-risk changes.

The regulatory pressure was intensifying. The UK Prudential Regulation Authority had issued formal observations about the client's operational resilience posture, specifically citing the concentration risk of running critical banking functions on aging technology maintained by a shrinking internal team. Two senior architects familiar with the legacy stack had retired in the preceding 18 months. Recruiting replacement expertise in London was slow and prohibitively expensive.

The client explored three alternatives before engaging Corpshore Vietnam: a full replatform to a modern core banking vendor (rejected as an 18-24 month, £30M+ program that would freeze other product initiatives), an offshoring partnership with a large Indian systems integrator (rejected due to concerns about resource dedication and cultural fit), and building an in-house nearshore team in Poland (rejected on cost and difficulty attracting COBOL-adjacent talent). None of the alternatives credibly addressed the combination of speed, cost, and technical depth the client needed.

Why Corpshore Vietnam

The bank selected Corpshore Vietnam after a competitive evaluation of five vendors. Three factors were decisive: our ability to assemble a 40-person team combining COBOL and modern Java/Kotlin skills within four weeks of contract signature, our Toronto-based account team structure that gave the CTO a single point of commercial accountability, and our demonstrated PDPD and GDPR compliance for handling regulated customer data flows.

During the evaluation, our proposed technical lead spent a full day at the client's London office, reviewed sample legacy code, and identified three specific architectural decoupling opportunities that competing vendors had missed. This depth of technical engagement during pre-sales, rather than after contract signature, materially shifted the client's assessment.

The engagement

The engagement launched in June 2025 with a 14-person team in Ho Chi Minh City. The team expanded to 42 engineers by month six, split across HCMC (32 engineers) and Hanoi (10 engineers, focused on payments integration and regulatory reporting). Team structure: one Toronto-based engagement director, two Vietnam-based technical leads, seven senior engineers, 24 mid-level engineers, six junior engineers, one QA lead, and one DevOps engineer. Daily standups run 8:00 AM UK time (2:00 PM Vietnam) with weekly business reviews at 3:00 PM UK time.

Approach and methodology

Phase 1 (months 1-3): Discovery and stabilization. The team documented the legacy platform's actual behavior against its intended behavior. Twenty-seven undocumented behaviors were catalogued. Test automation coverage rose from 12% to 46% during this phase, establishing the safety net required for aggressive refactoring.

Phase 2 (months 4-9): Strangler fig migration. New functionality was built on a modern Java 21 / Spring Boot 3 stack running in parallel to the legacy platform. API gateways progressively routed traffic away from legacy modules. No big-bang cutover was attempted. This approach limited risk and satisfied regulatory expectations for change management.

Phase 3 (months 10-18): Modernization at pace. With 82% of new development happening on the modern stack, the team focused on retiring legacy modules and rebuilding the payments processing pipeline for real-time settlement. Regulatory reporting automation reduced monthly compliance workload from 320 person-hours to 84.

Results

By month 12, the client had achieved a 92% reduction in release cycle time (42 days to 3.2 days), an 81% reduction in production incidents (from 47 monthly to 9), and had retired 62% of the legacy platform's LOC to the modern stack. The PRA closed its operational resilience observation in month 14. Recruitment cost avoidance was estimated at £2.8M annualized (equivalent London-based hiring).

The bank has since expanded the engagement to include a mobile banking modernization workstream (adding 18 engineers in month 15) and a fraud analytics platform buildout using our AI division's data annotation capabilities.

Enduring value

Beyond the immediate modernization outcomes, the engagement built durable capability the client now owns. Twenty-two of the 42 engineers have been on the account for over 12 months, developing deep institutional knowledge of the bank's systems. Attrition on this account is 8% annually versus a London BFSI benchmark of 22%. The engineering documentation the team produced during Phase 1 has become the bank's internal reference for the legacy stack, valuable independent of the vendor relationship.