Insurance Restoration Supplement Software: Why We Didn't Build One

The oddly specific problem

Every contractor doing insurance restoration work runs a second, unpaid job on top of the first one, and nothing on the market walks the whole loop.

Every pitch for insurance restoration supplement software opens with a story like this one. A roofing estimator lays out the arithmetic. The carrier has bundled starter course and hip/ridge into a single waste percentage. He measures the roof, counts the field shingles, and finds that the field alone consumes more material than the total allowance. Starter and ridge, in this version of reality, get installed out of thin air.

He submits the supplement. The carrier replies that existing waste is sufficient.

So he escalates. He pulls the actual material invoices, redacts the pricing, and sends proof of what was physically bought and nailed to the roof. The carrier denies it again, this time with a new theory: his crews must be installing shingles incorrectly and buying extra bundles to pad the bill.

That is the shape of the problem. Every contractor doing insurance restoration work runs a second, unpaid job on top of the first one: reconstructing what the adjuster left out, documenting it, submitting it, following up, and absorbing the denial. There is no purpose-built tool that walks the whole loop. Xactimate writes estimates. EagleView measures roofs. Nothing sits in the middle and says "the adjuster missed drip edge, your waste factor is mathematically impossible, here's the packet."

That gap looks like a product. We spent a while looking at it. Then we put it down.

Wait, is this actually a problem?

Partly. Here is where we have to be careful with you, because the numbers floating around this space are unusually self-interested.

$180K/year in uncollected supplements for a mid-size shop, a figure that comes from people selling the cure.

The figures you will find everywhere ($180K/year in uncollected supplements for a mid-size shop, $7,000 to $8,000 average supplement value, 20 to 40% added to the original estimate, 80 to 90% margin on recovered money) come from two sources: ClaimStack's blog and IA Solutions' blog.

Strip them out and what remains is: a thin but credible primary signal from contractors describing the fight, plus the structural logic of the industry. Adjusters do miss line items. Drip edge, starter strip, ice and water shield, code-required ventilation, and overhead & profit on multi-trade jobs get left off routinely. Small-to-mid losses handled by a TPA and a desk adjuster run on rigid carrier guidelines; items can be supplemented afterward with documentation. Large losses depend heavily on your relationship with the field adjuster, which is a polite way of saying the process is not fully rules-based.

So yes, contractors are underpaid and the recovery work is manual. What's unproven is the specific claim any software product here depends on: that better documentation makes carriers pay.

Who's already solving this

Pricing as of research; verify before you buy, since most of these vendors quote rather than publish.

So why isn't this a slam dunk?

Three reasons, in ascending order of how much they hurt.

The competitor nobody can explain. ClaimStack exists. It is purpose-built for supplement identification, documentation, and recovery tracking. It has a brand, a content operation, and enough presence that it shows up when contractors research the problem. Meanwhile the technical build is not hard: parse Xactimate XML, run rule-based gap detection against a curated line-item library, generate a PDF packet, track the pipeline. CRUD plus business logic plus document generation. No models, no GPUs, an eight-to-twelve week MVP for a competent team.

Put those two facts next to each other. Easy build, screaming need, purpose-built incumbent with a head start, and the category is still described as unsolved. Something in that story is false. The most economical explanation is that the product doesn't move carrier payments enough to generate the word-of-mouth and retention that a category winner needs.

The value proposition is worse than the one already on the table. Every analysis of this space frames Xactimate as the incumbent. It isn't. The incumbent is the contingency adjuster. IA Solutions charges 10 to 15% of what it recovers and zero when it recovers nothing. Software asks a contractor to pay $199 to $399 monthly, do the writing himself, and eat the denial. The per-claim math looks fantastic for the SaaS right up until you ask whether the software matches a licensed adjuster's success rate. Nothing in the evidence suggests it does. That isn't a pricing advantage to exploit. It's a risk transfer the buyer already enjoys and would be giving up.

The thesis may be wrong at the root. Insurance restoration supplement software assumes supplements get denied because contractors document them badly. The single best piece of primary evidence shows a supplement backed by actual material invoices denied on an invented pretext about crews installing shingles wrong. That is not a documentation failure. That is a carrier deciding not to pay and reaching for a reason afterward.

Better formatting does not change that calculus. It produces better-formatted denials.

Two more things sit underneath. Distribution has no answer: the buyer is an owner-operator who distrusts software, has already been burned documenting a supplement properly and losing anyway, and is being bid against by ClaimStack for the same handful of search terms. Inside sales to that buyer at $250 a month means a CAC that swallows the gross margin whole. And retention is weather-bound. Storm work is episodic. A contractor who runs 20 claims in a quiet year will not renew a $299/month subscription he opened four times. The compounding-SaaS model this business depends on does not survive contact with hail season variance.

What we're watching

Two questions would change the answer, and only two.

First: does documentation quality actually move carrier payment? Not according to a vendor blog. According to a sample of matched claims where documentation was the variable and denial rates were the outcome. If someone publishes that with real data and the effect is meaningful, the entire thesis flips from hopeful to fundable.

Second: what is ClaimStack's actual traction, and why is it where it is? "Weak sales motion and clunky UX" is a fixable reason and an opening. "Carriers deny regardless" is a tombstone. Anyone considering this build needs to know which one it is before writing code.

"Weak sales motion and clunky UX" is a fixable reason and an opening. "Carriers deny regardless" is a tombstone.

We're also watching three softer signals: whether a franchise network or shingle manufacturer starts bundling supplement tooling (that would solve the distribution problem someone else's way), whether carriers respond to more aggressive supplementing by tightening guidelines or adding pre-authorization (which would shrink the opportunity while everyone builds for it), and whether any tool finds genuine off-season utility so the subscription survives a calm summer.

If you have this problem right now, buy the aerial report and check your line-item list. If the two questions above ever get answered, we'll revisit.