Field service software runs the job. It does not run the claim. That single distinction costs insurance-heavy contractors more than any line item in their software budget — and no major platform has closed it.
We compared the five most widely used field service management (FSM) platforms — Jobber, Housecall Pro, ServiceTitan, Service Fusion, and Connecteam — against the workflow that determines whether a restoration contractor gets paid: loss intake, claim documentation, adjuster communication, certificate-of-insurance compliance (the paperwork TPA programs and commercial clients demand before you're even on the job), and the supplement cycle. The result was unanimous. Not one platform treats the insurance claim as a first-class object. The claim lives in a spreadsheet, an inbox, and a folder of photos — everywhere except the system of record.
If you spend any time in contractor forums you've seen the thread: "what software do you use for insurance work?" — asked every few weeks, never with a good answer. This piece is the long version of why there isn't one: why the gap exists, what it actually costs, and what an insurance-ready platform would have to do differently.
What is the real unit of work in insurance restoration?
For a residential plumber, the unit of work is the job: schedule it, do it, invoice it, collect. Every major FSM platform was architected around that loop, and they execute it well.
Insurance-driven work breaks the model. In restoration, most fire, water, and mold losses come through an insurance claim. The customer on site is not the party who pays. The scope gets negotiated against documentation, over weeks, with an adjuster who was never a user of your software and never will be. Payment follows the file: photos tied to line items, daily moisture readings logged against a dry standard, cause-of-loss evidence, a written communication trail, and often a supplement cycle after the first approval.
The job closes in days. The claim closes in months. A system built around the job simply has nowhere to put the thing that determines whether the work was profitable.
What the big five actually do when insurance enters the job
The pattern across the market, verified against current vendor documentation and user reports:
- Jobber — built for residential quoting, scheduling, and payments, with the best mobile app among true FSMs in the SMB category. Its finance model is consumer-facing; there is no claims object, no adjuster workflow. Commercial and insurance work hits a ceiling fast.
- Housecall Pro — the go-to tool for 1–15 tech residential service shops; strong on booking, review automation, and flat-rate pricebooks. Same consumer-payment DNA. Insurance documentation is a camera roll and an email thread.
- ServiceTitan — the enterprise standard for HVAC, plumbing, and electrical, with deep operational analytics. It touches insurance only at the accounting layer. There is no loss-to-payout workflow, and its implementation cost and 6–12 month onboarding put it out of reach of most 1–15 truck operations anyway.
- Service Fusion — flat-rate pricing and solid dispatch for growing teams. Its insurance capability is certificate-of-insurance generation. That covers one document out of the dozens a claim file needs.
- Connecteam — excellent workforce compliance and time tracking, but not a true FSM: no quoting, invoicing, or customer records at all.
Five platforms, one blind spot. Restoration operators typically respond by bolting on restoration-vertical software beside their FSM — DASH for job management, MICA for moisture documentation, or a hand-built Excel system — which recreates the exact disconnected-tools problem the FSM was bought to solve.
Why the gap persists
Three structural reasons.
The DNA is residential-finance. Jobber and Housecall Pro grew up on homeowner-pays-by-card work. Every design decision downstream — estimates, invoices, payments — assumes the person receiving the service is the person paying for it. Insurance work violates that assumption at the root, and retrofitting a third-party payer into a consumer-payment architecture means rebuilding the billing core.
The adjuster is not a seat. FSM vendors monetize per user. An insurance adjuster will never buy a seat, log in, or appear in a demo — so the persona was never designed for, even though that persona controls the largest checks in the vertical. Back when we were shopping platforms for our own shop, every salesperson asked how many techs we ran; not one asked how we got paid on a water loss. Per-seat economics quietly deprioritized the claim for a decade.
And the vertical looked small from the outside: restoration is a fraction of the contractor market by company count, so horizontal platforms optimized for plumbers and HVAC — where "FSM for plumbers" is a crowded, ranked, fought-over search term. But claims-adjacent work extends well beyond restoration. Roofing after hail, HVAC after power surges, plumbing after burst pipes, electrical after fire — any contractor who has ever waited on an adjuster has lived in this gap.
What the gap actually costs
The costs hide in three places, none of them labeled "software."
Shaved scope. Adjusters cut what you can't prove. When photos are not tied to line items and readings are not logged on a timeline, every negotiation starts from a weaker position. The file is the argument, and today the file is assembled by hand — or not at all.
Owner hours as integration software. In a typical insurance-heavy shop, the owner or office manager is the sync layer: re-keying job data into claim documents, forwarding photos, reconstructing timelines when a supplement gets contested. In our shop, that sync layer has been me more nights than I want to count — pulling scope lines back together after the crews went home. Every one of those hours is unbilled and unrecorded, the most expensive labor in the company doing data entry.
Referral relationships left untracked. Claims work arrives through relationships — insurance agents, adjusters, property managers, home inspectors. Industry benchmark data puts a referred lead at roughly $25 against $91 for paid search: the cheapest, highest-trust acquisition channel in the trades. Yet none of the five platforms can tell an operator which partner sent which job, what it was worth, or whether anyone ever closed the loop with a thank-you. Not one of the five has a field for the referral source, let alone a loop back to the partner who sent it.
What would "handling the claim" actually look like?
A checklist for any operator evaluating software for insurance-driven work. Make the vendor demo each one live before you sign:
- Loss captured at the source — cause-of-loss photos, notes, and moisture readings recorded in the field app at first loss inspection, timestamped, before mitigation begins. The dry standard established on day one.
- Documentation tied to line items — every line linked to its evidence, one export, adjuster-ready.
- A written adjuster trail — claim communications logged against the claim, so "per our call, you approved X" is always retrievable.
- Claim status distinct from job status — the job can be complete while the claim is open; the system should know the difference and track the receivable through the supplement cycle, with the cause-of-loss file kept intact for when the carrier's subrogation demand comes asking for it.
- Referral partner visibility. Who sent the job — agent, adjuster, property manager. Whether anyone closed the loop. And a way for partners to submit and track referrals without calling your office.
Score today's platforms honestly against those five and the market's answer is a row of zeros — with partial credit, at best, for a COI generator.
Where this is heading
Full transparency on our position: ServiceReady is building WORKFORCE™, an FSM platform for the trades, and this gap is the reason it exists. Of the five capabilities above, the referral partner portal — partners submitting and tracking their own referrals — is live in the platform today. The claim as a first-class object is where the roadmap points, built by operators who have sat across from adjusters. We publish the thesis before the feature list because the gap matters whether or not you ever use our software.
The first system to build is the referral system
Software or no software, the highest-leverage move for a claims-adjacent contractor costs nothing: systematize the relationships that create the work. Ten named partners, a closed loop after every referred job, and a record of who sent what. That system is worth building this week — in a spreadsheet if that is what you have.
We put exactly how to do it — the partner economics, the failure protocol, the two-direction ledger — into the Referral Engine Playbook. Leave your email there and it lands in your inbox right away.