One record, from concept to the thirtieth year
Construction does not lose money because nobody worked hard. It loses money because the record of what was agreed, when, and on what basis is scattered across email, spreadsheets and somebody’s memory of a site meeting.
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 191 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 no AI agent in the system holds a mandate above
PROPOSE — governance decisions are human by construction, not by policy.
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. 287 API endpoints, 32 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.
See the record work
A worked project runs concept to operations and then verifies itself against its own chain.