Work

About Me

Contact

← Lead Management System / Module 02
01 / COMPULSORY LIFE INSURANCE RENEWALS

Compulsory Life InsuranceRenewals.

From a file passed between people to a connected renewal system.

A renewal journey for managing 1,000+ companies each month through a structured status model and live updates from the external government insurance platform ().

ROLESolo Product Designer
MODULE2 of 5
SCALE1,000+ companies monthly
CONTEXTEnterprise CRM, company renewals
LAUNCHEDTBC
DEPENDENCY REMOVEDREQUEST MONTHLY EXCEL FILEOPEN CURRENT PORTFOLIO
ADD RENEWALS INTERFACE
02 / THE DEPENDENCY

The system of record was a file someone had to send.

More than 1,000 companies were renewed each month, but representatives could not see their own portfolios directly. Someone first had to export the latest file from the external government insurance platform () and send it to them.

1,000+COMPANIES RENEWED MONTHLY

  1. STATUS LIVES IN

    Renewal information existed outside the LMS.

  2. MONTHLY EXPORT

    Someone downloaded the latest Excel file.

  3. MANUAL HANDOFF

    The file was sent to representatives.

  4. PORTFOLIO SEARCH

    Each representative found their assigned companies.

  5. OUTDATED VIEW

    By the time the file arrived, it could already be out of date.

03 / THE STATUS MODEL

Give renewal work a controlled language.

I analyzed the existing Excel file, ran card sorting sessions with sales representatives, then validated the model through interviews and focus groups. The goal was not to capture every variation. It was to define only the statuses needed to move a renewal forward.

  1. 01EXISTING EXCEL FILE

    I mapped the terms and working patterns already used by the team.

  2. 02CARD SORTING SESSIONS

    Sales representatives grouped how they understood and described renewal work.

  3. 03INTERVIEWS + FOCUS GROUPS

    I validated the shared meaning and boundaries of the proposed model.

  4. 04STRUCTURED STATUS MODEL

    The validated structure became a controlled set of renewal statuses inside the LMS.

THE RISK

Every exception could become another status.

THE DESIGN DECISION

I kept the model deliberately limited to prevent status bloat.

The result was a shared structure representatives could use consistently, not a list of every possible scenario.

04 / THE INTEGRATION

Let status updates arrive without being chased.

Working with developers and IT, we connected the LMS to the external government insurance platform (). Status updates could now reach the renewal record directly instead of requiring representatives to repeatedly log in and check each company manually.

BEFORE
MANUAL LOGINFIND THE COMPANYCHECK THE STATUS

Representatives had to leave the LMS and check company statuses manually.

CONNECTED
STATUS UPDATESYSTEM CONNECTIONLMS RENEWAL RECORD

The latest available status became visible inside the renewal workflow.

CROSS-FUNCTIONAL DELIVERY
PRODUCT DESIGN + DEVELOPERS + IT

The workflow and the external platform connection were delivered as one product change.

Representatives could see the latest available status inside the LMS without manually checking .

05 / THE COMPANY RECORD

Keep the renewal around one company record.

I brought the supporting renewal work into the company profile so representatives could assign responsibility, check company debt, continue from the existing history and manage the people involved without rebuilding context elsewhere.

THE COMPANY PROFILE

One record carried the renewal and its surrounding context.

Ownership, financial context, history and contacts remained connected to the company.

  1. 01
    OWNERSHIP

    Assign renewals between sales representatives and customer service.

  2. 02
    COMPANY DEBT

    Check company debt within the renewal context.

  3. 03
    LEAD HISTORY

    See the full lead history inside the company profile.

  4. 04
    COMPANY CONTACTS

    Manage human resources, finance and executive contacts in one place.

    FINANCE
ONE COMPANY · ONE CONTEXT

The renewal could move between people without losing its history.

06 / CONNECTED OUTCOME

Replace dependency with direct visibility.

Representatives gained direct, self-serve access to their own renewal portfolios. Asking colleagues to download and send the monthly spreadsheet was removed from the journey entirely.

BEFORE

ASK FOR THE FILE

CONTACT A COLLEAGUEWAIT FOR THE EXPORTSEARCH THE SPREADSHEET

Portfolio access depended on another person.

CONNECTED SYSTEM

OPEN YOUR PORTFOLIO

ENTER THE LMSVIEW ASSIGNED COMPANIESCONTINUE THE RENEWAL

Portfolio access became direct and self-serve.

DEPENDENCY REMOVED

Representatives no longer needed another person to access their monthly portfolios.

The LMS became the shared place to see ownership, renewal status and company context.
ACCESSFile sent by a colleagueSelf-serve portfolio visibility
STATUSManual external checkingUpdates visible inside the LMS
CONTEXTRenewal information spread across toolsOne connected company record
NEXT MODULE03 / 05Individual Life Insurance RenewalsVIEW NEXT MODULE ↗

LET’S CONNECT

Now I’d like to hear from you.

Whether it’s a role, a project, or just a conversation, I’d love to hear from you.

Nigu.

Doha, Qatar

nigudesigns@gmail.com

Linkedin ↗