Case study 02 / Independent project

From forwarded files to the next follow-up.

An AI-powered WhatsApp CRM built around an insurance advisor’s actual workflow.

Role

Product & engineering

When

May–Aug 2026

Routine client servicing~45 minutes → ~2 minutes

01 / The problem

InsureFlow AI

Insurance servicing involves a lot of small, connected tasks: receive a file, find the customer, extract policy details, organize the document, and remember the next action. A useful product needs to address that whole workflow.

Inside the system01 / 04

The work arrived in WhatsApp.

Client documents, policy information, and follow-ups needed to become organized records an advisor could act on.

Simplified flow · based on the project summary

WORKFLOW / 02
  1. 01Forwarded files
  2. 0220+ KYC / policy fields
  3. 03Customer matching
  4. 04Documents & follow-ups
Conceptual sequenceNo live data

03 / What I changed

The intervention.

  1. 01

    Built an AI-powered CRM around WhatsApp for insurance advisors.

  2. 02

    Automated extraction of 20+ KYC and policy fields, customer matching, and document filing from forwarded files.

  3. 03

    Surfaced renewals, payment dues, pending documents, and follow-ups to advisors.

The engineering considerations

Extracted text becomes useful only when it is connected to the right customer and the right action. Ambiguous documents and incorrect matches are important risks in this kind of workflow. No extraction-accuracy percentage or autonomous decision-making claim is made here.

04 / The result

~45 minutes → ~2 minutes

Routine client servicing was reduced from approximately 45 minutes to approximately two. This is a workflow outcome, not an extraction-accuracy score or a promise that every document can be processed without review.

Reported project outcomes from my résumé. Diagrams are simplified explanations, not production topology or benchmark telemetry.