Scattered information
Customer and lead data lived across different tools and personal records.
An internal platform for managing insurance leads, follow-ups, contract creation, renewals, and sales performance.

Interface built within PASHA LIFE's existing design system.
The LMS brought five distinct journeys into one connected ecosystem. Each followed a different operational process, while sharing the same foundation of lead profiles, statuses, follow-ups, notifications, and activity history.

From first contact to a confirmed policy. Acquiring new customers through lead management, follow-ups, and a Face2Face contract flow simplified from seven steps to three.

Turning a shared spreadsheet into a connected renewal system. Managing high-volume company renewals through a structured status model and live updates from the external government platform.

Renewing existing customers without starting again. Reusing customer and contract data, coordinating confirmation steps, and supporting multiple contracts within one renewal journey.

Defining a sales process where none existed. Transforming an undefined corporate workflow into six clear stages, from initial contact and meeting preparation to proposals and contracts.

Giving managers oversight without micromanagement. Connecting targets, callback responsiveness, and team performance through interactive dashboards designed for progressive exploration.
Lead information lived across Excel files, Power BI dashboards, the old LMS, personal notes, and paper forms. Sales representatives repeatedly entered the same customer information, missed follow-ups, and could not see a reliable history of previous interactions.
Customer and lead data lived across different tools and personal records.
Sales representatives copied the same information between systems or entered it again later.
Previous conversations, contract statuses, and follow-up actions were difficult to trace.
Sales representatives kept explaining the old LMS instead of describing their natural process. I needed to understand its fields, actions, and workarounds before redesigning it.
sessions with sales representatives
Including in-person visits, watching representatives close deals in front of me.
As the five journeys expanded, separate flows began to feel fragmented and I was no longer sure I had the complete picture — that uncertainty is why I pivoted to Object-Oriented UX.
A sales representative could open a lead and see previous calls, meetings, reminders, applications, and contracts before contacting the customer again.
New Individual Sales used a compact lead list with priorities and follow-up actions. The Analytical Module summarized the same lead, contract, and activity data for managers.
Sales representatives gained a consistent place to manage leads, interactions, contracts, and renewals. Managers gained clearer visibility into sales activity and outcomes. The same underlying structure could support five sales journeys without making their interfaces identical.
Across 2.5 years, this meant more than 100 sessions, interviews, and focus groups spread across all five journeys.