I want to talk you out of this first, because for a long stretch of my working life the honest answer was that I did not need it.
One truck. Me on every roof. Every walk in the same order because there was only one person doing it. A phone full of photos and a memory of the property. It was not a system, but it did not need to be — the system was me, and I was always there.
If that is your shop today, you can stop reading and go back to work. Nothing below will pay for itself yet.
The moment it changes
It is not a headcount. It is the first time somebody else runs an inspection under your name.
Mine was a hip roof off Route 9. Marcus had been with me two years, good hands, good with customers. He came back with fourteen photos and a note that said "some hail, needs a closer look." I drove out the next morning and did the entire inspection again.
That is the moment. Not because Marcus was careless — he was not — but because everything that made my inspections consistent lived in my head and had never been written down. The minute I was not the one on the roof, it stopped existing.
The second trigger is quieter: the first time a customer asks you a question about a job from eight months ago and you cannot answer it without going and looking. That one is about the record, not the crew.
What a small shop should refuse to pay for
Most of the feature grid, on a crew of three.
- Per seat pricing, if you have a part-timer who runs two inspections a month. You will be paying a full seat for somebody generating almost no volume. Ask for something that tracks work rather than headcount.
- Integrations you do not have the other half of. A CRM connector is worthless until you have a CRM you actually use.
- Dashboards and analytics. At three crews you know what is happening because you talk to everybody. Reporting is for the shop that has outgrown that, and buying it early is buying a graph nobody opens.
- Anything that needs an implementation call. If a tool for a three-person contractor requires onboarding sessions, it was built for somebody else.
What is worth paying for at this size is narrow: the client can watch without installing anything, it works badly-but-usably on a poor connection, the record survives, and a new person can run it without you.
Rolling it out without a bad month
Do not switch everybody at once. You have three crews and no slack; one bad week is a real dent.
Pick one crew and one inspection type — the most routine thing you do, not the tricky ones. Run it for two weeks alongside how you already work, not instead of it. The redundancy is the point; it means a failure costs you nothing but time.
Then look at what came back, and fix the walk order before you roll it wider. The walk order is where the value is. The software is just what makes it repeatable when you are not there.
What to measure
Two numbers, and neither is engagement.
Second trips per ten inspections. This is the one that pays for the tool. If it does not fall, either people are not watching or you are sending the link to the wrong person.
Inspections you had to redo. The Marcus number. If a new person's walk still needs your walk on top of it, the process is not written down clearly enough yet, and no software fixes that for you.
Both of those are countable on a whiteboard. If you cannot move them in a month, the problem was never the tooling.
Frequently Asked Questions
When does a small contractor actually need inspection software?
The first time somebody else runs an inspection under your name. It is not a headcount threshold — it is the moment your process has to exist outside your own head. Before that, a fixed walk order and a phone is a legitimate answer, and cheaper.
What should a three-person shop not pay for?
Per-seat pricing if you have part-timers, integrations for systems you do not run yet, dashboards you will not open, and anything requiring an implementation call. At that size the list of things worth paying for is short: no install for the client, usable on a poor connection, the record survives, and a new hire can run it without you.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.