The reason most construction software fails is not technical. It is that it makes the site team's day longer so the office can have better reports.
The short answer
Build for the person on site first. If capturing a job is faster than photographing a paper sheet and sending it on WhatsApp, the app gets used and the office gets its data automatically. If it is slower, nothing else matters.
What actually goes wrong
Job sheets on paper. Photographed, sent on WhatsApp, and lost in a thread with 400 other messages.
Site photos everywhere and nowhere. On six phones, in three groups, unattached to any job.
Certificates and compliance documents. Which have to be produced on request, sometimes years later, and frequently cannot be found.
Quoting on evenings and weekends. Because it is nobody's day job and there is no system for it.
Timesheets as a negotiation. Reconstructed from memory at the end of the week.
The office has no idea what is happening on site. Until something goes wrong.
What we build
- Job management on siteAssigned jobs, status, notes, and sign-off, from a phone with gloves on.
- Photo capture attached to jobsSo the picture is filed against the work rather than sitting in a camera roll.
- Certificates and compliance captureFilled on site, stored properly, retrievable years later.
- TimesheetsCaptured as the day happens instead of reconstructed on Friday.
- Quoting and materialsBuilt around how your firm actually prices work.
The constraints that matter here
No signal. Basements, steel frames, rural sites. Everything must work offline and sync later. How offline-first apps are built.
Old phones. Not everyone on site has a current handset. An app that needs a recent device excludes half your team.
Gloves, rain, and one hand. Large targets, few taps, no fiddly forms.
Adoption is the whole risk. More construction software dies from non-use than from bugs. Why teams refuse the software you bought.
Accounting integration. Xero and Sage have proper APIs and integrate cleanly. Assume anything older needs an export rather than live sync.
Common questions
Will my team actually use it?
Only if it is faster than what they do now. That is the whole design brief. If capturing a job takes longer than photographing a paper sheet and sending it on WhatsApp, it will not be used, and no amount of training will fix that.
Does it work with no signal on site?
Yes, and it has to. Everything is captured on the device and syncs when signal returns. Any supplier who does not raise this before you do has not built for construction.
Does it link to Xero or Sage?
Usually. Both have proper APIs, so pushing approved timesheets or invoices across is straightforward. Older or bespoke accounting systems are a case-by-case conversation.
We already pay for a site app nobody uses. Why would this be different?
Because most of those are built to satisfy the office, not the person on site. If the app makes the site team's day longer so the office can have better data, it will fail. Solve the site problem first and the office data arrives as a side effect.