One record, from concept to the thirtieth year

Why CONSTRUX was created

CONSTRUX comes out of Justin Nseya's years of work as an MCIOB construction professional and senior project-management leader. It was not designed from a market gap. It was designed from the same failure, met again and again, on project after project.

The failure, precisely

Design, programme, cost, procurement, contracts, field delivery, commissioning and handover were each managed competently — and each in a different system, by a different team, on a different clock. Every one of those systems was fine on its own. What did not exist anywhere was the join.

That produced the same three symptoms every time:

• Critical information arrived late. Not missing — late. The drawing revision that changed the pipework interface was issued on time and reached the people pouring concrete a fortnight after they needed it.
• Risks were identified after they had already cost money. A risk register reviewed monthly finds a risk that landed three weeks ago. By then it is not a risk, it is a variation, and the argument is about who pays for it.
• Experienced managers spent their time chasing updates rather than controlling delivery. The most expensive people on the project, reduced to a human integration layer between systems that would not talk to each other.

None of that is a people problem, and it is not solved by working harder or by buying a better version of any one of those systems. It is a structural problem: there was no single place where what happened was recorded once, in a form every discipline could read, at the moment it happened.

Why the gaps between stages are where projects fail

A construction project is not a sequence of stages. It is a sequence of handovers between stages, and every one is a place where context is lost and has to be reconstructed from memory. The estimator's assumption about ground conditions does not travel to the site manager who meets the ground. The reason a clause was negotiated does not travel to the quantity surveyor who has to enforce it. The commissioning engineer inherits an asset and not the decisions that shaped it.

Each of those gaps is survivable. Together, over a two-year programme, they are where the margin goes — and they are invisible on any single team's dashboard, because no single team owns a gap.

What was built instead

A construction-specific operating system that connects every stage — concept and design through tender, construction, commissioning, handover and thirty years of operation — into one auditable delivery environment. One record, written once, readable by every discipline that needs it, and provable afterwards.

Its 81 AI agents examine that evidence continuously rather than at the month end: identifying emerging risks, coordinating the workflows between disciplines, and telling each person what has changed, what is at risk, what is costing money, and what has to happen next. Continuously, because the month-end review is precisely the instrument that finds things three weeks late.

That they almost all only ever propose is not a limitation added afterwards. It follows directly from the problem: the failure was never that decisions were made badly. It was that the people making them did not have what they needed in front of them at the time. So the system's job is to put it there — and the decision stays with the person carrying the duty for it.

2 of the 81 may act without being asked, and neither of them decides anything. One files the return register off an invitation the platform has already read; the other says the platform itself is unwell, which is the one act on this system where waiting for an approval makes the outcome worse. Both are confined to an envelope naming the exact commands, granted by a person with governance authority, carrying an end date, revocable, and recorded — and both carry a value ceiling of zero.

Why it is built as a record rather than a workflow

Twenty years of adjudications, final accounts and insurance renewals teach the same lesson: at the moment it matters, the only question is what was notified, on what date, supported by what evidence. Everything else is recollection. A workflow tool helps you do the work. A governed record lets you prove you did it — and those are different products, however similar the screens look.

What this is not

CONSTRUX was not created as another piece of construction software. There is no shortage of those, and adding to the pile would have reproduced exactly the problem it exists to solve: another system, holding another fragment of the truth, that somebody has to reconcile by hand.

It was created to be the integrated project control system that construction teams have been working without — by someone who spent years working without it.

What we build

A single governed spine for an asset's whole life — concept, design, tender, construction, commissioning, handover and thirty-plus years of operation. Not seven products with an export button between them. One data model, one permission system, one append-only record.

Why the record is the product

When a dispute reaches adjudication, the question is never who worked hardest. It is what was notified, on what date, supported by what evidence. A platform that stores documents answers that badly. A platform that records every state change as a hash-chained event, and can replay the whole project from the log alone, answers it exactly.

That is why 806 event types are a closed catalogue rather than a free-text field. An event nothing can emit is a capability that does not exist, and a test fails if one appears. It is why a correction is a new event and the original stays visible. And it is why governance decisions are human by construction rather than by policy: the catalogue marks those events closed to AI authorship, so 79 of the 81 agents can do nothing but propose, and the 2 that may act cannot reach a governance event whatever envelope anybody tries to grant them.

What we will not do

We do not show invented numbers. If the platform has not measured something, it says so rather than estimating it into a dashboard. A denial is displayed as a denial, never as a zero. Where a figure depends on an exchange rate nobody published, the figure appears in its own currency with the reason.

This site follows the same rule. Every count on these pages is read from the running product. There are no customer logos we do not have and no case studies we did not run.

How it is built

Zero runtime dependencies. 1220 API endpoints, 51 of which are reachable without a credential and each one listed in a test that fails if that number changes by accident. Tenant isolation applied on every read. Money in minor units everywhere, because a floating-point pound is a rounding error waiting to reach an invoice. The record is journalled to the volume before it is acknowledged and shipped to Postgres behind that, where a standby can follow it live — so recovery is a boot, not a restore from a backup.