PriComp is a product of Catolyst, a UK development house. It isn't a repackaged generic asset system — it grew out of real compliance operations, one module at a time, in response to what the people running them actually hit.
PriComp began as a set of compliance registers — the minimum needed to stop a portfolio's statutory position living in a spreadsheet. What followed was not a roadmap drawn in a boardroom but a sequence of honest questions from the people using it. If we're tracking the check, why aren't we tracking the equipment it's for? If the report says work is needed, why am I retyping it into a job? If the certificate already says the next due date, why am I typing that in as well?
Each answer became a module. The location model was rebuilt as a proper property model so everything could hang off it consistently. Assets became a real register. Planned maintenance arrived, then jobs, then risk, notes, reporting, organisations and departments. Most recently the document layer: safety sheets and engineer reports read automatically into structured records, with remedials that become jobs in a click.
The platform is still built that way. Support and development are the same team, so a problem raised from a site on Monday reaches the person who can fix it, not a queue.
Catolyst is a UK development house building bespoke platforms end to end — front end, API, database and infrastructure. PriComp is its property compliance product: the same engineering standards, applied to one problem rather than to a client brief. That means the people who designed the data model are the people who answer the phone.
Compliance software carries a particular obligation: it becomes the record. These are the rules that follow from taking that seriously.
Deletion is always soft. A retired record leaves the list but keeps its history — because an audit trail with gaps in it isn't one.
If the dashboard, the export and the register disagree about what “compliant” means, the system is worse than a spreadsheet. Each figure has one definition, in one place.
AI extraction fills forms and flags actions. It never writes to your compliance position unreviewed, and we'll always tell you what it's doing.
Database changes are recorded as dated migrations and applied once. Nothing alters the shape of your data without a written record of it.
Curated regression suites run on the front end and the API on every change. A feature isn't finished until its test exists and passes.
Background work sweeps, retries and recovers on its own. A system that needs someone to notice it has stopped has already failed.
“The best compliance system is the one that makes the awkward question boring to answer.”
No qualification call, no discovery funnel. Tell us the shape of your estate and what's currently going wrong, and you'll get a straight answer — including “this isn't a software problem” where that's the truth.