Water & Fire Restoration · Vancouver WA / Portland OR

You are leaving money on every single job.

Two ways to fix that. We write your estimates and take on the carrier for you — or we build you the AI tools to do it in-house and hand them over. Start with either.

Taking on new restoration companies this month

Two ways we make you money.

One is a service we run for you. The other is software we build once and hand over. Take either. Most companies start with one and add the other.

We do the work

Estimating & insurance negotiation

You send us the job. We write the estimate. You get paid for the work you actually did.

3% of written revenue to write the estimate
6% of approved revenue to write it and negotiate it

Cost it against your own volume →

  • Mitigation and reconstruction scoping
  • Rebuttals with code and IICRC citations
  • Typically back inside 48 hours
  • Nothing written means nothing billed

Best if estimating is the bottleneck right now and you want it off your plate this week, without hiring.

See how estimating works

You own the tool

AI tools built for restoration companies

We build the system around how your company already works, train your team on it, and hand it over. One payment, no subscription, no monthly bill.

$2,000 and up, one time per build, yours to keep
$500 model setup stacks under any build
  • Mitigation Estimate Writer$7,500
  • Missed Revenue & Supplement Finder$4,500
  • Rebuttal Agent$3,500
  • Internal Website + Full Analytics$3,500

Best if you want the capability in-house permanently, rather than paying a percentage on every job forever.

See all seven builds
Own it, don't rent it. Subscription AI tools in this space typically run $199–$399 a month, for as long as you use them. These are one-time build fees.
3%
Of written revenue to write the estimate
6%
Of approved revenue to write it and negotiate it
48hr
Typical estimate turnaround
0
Retainers, contracts or monthly fees

The problem

The money isn't lost on the job. It's lost on the paperwork.

Restoration companies rarely lose money in the field. They lose it in the estimate, in the rebuttal they never wrote, and in the line items nobody remembered to include.

01

Missed revenue

Line items that belong on the estimate and never make it there. Antimicrobial, equipment days, detach and reset, PPE, containment. Two or three misses per job, every job, compounds into six figures a year.

02

Weak rebuttals

The adjuster cuts a line and someone on your team writes back three sentences with no code citation, no IICRC reference, no photo. The cut sticks. It shouldn't have.

03

Slow estimates

Writing it is not the slow part. It's scrolling three phones for the one photo that proves the tear-out, re-keying moisture readings off a paper log, and rebuilding scope from notes nobody wrote for a stranger to read. Four days later it goes out, on a job you already won.

04

Nobody owns it

Estimating gets bounced between a PM, an owner, and whoever has time. There's no standard, no review, and no one accountable for what got left out.

Who you're working with

We run AI inside real restoration workflows. Not slides about what it could do.

We're restoration estimators and AI systems builders with hands-on experience using artificial intelligence inside real restoration and construction workflows. We've built and implemented AI-powered tools for estimating, estimate review, insurance rebuttals, scope analysis, document organization, KPI tracking, and internal operations. These systems run in day-to-day production environments — cutting repetitive work, improving consistency, surfacing missed opportunities, and helping teams make better decisions faster.

  • Estimating, estimate review and scope analysis
  • Insurance rebuttals built from real job documentation
  • Document organization and KPI tracking
  • Internal operations and workflow automation
Practical, not impressive. The goal is to leave each company with systems their own employees can understand, use, maintain, and improve.

More on the background →

Next step

Twenty minutes. Bring one job file.

Bring a recent estimate you've already sent and we'll tell you what's missing from it. Here for a build instead? Tell us where your team loses the most hours and we'll say which one pays for itself first — or that none of them do yet.

Pick a time