Almond Fintech
Borderless Financial Technology For Everyone
TL;DR
We redesigned a fintech platform for three distinct user types — clients, agents and admins — inside a single coherent system. A project pivot from mobile-first to desktop-first exposed better design decisions than the original brief would have.
Sending money across borders
We overhauled the full design system deliberately, working across five months with a parallel development handoff. Building new components from scratch would have delayed the flows that actually needed to ship.
We worked in Figma with a shared component library, running weekly reviews with the project manager to keep stakeholder alignment tight.
The biggest inflection point came when stakeholders redirected the team from mobile-first to desktop-first — a pivot that required us to restructure several flows we had already refined.
The mobile-to-desktop pivot forced better decisions than the original brief would have
When stakeholders shifted priorities to desktop-first, the instinct was to treat it as a setback.
Instead, it exposed a real gap: our mobile-first flows had been optimizing for simplicity at the cost of the power features agents and admins needed.
The desktop canvas gave us room to surface those features without cluttering the client experience. We rebuilt the interaction and reporting flows for desktop first, then adapted back to mobile — which produced a more honest hierarchy than our original approach.
The bounce rate on the transfer initiation flow dropped 5% after the restructured flows went to development.
Early wireframes
Desktop build
Results
+6%
Engagement
+6%
Downloads
+5%
Customer retention
These numbers reflect something simple: when users find an interface that matches how they think, they stay.
Adapted to mobile
Reflection
What this project taught us.
The mobile-to-desktop pivot was the best thing that happened to this project. Constraints that feel like setbacks often expose assumptions worth challenging.
User segmentation is obvious in hindsight, but most fintech platforms skip it — they build for the average user and expect everyone else to adapt.
We would push harder for role-specific usability testing rather than testing with a general user group. Our research was strong, but a dedicated agent testing session would have caught the reporting hierarchy gaps earlier.
Next we'd want to instrument the post-launch flows to see whether the retention lift was driven by the onboarding redesign or the transfer flow — that distinction would shape where UX investment goes.
Have a project in mind?
Let's talk about what we can build together.