DigiPro

The challenge

Carriers ran claims and inspections on paper and over the phone. An agent captured evidence on a personal phone, wrote the report later from memory, and mailed or emailed it in. The office could not see what was in progress, photos arrived detached from the claim they belonged to, and reporting meant reconciling records by hand.

Collaboration

I engineered the product end to end and worked directly with stakeholders to turn insurance business rules into product behaviour. Agents lived in the mobile apps. The carrier lived in the dashboard. I owned both, plus the APIs between them, and took claims and inspections from paper and phone calls to a system the office could run.

From discovery to production

• Agent apps on iOS and Android for filing, documenting, and tracking claims
• Photo and video evidence captured and annotated on the device, attached to the claim before upload
• Field inspections: capture, annotation, and report submission on site
• The carrier dashboard for claim review, inspection records, and day-to-day operations
• REST APIs for claims, inspections, media, reporting, and client operations
• A MongoDB model that could vary by insurance product without a migration for every product line

How it was solved

Agent apps and the carrier dashboard share one Node.js REST API and MongoDB. Photos, video, and annotations are captured on the device and attached to the claim or inspection before upload, so evidence cannot arrive as loose files to be matched up later. That also lets an agent finish a claim on a site with no usable signal and sync when they are back. MongoDB holds the records because insurance products differed enough in their fields that a rigid schema would have meant a migration per product line.

Key technical decisions

• 01React Native so iOS and Android were one codebase. Agents used the phones they already carried, not a standard fleet.
• 02Capture and annotation on the device, attached to the record before upload, so evidence stays bound to the claim.
• 03MongoDB for claim and inspection records, because product lines did not share one fixed set of fields.

Screenshots

Impact

• Agents file and track claims from the phone, with evidence attached at the site.
• The office sees the pipeline in the dashboard instead of reconstructing it from a mailbox.
• Reporting no longer depends on matching loose photos to a claim after the fact.
• The product covered differing insurance lines without a schema migration for each one.