Why I built Compliance OS
Symmorphosis started with a frustration I knew from my own compliance work: the hardest part was still left to us.
KYC checks, screening and AML workflows matter. But they are only part of the job. There is also the work of understanding which rules apply to a particular firm, what those rules require, and how to connect them to controls, reporting and everyday decisions.
That was the gap I wanted to address. A place for the wider compliance picture, with the firm's context connected to the work that follows.
Compliance OS is the tool I wanted on the other side of my own desk.
Giving AI maintained regulatory context
AI changed what felt possible. It could help us read, question, compare and reason through complex material. But a capable model still needs context: the firm, its activities, the relevant sources and the questions that remain unresolved.
The ambition behind Symmorphosis is simple: less time rebuilding that context in every conversation. More time using it.
Through the Compliance OS connector, a compatible AI client can retrieve structured company context, profile questions, obligations, controls and source references. The aim is to make the AI you already use far more useful for the work you actually do.
The connector makes recorded company facts and regulatory requirements available for retrieval during an AI conversation, so the professional can review the analysis against that context.
This approach centres on maintained context rather than custom model training for each firm. AI helps with the analysis. The compliance professional brings judgement, reviews the evidence and confirms the outcome.