Industries
Construction software development
Construction software has to work where there is dust, gloves, poor signal and a subcontractor who will use it exactly once if it is annoying.
The site knows, the office finds out later
Progress is reported by phone call and photos in a group chat. Snags are on a clipboard. Timesheets arrive at the end of the week from memory. By the time the office has a picture of the project it is several days old, and disputes about who did what and when are settled by whoever kept better notes.
What we build
- Site progress and daily reporting
- Snagging and defect tracking with photo evidence
- Timesheets and labour tracking
- Health and safety documentation and sign-off
- Subcontractor access and permissions
- Cost tracking against budget
What makes this sector hard
Photo evidence is the core data type
Almost every record on a site is a photo with context: which unit, which defect, whose work, what date. That means reliable capture with metadata, compression that survives a slow connection, and storage that stays affordable when a project generates tens of thousands of images.
Adoption dies on the second annoyance
Site staff are not going to fight software. If logging a snag takes more than a few taps it will be done on paper and typed up later, or not at all. We design the two or three most repeated actions to be almost frictionless and accept a clumsier interface everywhere else.
Many companies, one project
Main contractor, subcontractors, client and inspectors all need different slices of the same project, and a subcontractor must not see another's commercial data. Permissions are a first-class part of the model here, not an admin screen added at the end.
On experience in your sector
We are straight about this: these are capability pages, not a client list. Where we have delivered in a sector we will name the client on the projects page. Where we have not, what we bring is the engineering, the compliance groundwork and a willingness to learn your domain quickly rather than pretend we already have.
FAQ
It has to. Progress entry, snagging and photo capture are built to work offline and upload when the device reaches a connection. Photos queue and retry, which matters because a large upload over a weak connection is the most common point of failure.
That is a decision worth making early because it drives the pricing and access model. Requiring every subcontractor to hold a paid seat is the most common reason this kind of system fails to get used. We usually design for limited-scope guest access instead.
Have a product that needs to ship?
Tell us where things stand and what you're trying to hit. We'll respond within one business day with next steps.