Design Systems > Case Study

Design Systems · Enterprise SaaS · Cybersecurity

One design system. Three platforms. 32% faster triage.

Built and shipped the token architecture and component library for CYGNVS, a high-stakes cybersecurity SaaS platform, replacing fragmented UI across web, iOS, and Android with a single source of truth. No full design systems team required.

Role

Design Systems Lead

Duration

14 weeks

Platforms

Web, iOS, Android

Scope

Token architecture, component library, governance

60+

Components

180+

Semantic tokens

3

Platforms (Web, iOS, Android)

-32%

Triage time

+18%

Analyst satisfaction

The problem

Security analysts were switching between web, iOS, and Android views of the same platform, and every switch meant relearning the interface. Buttons, alerts, and status indicators looked and behaved differently depending on which surface they hit.

Engineering was building the same components three times, once per platform, with no shared token layer. Every rebrand, dark mode request, or accessibility fix became a manual, error-prone sweep across three codebases.

If your team is shipping the same button three different ways across your product, this is the exact problem we solved.

Architecture

Token-first. Single source of truth.

Foundation

Raw hex, spacing, type scale

Semantic

--text-primary, --surface-hover

Component

Scoped overrides per platform

Every color, spacing value, and interaction state traces back through three layers: raw hex primitives, semantic aliases, and component-bound tokens. Change one primitive and it propagates correctly across all three platforms, without touching a single component file.

220 tokens across 11 families

220 design tokens across 11 color families. WCAG AA compliant by construction, not retrofitted after launch.

Delivery

Three phases. Fourteen weeks.

01

Audit

Weeks 1-3

Mapped every hardcoded value and inconsistent pattern across the existing web, iOS, and Android codebase. Surfaced exactly where design and engineering had drifted, and what it would cost to leave it unresolved.

02

Build

Weeks 4-10

Designed the three-tier token architecture first, components second. Web, iOS, and Android were built in parallel so no platform fell behind. 60+ components shipped with full variant coverage, interaction states, and documentation.

03

Embed

Weeks 11-14

Handed off a governance model, versioning strategy, and component documentation structured for the engineer searching at 11pm before a deadline, not the team reading it cover to cover. The system outlived the engagement.

Outcome

Triage time dropped 32%. The design system made it possible to ship an AI grouping banner — "12 alerts grouped into 1 incident" — that let analysts work at the incident level instead of chasing individual alerts. That single interaction pattern changed how the entire SOC floor operated.

The 18% increase in analyst satisfaction reflected daily friction removed: fewer support queries about inconsistent UI, faster onboarding for new analysts, and a product that finally felt like one system instead of three bolted together.

A $3.25M ARR platform, shipped consistently across three platforms, governed to scale without the original designer in the room.

About this work

Original interface details are NDA-protected. Token architecture, methodology, and outcomes reflect the actual engagement.

HFI-CUA certified. 15+ years in enterprise SaaS and cybersecurity product design.

Have a similar problem?

Three engagement tiers. Fixed scope. Delivered in weeks, not quarters.