UNUS London exists because every regulated organisation in the UK faces the same structural problem — they have compliance policies, but they cannot evidence compliance when it is demanded. The solution is not a better policy document. It is infrastructure that makes evidence automatic.
The problem that created UNUS London is not complicated to describe. Regulated organisations are required to evidence compliance. Almost none of them can. When a regulator arrives — an SRA inspector, an FCA supervisor, a CQC assessor — what is typically produced in response to their questions is a collection of documents, spreadsheets, and folder structures that were never designed to be interrogated under pressure. The evidence is inconsistent. The records are incomplete. The outcome is a finding that could have been avoided.
Meshach McKenzie observed this pattern across multiple regulated sectors and drew a conclusion that most compliance consultants resist: the problem is not a training problem, a process problem, or a policy problem. It is a systems problem. Organisations without governance infrastructure will fail to evidence compliance regardless of how well their people understand the regulatory framework, because there is no system producing evidence automatically and immutably.
The conventional response to compliance failure is to commission a consultant to write a new policy, run a training session, or implement a generic software tool. None of these address the root cause. A policy document cannot produce evidence on demand. A training record does not generate an audit trail. A SharePoint folder is not a compliance system.
UNUS London was founded on a different premise: that compliance infrastructure must be built at the database level, where enforcement is structural rather than procedural. When the compliance rule is encoded in a PostgreSQL trigger, it cannot be bypassed by oversight, convenience, or time pressure. The audit trail is immutable because the database makes it so — not because someone remembered to update a spreadsheet.
This is not a theoretical position. Every system UNUS London builds has been deployed in a production environment for a real regulated client. The SRA Supervision Register enforces the self-supervision prohibition at the trigger level. The Client Matter Checklist Engine blocks closure until every required step has been completed. The SRA Readiness Report Generator produces audit-ready evidence on a weekly schedule without human intervention. Evidence is not gathered when the regulator arrives. It has already been generated, timestamped, and stored — continuously, automatically, without anyone having to think about it.
The name UNUS — Latin for one — reflects the founding principle: one infrastructure layer, one source of truth, one audit trail. All compliance evidence flows from a single, structured, immutable record. There are no parallel spreadsheets. No conflicting versions. No question about which document is current. The database is the record, and the record is always correct.
Understanding what UNUS London declines to be is as important as understanding what it builds. These distinctions are not marketing positions. They are the consequence of a firm belief about what actually closes the compliance evidence gap.
Every UNUS London engagement follows the same disciplined approach — from regulatory obligation to production system. The sequence is non-negotiable because every step depends on the one before it.
Every system deployed by UNUS London is aligned to one or more of the following regulatory frameworks at the clause level. Alignment means the specific database constraint, trigger, or workflow node is traceable to the paragraph it enforces.
I built UNUS London because I kept watching the same thing happen to good organisations. A regulator arrives. The people in the room understand their regulatory obligations perfectly. But they cannot produce the evidence to prove they have been meeting them — because no system was ever built to generate that evidence automatically.
The outcome is always the same. Findings are raised. Conditions are imposed. Reputations are affected. And the organisation goes back to writing a new policy — as though the problem was that the rules were not documented clearly enough.
The rules were not the problem. The absence of infrastructure was the problem.
Every system I build at UNUS London is designed to close that gap permanently. Not by describing what compliance looks like — but by building the infrastructure that makes compliance automatic and its evidence irrefutable. When the inspector asks for proof, the answer is already in the database. It has been there since the first record was written.
That is what I mean when I say evidence must be structural. And that is what every UNUS London system delivers.
A 60-minute discovery call with Meshach McKenzie identifies your compliance evidence gaps and scopes exactly what infrastructure will close them. No generic recommendations. No policy documents. A system — built and transferred.