Claims operations, end to end, on one system.
Built for claims adjusting and investigation firms and for the carriers who hire them. From opening a claim through settlement and billing, across several legal entities, including the document generation that takes most of an adjuster's day.
Active cases
3,218
+4.2%
Awaiting approval
23
−11%
Days per case
47
−22%
Billed this month
$8.5M
+6.1%
Efficiency by adjuster
| Adjuster 1 | 34 claims | Monterrey | 94% | |
| Adjuster 2 | 29 claims | Guadalajara | 88% | |
| Adjuster 3 | 31 claims | CDMX | 71% | |
| Adjuster 4 | 22 claims | Mérida | 58% | |
| Adjuster 5 | 18 claims | Chihuahua | 46% |
Case load by office
- CDMX82
- Monterrey71
- Guadalajara64
- Mérida43
- Chihuahua31
- Occidente26
Claims processed for the market's major carriers.
These carriers are clients of the firms whose claims work runs on the platform. The system underneath is the one we built.
What it handles today.
- Claims processed per year
- 24,500+Claims processed per year
- Concurrent users
- 300+Concurrent users
- Legal entities on one system
- 28Legal entities on one system
- Carriers served
- 24+Carriers served
Figures from the deployment running now, not a capacity estimate.
Built for the firms doing the work.
Claims adjusting and investigation firms
Independent firms hired by carriers to investigate, document and settle claims, especially those operating as several legal entities.
Insurers with in-house adjusting
Carriers running their own field operation who need the same lifecycle discipline without replacing a core policy system to get it.
Groups with several legal entities
Each office keeps its own tracking and each entity invoices separately, so knowing how the whole group is doing ends up as manual work at month end.
What it replaced.
A claims operation is split across tools that each do part of the job and none of it together. We replaced them across 28 companies running more than 24,500 claims a year between them.
- 01SmartSheet for tracking and dashboardsRetired
- 02Excel workbooks with 93 fields per caseRetired
- 03Word templates for every letter and settlementRetired
- 04Email threads as the system of recordRetired
- 05Shared drives organized by conventionRetired
- 06One person's memoryRetired
Every legal entity, every office, and one place a case lives.
What it does today, in production.
Nine pieces a firm uses every day, running inside the same system.
Multi-entity architecture
Every case, office, template and invoice belongs to a legal entity, and every query is scoped accordingly.
Staged case lifecycle
Each stage carries its own rules about who can act and what must be recorded. Status is the case's position in it.
Governed document generation
Letters, reports and the full adjustment file, generated from each carrier's own template, with its format and letterhead.
Correspondence in the case record
Carrier email and WhatsApp attached to the case, where the next person to open it will find them.
Role-based access
Each role sees only the cases and offices it is entitled to, and the system enforces it on every query.
Reserves, settlement and billing
Reserves, settlement agreements, invoicing under the right entity's tax identity, and collections tracked to closure.
Fraud and irregularity review
Flags and review steps inside the workflow, so a questionable case is caught before a payment goes out.
Dashboards by role
Executive, operational, financial and catastrophic-event views, each scoped to what the viewer is entitled to see.
Search and archive
Every closed case comes back whole years later, with its documents and its correspondence, the day someone asks.
Collecting from the insured, without leaving the case.
The adjuster writes inside the case and sends it, by email from their own mailbox or WhatsApp as a pre-approved template. Replies and attachments return by conversation thread and file themselves against the case.
Hover or select any step to see what the system does at that point.
One page per stage, and the stage is the status.
Moving a case forward means completing a stage, so status stays accurate without anyone maintaining it.
Intake
The case is opened with the insured, the policy, the carrier, the loss type and the line of business. From that moment it cannot be deleted: only closed, and with a written reason.
Capture once. The report assembles itself.
No separate write-up at the end. The document builds from what the stages already captured, in the carrier's own format.
Step through how the report is produced.
Adjustment report
- Reference
- [ empty ]
- Insured party
- [ empty ]
- Policy
- [ empty ]
- Loss type
- [ empty ]
- Amount claimed
- [ empty ]
- Amount determined
- [ empty ]
Template
The carrier's own format: their letterhead, their sections, their required fields. Empty, waiting for a case.
Where your data lives, and who can reach it.
Claims files hold medical reports, financial records and personal data belonging to people who never chose to deal with us. That shapes where the system runs.
Your environment or ours
Deploy it inside infrastructure you own and we operate it without ever holding your data. Where you would rather we host, each deployment is isolated.
Access is scoped, not trusted
Scoping is enforced at the query level, so a user cannot reach a case outside their entitlement even by URL. Administrative access requires multi-factor authentication.
Encrypted at rest and in transit
Managed keys under annual rotation, every connection encrypted end to end, and credentials in a managed secret store rather than configuration files.
Monitored continuously
Threat detection, posture monitoring, a web application firewall and vulnerability scanning, with high and critical findings alerting a named person.
Secure development, enforced by the pipeline
Static analysis on every pull request, a dependency audit that fails the build on any high or critical advisory, and weekly dynamic scanning.
Auditable after the fact
Privileged actions and document access go to an append-only log, so when a carrier or a court asks months later who opened a file, the answer exists.
We hand over all the evidence a carrier asks for, with every control documented, and a named contact for vulnerability disclosure.