Rebuild vs. Restoration360: Which AI Estimate Actually Opens in Xactimate?

If you run a growing restoration company, you’ve probably already heard the pitch: AI can write your estimates now. It’s true. The tools are real, and the speed is real.

But “AI writes your estimate” glosses over the part that decides whether the tool actually saves you time: what lands in Xactimate at the end. A draft you export and then rebuild by hand is not the same thing as a native .esx that opens with the sketch, the rooms, and priced line items already in place.

This is an honest look at two names that come up when operators start shopping for AI estimating: Rebuild and Restoration360. Both use AI. Both produce Xactimate-ready estimates. The difference isn’t the pitch. It’s the file.

The short version

Rebuild is a focused AI estimating tool. You feed it photos, voice notes, and scans, and it drafts an insurance-compliant estimate you can push to Xactimate. If the one thing eating your week is writing estimates, it does that one thing.

Restoration360 makes R360 Scope: software that turns job-site photos into a priced, native Xactimate .esx in minutes. The sketch, the rooms, and the line items open in Xactimate exactly as drafted, and the file reprices on your own price list on import. Your estimator QAs the draft and submits it; the AI does the assembly, not the judgment call.

One drafts an estimate you push toward Xactimate. The other hands you the Xactimate file itself.

Where the two overlap

Credit where it’s due, there’s real common ground, and pretending otherwise would insult your intelligence:

• AI-drafted estimates. Both turn field documentation into a scope in minutes, not an evening.
• Xactimate-ready output. Both produce line items in the format carriers expect.
• Photo-driven capture. The photos your crew already shoots feed both engines.
• Cycle-time reduction. Both cut the time from inspection to submitted estimate.

If your entire problem is “my estimator is the bottleneck,” either tool moves that needle. So the real question isn’t whether AI can write a scope. It’s what shows up when you open the result in Xactimate, and what it costs you to get there.

Where R360 Scope pulls ahead

1. A native .esx, not an export

We obsess over the part most tools quietly skip: the import. “Xactimate-ready” should mean a genuine, import-ready .esx that drops in clean, sketch, rooms, and priced line items intact, not a file that’s 90% there and leaves your estimator fixing every third line. A 90%-there import isn’t a time-saver; it’s data entry in a nicer shirt. If you’ve ever spent forty minutes cleaning up an “AI” estimate after import, you already know which one matters. (More on why the ESX file is the part that actually counts.)

And because the file is native, Xactimate reprices every line item on your price list the moment you import it. The draft is never tied to somebody else’s stale pricing.

2. Trained on real restoration work

R360 Scope was built by two operator-founders who’ve swung hammers and written Cat 3 scopes, and it’s trained on 200 real, self-written restoration projects and 20,537 field photos, not a generic vision model with a restoration sticker on it. Line items reference IICRC S500. And the estimator stays in the loop on every file: the AI drafts, a human QAs and submits.

3. You can edit the draft in plain English

Before you export, the draft is editable in chat: add a line item, remove one, change a quantity. You correct the scope the way you’d tell a junior estimator to, instead of hand-editing after import.

4. Three tools, not one

• Photos → .esx. Job-site photos in, priced native estimate out.
• PDF → priced .esx. Turn a PDF estimate into a working Xactimate file.
• Estimate compare. Put two estimates side by side and see where they differ.

5. Pricing you can test without a sales call

The first run of each tool is free. After that it’s $79 per estimate pay-as-you-go, or plans from $599/month that drop the per-estimate cost to $19 at volume. Priced per estimate, never per seat, so putting your whole team on it costs nothing extra.

An estimate isn’t done when the AI writes it. It’s done when it opens in Xactimate, priced on your list, and your estimator signs off.

Side-by-side

Comparison reflects each company’s publicly available product information as of June 2026. Rebuild is a capable, well-built estimating tool, this is a difference of output and pricing model, not of quality.

So which one should you choose?

Be honest about what you need the file to be.

If a solid draft you finish by hand is enough, and your workflow already leans on voice notes and scans, Rebuild may fit the way your techs already document. Fast draft, done.

If you bill your estimator’s hours against the whole file, capture to import to QA to submitted, then the native .esx is the difference that shows up on the clock. That’s the R360 Scope case: photos in, a priced Xactimate file out in minutes, repriced on your list, reviewed by your estimator, submitted the same day.

And you don’t have to take either pitch on faith. The right way to judge an AI estimating tool is to run a real job through it and open the file.

Run a real job through it, free

Your first run of each R360 Scope tool is free. Upload the photos from a job you already scoped by hand, open the .esx in Xactimate, and compare it against what you wrote. That’s the whole evaluation, no deck, no demo call.

Run your first estimate free →

Keep reading

• What is Xactimate? An operator’s guide
• R360 Scope: photos to priced .esx
• Field Notes