Integrated data platform: one design language for a financial player
Separate systems, separate logins, dashboards nobody opened. How we built one integrated data platform with role-based access and one design language.

For a market leader in the financial sector, we built an integrated data platform. Separate applications, dashboards and data sources came together behind the same access rules and the same interface. The client remains anonymous. Unfortunately, the problem is anything but unique.
Our client had a digital landscape that had grown apart over the years. Every application had its own interface, its own login and its own data source. We brought that together in one platform with one design language. Even so, this was not a job of a few weeks, but a programme in phases.
The project in brief
- Client
- A market leader in the financial sector (anonymous).
- Sector
- Financial services.
- What we did
- UX/UI design, web application development, a design system and the data and AI work.
- Technology
- Figma, React, C++, Azure and Power BI.
What was wrong with the existing systems?
They were disconnected, and that cost money and usage. Every application had its own interface, its own login and its own way of naming things. As a result, staff had to relearn where everything was in each system. And management meant doing the same work in several places.

There was also something I often see at organisations with a strong analytics team. Analysts built dashboards that were hardly ever opened. That had nothing to do with their quality. The people who needed the dashboards simply couldn't access them or couldn't find them.
To me, that may be the most painful part. The work has been done, the insights are ready, and still nobody makes a decision with them. That is not an analytics problem. It is a problem of access and interface.
Why did we choose an integrated data platform?
Because separate solutions only move the problem. Another application or another dashboard just makes the landscape more crowded. So we chose one platform with one set of access rules and one shared design system. That way, every application feels like part of the same whole.
My view: integration doesn't start with technology, but with how people work. That is why we didn't start by building. We started by researching how staff actually use the existing systems. It sounds slow, but it saves you a rebuild later.
Wondering whether custom software was the right choice here? On our blog you can read more about custom software or an off-the-shelf package. For this project, the existing infrastructure weighed heavily, and that calls for integration rather than replacement.
Do you also have applications that work past each other? We build web applications that connect to your existing systems and identities.
See web application developmentHow did we build it?
In seven phases: UX research, UX design, UI design, a design system, frontend, backend and finally launch with ongoing support. That last phase is still running, because we support the platform to this day. Each phase delivered something that made the next one concrete.

Where did the research start?
We analysed how staff actually use the existing systems. We also talked to stakeholders about their goals. That gave us a picture of where time was being lost and which information people were missing.
How did we design the user journeys?
Based on that research, we designed user journeys and wireframes. Above all, they remove the main bottlenecks and align the interactions across the applications. Only then did the UI design follow, also in Figma.
How do the frontend and backend work?
The designs became responsive interfaces in React. On the back end, we integrated the new systems with the existing infrastructure on Azure. We use C++ for the heavier processing, and the dashboards run in Power BI. Security, scalability and the performance requirements of the financial sector ran through the entire programme.
How does access to data work?
It is role-based, linked to the existing Microsoft identities. Staff see the data that belongs to their role and user ID. So they don't need separate accounts or separate permission lists.

But it is more than a security measure. Because access is automatically right, fund managers and decision-makers can go straight to the dashboards the analytics team builds. The same choice solves two problems at once.
What does the design look like?
At its core is a shared design system: one set of components, colours, typography and patterns that recurs in every application. First of all, that speeds up design and development. Above all, it means a user who knows one application immediately understands the next.
I see a design system as a shared language. Without it, every system calls the same thing something different, and staff have to keep translating. With it, that translation work disappears, for users and developers alike.
What does an integrated data platform deliver?
The organisation names three outcomes of bringing everything together: lower operating costs, higher adoption and better decision-making. These are not measured figures. They are what changed in day-to-day work, and I think it is more honest to present them that way.
Lower costs, because there is one managed environment instead of separate systems. That means less duplicate management, less integration work and less maintenance. Higher adoption, because anyone who knows one application also understands the next. And better decision-making, because dashboards finally reach the people who make decisions with them.
Another example of an overview on top of existing systems is our AI agents overview for a retail organisation. There too, the existing systems stayed in place and a layer was added on top.
Want to find out first where your data gets stuck? Tell us which systems you use now, and we'll look together at where the gains are.
Book an intro callUpdated
Get in touch with us directly. We'll get back to you as soon as we can


Your message goes straight to our team in Amsterdam.Who built this data platform?
Your Tech Club. We did the user research, the UX/UI design, the shared design system and the development of the web applications. We integrated those with the client's existing infrastructure.
What did Your Tech Club build for this organisation?
One integrated data platform where separate applications, dashboards and data sources come together behind the same access rules and the same interface, with a design system used across all applications.
What technology does the platform run on?
React on the front end and Azure on the back end, with C++ for the heavier processing and Power BI for the dashboards. The design was worked out in Figma.
How do you set up role-based access to sensitive financial data?
By linking access to the identities the organisation already uses, in this case Microsoft accounts. Roles and user IDs determine which datasets and dashboards are visible. So there is no separate permissions administration to maintain.
Why do dashboards so often go unused?
Usually because they are hard to find, or because the people who need them can't access them. That is an access and interface problem, not an analytics problem. Link access to roles and put dashboards in the same environment as the rest of the work, and that barrier disappears.

