Why we built Valegrid Flow

The problem wasn't a lack of construction software. It was that none of it was built for how a UK subcontractor actually works. The big platforms were priced for main contractors with IT departments. The cheap ones were timesheet toys that had never heard of CIS, didn't know what a payment application was, and treated RAMS as someone else's problem.

So the week ran on spreadsheets. Hours copied from texts and voicemails. CIS worked out by hand, checked twice, still wrong sometimes. A valuation typed up on Sunday night from a timesheet that lived in a van. Photos that would have won a payment dispute — somewhere on an old phone.

Valegrid Flow started as the tool for one firm's own sites, built in the evenings and tested on real jobs the next morning. The rule from day one: one approval should drive everything. When a supervisor approves a timesheet, payroll knows, CIS knows, the HAVS record knows, the valuation knows, and the site diary already has the photos and the weather.

That's still the rule. It's why Valegrid Flow is priced per active worker — the way a subcontractor actually staffs a job — and why every tax figure in it follows HMRC's rules to the penny, because the founder files those returns himself.