SaaS · Mobile
DigiPro
DigiPro is an insurance platform where agents file and track claims and run field inspections from mobile, while the carrier manages the whole operation from a web dashboard.
Overview
Insurance operations moved off paper and phone calls — claims filed with photo evidence from the field, inspections captured on site, and one dashboard the carrier runs the business from.
The challenge
Insurance carriers ran claims and inspections on paper and over the phone. An agent visiting a site captured evidence on a personal phone, wrote the report later from memory, and mailed or emailed it in. The office had no view of what was in progress, evidence arrived detached from the claim it belonged to, and reporting meant reconciling records by hand.
The solution
One system spanning the field and the office: mobile apps for agents on iOS and Android, a web dashboard for the carrier, and backend services shared by both. Claims are filed from the phone with photo and video evidence attached at the point of capture, inspections are recorded on site, and the dashboard gives the office a live view of the pipeline instead of a mailbox.
What we delivered
- Owned the React Native apps for iOS and Android, including on-device media capture and annotation
- Built the REST APIs backing claims, inspections, media, reporting, and client operations
- Built the React admin dashboard covering claim review, inspection records, and reporting
- Modelled claim and inspection data in MongoDB across differing insurance product requirements
- Worked directly with stakeholders to turn insurance business rules into product behaviour
Architecture
Agent mobile apps (React Native, iOS & Android) ─┐
├─→ REST APIs (Node.js) → MongoDB
Carrier web dashboard (React) ─┘ │
└─→ Media storage (photos, video, annotations)Key engineering decisions
- React Native for the agent apps — one codebase covering iOS and Android, which mattered because agents were on whatever device they already carried rather than a standardised fleet.
- Media captured and annotated on the device, attached to the claim or inspection before upload, so evidence stays bound to its record instead of arriving as loose files to be matched up later.
- MongoDB for claim and inspection records — insurance products differed enough in their required fields that a rigid schema would have meant a migration per product line.
Tech stack
Engagement
2018 – 2019 · Full-Stack Engineer
Results
Delivered a scalable insurance platform that digitised claims processing, field inspections, and insurance management, improving operational efficiency, reporting accuracy, and the experience for both agents and clients.
Lessons learned
- Field software is judged on the worst connection it meets, not the best. Capture and annotation happening on the device — before anything is uploaded — is what let agents finish a claim at a site with no usable signal and sync when they got back.
Have a hard problem like this?
Let's talk about what you're building.