Certa.
Compliance as an operating system. The statutory obligations every property carries, turned into a schedule that keeps itself.
Every commercial property in the UK carries a set of legal obligations it cannot opt out of — fire, gas, electrical, water, asbestos, lifts. Miss one and the exposure is not abstract: fines, void insurance, a building you can no longer legally operate. Most operators track this in spreadsheets and memory. Certa turns it into a system.
Describe a property — its sector, its services, what it contains — and Certa generates the exact compliance schedule the law requires for it. From there the work flows: certificates and reports filed against each obligation, jobs split between in-house and contractor, a calendar that knows what is due and what is overdue, and a directory of contractors who can upload documents through secure, time-limited links without an account.
On top sits a risk model — not a black box. It puts a pound figure on falling out of compliance by combining the statutory fine, the insurance exposure, and the cost of the underlying asset. Transparent arithmetic, shown working, so an operator can see exactly why a number is what it is and act before it matters.
Underneath: a per-property health score weighted by category, an asset register with condition tracking and lifecycle cost, a document ingestion portal, and reporting on SLA adherence and spend. The discipline is the same one that runs through the rest of this file — turn a sprawling, high-stakes obligation into a system that holds itself together. Risk and compliance, made operable. Built on Next.js and Supabase, with full per-organisation data isolation from the first migration.
Co-founded with someone who lives the problem — he runs a maintenance company, so the compliance burden is his daily reality. He brings the domain and the route to market, through facilities-management operators who feel the same pain. The product, end to end, is mine.