Case Studies Leadership About Process Impact Contact
Concept case study · SaaS · CRM

RelateCRM — Sales Platform

A CRM concept centered on adoption: reduce the clicks around routine selling, make editing immediate, and keep pipeline information clear enough for daily use.

RoleLead Product Designer · Design Systems
IndustryCRM SaaS
Year2022
StatusConcept case study
RelateCRM — Sales Platform — CRM SaaS UX/UI product interface
RelateCRM — Sales PlatformThis is a concept / representative case study. Outcome figures are framed as targets or validation criteria and should not be read as verified client results.
+49%Daily active use
-33%Data entry time
60%Faster design-to-dev
Concept / representative targets. These figures are success criteria, not a claim of verified client performance.

Project overview

A CRM redesigned so daily selling takes fewer clicks — a calm pipeline that teams actually adopt.

A CRM redesigned so daily selling takes fewer clicks — a calm pipeline that teams actually adopt.

The challenge

Sales teams abandoned a powerful CRM because daily tasks took too many clicks.

Powerful CRMs often accumulate interface cost as features grow. When common updates require navigation through multiple views, users work around the system or stop maintaining data. The design problem is therefore task efficiency and hierarchy, not feature count.

The product response

A streamlined pipeline, inline editing, and a calm information hierarchy for speed.

A drag-and-drop pipeline, inline editing, and calmer information architecture keep high-frequency actions close to context. A reusable design system supports consistency as the product expands and helps reduce design-to-development friction.

Edit in contextPrioritize daily tasksCalm dense informationScale through reusable components

Key product decisions

The interface direction is anchored in three concrete product decisions from the case-study scope.

01

Drag-and-drop deal pipeline

Keep sales stage changes direct and visible so the core workflow can be updated without opening secondary forms or losing context.

02

Inline editing everywhere

Allow routine updates where the information already lives, reducing mode switches and repeated navigation during daily work.

03

Calm information hierarchy

Prioritize the fields, statuses, and actions users need most often so dense CRM data remains scannable.

Success criteria & validation targets

This is a concept / representative case study. Outcome figures are framed as targets or validation criteria and should not be read as verified client results.

+49%Daily active use
-33%Data entry time
60%Faster design-to-dev
Concept / representative targets. These figures are success criteria, not a claim of verified client performance.

Tools, stack & product focus

The stack reflects the implementation-aware nature of the work: interface decisions were framed so they could translate into reusable, accessible front-end patterns rather than static presentation only.

FigmaDesign SystemReact
SaaSDashboardUX

What this case study demonstrates

This concept demonstrates enterprise SaaS UX, CRM workflow design, pipeline interactions, inline editing, information hierarchy, design systems, and adoption-focused product thinking.

Explore the full portfolio

Browse the other case studies across fintech, commerce, SaaS, health, education, real estate, and data-rich products.

View all case studies →