Engineering customer acquisition and lending origination for ABSA

Customer acquisition and lending origination sit at the revenue-generating core of a retail and commercial bank, and they are among the hardest journeys to modernise. An origination flow has to capture an applicant cleanly, run affordability and risk checks, satisfy regulatory obligations and reach a credit decision — often across products with different rules and different underlying systems.

For a bank at ABSA's scale, that complexity is multiplied by volume and by the number of teams, products and legacy platforms involved. A programme that touches acquisition, lending and self-service at once needs to hold a consistent data model and a coherent journey across all of them, or it fragments into disconnected point solutions.

Adding self-service journeys raised the bar further: work that previously depended on a banker in the loop had to be re-engineered so a customer could progress it themselves, without losing the controls the assisted process enforced.

Origination is where lending revenue is either captured or lost. Friction in the acquisition and lending journey suppresses conversion at the exact point the bank is trying to grow, while weak controls create risk and rework downstream. Getting both the journey and its governance right is a direct commercial and regulatory concern.

At this scale, delivery risk is itself a stake. A multi-workstream programme spanning acquisition, lending and self-service can stall without a management office to sequence dependencies, hold scope and keep releases coordinated — which is why the engagement was structured as a governed programme, not a loose set of builds.

The engineering team began with discovery across the acquisition and lending journeys — mapping the products in scope, the decisioning and compliance steps each required, and the systems origination had to integrate with. That analysis set the data model and the boundaries between what the platform would own and what it would call out to.

Delivery ran iteratively against that architecture. Origination and onboarding capability was built on Financial Services Cloud, extended with custom engineering where standard configuration could not express the bank's products or rules, and hardened through testing before each release rather than after it.

A programme management office coordinated the workstreams — acquisition, lending origination and the self-service (MPO Self Journey) journeys — sequencing dependencies, managing scope and keeping releases aligned so the pieces landed as one coherent capability instead of competing projects.

Cloud23 engineered a customer-acquisition and lending-origination capability on Salesforce Financial Services Cloud, extended with custom engineering to handle the products, decisioning and integrations the bank's origination flows required. Applications are captured, progressed through the necessary checks and moved toward a decision on a consistent platform.

The MPO Self Journey work re-engineered selected steps for self-service, letting customers advance their own journeys where previously a banker was required — while preserving the checks and controls the assisted path enforced.

The programme management office wrapped the build, giving ABSA structured delivery governance across the acquisition, lending and self-service workstreams so the programme progressed as a managed whole.

The programme delivered a modernised acquisition and lending-origination capability on a shared platform, giving the bank a consistent foundation for capturing applicants and progressing them through origination rather than a patchwork of disconnected flows.

The self-service journeys give customers the ability to advance parts of the journey themselves, shifting work that previously required a banker onto a controlled digital path.

The programme management office gives the bank coordinated delivery governance across the workstreams — a structure for sequencing dependencies and keeping releases aligned as the capability continues to evolve.