claimOS vs Xactimate: What Public Adjusters Actually Use Day-to-Day

Tuesday morning, Houston. A public adjuster has four files on her desk. The Xactimate estimate for the Galveston roof is due to the carrier by 5 p.m. The Bellaire water file needs a moisture map attached and a supplement letter drafted. The Pearland fire file is waiting on a sworn proof. The Spring hailstorm intake came in overnight — call the homeowner, pull NOAA, schedule the inspection. Xactimate handles one of those four jobs.

That gap is the whole comparison. Xactimate is the estimating software the industry has standardized on; depending on which trade survey you read, somewhere between 75% and 80% of property adjusters use it to write line-item scopes. claimOS is an operating system for the file the estimate sits inside. The two are not competing for the same hour of the day. They are competing for two different hours, and most public adjusters end up paying for both because there is no honest substitute for either.

What Xactimate is, and what it isn't

Xactimate, owned by Verisk since the 2014 acquisition of Xactware, is a line-item estimating engine. The user opens a sketch, drops walls, windows, and slopes, and the software generates a priced estimate against Verisk's reconstruction pricing database. Pricing updates monthly; the database covers most North American zip codes. Xactimate Pro adds Sketch AR with LiDAR for direct-to-sketch measurement, XactScope for guided estimating, and XactAI for line-item suggestions and photo labeling. The tool is good at what it does. A roofer or public adjuster who knows Xactimate can produce a clean, defensible scope estimate that the carrier's desk adjuster will recognize.

XactAnalysis is the companion product, and the two get conflated. XactAnalysis is a carrier-side claim assignment and workflow platform. Carriers route assignments to staff and independent adjusters through it; those adjusters write estimates in Xactimate and submit back through XactAnalysis. Public adjusters work the policyholder side of the file and do not receive carrier assignments through XactAnalysis. That single fact is the source of half the confusion in any comparison conversation: when a carrier's adjuster says “send it through Xact,” they mean the XactAnalysis review queue, which a public adjuster does not have an account on.

Xactimate's 2026 subscription runs about $100/month on annual billing or $149/month month-to-month per seat, with one active login at a time. A team of five with two estimators sits at $2,400 to $3,500 a year on the estimating tool alone. That number is worth holding next to whatever the team spends on the parallel stack — CRM, file storage, e-sign, document drafting — because the parallel stack is where the rest of this post is going.

The seven things a public adjuster does that Xactimate cannot

A claim file is more than the estimate. Walk through a Tuesday on a live file and the estimate sits in roughly one hour out of eight. The other seven hours run on documents, correspondence, photos, deadlines, and a homeowner who calls every other day. Xactimate is not built for any of that, and the trade publications are honest about it — adjusters who try to make Xactimate the file system end up with a file no one can defend.

Intake is first. A FNOL phone call captures policy number, loss description, date and address of loss, homeowner availability, and referral source. That record is the spine of every later artifact. Xactimate has no FNOL screen. Most teams handle intake on a CRM, a Google Form, or a notepad, and the fragility of that handoff shows up in week twelve when the inspection notes do not match the loss description the carrier received.

Evidence is second. A water file needs a moisture map, a drying log, equipment lists, plumber reports, and dated photographs. A hail file needs slope-by-slope chalked test squares, soft-metal photos, and an attic decking pass. Xactimate stores photos against a sketch, but they do not carry across files, do not group by peril, and do not surface as searchable evidence later. The evidence library lives on Dropbox or Google Drive in most teams. That is where evidence gets lost.

Carrier correspondence is third. A serious public adjuster sends a letter of representation, three or four supplement letters, a sworn proof of loss, a demand letter when the prompt-pay clock lapses, and a Civil Remedy Notice in Florida if the carrier blows the statute. Drafting from scratch is how a small team loses a Friday. Drafting from a prior letter is how a team produces an LOR with the wrong claim number on it.

Statutory deadlines are fourth. Texas § 542.058 carries 18% statutory interest plus attorneys' fees once the prompt-pay clock blows past acceptance. Florida § 627.70131 — the post-SB 2-A version — runs 60 days from notice of loss for residential property; the Civil Remedy Notice starts a 60-day cure window before bad-faith suit. California 10 CCR § 2695.7 sits at 40 calendar days from proof of loss with 30-day status updates. Louisiana R.S. § 22:1892 imposes up to a 50% penalty when delay is arbitrary, capricious, or without probable cause. None of these clocks live in Xactimate. Most teams track them on a spreadsheet, which means they track them until somebody forgets.

Depreciation recovery is fifth. Xactimate calculates ACV and withheld depreciation; it does not track which line items were repaired, which invoices came in, or which depreciation has been triggered for recovery. Files that close on ACV and never come back for the recoverable piece are the single most common money- left-on-the-table pattern in this industry. Closeout is sixth — a structured file holding policy, scope, evidence, correspondence, and signed releases under one slug, ready to hand a referring attorney or sister firm. Client communication is seventh — the homeowner-facing portal that shows status, signed documents, and the next move.

Those seven jobs eat the week. A team running them on Xactimate plus a spreadsheet plus Dropbox plus DocuSign plus QuickBooks is paying for five tools and getting a file that none of them owns. That is the competition claimOS is actually in.

The capability matrix

The honest comparison is feature-by-feature. Most rows are non-overlapping — Xactimate does line items and sketch, claimOS does the file around the line items.

The honest read. Xactimate is the estimating tool; claimOS is the file the estimate sits inside. A public adjuster team ships better work running both than running either one alone. The comparison most teams should be making is not Xactimate vs claimOS; it is whether the parallel stack — CRM, Dropbox, DocuSign, the deadline spreadsheet — is the right home for everything that is not the estimate.

Where the criticism of Xactimate actually lands

Pricing is the loudest complaint, and it is fair. Xactimate's reconstruction database is updated monthly against a contractor survey, and the prices reflect the median of what the survey reports. United Policyholders has documented that median regional pricing under-prices custom homes, historic properties, and high-value markets. The Property Insurance Coverage Law Blog has flagged Section 12.3 of Xactimate's end-user license, where the company itself disclaims pricing accuracy. The practical answer on a custom or high-value file is to write the Xactimate scope as the floor and supplement it with a licensed contractor's independent estimate. The carrier's adjuster recognizes the Xactimate format; the contractor estimate carries the burden of actual cost.

Workflow ownership is the quieter complaint. Xactimate was carrier infrastructure before Verisk bought Xactware in 2014, and Verisk sells data products to the same carriers. The estimate math is not biased, but the assumptions baked into the price list, depreciation defaults, and standard line items reflect a carrier-friendly midpoint. A public adjuster producing a file of record on claimOS — photos, moisture map, contractor report, statute-cited deadline calendar, sworn proof drafted from the actual evidence — makes the rest of the file argue for the scope. That is the leverage Xactimate alone does not produce.

What this looks like on a Tuesday

Back to the four files on the desk. The Galveston roof estimate gets written in Xactimate the way it always has — slopes, soft metals, drip edge, code upgrades. That estimate exports as a PDF and an ESX, and both attach to the Galveston file inside claimOS. The Bellaire water file gets the moisture map photographed, the plumber report uploaded, and a supplement letter drafted from the existing scope. The Pearland fire file produces a sworn proof with the inventory and the ALE ledger filled in from the line items. The Spring intake becomes a new claim record, with NOAA pulled to the date of loss and an inspection on the calendar. Xactimate did one thing well. claimOS did the other six. See how the file sits on the public adjuster surface, and how the rest of the estimating-tool comparison stacks up on the best public adjuster software comparison.

Frequently asked questions