Insurance marketplace, IndiaLive

From retyping policies to ~98% of fields read correctly

A private document engine turns policy PDFs into checked fields on the client's servers. Field accuracy is measured on a hand-verified test set.

Delivered by our founding team at a previous firm. Clients anonymised under NDA.

In brief

What problem needed solving?

Every quote and every policy was retyped from PDFs by hand, twice. A policy arrived on WhatsApp, email or chatbot; ops retyped every field, priced it across four or five insurers, then retyped again to issue. Rule-based tools caught ~12 fields; generic AI hit 83% on ~40 of 180+. Regulators want the data kept in India.

What did the team build?

A private document AI engine on the client's own servers. Six steps on every document: receive, identify the policy type and load its rulebook, mask names and IDs before any model reads it, extract 180+ fields, verify every field against the rules, route failed checks to a person. An open-source model replaced per-call public AI fees.

What changed?

About 98% of fields read correctly on a hand-verified test set. Turnaround 80% faster. Ten to twenty percent more quotes became issued policies. AI cost per document fell 78%. No PII went to public AI. No new hires: the same team moved from typing to reviewing exceptions. Started with motor, now extended to life, health and home.

The impact

~98%
fields read correctly
hand-verified test set
80%
faster turnaround on quotes and policies
client-reported result
+10–20%
more quotes converted into issued policies
client-observed range
78%
lower AI cost per document processed
hand-verified test set

Delivered by our founding team at a previous firm. Clients anonymised under NDA.

The challenge

Every quote and every policy was retyped from PDFs by hand, twice.

  1. PDF arrives
  2. Ops retypes it
  3. Ops prices it
  4. Customer picks
  5. Ops retypes again

The document moves. The personal data stays private.

  1. Policy PDFs

    Receive, identify and mask personal data.

  2. Read & verify

    Extract fields and apply policy rules.

  3. Review exceptions

    Failed checks go to a person.

Live. Delivered by our founding team at a previous firm. Clients anonymised under NDA.

The approach

  1. Receive

    WhatsApp, email, chatbot

  2. Identify

    Identify policy type and load its rulebook

  3. Protect

    Mask names, phones and IDs before any AI reads it

  4. Extract

    Extract 180+ fields

  5. Verify

    Verify every field against format and policy rules

  6. Route

    Route failed checks to a person

Failed checks go to a person.

Clean records land in your system.

What transfers to your insurer

  • Document intake and field extraction for policy, quote and endorsement documents.
  • Masking personal data before any model reads it.
  • Failed checks routed to your team for review.
  • Validate on your data: your document types, your field list and your core systems.

Read next

Bring one problem.

Tell us about one costly process. A founder replies within two working days.

Start with the problem. Agree the right next step together.

For example:

  • a document your team retypes
  • a queue that grows with volume
  • data that can't leave the building