Plans change hourly
Programme, drawings and specification all move. Any system built around a fixed plan spends its life out of date and gets abandoned.
Construction & real estate
The site does not care what the schedule said.
Construction software has to survive contact with a physical world that refuses to behave. Weather moves, subcontractors overrun, a delivery arrives on the wrong day, and a variation is agreed verbally at eight in the morning and written down at six that evening, if at all. Software that assumes the plan is true is software nobody on site will open twice.
What buyers here open with
“Will the people on site actually use it, with gloves on, in the rain?”
2
Named construction and infrastructure clients on our wall
The pressure
Four things the software has to survive.
Distributed workforce
Head office, site teams, subcontractors and suppliers, most of whom do not work for you and will not adopt your tooling because you asked.
Documents are the contract
Drawings, RFIs, variations and sign-offs are the legal record. Version confusion is not an inconvenience, it is a dispute.
Thin margins
Project margin is often single digit. The difference between a good year and a bad one is usually visibility of cost while there is still time to act.
Two buildings
The office thinks it is one system. Site knows it is two.
Almost every abandoned construction platform was designed by people sitting down, indoors, with a keyboard and a stable connection. Here is the difference we build for.
What head office assumes
- A connection is available.
- The programme in the system is the current programme.
- People will log things at the time they happen.
- A form with fourteen fields is thorough.
- Photographs are supporting evidence.
- Approval happens in the tool.
What site actually needs
- Works with no signal, syncs when it finds one, never loses an entry.
- Shows what changed since you last looked, and who changed it.
- Capture takes under fifteen seconds or it happens in the van at six o’clock, badly.
- Three fields and a photograph. The rest is inferred or asked later.
- Photographs are the record. Everything else annotates them.
- Approval is a name, a time and a version, and it holds up in a dispute.
The work
What we build for contractors and operators
Four systems, judged on whether someone in a hi-vis jacket opens them twice.
Project and programme tooling
Progress, cost and variation captured where the work happens rather than reconstructed in the office a week later.
Document and drawing control
One current version, a visible history, and a record of who approved what and when.
Site capture
Mobile-first, tolerant of no signal, designed for a gloved hand and a bright screen. Data syncs when the phone finds a network again.
Asset and portfolio systems
For the operators rather than the builders: maintenance, occupancy, compliance and lifecycle cost across a portfolio.
Non-negotiable
Four rules that decide adoption
- Offline first
- Signal on site is unreliable and a system that only works connected does not work. Capture locally, reconcile later, never lose an entry.
- Immutable records
- Variations, approvals and inspections form the evidence in a dispute. They are appended, never quietly edited.
- Interop with what exists
- Everyone already has a scheduling tool and an accounting system. New tooling integrates or it does not get used.
- Usable in gloves
- Large targets, high contrast, few taps. Interface decisions here are safety and adoption decisions.
Where AI actually lands
Four places it earns its cost, and one line we do not cross.
Worth doing
- Reading drawings and specifications to find the clashes and omissions a person would eventually catch, sooner.
- Progress assessment from site photography, compared against the programme.
- Variation and claim drafting, turning a site note into a documented instruction with the right references attached.
- Cost forecasting from historic project data, which most contractors hold and almost none use.
Where we stop
Anything with a safety consequence, and anything that signs on your behalf. Approval is a human act with a name attached, and that is exactly what a dispute turns on.
Evidence
HOCHTIEF Infrastructure and Construction & Design S.A.E are both clients. The Constec review describes a team that stayed with the detail rather than delivering a demo.
How we deliver it
The services this work draws on.
Mobile App Development
Native and cross-platform builds that pass review the first time.
Enterprise Software Development
Platforms that hold up under real load, real compliance, and real headcount.
Custom Software Development
Systems built for one business, owned outright, with no licence renewal attached.
Other sectors we work in
Next step
Talk to the engineer who would run your build.
No discovery call with a salesperson, no deck. A senior engineer reads what you send and replies with a real assessment, including when we think you shouldn’t build it.
