The CRM is an internal enterprise platform designed to help multiple teams manage prospects, leads, follow-ups, assignments, customer interactions and operational activities from a centralized workspace.
As HealthSy's operations expanded, multiple teams became involved at different stages of the customer journey. The CRM needed to create a shared source of operational information while allowing each team to work according to its responsibilities.
How might we build one scalable system that supports multiple teams, different responsibilities, complex workflows and large amounts of operational data without making the experience overwhelming?
The product had to be established from the ground up. I began by understanding the system behind the interface before defining individual screens.
The CRM was designed for a multi-role environment. Different users interact with the same underlying information but have different priorities, responsibilities and available actions.
This created a predictable relationship between where users are, what they are looking at and what they can do.
A central UX problem was representing the movement of prospects through the CRM.
Instead of treating every prospect as an isolated record, the experience was organized around lifecycle stages.
The goal was not to create a completely separate product for every team. The underlying system remains shared, while the experience surfaces the information and actions relevant to each responsibility.
The dashboard was designed to answer this practical question. Information was organized around operational relevance rather than simply displaying every available metric.
CRM users work heavily with structured information, so tables were treated as a primary working environment rather than a passive data display.
The record-detail experience brings together the information required to understand and act on a prospect without repeatedly switching between unrelated screens.
Because several teams interact with prospects, ownership is a critical part of the experience. The interface was designed to make responsibility visible and reduce ambiguity around who should act next.
I established consistent feedback and recovery patterns across the CRM.
The product contains multiple teams, workflows, permissions, records, statuses and actions. The design principle was simple:
Complexity should exist in the system, not in the user's mental model.
Because the product was built from scratch, reusable UI foundations were established alongside the product experience.
The CRM was designed as a product foundation, not a collection of one-off screens. Decisions around components, navigation, tables, filtering and role-based experiences were made with future modules and growing operational complexity in mind.
The design process moved from understanding the business to making the product implementation-ready.
Interactive prototypes were used to validate important workflows before development. The focus was on comprehension and task completion: could users understand where they were, find the right prospect, identify ownership, understand status and perform the next action without confusion?
My role extended beyond creating Figma screens.
I worked with development to make the product implementation-ready.
The product was shaped by a set of principles that balanced enterprise complexity with everyday usability.
The result was a from-scratch CRM foundation for HealthSy's internal teams, bringing multiple workflows into a structured digital workspace.
Designing the CRM reinforced that enterprise UX is less about making individual screens beautiful and more about making complex systems understandable.
Building a CRM from zero for a multi-team healthcare organization.
A complex internal platform designed to bring prospects, teams, workflows, ownership and operational data into one scalable workspace.