Axiom vs. Rebuild: who is holding the file at the end

Two products, two different deals

Axiom and Rebuild both promise the same outcome: fewer hours between a documented loss and a Xactimate estimate. Both use AI to get there. The difference is what lands at the end and who is holding it. One hands your estimator an editable draft and a native ESX file to import when the team is ready. The other takes the job, finishes it out of sight, and puts the completed file into your Xactimate for you.

This comparison uses two sources: what each company publishes, and a first-hand account of a Rebuild engagement covering what the field team entered, how long delivery took, and how the finished estimate arrived. Every Rebuild claim quoted here comes from its own site as of August 22, 2026.

Neither company is a mystery about what it sells. Read the two rows that matter to your week, ESX delivery and Xactimate access, and most of the decision is already made.

What Rebuild markets

Rebuild's website leads with restoration estimates in seconds, and says an estimate is generated in 90 seconds to two minutes. Its field application takes voice notes, images, documents, 3D scans, and time-and-material information, then asks follow-up questions. Coverage is broad: mitigation, interior and exterior reconstruction, contents, mold, fire, biohazard.

The company says the product standardizes field documentation, identifies missing line items, tailors estimates to a carrier, adds estimating capacity, cuts cycle times, and exports or uploads the result to Xactimate. That is a strong pitch, and the problem it names is real. Estimating is the bottleneck in most shops, and one experienced writer is usually the whole department.

The pitch describes a two-minute, self-service experience. The engagement reviewed for this comparison was not one.

What the evaluated workflow actually did

Onboarding started with a request for the contractor's estimate data. That presumably tunes the recommendations to how the shop writes. Depending on what gets handed over it can include historical estimates, preferred line items, macros, price-list usage, and carrier requirements.

Field personnel then worked inside Rebuild's application: identify damaged materials, record affected dimensions, add scope information, answer job-specific questions, submit the file. After submission the contractor waited roughly three to twelve hours. Rebuild then uploaded the finished ESX directly into the contractor's Xactimate instance, and the contractor could not be working in that instance while the upload ran.

That is not an AI feature living inside the contractor's workflow. It is estimate completion and Xactimate delivery handed to a vendor.

The marketing sells AI speed. The customer experiences a managed handoff.

Ninety seconds of generation is not a turnaround

The 90-second claim most likely describes how long the system takes to generate something once processing begins. That is not the same as a contractor having a usable estimate in 90 seconds. Rebuild's own about page is more conservative than its homepage, putting cycle times at less than a day. The engagement reviewed here ran roughly three to twelve hours from submission to delivery.

None of that proves work is being written by hand, offshore or anywhere else. It proves something narrower and more useful: between submit and upload, the customer cannot see or control the work. Those are the questions worth asking on a demo call.

• What happens during those hours?
• Is the estimate sitting in a queue, or being worked?
• Does a person review it, and does any part get written by hand?
• Are those people employees or outside contractors?
• Why does the vendor upload the ESX instead of sending it to you?
• Why must your team stay out of Xactimate during delivery?
• What happens to that window when catastrophe volume hits?
• How fast do rush files and revisions come back?

Who built each one

Founder background tends to show up in the product, so it is worth reading both. Rebuild's company history says co-founder and CEO Alex Toporek grew up around his father's manufacturing and construction businesses, and that as the family's restoration company grew, its most experienced estimator became the bottleneck. He was building vertical AI companies when he sat with the estimating team and saw the opening. Co-founder John Reim came from construction technology and product.

Rebuild also credits Angelo Ferrante, a construction professional with more than 40 years in the industry, as the estimator who helped define, scope, and test the first version, which the company says was originally called 'Ask Angelo!' So there was real industry input. But the founding experience was AI, product, and construction technology, and the product reflects it: one estimator's knowledge, turned into a standardized process other people can follow.

Axiom started in the operator's seat. Jakeb Shelton spent ten years in restoration and exited a company he built, running crews, carrying losses, and writing the Xactimate. Matthew Gregory has launched several software products for the restoration industry and built the estimating engine, which is trained on real restoration claims rather than a general vision model with a restoration label on it.

That is why the product does not ask you to hand over the estimate. It drafts it, shows the decisions, and gives the file back.

What Axiom does with the same job

Axiom starts from documentation the crew already produces, so nobody has to adopt a new field process to make the software work.

• Jobsite photos, plus the wide and boundary shots that decide accuracy
• Room measurements, and floor plans as ESX, PDF, or a photographed sketch
• EagleView and HOVER roof reports
• Technician notes and loss details
• CompanyCam, Encircle, and DocuSketch share links
• Projects captured in the Axiom field app

The review is the product

Axiom builds a first draft organized by room, and the estimator inspects all of it: rooms, dimensions, affected areas, Xactimate codes, line items, editable quantities. Where the documentation cannot settle a condition, the software asks a room-specific question instead of quietly adding a line item. Nothing is final until the estimator says so.

That is the whole difference in one sentence. Rebuild asks you to submit the job and trust the hours that follow. Axiom puts the draft in front of the person whose name is on the estimate. AI should give an estimator a head start, not remove them from the decision and hide the file until a vendor is ready to place it.

Axiom writes the first draft. Your estimator approves the final scope.

Delivering a file is not the same as touching your Xactimate

A native ESX is not a minor feature, because it decides who controls the last step. When the vendor performs the upload, delivery depends on the vendor's timing and on access to your environment. When the file is handed to you, the last step is yours.

With the file in hand your team can inspect the draft before anything moves, store it with the claim, import it when convenient and into the instance you choose, and apply the correct price list, since Xactimate reprices every line on import against the price list for the job's own area code. You can keep working in Xactimate while other jobs process, and revise or reimport without waiting for a delivery window. A contractor should not have to give up use of its primary estimating system to receive an estimate.

Four workflows, one pool of credits

Photos to a draft is where most teams start, but it is one of four workflows, and every one of them spends from the same pool. PDF to Xactimate converts a finished estimate PDF back into an importable ESX, which removes the retyping when a carrier or adjuster sends only a printout. Compare puts the carrier's estimate next to yours, shows what was left out, and returns a reconciled file with justification notes, the same job some shops build by hand with a general AI tool.

Playbook Scope takes loss details, rooms, and measurements, then recommends line items from your approved estimate history with the reason behind each suggestion. Rebuild covers a wide range of job categories. Axiom covers the different document problems a team hits across one claim, which is why it behaves less like a photo-scoping tool and more like an estimating workspace.

Before you hand any vendor your estimate history

An estimate library is not a neutral file transfer. It can expose preferred line items and macros, how your shop writes, average job values, price-list geography, carrier and TPA relationships, supplement strategy, production volume, and customer and claim details.

None of that is an accusation against anyone. It is a reason to get the answers in writing before the upload rather than after.

• Which files are actually required?
• Is the data used to train a model?
• Is what the system learns about your shop isolated from other customers?
• Which employees or contractors can open the files?
• Are outside estimating resources involved at any step?
• How long is the data retained?
• Can it be permanently deleted on request?
• What happens to it when the account closes?
• Is the company-specific logic exportable if you leave?
• Will the vendor put all of the above in the contract?

The price is public, and so is the whole clock

Axiom publishes its pricing: $150 for a single estimate, falling to $50 each at 25. No subscription, no monthly minimum, no per-seat charge, and estimates do not expire, so putting the whole team on one account costs nothing extra. Accounts are provisioned after a demo, so you will talk to someone either way. The difference is that you can run the math on your own volume first. Rebuild does not publish pricing on the public pages reviewed; the path is a demo request.

When you do compare them, measure the whole loop rather than the advertised generation time. Start the clock when your team starts documenting and stop it when the estimator has a file they would send. A vendor-controlled upload that lands hours later should not be scored against a self-service draft using the vendor's own two-minute number.

Run the same three jobs through both: a well-documented residential mitigation loss, one with missing or contradictory information, and a complex reconstruction or commercial file. Then compare total turnaround, field-entry time, line-item recall, unsupported items, quantity accuracy, room organization, estimator correction time, how the ESX is delivered, Xactimate downtime, revision speed, cost per completed estimate, and total employee hours.

The verdict

Rebuild may suit a contractor who wants estimate completion handled by an outside workflow. The application gives less-experienced field staff a structure for damage notation and dimensions, and standardizing what the field collects has real value.

The tradeoff is the part to weigh honestly. You submit the job, wait a window you cannot see into, depend on the vendor to finish, and hand that vendor the last step inside your own Xactimate. Axiom takes the documentation you already collect, gives back a visible and editable draft, keeps your estimator in the decision, and delivers the native ESX to you. Your team decides when and where it enters Xactimate.

You do not have to take either pitch on faith. Book a demo and bring a job your team already wrote by hand. Run the original documentation through, then open the file next to the estimate you know is right. Do not judge AI estimating by the promise. Judge it by the file.