Overview
BNP Paribas Cardif is one of the world's leading insurance companies, operating in Brazil as a regulated financial institution under the Central Bank of Brazil. Their insurance activation process ran entirely through a call center. The goal was to replace that with a self-service digital portal, reducing operational cost while making the experience faster and more accessible for customers.
The Challenge
The core technical challenge was building a single form experience that handled the Cardif insurance products in scope — each with its own eligibility rules, data requirements, and activation flow. A customer activating a credit card protection plan follows a completely different path than one activating a life insurance policy. The portal had to branch dynamically based on the product type, guide the user through the right sub-flow, validate according to product-specific rules, and integrate with the backend at each step. Building this as isolated forms per product was not an option — the architecture had to be shared and consistent across products to be maintainable.
My Role & Process
Frontend Development
- Built the Angular frontend from scratch as part of a two-dev frontend team, splitting ownership by feature and screen to maximize parallel delivery
- Implemented a dynamic multi-branch form architecture in Angular — a single entry point that conditionally rendered different steps and validations based on the selected insurance product
- Integrated REST APIs provided by the backend team, handling async validation, error states, and partial form persistence across product-specific flows
- Maintained consistent component architecture across both frontend developers — reusable form controls, shared validators, and Angular Material components applied uniformly
- Delivered all features on schedule within a tight 5-month engagement on a project with no tolerance for delays
The Solution
A production Angular application that allows customers to activate BNP Paribas Cardif insurance products through a guided digital flow. The portal replaced the call center as the primary activation channel, handling the products in scope through a shared component architecture with product-specific branching logic.
Results & Impact
The portal contributed to a 30% reduction in operational costs as self-service activation replaced call center volume. It was delivered within a five-month engagement with no tolerance for delays, under a shared architecture built to stay maintainable as products were added.