Designing a financial platform for individuals, arbitrage teams and businesses — from a fragmented MVP to a consistent product for payments, virtual cards and accounts.

Designing a financial platform for individuals, arbitrage teams and businesses — from a fragmented MVP to a consistent product for payments, virtual cards and accounts.

Team

Product Manager, Developers

Product Manager, Developers

Timeline

10 months, part-time

10 months, part-time

Role

UI/UX Designer: research, flows, UI, design system, dev handoff

UI/UX Designer: research, flows, UI, design system, dev handoff

01. Project Overview

I joined a fintech MVP at an early stage and helped turn it into a product people use to manage their money every day.

At its core, the platform works like an online bank built around virtual cards: users open accounts, top them up, pay and transfer money. They can pick a ready-made card from the showcase or create a custom card for their own tasks, and each card comes with its own payment and usage conditions.

On top of that sit the features that make it a full financial product: analytics, deposits and credit applications.

I owned UX/UI decisions across existing and new functionality, working part-time for 10 months side by side with the product manager and developers. Release scope was always aligned with the PM.

At its core, the platform works like an online bank built around virtual cards: users open accounts, top them up, pay and transfer money. They can pick a ready-made card from the showcase or create a custom card for their own tasks, and each card comes with its own payment and usage conditions.

On top of that sit the features that make it a full financial product: analytics, deposits and credit applications.

I owned UX/UI decisions across existing and new functionality, working part-time for 10 months side by side with the product manager and developers. Release scope was always aligned with the PM.

02. Challenge

The MVP worked, but every new feature made it harder to use, because there was no shared structure to build on.

I started with a UX/UI audit. It showed broken navigation, usability problems across the main flows, inconsistent UI and a messy design system. That was expected at the first MVP stage, but it had to be fixed before the product could grow.

The task then got bigger: keep the experience consistent while the product became more complex. Cards, accounts and users had different configurations, conditions and permissions, and everything had to work on web and mobile, in English and Russian.

I started with a UX/UI audit. It showed broken navigation, usability problems across the main flows, inconsistent UI and a messy design system. That was expected at the first MVP stage, but it had to be fixed before the product could grow.

The task then got bigger: keep the experience consistent while the product became more complex. Cards, accounts and users had different configurations, conditions and permissions, and everything had to work on web and mobile, in English and Russian.

03. Approach

I fixed the foundation first, then let user feedback and the client’s tasks shape what we built next.
  • Order first. Fixed navigation, the most painful UX issues and the UI, rebuilt the design system.

  • Grow with real users. The product was already live. Feedback from first users, combined with the client’s tasks, guided each new feature.

  • Clear ownership. UX/UI decisions were mine. The functionality and scope for each release were aligned with the PM, and I stayed in close contact with developers.

  • Web and mobile together. Every screen was designed for both, in two languages.

  • Order first. Fixed navigation, the most painful UX issues and the UI, rebuilt the design system.

  • Grow with real users. The product was already live. Feedback from first users, combined with the client’s tasks, guided each new feature.

  • Clear ownership. UX/UI decisions were mine. The functionality and scope for each release were aligned with the PM, and I stayed in close contact with developers.

  • Web and mobile together. Every screen was designed for both, in two languages.

04. Design Decisions

Bank-like money flows

Solution: Flows for top-ups and transfers between cards, accounts and users, including crypto. The structure follows what users know from online banks, and a shared set of components keeps every operation clear, though flows differ by operation type.

Why: Familiar patterns keep money movement fast, simple and clear.

Solution: Flows for top-ups and transfers between cards, accounts and users, including crypto. The structure follows what users know from online banks, and a shared set of components keeps every operation clear, though flows differ by operation type.

Why: Familiar patterns keep money movement fast, simple and clear.

Ready-made and custom virtual cards

Solution: A showcase of ready-made cards for different needs, and a separate flow for creating custom virtual cards.

Why: Every card has its own payment and usage conditions, so people choose or build the one that fits their task.

Solution: A showcase of ready-made cards for different needs, and a separate flow for creating custom virtual cards.

Why: Every card has its own payment and usage conditions, so people choose or build the one that fits their task.

Analytics by cards, accounts, employees

Solution: A large analytics section: income and expenses, active and closed cards, expense structure, transactions, and the dynamics of top-ups, spending and balances. It covers all accounts or selected ones, by card or by employee. The hard part was keeping dense data readable, especially on mobile.

Why: Users can follow trends and channels of spending and top-ups at every level.

Solution: A large analytics section: income and expenses, active and closed cards, expense structure, transactions, and the dynamics of top-ups, spending and balances. It covers all accounts or selected ones, by card or by employee. The hard part was keeping dense data readable, especially on mobile.

Why: Users can follow trends and channels of spending and top-ups at every level.

Team accounts for managers

Solution: A separate account type for managers: they create a team and give employees access to specific cards and accounts for work, with their own permissions and analytics views.

Why: It fits arbitrage teams, where a manager decides who can use which cards.

Solution: A separate account type for managers: they create a team and give employees access to specific cards and accounts for work, with their own permissions and analytics views.

Why: It fits arbitrage teams, where a manager decides who can use which cards.

Improving a live MVP while the product kept growing.

Instead of a one-time redesign, I fixed the existing experience and its UI patterns in parallel with new features. That meant balancing quick usability fixes with consistency and reusability in a product that was still changing.

Instead of a one-time redesign, I fixed the existing experience and its UI patterns in parallel with new features. That meant balancing quick usability fixes with consistency and reusability in a product that was still changing.

Mockup image

05. Results

Over 10 months the platform grew from a handful of early users into a live product with a growing audience and a much wider set of tools.

Exact figures are confidential, so here is each signal we followed and where it went:

  • Real users: the number of active users kept growing after launch.

  • Money turnover: the volume of money moving through the platform increased noticeably.

  • Trust and adoption: users showed growing interest in the full range of tools, not only cards: analytics, deposits and credit applications.

  • Product scope: six product areas designed and released, all on one consistent system for web and mobile, in two languages.

Growth like this cannot be credited to design alone. My contribution was UX/UI improvements to the existing MVP, new financial workflows, and the structure and continued development of the design system.

Over 10 months the platform grew from a handful of early users into a live product with a growing audience and a much wider set of tools.

Exact figures are confidential, so here is each signal we followed and where it went:

  • Real users: the number of active users kept growing after launch.

  • Money turnover: the volume of money moving through the platform increased noticeably.

  • Trust and adoption: users showed growing interest in the full range of tools, not only cards: analytics, deposits and credit applications.

  • Product scope: six product areas designed and released, all on one consistent system for web and mobile, in two languages.

Growth like this cannot be credited to design alone. My contribution was UX/UI improvements to the existing MVP, new financial workflows, and the structure and continued development of the design system.

0

month of product development

0

functional areas designed and improved