How Fluida accelerated its acquisition through a scalable design system across four products

Fluida is an HR Tech startup that simplifies the relationship between workers and companies. They offer an ecosystem of mobile and desktop products for workforce management, including attendance tracking, leave management, and employee communication tools.

Fluida had an ecosystem of mobile and desktop products with several applications to manage. The challenge was creating a unique and scalable design library that could work across all of them. Without a unified system, inconsistencies slowed down development and made it harder to ship features across products.

— Build a cross-platform design system that works mobile-first but scales to desktop

— Ensure visual and interaction consistency across 4+ products

— Reduce design and development time for new features

— Support easy integration with IoT devices like the Fluida Station

The design system accelerated development cycles, reduced inconsistencies, and fostered collaboration across teams. By adopting the multi-brand design system, Fluida maintained visual harmony, reinforcing brand identity and creating a seamless user experience across all its products. Fluida was acquired after 15 months of collaboration.

Discovery and audit
We started by mapping Fluida's existing product ecosystem. We identified patterns, inconsistencies, and shared elements across their mobile and desktop applications. This gave us a clear picture of what the design system needed to cover.

Design system architecture
We created "Wave," a cross-platform design system built mobile-first from the ground up. We considered the unique challenges of smaller screens first, then scaled components for larger devices. The system was designed to maintain consistency across multiple products and integrate with IoT devices.

Component design and documentation
We designed and documented 40+ components and 10+ patterns. Each component was built to be reusable across Fluida's product suite. Documentation ensured that multiple teams could adopt the system independently.

Governance and adoption
We ran 40+ governance meetings with 5+ teams involved. These sessions ensured alignment, handled edge cases, and drove adoption across the organization. The process kept all teams on the same page as the system evolved.

The project deliverables included:

— Cross-platform design system ("Wave")

— 40+ components documented

— 10+ patterns defined

— Component documentation for self-service adoption

— IoT device integration guidelines

— 100+ features impacted across 4+ products

Cross-platform complexity
Designing a system that works across mobile, desktop, and IoT devices while maintaining a cohesive experience required careful consideration of each platform's constraints.

Multi-team coordination
Coordinating 5+ teams to adopt a shared design language meant balancing different workflows, priorities, and technical requirements.

Mobile-first scalability
Building components that scale from mobile to desktop without losing the mobile-first philosophy required thoughtful architecture decisions at every level.

Mobile-first design system
We built "Wave" as a mobile-first design system, engineered to prioritize and excel on mobile devices before scaling to desktop. This approach ensured the best possible experience on the platform where most users interacted.

Governance process
Established a structured governance process with regular meetings to drive alignment across teams. These sessions handled edge cases, resolved conflicts, and kept adoption on track.

Multi-brand consistency
The design features of Fluida allow for easy integration with IoT devices, such as the Fluida Station. The software and interfaces are highly scalable, offering a seamless and smooth interaction, adapting to the specific needs of different devices.

Before the design system, Fluida's product ecosystem lacked a shared design language. Each product had its own UI patterns, which led to inconsistencies and slowed development. Teams spent significant time rebuilding components for each new feature, and IoT device integrations required custom design work every time.

After implementing Wave, all products share a unified, mobile-first design system with 40+ documented components and 10+ patterns. Development cycles accelerated, inconsistencies disappeared, and 5+ teams now work from the same foundation. The system scales seamlessly from mobile to desktop to IoT devices, and Fluida was acquired after 15 months of collaboration.