Keep submitting in Xactimate.
Just get smarter at it.
Your adjuster needs an ESX. Your business needs to know what every carrier actually settles for, before you submit, and to learn from every settled response. ClaimNorth is the intelligence layer that sits alongside your Xactimate workflow.
Try the live demo →Build it in ClaimNorth
Scope the loss the way you'd build any estimate. See per-line market signals: "Allstate settles ~91% of ask on Drywall in your region." Adjust before you submit.
Export to ESX, submit through Xactimate
One click exports a clean ESX with photos, room dimensions, depreciation, line items. Open in Xactimate. Submit to your carrier the way you always have. Nothing changes for the adjuster.
Drop the settled ESX back in
When the carrier sends back the settled response, drag the ESX into ClaimNorth. We auto-diff submitted vs settled, anonymize the contractor, and add it to the federated market signal. Next time you scope a similar job, the chip shows up tighter.
The compounding moat
Every ClaimNorth user, by dropping settled ESX files into their projects, makes the federated market signal more accurate for every other ClaimNorth user. Verisk and Xactimate cannot do this because they sell to carriers; we sell to contractors.
- For you: tighter, more confident pricing, fewer adjuster pushbacks, less back-and-forth.
- For the network: "Allstate cuts 9% on drywall in Indiana" becomes ground truth, not guesswork.
- For your adjuster: the same Xactimate-compatible ESX they always get.
× Xactimate alone
- $135/mo per user
- Verisk owns the catalog; their incentive aligns with carriers
- No after-settlement learning loop
- Your firm's experience evaporates between jobs
- Same number every contractor in your zip uses
✓ ClaimNorth Companion
- Flat $99/mo, $0 for ESX export
- Catalog + regional pricing + carrier behavior
- Settled ESX import auto-captures intel
- Federated rates tighten with every job
- Per-carrier intel: "State Farm settles 98% in IN; Allstate 91%"
Companion FAQ
No. ClaimNorth is purpose-built to coexist. Build in either; export ESX; settle in either; learn from both.
The settled prices feed federated_rates_aggregates anonymously — your org_id is hashed with a weekly-rotating SHA-256 salt before storage. Carriers, line-item codes, regions stay; firm identity does not.
Not unless you tell them. The ESX format is the same; no ClaimNorth metadata is embedded by default.
After ~30 settled observations per (category, region, carrier) tuple, confidence reaches 100% and the federated median replaces 60% of the algorithmic price. We're already showing useful signal at 3 observations.