Inspection and compliance apps
Checklists bound to the asset, photo evidence, and a certificate the client can accept without a phone call.
Construction
Construction software that starts with the inspection record
We build the apps crews use on site and the systems the evidence lands in. Anchor testing, site safety, plant and the certificate at the end. Clients in the UK, the US and Australia.
70%Faster reporting at a UK inspection provider
2UK construction platforms shipped
40+Developers on staff
12+Years average leadership experience
What this is
Construction software, defined by who has to sign it
Construction software development covers a wide field. The part we work in is narrow and easy to describe. A person on site performs a check, and months later somebody who was not there has to be satisfied the check happened and the result was acceptable.
Everything else follows from that. The app has to work where the signal does not. The reading should come from the instrument. The record has to carry who, when, where and against which standard.
If that is not your problem, a platform already on the market is a better buy than a build, and we will say so on the first call.
Where we came from
Our first construction client made portable pull testers. The second sold the inspection itself. Both taught us that the instrument and the certificate are the product, and the app is the thing in between.
How small it can start
One workflow, or one device integration. The team grows when the roadmap needs it.
Services
What we build for construction teams
Eight pieces of work. Most engagements start with one of them and grow from there.
Anchor and pull testing
Apps that read the tester over Bluetooth and record the load against the fixing that was actually tested.
Site safety and permits
Toolbox talks, permits to work and near-miss reports that reach the office on the day.
Equipment and plant tracking
Where the plant is, who signed for it, and when the next thorough examination falls due.
Field and crew mobile apps
Offline first, because the signal in a basement or a steel-framed unit is not something you can plan around.
Progress and compliance reporting
Dashboards built from what the crews recorded, so nobody updates a spreadsheet on Friday.
Integration with what you already run
Procore, Sage, SharePoint, an ERP or a CMMS. The result has to land somewhere other than a PDF folder.
Computer vision on site
Defect and PPE detection where the volume of images justifies training a model.
Standards
The rules your records have to satisfy
These decide the data model long before anyone argues about the colour of a button.
LOLER 1998Six months between thorough examinations for equipment that lifts people and for lifting accessories. Twelve months for other lifting equipment, unless a written scheme of examination says otherwise.
PUWER 1998Work equipment inspected where safety depends on the installation conditions, and inspected again after anything that could affect it.
BS 7883:2019Fall protection anchor systems. An inspection is graded pass, conditional pass, conditional fail or fail, so a yes or no field does not model it.
BS 8539Site testing of fixings in concrete and masonry. Most fixings are proof tested as a sample, while eyebolts for safety harnesses are tested one by one.
CDM 2015The record trail a principal contractor hands over at the end, assembled from checks taken months apart by people who have since left.
What LOLER asks of inspection software goes through the scheduling side in full.
Case studies
Two builds for construction, both still running
Inspection provider, United Kingdom
Work-at-height anchor and torque platform
Proof-load and torque checks ran on spreadsheets and email. We built the planning dashboard, the field app that reads testers over Bluetooth, and the certificate that carries GPS, timestamps and readings.
70%Faster reporting cycle
Equipment maker, United Kingdom
Hydrajaws Limited
A maker of portable pull testers arrived with an application nobody had documented. We rebuilt the environments, then shipped a free and a paid version with digital torque reading through the KTC SDK.
500%Rise in potential clients reported
Build or buy
When a custom build is the cheaper answer
Four conditions. If none of them is true for you, buy the platform.
1
The check is yours
The sequence a client signs off came out of your method statement. A platform hands you its own form and asks you to work around it.
2
The result has to land in your system
An inspection that ends in a PDF folder has not finished. It finishes when the ERP, the CMMS or the client portal has it.
3
Instruments should feed the record
A torque wrench or a pull tester with an SDK writes its reading straight into the form. A typed-in number is the thing an auditor questions first.
4
Per-seat pricing stops adding up
At a few hundred field users on one tenant, the licence line starts to look like a build budget.
Who we build for
The four kinds of team that call us
Principal contractors and specialist subcontractors
Teams with their own method statements, and clients who ask for the evidence.
Testing and inspection providers
Firms selling the inspection itself, where the certificate is the product.
Equipment and instrument makers
Manufacturers who want the app shipped beside the tool, under their own brand.
Asset owners and facilities teams
Portfolios where the statutory register has to be right on the day somebody asks.
Technologies
Technologies and platforms
FAQs
What construction buyers ask first
Should we build, or just buy Procore?
Buy, in most cases. If your inspection is checklists, photos and issues on commercial projects, a platform on the market will cover it for less than a build costs. We get called when the check is specific to your trade, when an instrument has to supply the reading, or when per-seat pricing across a few hundred field users has stopped making sense.
Can the app read our testers and torque tools?
Usually yes, over BLE or a gateway. Where the maker provides an SDK we integrate against it, as we did with KTC for digital torque on the Hydrajaws platform. Send us the model numbers and we will tell you which ones we can read.
What happens on a site with no signal?
Every record is written to the device first and queued for sync. Basements, lift shafts and steel-framed units kill mobile data, so a system that needs a live connection at the moment of the check will lose records exactly where the check matters.
How long before a crew is using something?
The first scope is one workflow. We will not put a date on it before seeing the workflow, and anyone who does has not looked at your process yet.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name, so leaving us never needs a migration project.
Send us one workflow
Thirty minutes with the engineers on the check your crews run now, the instrument behind it and the system the result has to reach. If a platform on the market fits better, you will hear that on the call.