Post-Merger Banking Platform Consolidation

A Tier 1 European bank was in the middle of a high-profile post-merger integration. The target state was a single digital platform replacing nine disconnected legacy systems across COBOL, legacy Java, and manual operational processes.

Nine months into the programme, backend integration work had not materially progressed. The most difficult part was not the user interface. It was the orchestration behind it: asynchronous risk checks, factoring workflows, state transitions, exceptions, and hand-offs that had accumulated across years of legacy operations. The programme was exposed to delivery pressure, commercial escalation, and loss of client confidence.

The first step was a deep architecture and process analysis: which systems owned which decisions, where risk checks happened, which steps were synchronous versus asynchronous, and which manual interventions had to be preserved, redesigned, or eliminated.

The recovery architecture combined event-driven microservices with BPM orchestration. Microservices handled bounded business capabilities and integration points; BPM handled long-running workflows, human tasks, exception paths, and auditability. This gave the programme a way to model the real banking process without forcing every legacy behaviour into a brittle request-response design.

The microservice boundaries were also designed around delivery ownership. Each engineering team owned a service or small set of related services, which made the distributed delivery model easier to govern and reduced cross-team dependency friction.

The platform used an event-driven design not only between services, but also within service boundaries where asynchronous state changes, risk decisions, and workflow events needed to be explicit and auditable. Kafka-based event streams and well-defined API contracts gave the programme a stable integration model for complex banking workflows.

To prevent teams from being blocked by unfinished dependencies, API interfaces and event interfaces were mocked from the start. This contract-first approach allowed teams across multiple locations to build, test, and validate their services independently while the wider platform was still coming together.

The work then moved from architecture into execution. A delivery roadmap was established, engineering capacity was sourced and scaled from scratch, and the programme moved from stalled analysis into full-speed build. The architecture gave the engineering teams clear service boundaries, integration contracts, and workflow ownership so delivery could proceed without every decision re-opening the target design.

The consolidated platform was delivered and handed over to the maintenance organisation. The programme moved from a stalled backend recovery situation to a working platform that could support the post-merger operating model.

The contract-first, event-driven delivery model reduced cross-team blocking and gave the programme a practical path from stalled backend integration to coordinated multi-team execution.

The turnaround helped restore client confidence in the delivery team and created the basis for a longer-term commercial extension for the consulting firm. The important lesson was architectural: post-merger consolidation succeeds when legacy workflow reality is made explicit, modelled deliberately, and governed through execution, not hidden behind a simplified platform roadmap.