Construction software that works where the work happens
Three production systems built for site conditions: no signal, dirty hands, and an argument that arrives months after the crew left.
Site disputes are won by whoever recorded the work, not whoever did it. Your argument arrives months later, long after the crew moved on. The only evidence is what someone typed on a phone in a basement with no signal.
What site engineering actually demands
4 things that decide this
- 01Offline capture that keeps the device clock and the server clock as separate facts, so a record taken in a basement still holds up in an argument.
- 02TankAware runs inspections, deficiency tracking and vendor work orders across hundreds of sites, with dynamic checklists and per-site document version control.
- 03WorkmateAI verifies tradespeople through ABN validation, trade licence, insurance and identity checks before they can take work at all.
- 04Payment held against the job and released on sign-off, with a dispute freezing the release and locking the evidence at submission.
Systems running in site and trades businesses
TankAware
AI + IoT petroleum site management for Sutherland Excavating Ltd.
Read the case study →
WorkMateAI
Dispute resolution, payments, and compliance for Australia's on-demand trades.
Read the case study →
WAIQ
Business operations and execution platform for multi-site organizations.
Read the case study →
Three builds, three site problems
Snagging, subcontractor risk and method consistency are the three that cost money. Each build attacked one.
| Build | What it does | The site problem it solves | Where it runs |
|---|---|---|---|
| TankAware | Inspections and deficiency-to-work-order flows. | Snagging that turns into assigned, closed work. | Oil and gas, Canada |
| WorkmateAI | Verification, held payments, staged disputes. | Subcontractor checks and payment on sign-off. | Trades marketplace, Australia |
| WAIQ | One method and training record per site. | Every crew works to the same documented method. | Multi-site operations |
- CapturePhoto and note, no signal.
- QueueHeld on the device, timestamped.
- SyncBoth clocks kept, neither overwritten.
- AssignBecomes a work order with an owner.
- Sign offClosed, with who and when.
Skip the queue step and every record you produce is challengeable.
Write the dispute process before you need it
Most teams design the happy path and improvise the argument. WorkmateAI was built the other way round, because a marketplace holding money between two strangers cannot improvise.
Funds sit held against the job. Opening a dispute freezes the release and locks the evidence at the moment it was submitted. Escalation runs in stages rather than landing on one person's desk.
- Lock evidence when it is submitted. Anything editable afterwards is worthless in an argument.
- Hold payment against completion, and define what completion means in writing.
- Escalate in stages. A single adjudication step turns every disagreement into a crisis.
The physics of site work does not change
Signal drops. Hands are dirty. The person recording the job would rather be doing the job. Every system on this page had to survive those three conditions before anything else mattered.
So these builds start at capture and work outwards, rather than at a head-office dashboard. A record your crews will not create is worth nothing to whoever reads your reports.
- 01Offline-first capture with signed, timestamped records that survive a challenge.
- 02Deficiency and work-order lifecycles, from flag through assignment to closed sign-off.
- 03Contractor verification: ABN validation, trade licence, insurance and identity checks.
- 04Held payments, staged disputes and per-site document version control with audit trails.
The stack behind this work
Field
Money and identity
Controls
“TankAware has revolutionized how we manage petroleum sites. The real-time data and automation have exceeded expectations.”
Blake Sutherland · President, Sutherland Excavating Ltd.
What site businesses ask us
01What site work have you actually shipped?
TankAware, built for Sutherland Excavating Ltd., runs inspections, deficiency tracking and vendor work orders across hundreds of sites in Canada. WorkmateAI verifies tradespeople and holds payment against the job. WAIQ keeps one documented method running across every location.
02Will the app work in a basement with no signal?
It has to be built for that from day one. The entry is written to the device with its own timestamp, queued, and reconciled when the connection returns. An app that assumes signal produces records that contradict each other.
03How do we prove what a subcontractor actually did?
By capturing the evidence at the moment of the work and locking it. Photo, timestamp, location and the person who recorded it, none of them editable afterwards. WorkmateAI locks dispute evidence at submission for exactly this reason.
04Can we hold payment until work is signed off?
Yes, and WorkmateAI is the build that does it. Funds are held against the job through Stripe Connect and released on completion, with a dispute freezing the release. The design work is defining sign-off precisely enough that it can be automated.
05Our crews ignored the last system we bought. What would change?
Ask what the system gives back to the person using it. Crews adopt tools that shorten their day and abandon tools that only feed a head-office report. If a foreman still fills in paper afterwards, the software has failed regardless of what the dashboard says.
