NexaPortal CRM — Enterprise Health Tourism SaaS

The Challenge

Health tourism operations are operationally complex: international patient leads, multilingual communication, package management, clinic coordination, payment tracking, follow-up scheduling, and case documentation — all running simultaneously, often across 50+ active cases per operator.

NexaPortal Group needed a CRM purpose-built for this context — not adapted from a generic Salesforce template, but designed from the ground up for how health tourism businesses actually work.

My Role

Co-Founder & Head of Product, responsible for:

• User research with clinic operators and coordinators
• UX architecture and interaction design
• Design system creation (components, tokens, documentation)
• Engineering collaboration and developer handoff
• Product roadmap definition

Led design across a 12-person cross-functional team (engineers, designers, operations, marketing).

The Work

Research

Interviewed clinic operators and patient coordinators at 6 Turkish health tourism companies. Key pain points:

• Lead loss: 30–40% of inbound inquiries never received a follow-up within 48 hours
• Status opacity: No single source of truth for case status; operators maintained personal spreadsheets
• Package complexity: Multi-item packages (surgery + hotel + transfer + follow-up) were managed across 4+ disconnected tools
• Multilingual friction: Communication with patients in EN/RU/FA/AR required manual translation at every touchpoint

Design System First

Rather than designing pages in isolation, I began with a complete design system:

• Token architecture: Color, spacing, typography, shadow, and border radius tokens in Figma
• Component library: 60+ components covering all UI states (empty, loading, error, success, partial data)
• Documentation: Usage guidelines and do/don't examples for every component
• Developer handoff: Auto-layout structures designed for direct CSS translation

Result: 35% reduction in design-to-development handoff time. Engineers could implement components without design review loops.

Key Design Decisions

Pipeline view as primary navigation: The core of the CRM is a kanban-style pipeline (Lead → Qualified → Package Sent → Confirmed → Pre-Op → Post-Op → Closed). Each card shows: patient name, procedure, days in stage, and next action due. One view, full team alignment.

Smart follow-up system: Automated follow-up reminders keyed to stage duration. A lead in "Package Sent" for 5 days without response gets flagged automatically. Human oversight, system-initiated.

Unified patient profile: All patient data — communications, documents, appointments, payments, and case notes — in a single timeline view. Eliminates the 4-tool problem.

Multilingual messaging: Built-in translation assistance for outbound patient communications in 4 languages, with review-before-send workflow.

Outcomes

What I Learned

Enterprise SaaS design is about reducing cognitive load in high-pressure operational environments. The operators using this system were handling 50+ active cases simultaneously. Every interface decision had to serve someone under pressure, not someone with time to explore.

The design system investment paid off most during rapid iteration — when a business requirement changed mid-sprint, the component library meant we could adapt without rebuilding.