Insurance operations · Bangladesh

The operating layer for regulated insurers.

Lance gives Bangladesh's insurers one place to run claims — surveyor dispatch, document chain-of-custody, deadline arithmetic, and IDRA-aligned exports. Every action timestamped. Built around your core insurance system, not against it.

Book a 30-min walkthrough→Talk to us
AllOverdue · 4Today · 1242 open
CLM-24817Motor — Dhaka NorthSurveyor report due · Mahmud Karim−2 days
SLA 14d
CLM-24812Health — ChittagongAwaiting hospital invoice · ext. party1 day
SLA 7d
CLM-24806Property — KhulnaApproval queued · Rashida Ahmed4 days
SLA 10d
CLM-24799Marine — Mongla portDocuments complete · ready to settle6 days
SLA 21d
CLM-24791Motor — SylhetGarage estimate received9 days
SLA 14d
02 · The platform

Four modules. One policy data layer.

Lance is built around a shared, IIMS-compatible policy data layer. Each module sits on the same tenancy, the same audit log, the same exports. You buy one module today; you don't migrate when the next one ships.

Live · pilotM01 · Claims

Lance ClaimsFor insurers

The claims operating system. Surveyor GPS, document chain-of-custody, IDRA quarterly returns generated from the same events your auditor verifies.

  • ·Role-scoped queues for adjusters, surveyors, approvers
  • ·Audit-log architecture designed for immutability, signed exports
  • ·External-party intake — garages, hospitals, surveyors
  • ·SLA arithmetic with regulator-rule pauses
Customer · Insurers
03 · Lance Claims · the lead module

Built around the claim, not the inbox.

Operations, compliance, and leadership stop reconciling spreadsheets. The same claim record drives the queue, the ledger, and the executive board — only the lens changes.

Three roles, one source of truth.

Claims arrive once and follow a defined path. Surveyors, adjusters, and approvers each see what's theirs to do — nothing more, nothing less.

  • →Role-scoped queuesAdjusters see open assignments. Compliance sees policy exceptions. Leadership sees portfolio risk.
  • →Deadline arithmetic, automatedSLA timers honour holidays, regulator rules, and clock pauses for documentation requests.
  • →External parties on the same recordGarages, hospitals and surveyors submit to a secured intake — no email back-and-forth, no lost attachments.
  • →Exports for IDRA, Bangladesh Bank, internal auditQuarterly returns, suspicious-activity packets, board reports — generated, not assembled.
CLM-24817MotorDhaka NorthSLA −2d
DOCSurveyor reportLocked · 14:02 · hash 9f2a…41c1.4 MB
signed
DOCGarage estimateReceived from Continental Auto · awaiting review0.8 MB
verified
NOTEAdjuster notes3 entries · last by r.ahmed at 15:08—
internal
SMSClaimant notificationDelivered to +880 1XX · 14:51OK
logged
SLASettlement deadlineRegulator rule 4.2(b) · paused for documentation−2d
at risk
05 · How a claim moves

From first notice to settled, on a clock everyone can see.

01
Intake · Day 0

One door, every channel.

Branch, broker, agent app, and direct claimant — all routed to a single record with policy match, fraud check, and SLA timer started in under sixty seconds.

Time to record open · target
12 min→52 sec
Year-one target. Measured against insurer's incumbent process at pilot start.
02
Investigation · Day 1–7

Surveyor and documents in the same place.

Surveyors submit reports through a signed intake — GPS-stamped, hash-locked. Garages and hospitals upload invoices to the same record. Internal review never waits on email.

Document chase · target
3.2→0.4
Average follow-up requests per claim. Year-one target.
03
Review & approval · Day 7–10

Approvals match policy, not memory.

Approval limits, four-eyes thresholds, and exception paths are encoded once. Reviewers see exactly what they're authorised to act on.

Exception backlog · target
14d→3d
Median time an exception case sits before resolution.
04
Settle & report · Day 10+

Disbursement, with the receipts attached.

Payment instruction, claimant notification, and the final ledger entry happen on the same record. Quarterly returns generate from the same events your auditor verifies.

Quarterly return prep · target
5 days→2 hrs
From "ask compliance" to "submit to IDRA."
06 · Who it's for

Different desks, the same record.

OperationsAdjusters · Surveyors
A queue ordered by what's at risk, not what's loudest. Deadlines visible by default. Every action — note, document, decision — recorded once and never re-typed.
ComplianceRisk · Internal audit
A continuous, audit-log architecture designed for immutability — ready to hand to a regulator unchanged. Quarterly returns generate, they don't get assembled. Exception evidence is one query away.
LeadershipCEO · COO · Board
A single view across motor, health, property, and marine. Where the portfolio is slipping, by line of business and branch — without waiting for someone to build a deck.
IT & SecurityCISO · Platform
SAML/SSO, role-based access, signed exports, and event-level webhooks. Integrates with your core insurance system, not around it.
Next step

See what's in your audit log this quarter.

A 30-minute working session with your compliance and operations leads. We'll map your current claim flow against IDRA SLAs and show exactly where Lance fills the gaps.

Book a working session→
In the session

What we walk through together.

  • IDRA circular mapping & control matrix
  • Sample audit ledger export (signed)
  • Data-residency & encryption posture (current + Pilot-Trigger)
  • Tenancy & role-based access reference
  • Sandbox dossier extract — BIA conflict review
  • Implementation timeline (6 / 10 / 14 weeks)
Talk to us→