Estimate Cycle Time: The Quietest Cap on Restoration Growth
The hours between an inspection and a submitted estimate is the growth cap nobody measures. Why it throttles the whole business — and what changes when the first draft is done for you.
Ask a restoration owner what’s capping their growth and they’ll usually point at leads, or hiring, or the carriers. Almost nobody says the real answer: the number of hours between an inspection and a submitted estimate. Estimate cycle time is the quietest growth cap in the business, because it’s invisible on the P&L and obvious only when you finally measure it.
Why cycle time caps growth
In most growing shops, the estimator is the owner, and the owner is finite. When the time from inspection to submitted scope depends on one person’s nights and weekends, the whole business is throttled to that person’s calendar. You can generate all the leads you want; if scopes go out four days slow, you lose losses you could have won, your supplements stack up unwritten, and your cash conversion lags by exactly as many days as your scopes do.
Cycle time is also a margin issue, not just a speed issue. A scope written fast but thin leaves money on the table. A scope written thoroughly but slow strands the file. The job is to get both — complete and fast — and that’s precisely the trade-off a single human estimator can’t win at volume. It’s one of the seven numbers in the KPIs that predict scale for exactly this reason.
Estimate cycle time is the number that quietly caps your growth. When scopes depend on one person’s calendar, the business is throttled to that calendar — no matter how many leads you generate.
Where the hours actually go
Break a slow scope down and the time isn’t in the judgment — it’s in the assembly. Pulling the right line items. Mapping photos to rooms. Cross-checking the sketch. Writing the narrative that justifies each item to the desk adjuster. Re-typing the same Cat 2 water mitigation scope you’ve written two hundred times. The judgment — what’s in scope, what’s defensible, what the carrier will fight — takes minutes. The assembly takes the afternoon.
That split is the whole opportunity. The assembly is exactly the kind of work that should be drafted for you, leaving the estimator to do the part that actually needs a human: QA, judgment, and the carrier strategy. Understanding what Xactimate is really doing under the hood helps here — see the operator’s guide to Xactimate.
What changes when the draft is done for you
When the first draft of the scope — narrative, line items, photo citations — lands in minutes instead of an afternoon, the estimator’s role flips from author to reviewer. Output per seat climbs (we’ve seen 3–5× the scope output per estimator), cycle time collapses, and the owner stops being the single point of failure on the one task that gates revenue. The supplements get written because there’s finally time to write them, which is half of where restoration margin actually goes.
The engine that does the drafting
The estimating engine behind this work is R360 Scope. It’s trained on 200 real restoration projects and 20,537 field photos — not a generic model with a restoration sticker — and it drafts an IICRC-referenced scope narrative and a working ESX from the photos and sketch your crew already shoots. Your estimator QA’s and submits; there’s a human in the loop on every file.
R360 Scope is the same engine sold two ways: standalone and separately priced at r360scope.com, or fitted into a full engagement and tuned on your shop’s own approved scopes. Either way it’s the fastest path to taking estimator hours back — which, for a lot of shops, is the first leak worth closing.
What to do Monday
Measure it. Pull your last ten files and clock the hours from inspection to submitted estimate. If the answer is “it depends on when I get to it,” that’s the cap — and it has a fix that doesn’t require you writing scopes on Sundays.
Read by an R360 operator-founder. Want one at your table? Apply for the diagnostic