When products grow across teams and regions, inconsistency tends to sneak in like a stowaway. For Eptura, we helped unify a product suite under a scalable design system.
Overview
Eptura is a global workplace management platform serving organizations across facilities, real estate, and asset management. As Eptura's product suite grew — through both organic development and acquisitions — design inconsistency accumulated across teams, regions, and products. Different components, patterns, and visual languages had emerged independently, making it harder for design and development teams to collaborate effectively and harder for users to navigate across products.
SeaLab was brought in to build alignment: one scalable design system, usable across teams, that could serve as a shared foundation without sacrificing the individual needs of each product area.
The Challenge
Design system work at enterprise scale comes with a specific set of problems. It's not just a component library — it's an organizational challenge. Teams have existing patterns they're attached to, timelines that don't pause for systems work, and varying levels of Figma and systems fluency.
The system needed to be rigorous enough to create real consistency, but flexible enough that teams could actually adopt it without ripping out everything they'd already built.
Our Approach
Discovery and audit. We started by auditing the existing component landscape across Eptura's products — cataloging what existed, what was duplicated, what conflicted, and what was missing entirely. This gave us a clear picture of the delta between where things were and where they needed to go.
Token architecture first. Before building a single component, we established a robust design token architecture — color, typography, spacing, and elevation tokens that could flex across products and themes. Getting tokens right from the start is what allows a design system to scale without constant rework.
Component prioritization. Rather than trying to build everything at once, we worked with the Eptura team to prioritize the components with the highest cross-product usage. High-frequency, high-impact components first. Lower-frequency components documented as patterns for teams to self-serve.
Documentation built for real teams. Documentation that sits in a file no one reads is a wasted investment. We built documentation directly in Figma alongside the components — with usage guidance, do/don't examples, and accessibility notes — so that the system was usable without a design systems expert on hand.
Enabling the internal team. A design system is only as good as its adoption. We worked directly with Eptura's internal design and development teams throughout the process — walking through the system, answering questions, and building the internal fluency needed for the system to outlast our engagement.
Results
Eptura now has a unified design system that spans its product suite, with shared patterns, reusable components, and a token architecture built for scale. Design and development teams have a single source of truth. New features can be built faster and with greater consistency. And users experience greater coherence as they move across Eptura's products.
The system set up to scale without sacrificing quality — which is the only kind of design system worth building.
Need to unify a fragmented product suite? Let's talk.