Asset tracking & preventive maintenance

Asset tracking & preventive maintenance

Scan a code on a machine, see what it is and what it needs. Most businesses should buy an off-the-shelf maintenance system, and I will tell you if that is you. This page is about the cases where the standard tool does not fit — unusual assets, an existing system it has to live alongside, or a process nobody sells software for.

A free 30-minute call. If an off-the-shelf maintenance system fits what you need, I will point you at it and tell you what it costs — that happens often, and finding out costs you nothing.

When you need this

  • Your equipment list is a spreadsheet, and the person who maintains it is the only one who understands it.
  • Maintenance happens when something breaks, because nothing reliably says what is due.
  • Service history lives in a filing cabinet, a text thread, or one technician's memory.
  • You tried a maintenance app and abandoned it, because keeping it current was more work than the problem.
  • You know what an hour of downtime costs on a given machine, and you cannot say when it was last serviced.
  • Your assets move between sites or crews, and the record of where they are is always slightly out of date.

What we do

  • Asset registry with the fields your equipment actually has, not a generic template
  • Printed QR or barcode labels, generated in batches and verified before they reach a printer
  • Scan-to-record from any phone camera, with no app to install
  • Preventive-maintenance schedules by date, runtime hours, or meter reading
  • Work history per asset, so the record travels with the machine rather than the technician
  • Alerts for what is due and what is overdue, to the people who act on them
  • Integration with the accounting, ERP or CRM system you already run
  • Offline-tolerant capture for shops and yards with unreliable signal
How this gets built now

Where these projects actually go wrong

Not the software. It is whether anyone scans the label. A maintenance system is only as good as the habit of recording work in it, and a technician with dirty hands and a job to finish will not log into anything. That is why the scan has to resolve in one tap with no login, why the form has to be short enough to finish standing up, and why the schedule should be generated from data the machine already reports rather than from someone remembering to enter it. Any build that ignores this produces an immaculate database that is six weeks out of date. I would rather scope a smaller system people use than a complete one they abandon.

How I use AI coding agents on client work →
Examples from real engagements

What this looks like

The label encoder behind this

QR generation is where tagging projects quietly fail. The encoder used here is dependency-free and committed to the repository rather than pulled from a registry at build time, and every symbol is decoded by an independent decoder before it is accepted — because a code with one field misplaced still looks exactly like a working code. A run of labels that was never readable is an expensive thing to discover six months in.

Custom internal tooling, in daily use

The portal that runs this business is the same shape as an asset system: multi-user access, records with history, file attachments, nightly scheduled jobs, and dashboards built on top. It is not a demo — invoices, time entries and client work run through it every day. That is the machinery an asset registry is assembled from.

Phones as the scanner

Seven published iOS apps, so the mobile side is familiar ground. For most asset work a native app is the wrong answer anyway: a QR code that opens a web page in the phone's own camera needs nothing installed, nothing provisioned, and nothing updated when a new technician starts.

High-volume equipment records

Hundreds of machinery listings a week, pulled from a half-dozen separate platforms, normalized to one schema and deduplicated into a single queryable set. Equipment data arriving continuously from sources that disagree with each other is the same problem an asset registry has at scale.

Got equipment to tag and a maintenance schedule to keep?

Tell me what you're trying to fix — I'll reply the same day.

Want the reasoning rather than the pitch? Why a QR code can look perfect and scan as nothing.