Claims management software

The operating system for the public adjusting firm.

claimOS is built for the team running the recovery, not the carrier paying it. One claim-centric platform connects intake, weather evidence, document automation, AI drafting, e-signature, and the client portal, so a small firm can move like a large one and a large firm can stop fighting its own software.

Built at Insurance Claim Hero, an active public adjusting firm. Used in the field, every day, on real claims.

Why public adjusters end up here.

Most claims software was built for the carrier. The data model assumes a desk adjuster receiving an assignment, working a queue, and closing the file with a payment. The public adjuster sits on the other side of that table. You are reconstructing what was lost, fighting for what is owed, and translating a complicated insurance process into something a homeowner can understand. The tools written for the desk adjuster do not fit your job.

claimOS starts from your job. The first record in the system is the claim, not the contact. Every workflow is shaped around what a public adjusting firm actually does on a Monday morning: triage new losses, organize evidence, draft and send carrier correspondence, manage supplements, keep the client informed, and close the file with a clean record. The same platform supports a single-operator firm and a multi-state team without a different product per tier.

Built for the firm running the recovery, not the carrier paying it

Carrier platforms are designed to control cost from the desk side. claimOS is designed for the public adjuster who has to prove the loss, document it, and recover it. The data model, the AI prompts, and the default reports all start from your job, not theirs.

Claim-centric, not contact-centric

Every record in claimOS hangs off a claim. Contacts, properties, parties, photos, documents, communications, and money all roll up to the file. You do not manage relationships that happen to involve claims; you manage claims that involve relationships.

AI grounded in the file, not generic chat

The copilot does not invent details. It reads the policy, the scope, the timeline, and the photos, then drafts. When it writes a demand, it cites the line item. When it writes a status update, it references the weather report. You stay accountable for what gets sent because you can audit the draft against its sources.

iOS field capture that connects to the office

The field side runs on a native iOS app: structured photo capture, voice notes, scope worksheets, signature collection. Everything syncs back to the claim record automatically, so the adjuster who walks the roof and the operator who builds the package are looking at the same file.

What the platform actually runs.

The list below is not a feature checklist. It is the work claimOS removes from your day.

  1. FNOL to recovery on one timeline

    Capture first notice of loss from a phone call, web form, or referral. Every later artifact (inspection notes, photos, scope worksheets, carrier correspondence, supplements, settlement) writes back to the same claim record. The file you open in week 14 still shows what was true in hour one.

  2. Scope of loss that survives a re-inspection

    Pull federal weather data for the date and address of loss. Tag every photograph and video to a room or elevation. When a carrier desk adjuster pushes back, the evidence is already organized, dated, and addressable; you respond with citations instead of a search.

  3. ROI capture and depreciation recovery

    Track withheld depreciation against a real list of repaired line items. When invoices and proof of completion come in, the system surfaces what is recoverable and drafts the demand. Depreciation that used to slip past 12 months stops slipping.

  4. File of record for every settled claim

    Closeout produces a structured archive: policy, scope, evidence package, carrier correspondence, supplements, payment ledger, and signed releases. If a referring attorney or a sister firm asks for the file later, it exports as one organized package, not a folder of attachments.

  5. Copilot drafting that cites the file

    The AI copilot reads the actual claim, not a generic prompt. Demand letters quote line items from the estimate; status updates reference the specific weather event; supplements call out the photos that justify them. Every paragraph has a source you can click.

What claimOS replaces.

Most firms do not start with greenfield software. They start with a stack: a CRM, a shared drive, an estimating tool, a few inboxes, a task list someone keeps in their head. claimOS replaces the parts of that stack that are doing claims work badly, and integrates with the parts that are doing their own job well.

  • XactAnalysis assignment workflow

    Carrier-side assignment software optimized for desk adjusters. Public adjusters end up duplicating its data into a CRM, a spreadsheet, and a shared drive. claimOS replaces the parallel system.

  • Symbility Claims Connect / ClaimCenter

    Built for the carrier file flow, not the firm running the recovery. Estimating handoffs through Symbility still work; the case management, evidence handling, and client communication move to claimOS.

  • Generic CRMs (HubSpot, Pipedrive, Monday)

    Contact-centric tools that were never built for a claim-centric world. They track relationships well and claims badly. The data model fights you the whole way.

  • Manual stacks: Dropbox plus Gmail plus a shared spreadsheet

    The stack most firms grow into. It works at five claims and breaks at fifty. Files lose context, status lives in someone's head, and recovery slows down every time a teammate is out of office.

Built for public adjusters, not for carriers.

Symbility and the Xactware family (Xactimate, XactAnalysis) are excellent products. They are also carrier products. The defaults are tuned to the desk adjuster, the assignment workflow, and the cost-control reporting that a carrier needs. Public adjusters use those tools because the industry made them universal, not because they fit.

claimOS does not try to compete with Xactimate on estimating. We integrate with it. What we replace is the rest of the stack, the parts where a public adjusting firm is forced to operate inside a system designed for the other side of the table. Intake, evidence, drafting, supplements, client communication, and the file of record all move to a platform designed from your seat.

Honest pricing, no per-claim fees.

claimOS is priced per seat, monthly. There is no per-claim fee, no charge per document, no overage on storage, no separate line item for e-signature or the client portal. The starter tier covers a small firm; the growth tier adds the full automation, integrations, and reporting suite. Most firms know within two weeks whether the platform fits.

Questions firms ask before they buy.

Is claimOS only for public adjusters?
Public adjusting is the primary audience and the lens we design from. The platform is also used by attorneys handling first-party property claims, restoration firms running their own claim teams, and independent adjusters who want a claim-centric system instead of a CRM. The workflow is the same; the configuration changes.
Does claimOS replace Xactimate or Symbility for estimating?
No. Estimating in Xactimate and Symbility still works the way you use it today; claimOS pulls those estimates into the claim file and uses them downstream for demands, supplements, and reporting. Estimators keep their tools.
How does the AI copilot handle confidentiality?
The copilot operates inside your tenant. Documents, photos, and notes are not used to train external models. Outputs are drafts; an operator approves and sends. Every AI suggestion shows the file context it used so you can audit it.
What does onboarding look like for an existing firm?
Most firms onboard in two weeks. We migrate active claims first, set up your templates and signature workflow, train the team in two short sessions, and run a parallel period before you cut over. Insurance Claim Hero, our sister public adjusting firm, runs on the same platform, so the implementation team has actually closed claims on it.
How is claimOS priced?
Per seat, monthly, with a starter tier for small firms and a growth tier for teams that need the full automation suite. There is no per-claim fee, no overage on storage, and no separate charge for e-sign or the client portal. See the pricing page for current numbers.
Where does claimOS sit relative to other public adjuster software?
There are good purpose-built tools in the public adjusting market. claimOS is the most ambitious of them on AI grounding, document automation, and the depth of the connected workflow. Other vendors do parts of this well; few do all of it on one claim-centric platform.

See it working on real claims.

15 minutes. Your actual workflow. No sales theater.

Or email us at hello@claimos.net