Skip to main content

FiftyFive Tech

Email Us sales@fiftyfivetech.io
Get in Touch
Aerial view of a snow-dusted coastal city with colourful rooftops, dark blue sea and a snow-covered mountain range under a clear blue sky

Cloud & modernisation

Modernising a live Nordic investment platform: 40% fewer defects

FiftyFive modernised a live Nordic investment platform: modular backend, React rework, CRM sync and automated QA, cutting post-launch defects by 40%.

Discuss modernising your platform
Industry
Fintech — wealth management technology
Region
Nordics
Solution
Modernised live Nordic investment platform
Story

About the client

The client provides digital investment software to private banks, wealth advisers and asset managers across the Nordic region, under Nordic financial requirements. Its platform was live and carrying real transactions, so every change had to land without disrupting users. The client wanted a better user experience, stronger performance and faster feature releases, and brought in FiftyFive to work alongside its internal tech lead.

Challenge

Changing a live investment platform nobody had documented

  • A five-technology backend. PHP, Node.js, TypeScript, Python and MariaDB with SOAP APIs on Google Cloud, and refactoring had to happen while transactions kept flowing.
  • A frontend without a pattern. The React, Redux and Webpack frontend lacked consistent state management and build structure, which slowed rendering of live investment data.
  • Two versions of the client. CRM and core investment system were not synchronised, so advisers worked from partial or conflicting records.
  • Missing services. There was no notification service, and no link to the brokerage accounts many end users held, so positions had to be reconciled by hand.
  • Unmeasured release risk. Test coverage was minimal and validation was not formally defined.
Solution

What FiftyFive built

FiftyFive structured the work as full-cycle development and testing rather than a one-off sprint, working under an agile model with the client's tech lead. The team: reverse-engineered and documented the legacy codebase before changing it; refactored the backend into modular components with clearer service boundaries; standardised state management and rendering in the React and Redux frontend and added localisation; developed and deployed a notification service and a brokerage-linking service; integrated the CRM with the core investment system; introduced automated regression, validation and performance test cycles, and updated the technical documentation.

How the solution works

  1. Documentation first

    • The team rebuilt an accurate picture of existing business logic and recorded it as technical documentation.
    • Refactoring decisions were then made against that reference rather than against assumptions, and future engineers inherit the same map.
  2. A modular backend

    • Backend logic was reorganised into modules with defined boundaries, so services can be maintained, tested and scaled independently across the PHP, Node.js, TypeScript, Python and MariaDB stack.
    • Communication over the SOAP interfaces on Google Cloud was made more efficient, giving a structure that scales without full-system rewrites.
  3. A consistent frontend

    • State management patterns were standardised across the React and Redux application, dynamic rendering of portfolio and account views was improved, localisation support was added, and the Webpack build was aligned with the new structure.
  4. New services inside the modular backend

    • A notification service tells end users about portfolio and account events.
    • A brokerage-linking service synchronises brokerage account data with the platform, removing manual reconciliation.
    • Both run within the refactored backend rather than as bolt-ons.
  5. One client record

    • FiftyFive mapped client data models across the CRM and the investment-management modules and set up a synchronised data flow between the two systems, removing duplicate entry and conflicting records.
  6. Automated quality gates

    • Ad hoc testing was replaced by automated regression, validation and performance cycles, with validation workflows defined where none had existed.

Technology stack

PHP, Node.js, TypeScript, PythonBackend services, refactored into modules
MariaDBPlatform database
SOAP APIsService interfaces, made more efficient
React and ReduxFrontend, with standardised state management and localisation
WebpackFrontend build, aligned to the new structure
Google CloudHosting for the platform and its APIs

What the solution enabled

Outcomes

Business transformation

40%

Fewer post-launch defects

35%

Faster user onboarding

99.9%

System uptime

40% fewer post-launch defects

Automated regression, validation and performance testing replaced manual checks.

35% faster user onboarding

Synchronising CRM and core investment data removed duplicate entry.

99.9% system uptime

After the backend refactoring and automated performance testing.

A documented, modular codebase

That new engineers can be onboarded onto and that scales without a rewrite.

FiftyFive Technologies is modernising the digital investment platform of a Nordic wealth-technology provider that serves private banking, wealth advisory and asset management firms. The platform ran on an undocumented, multi-language legacy codebase with minimal test coverage. A four-person FiftyFive team reverse-engineered and refactored the PHP, Node.js, TypeScript and Python backend, reworked the React and Redux frontend, built notification and brokerage-linking services, synchronised the CRM with the core investment system and automated QA. Post-launch defects fell by 40% and user onboarding became 35% faster.

FAQ

Technical questions

How do you modernise an undocumented legacy fintech codebase without disrupting live users?

FiftyFive Technologies began by reverse-engineering and documenting the existing business logic, then refactored the backend into modules with clear service boundaries while transactions kept running. Automated regression, validation and performance tests were added so each release was checked before going live. For this Nordic wealth-technology provider, post-launch defects fell by 40%.

How do you stop advisers working from conflicting client records?

FiftyFive mapped the client data models used by the CRM and the core investment system and set up a synchronised data flow between them, so both systems hold one consistent client record. Removing duplicate entry made user onboarding 35% faster.

Discuss modernising your live financial platform with FiftyFive's engineers.

Book a call

Project snapshot

Industry
Fintech — wealth management technology
Region
Nordics
Services
Custom software development, QA and testing, cloud deployment
Team
4 FiftyFive engineers alongside the client's tech lead
Duration
April 2023 to date
Status
Ongoing, in production
Core technologies
PHP, Node.js, TypeScript, Python, MariaDB, React, Redux, Google Cloud