Two weeks ago I wrote about what a ServiceTitan quote does to a shop with fewer than ten trucks. That piece answered the top of the range. The question underneath it was the other one, and it is much more common: you already run Jobber, it has been fine, and you just took on insurance work.
Nobody ranks for that question. Search "field service software for plumbers" and Jobber and Housecall Pro own the page. Search anything with the claim in it and the results thin out into listicles that rank the same five products against each other on the same five criteria, none of which is the claim.
So here is the honest version, from someone who has run the jobs and built the software.
Does Jobber actually work for a restoration job?
Yes — right up until the first supplement.
Everything Jobber is good at, it is genuinely good at. Quote, schedule, dispatch, invoice, take the card. The mobile app is rated 4.8★ on iOS and is the best field app in the category; ours is not, and I will come back to that. Two hundred thousand people use it and most of them are not wrong.
What it is built around is a residential service call: one customer, one visit, one price, paid at the end. Restoration is a different shape of work wearing the same uniform, and the difference does not show up on day one. It shows up in week three, on the job that pays late.
What breaks first?
The second payer.
On a water loss you have two customers who both have to say yes, and only one of them is standing in the kitchen. The homeowner authorizes the work. The carrier decides what gets paid, weeks later, by reading a file assembled by somebody who was never on site.
Jobber's data model has one payer. So the moment the adjuster's number comes back under yours, the disagreement has nowhere to live. It lives in your email, or in a spreadsheet named after the street, or in the head of the one person in the office who remembers the job. Nothing in the software knows the claim exists, so nothing in the software can tell you which jobs have an open dispute, how old it is, or what you are still owed on it.
That is not a bug in Jobber. It is what happens when you take a tool built to close a job in a day and run a job that closes in six weeks through it.
How long is the job, and does the software agree?
A drying job is not one appointment. It is placement, then a moisture read every day, then adjustments, then demo, then containment, then the rebuild — different crews, different days, one continuous scope. On a service-call board each of those becomes its own visit and the thread between them is a job name.
The practical cost is in what you can answer. "Which of my active jobs is on day six with readings that have not moved?" is a question a restoration owner needs answered every morning and a scheduling board built for one-hour appointments cannot answer at all. You end up rebuilding it in a whiteboard or a shared sheet, which is the same job you were paying software to do.
Jobber is also frank about its own edges here. No native overtime tracking, no geofencing, thin inventory — three things that matter more on a two-week job with a night crew and a trailer full of equipment than on a faucet replacement.
What is the deliverable at the end of a water loss?
A document. Not an invoice.
This is the sentence I would want somebody to have told me earlier. On a service call you finish and you bill. On a claim you finish and then you assemble: the photographs from before anything moved, the moisture log, the equipment count and the days it ran, the scope with the reason for each line, the authorization form. That package is the product. The invoice is a page in it.
Software built for the service call treats the photos as attachments on a visit and the notes as a text field, because for that job they are. For a claim they are the evidence, and the difference is that evidence has to be retrievable in an order somebody else chose — usually months later, usually by an adjuster who has never spoken to you, sometimes by an attorney.
Try this on your own system before you decide anything. Take one finished water loss. Produce everything the software can tell you about it, in one artifact, and hand it to somebody in your office who was not on that job. Ask them whether they could defend the third line item. What you learn in the next ten minutes is worth more than any comparison table, including this one.
Who sent you the job, and who tells them how it ended?
Restoration work arrives through people. Plumbers who open a wall, agents, adjusters, property managers, the roofer who found the leak. A referred lead costs about $25 to acquire against $90.92 for a paid search lead — those are the 2026 numbers and they are the whole reason the trade runs on relationships rather than ad spend.
Every FSM in the category handles this the same way: not at all. Partner and referral tracking is a spreadsheet problem in Jobber and Housecall Pro, an add-on tier in ServiceTitan, and absent everywhere else. So the source of the lead gets typed into a notes field, or lost, and the follow-up call that keeps the partner sending — the one where you tell them how their referral ended — depends on somebody remembering.
That is the gap WORKFORCE was built to close first, and it is worth saying exactly what "closed" means: partners get their own login, submit referrals directly, and see the status of the ones they sent. The source is stamped on the lead and follows it into the project. What is not built is the money side — commissions and payouts to partners are roadmap, not shipped, and anyone who tells you otherwise about any product in this category should be asked to show it to you.
Who should stay on Jobber?
Plenty of shops, and the honest list is longer than it is comfortable for me to write.
If most of your revenue is retail work billed to the person who called you — plumbing service, HVAC change-outs, cleaning, landscaping — and restoration is the occasional job you take because the customer asked, stay. Jobber does that better than we do, its app is better than ours, and the entry tier is $29 a month against a Plus team plan at $599. Watch the add-ons rather than the base price: a Marketing Suite at $79 and an AI Receptionist at $99 are how that number moves.
If you have one office person who has already built a system that works — a naming convention, a folder structure, a claims tab in a sheet she maintains — and volume is not growing, that system is cheaper than any migration. Software is not the constraint. Do not go looking for a project.
The point where it flips is not a truck count. It is when your second payer starts costing you real money and nobody in the building can tell you how much.
What we do differently, stated plainly
One platform instead of the four to six that a growing shop ends up running in parallel, with every technician included in the plan and nothing metered per seat. Setup runs about two hours and you can be running live jobs inside a week.
ClaimReady+ is the insurance-claims workflow and it is shipped — a premium add-on, not part of the base plan, and I would rather say that plainly than let you find out at the quote. The claim and its documentation live with the job instead of in a parallel spreadsheet.
What is not shipped, so you hear it from me: offline mobile, which matters in a crawlspace with no signal and is the thing I most want back. The Xactimate and estimating integration. Partner commission payouts. Our field app has no store rating at all, because nobody outside this company has run a week of jobs on it yet — that is what pre-launch means and it is a real reason to wait if waiting suits you.
What to do before you move anything
Run the one-job test above. Then count, from the last ninety days: how many jobs had a supplement, how many had a payment sitting past sixty days, and how many arrived from a person rather than an ad. If those three numbers are small, you have your answer and it does not involve buying anything.
If they are not small, the cheapest thing you can fix first is the third one, and it costs nothing. Write down the four people standing closest to your customer at the moment a loss happens, and get fifteen minutes at a meeting already on their calendar.
→ The Referral Partner Playbook covers the rest of it — who to pick, what each type actually wants, and the follow-up call that decides whether they send you a second one: https://serviceready.io/referral-playbook.html
Schedule a demo at www.serviceready.io.
Joshua Barnes