The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
A construction site is temporary, so no turnstile goes up and crews move between projects. Entry and exit are logged from the worker's own phone with a QR scan and a location check. At month end, who was where and for how long is read back out of those records.
An attendance record on a construction job has to carry two things at once: who worked, and where. Because the site is temporary, fixed hardware is ruled out before the conversation starts, and crews do not stay put either; the same worker can be on a different site by midweek, alongside several subcontractors. Paper carries both facts and proves neither of them afterwards. The contractor needed the record taken without putting anything on site at all.
We go through how the work runs today and what you expect from the software; the scope comes out of that.
We decide what the system is made of and where its information is kept.
We draw the screens and the flow before any code, and start building once you have approved them.
We write and hand over the software so another team could carry it on.
The QR code establishes who scanned and the location check which site, so a site name is never picked by hand.
Time on site comes from a matched entry and exit; an open entry stays flagged as incomplete until its exit scan arrives.
Payroll entitlement is generated from those record pairs, and a worker's hours on each site are totalled separately from the others.
A React Native (Expo) app runs on the worker's own phone; Laravel receives the scans, MySQL stores them, nothing is bolted to the site.
| Challenge | Result |
|---|---|
| A construction site is temporary, so fixed turnstile hardware never gets installed | When a site closes there is no hardware left behind to take down |
| Paper timesheets cannot prove who worked which site, or for how long, at month end | Entry and exit are logged by QR scan and location, not by manual site selection |
| Entitlement is calculated on top of that unverifiable paper, leaving disputes with no evidence | Entitlement comes out of the scan records, with no second calculation sheet |
| Several subcontractors work one site, and the same worker appears across different projects | One worker's records stay separate per site, so hours never run together |
Our own workshop software, built around the car on the ramp. A work order, the parts it consumes and the invoice it produces run as one chain, and the accounting side hangs off that same record. Maintenance history lives on the plate and chassis, so it travels with the car.
Our own product for HVAC, boiler and appliance service companies. The customer and device records the office works from are the same ones the technician carries into the field. A job can be opened and closed in a basement with no signal, and service history stays tied to the device.
Our own product, still in development and not yet live. How long an appointment runs, what it is booked against and how bookings stack all differ by trade, so we are keeping those rules configurable inside the product instead of fixing them in code.
Tell us how the work runs today and we will look at which step could move into software.
