Column · @gregorycwxl099
The Workflow Shift Behind the New Wave of Restoration Estimating Tools
Compact notes on what actually changed. The new wave of ai estimating software for restoration is not mainly about AI. It is about where the estimate gets written and who writes the first draft.
Example used throughout: Axiom. If you want to look at the tool itself, start with this platform. These notes stay on the workflow.
Old workflow
field: photos + sketch + notes -> office: estimator reads everything -> estimator re-keys rooms + line items in Xactimate -> submit -> carrier PDF comes back -> estimator re-keys carrier PDF to compare -> supplementBottleneck: the estimator is the author of every line, every time.
New workflow
field: photos + measurements + floor plan + notes -> software builds room-by-room draft (.esx) -> estimator reviews + answers questions + approves -> submit -> carrier PDF -> converted to ESX -> carrier vs contractor compared line by line -> supplementShift: the estimator becomes the reviewer of a draft, not the author of a blank file.
What moved, piece by piece
- Inputs: same things crews already collect. Photos by upload, drag-and-drop, iOS app, or CompanyCam / Google Drive / DocuSketch link. Measurements via 3D scan, existing ESX, 2D PDF, or typed rooms. Hand sketch photo -> editable floor plan.
- Draft: organised by room with Xactimate codes, line items, editable quantities. Drawn from patterns across thousands of real claims.
- Output: native .esx, opens directly in Xactimate, reprices on your price list. Not a PDF, not a portal.
- Gaps: scope assistant asks a question when photos don't settle an item. No guessing.
- After submission: PDF to Xactimate (PDF -> ESX) and Compare (carrier vs contractor, line by line).
What did NOT move
- Accountability. Draft only. Nothing final until an estimator approves room by room.
- Platform. Xactimate is still where the estimate lives. Background: Verisk Xactimate.
- Standards. Drying and scope still justified against IICRC practice (S500 for water).
- Carrier rules. Programs and TPAs still set their own guidelines.
Why ai estimating software changes staffing math
- Old: more volume = more estimators typing.
- New: more volume = more drafts to review. Review replaces authoring, but it is still real work and needs a named owner.
- Unlimited users, no per-seat fees on Axiom plans (at the time of writing, October 2026), so adding reviewers or field users does not change cost.
Where the category sits
Neutral map, not a ranking:
- Documentation / capture: DocuSketch, Encircle, magicplan.
- Human estimating as a service: offered by some documentation platforms, e.g. DocuSketch.
- Estimating-focused tools: Axiom, Rebuild, Wave, CapOut, x.build, each with its own approach.
Demo reference
In the walkthrough demo (about six minutes, recorded in the shipped product, July 2026): approx. $8,000 water loss, generation quoted about two minutes, took a little over one minute, 33 line items, then the ESX opened in Xactimate. One demo. Not a benchmark.
Pricing reference (at the time of writing, October 2026)
- Starter $899/mo: 15 estimates, 15 PDF conversions, 15 comparisons.
- Pro $2,500/mo: 50 estimates, unlimited conversions and comparisons.
- Enterprise: custom.
- One free PDF-to-ESX conversion for new accounts.
Adoption notes
- Pilot on closed jobs first. Compare drafts to what you billed.
- Track which scope questions repeat. Fix field capture habits.
- Write the "estimator approves every room" rule into your SOP.
Common objections, short answers
- "It will guess." It asks a question when photos don't settle an item.
- "I'll have to re-key it." Output is a native ESX, so no.
- "It only does mitigation." Job types include mitigation, put-back and exterior.
- "What's the accuracy?" No general rate is published. Test it on your own jobs.
One-line summary
The shift behind ai estimating software is from estimator-as-typist to estimator-as-reviewer, with the file staying in Xactimate the whole time.