Fleet inspection, service and parts platform for industrial equipment

Every powered industrial machine has to be inspected before each shift, and almost everywhere that inspection is still a paper pad hanging on the equipment. Nobody can prove it happened, a fault an operator finds doesn't reach anyone until the next person needs the machine, and the dealer servicing the fleet only hears about a breakdown when the phone rings. Around that sit more inefficiencies: service, parts and rental requests arrive by phone and email and get re-typed into the dealer's helpdesk by hand, nobody has a consolidated view of what any individual machine actually costs to run, and the warehouse runs parts-picking off printed lists with no bin-location guidance and no timing.

The system also had to serve two equipment power types with materially different inspection checkpoints while still producing one comparable outcome and a single history, and needed to work reliably for operators, three tiers of fleet manager and a dealer, each entering the platform at a different scope.

Every unit gets a generated QR code whose payload opens that exact machine inside the mobile app, so an operator scans a sticker and is already in the right inspection with the correct checklist family and pre-filled make, model and serial — removing most of the friction that kills adoption of pre-shift inspection. Rather than storing answers for a human to interpret later, each submission reduces to a three-state condition — safe, defective but operable, or out of service — written straight back onto the equipment record, so the fleet list becomes a live status board instead of an archive of past submissions.

A defect or lockout notifies the site manager, company fleet manager and dealer administrator simultaneously as both a stored notification and a push with a deep link to the affected machine, and equipment marked out of service keeps generating reminders on a fixed interval until the condition clears. Structured request forms create tickets directly in the dealer's helpdesk — with contact creation, company/site/serial context and priority derived from the machine's condition — so the re-keying step disappears. On iOS, a data-driven form engine renders screens from declarative row descriptors over a library of reusable input cells, so a new form is a description rather than a new screen; maintenance costs are aggregated per machine and denormalised back onto the equipment record so fleet-wide cost views stay cheap to render.

Pre-shift inspection became provable, with every submission carrying its submitter, timestamp, hour meter reading, photographs and a signature. A fault an operator finds now reaches every relevant tier of management within the same submission, and a locked-out machine can't quietly stay that way. Requests reach the dealer's helpdesk as tickets instead of messages, quoting became self-service, and fleet cost became visible per machine instead of scattered across invoices.

Something holding you back?

New build, rebuild, or adding AI to what you already have — I'll take a look and give you an honest perspective.