Most of the software I build doesn't start on a whiteboard. It starts with someone describing a part of their job they dread. InspectKit — the fire-inspection SaaS that's now the flagship product out of my Indianapolis studio — began exactly that way: with a clear, painful, completely unglamorous process problem. Here's the full story of how it went from paper forms to a live product.
The problem: the job didn't end when the inspection did
Fire-protection companies send technicians out to inspect extinguishers, alarms, sprinkler systems, and more. The inspection itself was never the bottleneck. The paperwork around it was.
Here's what the workflow actually looked like:
- An inspector fills out a paper form on site — sometimes a whole pad of them across a building.
- Those forms ride around in a truck, get coffee-stained, and occasionally go missing.
- Back at the office, someone re-types everything into a report.
- Deficiencies found during the inspection have to be turned into quotes for repair work.
- Completed work has to be turned into invoices.
Every one of those handoffs was manual, slow, and a chance for something to fall through the cracks. The company was effectively doing each inspection twice: once in the field, once again at a desk. That second pass is pure overhead — it doesn't make the building any safer, it just costs hours and delays getting paid.
Why a website couldn't fix it
This is the key fork in the road, and it's the same one I described in Do You Need an App, a Website, or Custom Software? The company didn't have a marketing problem. A prettier website wouldn't save a single hour of that re-typing. What the problem needed was software that lived inside the workflow — a tool that captured the inspection once, in the field, and carried that same data all the way through to the invoice without anyone re-keying it.
What I built
I designed and built InspectKit end to end — the field experience, the office side, and everything connecting them. The core ideas:
1. Capture the inspection once, on a phone or tablet
Inspectors do the inspection digitally in the field, including photos and markup. Critically, it's offline-first — mechanical rooms, basements, and back lots don't have signal, so the app holds everything locally and syncs the moment a connection comes back. No data lost, no "I'll fill it in later."
2. Turn that data into a report automatically
The moment the inspection is done, the report is essentially done too. No re-typing, no desk pass. The structured data the inspector captured is the report.
3. Carry it all the way to a quote and an invoice
Deficiencies become line items on a quote. Approved work flows into an invoice. The whole chain — inspection → report → quote → invoice — runs in one connected flow instead of three disconnected manual jobs.
The results, framed honestly
The point of InspectKit isn't a flashy dashboard — it's eliminating the second pass. When the inspection becomes the report, and the report flows into a quote and invoice, a few things change:
- Hours of re-typing disappear. The biggest time sink — turning paper into documents — is gone.
- Nothing gets lost. No more missing forms or coffee-stained pages; it's all captured and synced.
- Companies get paid faster. When the invoice is a few clicks from a finished inspection instead of a week of follow-up, cash flow improves.
- The work is more consistent. Every inspection is captured the same structured way, which makes reports cleaner and audits easier.
The bigger lesson
InspectKit is now a real, live SaaS, but it's worth remembering it didn't start as a "let's build a startup" idea. It started as a process that hurt — and the decision to fix it properly instead of living with it. That's the through-line in almost everything I build at No404, and you can see more of it on my Work page: I start with the question "what's slowing you down right now?" and design the software around the answer.
If your business is doing the same job twice — once in the field and once again at a desk, or once in one tool and again in another — there's probably a version of this story waiting to be written for you. Email me and tell me where the paperwork piles up.
Back to Insights