ANKIT YADAV

04 · Enterprise Platform

Live in production

Insurance CRM and Claims Platform

Motor claims CRM with six portals, plus claim and medical-policy flows. Accounting alignment with the core system runs on a scheduled job, and the UI is covered with Playwright and Vitest.

Role
End-to-end owner
Scope
Claims portals, policy flows, jobs, tests
Stack
React, Next.js, MUI

Client details are confidential. No client data is shown.

Insurance CRM and Claims Platform04 · SYNTHETIC EXAMPLEOpen12Review7Approved4Settled9Sample counts · role: staff
Administration path: a frontend, an API with authentication and roles, customer policy and claims services, and MongoDB.FrontendAPI + RBACServicesCustomersPoliciesClaimsMongoDB
Administration path: a frontend, an API with authentication and roles, customer policy and claims services, and MongoDB.

Overview

I owned delivery of the insurance CRM. It is a Next.js 15 and React application with MUI and Redux Toolkit, backed by Node.js and Express. The motor claims lifecycle runs across six portals: staff, garage, loss adjuster, contractor, finance, and broker. I also implemented three claim flows and the medical-policy flows in the same product.

The problem

A claim is not one screen. The garage, the loss adjuster, the contractor, finance, and the broker each see a different slice, and those slices have to describe the same claim. Core accounting has to agree with the CRM after the claim moves. A menu that shows every action to every role is how the wrong desk edits the wrong record.

What I built

  • The CRM interface and the API behind the claims lifecycle.
  • The six portals, each with the work that role actually does.
  • Three claim flows and the medical-policy flows.
  • CASL menus so a role sees its own actions.
  • An Agenda.js job that keeps CRM figures aligned with core accounting.
  • Playwright end-to-end tests and Vitest on the claims path.
  • Component work from the design files, including four-language interface copy: English, Arabic, Hindi, and Gujarati.

Architecture

The browser talks to the Node API. Role checks happen before a portal action. Claim and policy services write MongoDB. The scheduled job reconciles CRM state with core accounting. Socket.IO is used where a desk needs the record to move without a refresh.

Diagram

Key engineering decisions

One claim, six portals, instead of six applications. The role system is CASL on the menus and checks on the API, so hiding a button is not the only control.

Accounting alignment is a job with retries, not a step the user has to remember at the end of a status change.

Hard problems and how I solved them

The same claim is edited by people who should not share a screen. The portals split the work, and CASL plus API checks split the permissions.

CRM totals and core accounting drifted. The Agenda.js job keeps that alignment on a schedule.

Regressions across a long claims path. Playwright and Vitest cover the path that used to be checked by hand.

Reliability and failure handling

The accounting job can retry. Role checks sit on the API. The test suite is what makes a change to one portal less likely to break another.

Outcome

The CRM is in production for motor claims across those six desks, with the medical-policy flows in the same application.

Stack

React, Next.js 15, MUI, Redux Toolkit, Node.js, Express.js, MongoDB, CASL, Agenda.js, Playwright, Vitest.

What I would improve next

A published map of claim states per portal, so a new desk can see which transitions it owns without reading the API.

Client details are confidential. No client data is shown.