Skip to content
CodeWave Systems
Platform

Case study · Insurance

ClaimTrace

Investigation management for insurance investigators.

Category
SaaS platform
Industry
Insurance
Platforms
Web platform
Technology
Laravel · Vue · Inertia · MySQL

01 · Project overview

What was built, and for whom.

ClaimTrace is a software platform designed for insurance investigation companies to manage investigations, workflows, assignments, reporting and operational processes from one system. Each investigation firm operates in its own tenant; insurers and claim managers are given access to the cases that concern them.

Built for
Insurance investigation companies and their insurer clients
Type
Platform
Platforms
Web platform
Focus
insurance saas web

02 · Business challenge

The problem, as the business experienced it.

Investigation firms tracked cases, assignments and reports across spreadsheets, email and chat, leaving insurers waiting for status and managers without a clear view of workload.

An investigation passes through many hands — intake, assignment, field work, review, report — and every hand-off was a chance for a case to stall or a status to go stale. Insurers chased updates by phone; managers rebuilt the picture from spreadsheets.

  • Case files scattered across spreadsheets, email and chat
  • No live view of workload per investigator
  • Insurers and claim managers chasing updates by phone
  • Reports and investigator payroll compiled by hand

03 · Our approach

How we got from the problem to the system.

A tenant-based platform where investigations move through defined workflows, investigators are assigned and tracked, insurers and claim managers see status directly, and reporting and payroll come from the same data.

  1. 01

    Understand

    We followed real cases from intake to final report to capture the actual workflow, the exceptions and who needed to know what, when.

  2. 02

    Architect

    A multi-tenant model with strict tenant isolation, and a role model covering firm admins, investigators, insurers and claim managers.

  3. 03

    Design

    Workflow boards and unified dashboards were designed around how managers actually allocate and review work.

  4. 04

    Build

    Delivered in increments: investigations and assignments first, then insurer access, reporting, bulk uploads and payroll.

  5. 05

    Integrate

    Notifications, bulk import of claims and AI-assisted fraud analysis were layered onto the core workflow.

  6. 06

    Deploy & support

    Production deployment with monitoring and backups, and continuing support as firms onboard new insurers.

04 · Solution architecture

Layers of the system.

Clients at the top, the core application in the middle, integrations and data underneath. Green marks the integration layer where the system meets the outside world.

05 · Key features

What the system does.

Investigation management

Every case, its documents, timeline and status in one record.

Claims workflows & assignments

Defined stages from intake to report, with investigators assigned and tracked.

Insurer / claim manager access

Clients see the status of their own claims without calling.

AI-assisted fraud analysis

Cases flagged for closer review based on their characteristics.

Tenant-based architecture

Each firm runs in its own isolated tenant on a shared platform.

Reporting, payroll & bulk uploads

Operational reports, investigator payroll and bulk claim import from the same data.

06 · Technology

The stack behind it.

Chosen for the job — mature, supportable and straightforward to host and staff for in Kenya.

Backend
PHP Laravel
Frontend
Vue Inertia Tailwind CSS
Data
MySQL Redis
Analysis
AI-assisted fraud analysis

07 · Business impact

What changed for the business.

Outcomes are described qualitatively. Figures are published only when verified by the client and approved for release.

  1. 01

    Automated operational workflows from intake to report

  2. 02

    Insurers and claim managers see case status without phone calls

  3. 03

    Unified dashboards across all open investigations

  4. 04

    Reporting and payroll derived from completed work, not spreadsheets

08 · Screens

Interface illustration.

A representative illustration of the interface, not a live screenshot — no client data is shown.

Similar problem?

Have a process that looks like this one?

Tell us how it runs today. We will tell you what a system built for your operation would involve.

Start a Conversation
info@codewavesystems.co.ke +254 708 604 940