Case /

Nemuru

Designing a Scalable, White-Label Admin for Fintech

Client

Nemuru

Role

UI/UX Designer

Tags

UX, UI, Product Design, Design System, SaaS, Admin Panel

Duration

4 Years

Overview

Nemuru, a Fintech company in the lending space, needed a consistent and scalable Design System to power its growing B2C product suite — including a consumer-facing app and an internal admin panel. The system also needed to support white-label theming for banks and large brand clients like Iberia and Tesla.

Outcomes

Enabled scalable product development

Designed a white-label design system allowing multiple partners to customise branding while maintaining a shared product framework.

Financing infrastructure embedded into checkout flows

Designed payment widgets integrated into retailer checkout experiences, enabling businesses to offer split-payment financing to customers.

Supported platform growth and partnerships

Contributed to the product experience of a fintech platform that partnered with major banks and companies in Spain, including Iberia · Tesla · Ávoris · CaixaBank.

Goals & UX Drivers

  • Build a robust and reusable Design System from scratch

  • Ensure branding flexibility to support white-label clients

  • Improve UI consistency and visual hierarchy across touchpoints

  • Document and systematize component usage for both design and development teams


Enabled scalable product development

Designed a white-label design system allowing multiple partners to customise branding while maintaining a shared product framework.

Research & UX Considerations

  • Audited existing UI for inconsistency and misaligned components

  • Interviewed stakeholders (internal team + external partners) to identify gaps in usability and flexibility

  • Prioritized accessibility and clear UI patterns for fintech use cases (loan forms, financial status, error states)

System Architecture & UI Design

“We approached the design system like a product — built from primitives, abstracted through tokens, and documented with examples.”

  • Defined foundations: color tokens, spacing, typography scales, elevation levels

  • Crafted atomic components: buttons, inputs, cards, modals — with light/dark & brand variants

  • Designed patterns: loan application flows, status tracking, multi-step forms, dashboards

  • Supported white-label overrides via a clear branding layer

Cross-Team Collaboration

  • Worked closely with devs to ensure design-to-code parity via Storybook

  • Created Figma documentation and usage guidelines for scalable onboarding

  • Iterated with product team on edge cases and responsive behaviors

UI Design System Process

Designing the Nemuru system wasn’t just about creating a branded interface — it was about crafting a flexible, future-proof foundation for multiple products and brands. I approached the system as a modular framework.

  1. Foundations: Design Tokens and Primitives

I started by defining the core foundations:

  • Color tokens for brand, neutral, semantic (success, error, info), and states (hover, active, disabled)

  • Spacing scale using 4px increments (4–64px) to ensure consistent rhythm

  • Typography system including sizes, weights, and responsive behavior

  • Elevation and radius tokens to distinguish surfaces across app and dashboard contexts

These primitives formed the base for a tokenized design system, making it easy to apply brand overrides for white-label clients like Iberia and Tesla.

  1. Component Library: Atomic to Complex

Built a scalable library in Figma with atomic components:

  • Buttons (primary, secondary, ghost, destructive)

  • Inputs, dropdowns, date pickers with validation/error states

  • Cards, modals, banners

  • Progress steps, tables, badges for admin panels

All components were designed with:

  • Variants for size, state, and brand

  • Auto layout and responsive rules to adapt across breakpoints

  • Naming conventions and documentation for developer handoff via Storybook

Example: The loan application card was reused across 3 apps, each skinned with a different brand palette but maintaining structure and logic.

  1. White-Label Support

From the beginning, the system was designed to support white-label theming:

  • Used theme tokens to isolate brand elements: colors, logo containers, font overrides

  • Developed a theme switcher demo to show how components adapt across clients

  • Ensured all UI retained accessibility and contrast across light/dark modes and client themes


  1. Patterns for Fintech UX

Crafted page-level patterns for fintech-specific needs:

  • Multi-step loan applications with progress feedback and form autosave

  • Status dashboards with contextual states (e.g. “awaiting bank approval”)

  • Error handling and fallback messaging for key user actions

These patterns prioritized clarity, trust, and speed — essential values in the fintech space.

Conclusion

This project taught me how to scale design not just across screens, but across brands and teams. Creating a white-label-ready admin panel to visualize a large ammount of financial data.
The design system pushed me to think modularly, anticipate edge cases, and advocate for scalable logic.