Skip to content

Financial Services

One platform where advisors used to run six

One platform for client records, portfolio performance, advisor messaging and onboarding, replacing six systems that each held part of the answer.

  • Web and mobile on one API
  • 13 platforms integrated
  • Live data, not nightly batch
Book a 30-min call

At a glance

Client
Fynancial
Industry
Financial Services
Engagement
Dedicated full-stack engineering team
Services
SaaS Development, Software Development, Mobile App Development, Web Development, Cloud Development
Fynancial

Fynancial gives independent financial advisors one place to manage client relationships, track portfolio performance and stay in contact with the people whose money they look after.

The situation

What the business was running before

An advisor's working day ran across separate systems that had never been introduced to each other. The CRM held the relationship, a portfolio tool held the holdings, a reporting platform held performance, and the actual conversation with the client happened in inboxes, on calls and by text — recorded nowhere in particular.

None of those tools were wrong. The trouble sat in the space where they failed to meet: the same client existed in four places, in four slightly different versions, and keeping those versions in agreement was somebody's manual job. Fynancial wanted one platform that advisors could work inside all day, with the other systems feeding it rather than competing with it.

The constraints

What was in the way

These are the conditions the design had to survive. They are on the page because a study with no obstacles in it tells you nothing about how the team behaves when something goes wrong.

  1. Six systems, one client, four versions of the truth

    Advisors moved between a CRM, a portfolio tool, a reporting platform and a planning tool. Each held part of the client record, none held all of it, and reconciling them was manual work that nobody had time for.

  2. The conversation lived outside the system

    Clients were reached by email, by call and by text, and none of it was attached to the record. When an advisor left or an account changed hands, the relationship history did not transfer with it.

  3. A unified view had to be assembled by hand

    Investment, performance and client data sat behind different third-party APIs with different shapes and different refresh behavior. Producing one picture of a client meant pulling from several places and hoping they agreed.

  4. Onboarding was paper, and it was the first impression

    New clients arrived through typed-in details, printed forms and a CRM updated by hand afterward — slow, easy to get wrong, and the first thing a new client saw of a firm that manages their money.

  5. Every new advisor multiplied the problem

    Adding an advisor meant provisioning them across several platforms separately. Every hire made the data harder to keep consistent, clean and covered for compliance.

What we built

The system that replaced it

  • One platform for the whole relationship

    Client management, messaging, portfolio tracking, performance reporting and onboarding in a single application — so an advisor stops switching tabs to answer a question about their own client.

  • Advisor web app and client mobile app

    The advisor works at a desk in a Next.js workstation; the client carries a React Native app; both talk to the same backend API. One set of business rules, two front ends, no divergence.

  • A live investment dashboard

    Allocations, performance trends, holdings and transactions aggregated across accounts and custodians, with drill-down to the underlying positions — current, rather than as of last night's export.

  • A communication hub attached to the record

    Messaging between advisors, teams and clients, and every thread can be searched from the client it concerns. The relationship history stays with the firm when the advisor changes.

  • Onboarding as a connected flow

    A digital flow wired to the CRM that captures client data, collects documents, opens accounts and sends the welcome sequence, with progress visible to the advisor while it runs.

  • An integration layer built to be extended

    Standard API contracts, incoming webhooks and Kafka streams, so the next custodian or CRM is a connector someone adds rather than a project someone scopes.

How we worked

The order we did it in

  1. We sat with advisors before we designed anything

    Workshops with practicing advisors mapped the actual working day — which screens they lived in, where they re-typed the same thing twice, and which integrations were genuinely load-bearing rather than merely present.

  2. Event-driven, because the data has several owners

    A microservice architecture with Kafka pipelines, so an update in a custodian or CRM propagates through the platform as it happens. Aggregating from a dozen sources on request would have made every screen as slow as its slowest provider.

  3. Integration-first, not integration-later

    Integration contracts and the API that carries them were designed at the start rather than bolted on once the product worked. On a platform whose job is to unify other systems, that layer is the product, and retrofitting it is the expensive version.

  4. Web and mobile built in parallel, not in sequence

    The Next.js advisor workstation and the React Native client app were built at the same time against the same API. Building one and then the other is how feature parity quietly disappears and how the two apps start telling clients different things.

Built with

  • ASP.NET Zero
  • C#
  • Python
  • Next.js
  • React Native
  • Kafka
  • SQL Server
  • PostgreSQL
  • MongoDB
  • AWS

What changed

What the business can do now

What the business can do since the new system went live.

  • Advisors work in one place

    The client record, the holdings, the performance history and the conversation now sit on the same screen. The reconciliation work between systems — the part that was somebody's manual job — is no longer a job.

  • Onboarding is a flow, not a folder

    A new client is captured, documented, opened and welcomed through one connected process. The advisor can see where it has got to without calling operations to ask.

  • Adding a platform is a connector, not a rebuild

    New custodians, CRMs and compliance tools attach through the existing integration layer. The architecture that made the first 13 possible is what makes the next one routine.

Questions

Questions about this build

Running something that looks like this?

Tell us which systems are disagreeing with each other. That conversation usually tells us within half an hour whether the answer is integration, replacement, or leaving it alone.

Book a 30-min call

Published Nov 3, 2026