What we build
Everything below is built to order for one business. What is reused is the engineering underneath it, which is why the second system of any kind costs less than the first.
Android tablets and phones that work with no signal at all, capture the real time of the press, and sync themselves when a bar appears.
Built on React Native and Expo, locked to the app so the device cannot wander off, and managed remotely so a lost one can be found, locked or wiped without anybody driving out to it.
The chain an auditor walks backwards: from the finished thing, to the batch, to the container, to the person who handled it.
The database refuses records that break the chain. Nothing is edited in place, corrections are counter entries with a person and a reason, and the printed record is the deliverable.
One screen that says what is happening right now, what is late, and what went wrong today, readable from across an office.
Exceptions are the point. A dashboard that only shows you the good days is decoration.
One system across several branches, farms or depots, with a group view on top and strict separation underneath.
Site is a first class field from the first table, because retrofitting it later is a rebuild rather than a migration.
The unglamorous middle of a business: what came in, what went out, who did the work, and what it should be billed at.
Usually the fastest return, because it is where money quietly leaks.
Somewhere for your customers to log in, see their own information and give you theirs, without email attachments going back and forth.
The portal you are reading this on is the same one we hand to our own clients.
Anything that replaces a person's judgement. We build the system that records what was decided and by whom. A system that makes the decision carries a different kind of risk, and it needs a different kind of contract.
Migrating your old paper. Transcribed records are unattributed and unverifiable, and the gaps get filled from memory. We start on a clean date instead. Your paper stays as history, filed as it is.
Everything at once. One workflow, live and working through a real season, beats five half-built ones every time. The second is quick precisely because the first was done properly.
Anything we cannot support at 100km. If it needs somebody on site to restart it, it is the wrong design. Devices are managed remotely, updates go out over the air, and the dashboard says which device last checked in.
Usually it is the record that goes missing, the stock nobody can reconcile, or the job nobody can prove was done.
Start a conversation