Our client, Fuze, approached us with a request to implement new changes and integrations based on the needs of a potential customer for their wealth management platform.
One of the main challenges was integrating with the customer’s information source while also improving how financial data was visually displayed and grouped, ensuring it was better suited to the operational needs of this large company. To address this, we introduced a microservice architecture, developing the new module as an independent service to enable scalability and resource efficiency.
During our short-term cooperation, we delivered a stable, scalable integration with enhanced functionality, addressed critical edge cases, and ensured the platform was ready to meet the new client’s operational needs.
Fuze is a platform for up-to-date clarity and visibility across all your clients’ finances and investments. It is an all-in-one solution for various account holders, including financial advisors, wealth managers, financial planners, and private banks.
Essentially, it all boils down to this. Fuze aggregates and groups financial data for various organizations. For this purpose, the client supports a large number of integrations with third-party banking services like Open Banking, allowing you to simultaneously work with bank data, cryptocurrency, stocks, Wise, Revolut, etc.
Our client received a request from a potential large customer to integrate with their information source. Fuze also aimed to improve the visual presentation and grouping of financial data to suit the company’s operational needs better and expand the metrics with additional financial indicators.
In order to address Fuze’s need efficiently, our team immediately added back-end and front-end developers to the project and conducted a detailed review of the existing code. This was done to understand how to implement and quickly integrate new functionality, as well as identify potential risks that might arise.
During this stage, we discovered that the front-end part had large pieces of code written using v0 (Vibe coding with AI), and as a result, it was almost unreadable and poorly extensible. Although this approach accelerated initial development, the generated code didn’t have proper structure, clear naming conventions, and scalability principles, making it almost unreadable and hard to maintain.
Our team quickly understood that extending functionality or integrating new modules posed critical risks.
Therefore, we had to rewrite large chunks of the front-end to work with it effectively. On the back-end side, after the review, we decided to develop this module as a standalone microservice that could operate independently from the main application, since it was currently required by only one client.
This made it possible to qualitatively expand its functionality without affecting the main application while making it independent from its core components. During integration with this third-party service, we discovered many edge cases that did not fit the existing functionality’s logic or were poorly thought out. In order to reach the best possible results, we worked on such cases separately, presenting the customer with a ready-made solution for final approval while taking full responsibility for handling these edge cases, analyzing them in detail, and preparing solutions independently.
This decision allowed us to quickly and effectively integrate support for the new system and expand the existing functionality, without drastically affecting existing systems. The final result granted stability and minimal risk of making the overall system unstable.