← All case studies

Case 02 · Enterprise SaaS · FinTech · Swiss Banking

iLoy Suite

Loyalty & CRM Platform

We decomposed a monolithic Swiss banking loyalty platform into five governed modules and a token-based design system — so engineering ships new features with zero design regressions.

Client
iLoy Solutions AG
Location
Lugano, CH
Engagement
Product design & systems

Impact

4

Distinct user roles mapped via task analysis

5

Modules unified under one navigation shell

100s

Unique views governed by a single token system

0

Design regressions on new feature releases

01 / The Challenge

Four user roles. One legacy system straining to serve them all.

A Swiss banking institution's loyalty management platform had grown organically for years. CRM managers, campaign planners, compliance auditors, and configuration admins were forcing four distinct jobs-to-be-done through a single undifferentiated interface.

With hundreds of unique views, visual and behavioural drift was inevitable without a governance layer.

Unified navigation across five modules

02 / Our Approach

Modular architecture, governed by a single token system.

Our team ran stakeholder interviews and task analysis across all four roles before a single screen was drawn. We then architected a modular system — CRM, Campaigns, Promotions, Reports, Configuration — where each module owns its logic while sharing one navigation shell.

We mapped the full system into six operational pillars (Dashboard, CRM, Loyalty, Marketing, Reporting, System), locking Phase 1 scope, dependencies, and priorities such as RFM metrics and dynamic loyalty levels before high-fidelity work began.

The token-based design system became the platform's single source of truth: every new screen inherits correct spacing, colour, and component behaviour by default, not by convention.

CRM workspace
Customer 360 — customer details
Tree-view store management grid
Loyalty Program 360 dashboard
Reporting dashboard builder
Full system architecture map
Design system token reference

03 / Systems Outcome

New features shipped without design regressions.

The platform now runs consistent interaction patterns across every module, regardless of role or which team built the feature.

Engineering ships new functionality on a three-year-old codebase without re-litigating spacing or component behaviour on every pull request.

Capabilities deployed

  • UX Strategy
  • Information Architecture
  • Design Systems
  • CRM
  • B2B SaaS
  • Swiss FinTech

Next case study

iMIC

→

Facing a system this complex?

Book a call

Contact

Ready to untangle your product?

Tell us where the complexity lives. We'll bring the architecture — and a point of view on what to build first.

Prefer email? hello@brndventure.com

No retainers pitched on the first call. Just architecture.