Skip to content
PlayLab
Dark architectural volume lit by a single warm plane of light

WORK / 007 / 2025

Brainis

Designing an operating system for work.

Industry
AI / SaaS / Productivity
Discipline
Digital Product
Type
AI Platform / Product Ecosystem
Duration
12–16 weeks
Engagement
Multi-phase platform
PlayLab's role
Designed and developed
Status
Live and publicly accessible
Website
brainis.ai
Last verified
10 Aug 2026
Role
Creative Direction, Product Design, UX/UI, Design System, Web Application Design, Development, Product Architecture

Brainis positions itself as an AI-powered operating system for company work.

Instead of treating tasks, revenue, people, finance, marketing and company intelligence as isolated tools, the platform brings multiple operating layers into one AI-driven ecosystem.

The design problem was therefore fundamentally architectural. How do you make an enormous system feel coherent?

The spine

01  /  The brief

Make eight operating domains — work, revenue, people, finance, marketing, intelligence, data and the AI layer connecting them — read as one product.

02  /  The constraint

A system this large cannot be designed screen by screen, and every domain arrived with its own density, vocabulary and idea of a table.

03  /  What we made

  • 1 design system — 9 domains, shared density and hierarchy rules
  • 120+ application screens, desktop and condensed
  • Component library: rows, tables, panels, command surfaces
  • AI interaction patterns embedded in workflow, not bolted on
  • Product architecture and navigation model
  • Front-end build in step with design

04  /  What came of it

Every operating environment now inherits one set of rules, so a new domain ships as a variation rather than a redesign.

01  /  Context

Modern companies work across disconnected software. Task management lives somewhere. CRM somewhere else. Hiring somewhere else. Finance somewhere else. AI assistants sit on top of all of them.

Brainis attempts to connect those operating domains through a shared intelligence layer. The interface needed to communicate the scale of that ambition without looking like a collection of unrelated SaaS dashboards.

Dense structural grid in raking light

02  /  Idea

ONE COMPANY.ONE BRAIN.

The design system treats each operating domain as part of one larger system: work, revenue, people, finance, marketing, business intelligence, data — and the intelligence layer connecting them.

03  /  Experience

A modular visual system allows individual operating environments to retain their purpose while remaining recognizably Brainis.

Information density is managed through hierarchy rather than decoration. Actions remain prominent. Secondary information recedes.

AI is integrated into workflows rather than treated as a floating chatbot added to every screen. The result aims to make a large product ecosystem feel like one coherent operating environment.

Key experience areas

  • Work OS
  • Revenue OS
  • People OS
  • Finance OS
  • Marketing OS
  • Business Intelligence
  • AI Brain / Cortex
  • Data
  • Company-wide navigation
  • Tasks and workflows
Single illuminated surface in a dark volume
Layered translucent planes stacked in depth

04  /  Making

A platform this large cannot be designed page by page. Patterns, relationships, hierarchy and behaviour needed to scale across the entire ecosystem.

We built the system from the smallest decisions upward — density, rhythm, weight, the behaviour of a single row — then let each operating environment inherit them. Design and development ran as one process so the specification and the build never drifted.

Design challenge

Design the system, not the screen.

When everything connects, work stops feeling like a collection of tools.

Credits

Creative Direction
PlayLab
Product Design
PlayLab
Design System
PlayLab
Development
PlayLab
Client
Brainis
Two heavy stone masses meeting along a single lit seam

Next project

Noah Ventures