Home

Stori Bank

Stori had just finished a rebrand but the product was still stuck in the old world. I came in to fix that. Over two months, I built their design system from scratch. The architecture, every component, the rules, the documentation. All of it, so 15+ designers could finally work from the same foundation.

Client:

Stori Bank

Role:

Design system lead

Timeline:

2 months

Team:

5 designers (Replica) + 15 designers (Stori)

The brand was ready. Product wasn't

Stori had just gone through a rebrand. New logo, new colors, new typography, new visual language. But the product was still running on the old design, and the team had no shared system to build with. Every designer worked in silos, same patterns designed differently across teams, scattered across files nobody owned. The brief was two things at once: bring the new brand into the product, and build a system that keeps everyone aligned.

Old designs (When every screen looked like a different app)

New branding (Not bad, right?)

One system for every product Stori builds

Stori wasn't one product. Stori Card, Cuenta+, and more were either live or on the way. Each one needed its own look and feel, but the components underneath had to stay the same. The challenge was building a foundation flexible enough to support all of them without rebuilding anything every time a new product launches. On top of that, the dev teams used specific native libraries for Android and iOS, so every design decision had to account for what could actually ship.

Before any component, the architecture

Before touching any component, I built the layer everything sits on. Spacing scale, corner radius system, typography, and a color system designed to work across every product Stori ships.

The key decision was making the entire system variable-based. Switch one token set and every component, color, icon, and illustration changes from Stori Card to Cuenta+ to whatever comes next. Designers don't rebuild. They switch context and keep working.

What 2 months of building looks like

The full component library. Inputs, buttons, navigation, cards, modals, chat, notifications, progress indicators, native elements. Every component covers all states and works across every brand theme.

But components alone don't solve anything. I documented every one of them with usage rules, do's and don'ts, spacing specs, and card hierarchies. The point was simple: any of the 15+ designers on Stori's side should be able to pick up a component and use it correctly without asking me or anyone else.

Component documentation (So nobody has to ask how to use it)

3.7+ million people use this every day

This is the product after the redesign. Onboarding, home, credit management, savings, payments. Every screen built from the system, every interaction consistent across products. Nothing custom, nothing one-off. Just the system doing its job.