| Primary user | The public adjusting firm running the recovery | Carrier desk adjusters and assignment coordinators routing claims to vendors |
|---|
| Data model | Claim-centric: every record rolls up to the claim file you own | Assignment-centric: a workflow engine that routes claims through carrier-defined queues |
|---|
| Who owns the file | The firm. Your tenant, your data, your export. | The assignment lives inside the carrier system; vendors work the assignment, not the file. |
|---|
| AI copilot | Reads the claim file and drafts demands, supplements, and updates with citations | Workflow automation; not a generative AI claim drafting tool |
|---|
| Document automation | Templates merge claim data into demands, supplements, releases, and packages | Forms and letters scoped to the assignment workflow, not PA correspondence |
|---|
| Estimating integration | Imports Xactimate ESX into the claim file; uses estimate data downstream | Tightly integrated with Xactimate as part of the Xactware platform |
|---|
| Weather evidence | Federal weather data pulled and tagged automatically for the loss date and address | No native federal weather correlation in the assignment workflow |
|---|
| Client portal | Branded portal for the homeowner with status, documents, and signing | Carrier-side claimant communication; no PA-branded client portal |
|---|
| iOS field app | Native iOS capture app with structured photos, voice notes, and signatures | Mobile capture exists for assignment-driven inspections; oriented to carrier workflows |
|---|
| Pricing | Per-seat monthly subscription, no per-claim fee | Carrier-side enterprise contracts; PA firms typically access through assignments, not direct purchase |
|---|