Why we built this.
Because compliance shouldn't depend on whether the right person remembers where Robert Chen's suitability report lives. Or which Excel sheet logged a review date as 04/31/3036.
Our story
Amaea didn't start in a boardroom. It started in a spreadsheet - one that had a client's annual review date logged as 04/31/3036.
Hasna spent several years in financial services doing the work that compliance software was supposed to make easy: manually pulling data for Consumer Duty reports and board packs, trawling through folders to check whether a suitability report had been signed, cross-referencing dates across disconnected systems, and entering it all into a manual Excel sheet that nobody fully trusted.
The problem wasn't that firms were non-compliant. It was that they were doing everything right - and couldn't prove it. The work existed. The evidence didn't.
So Amaea was built around what firms actually need: a system that reads, classifies, and surfaces the evidence that was always there but never accessible. The work an experienced compliance officer would do if they had the time.
The result is a product that's easy to set up, easy to use, and actually solves the problem - not just makes it more visible. Amaea launches in 2028. We're currently working directly with IFA firms to make sure we get it right before anyone depends on it.
Who's building this
Why we exist.
To make regulatory compliance a property of systems, not a burden on people. For UK IFA firms.
A financial services industry where compliance protects every client and creates no burden for any firm.
What we stand for.
Four principles. Each one tested against the same question: would we make the same call on a Tuesday afternoon, when we're tired?
Cite the rule, always.
Every flag in the product carries its FCA reference. Every AI answer carries the source chunks it came from. If we can't show the rule, we don't ship the flag.
Refuse fabrication.
"I don't have a confident answer" is a first-class AI response. We'd rather log an honest "don't know" than ship a confidently wrong rule citation. A 50-scenario eval suite enforces it before every model release.
Default to the audit log.
Every flag, every read, every model call writes a row. If it isn't in the append-only log, it didn't happen. We built the log first and the product on top of it, not the other way around.
Build for the Tuesday afternoon.
Compliance work happens at 4pm Thursday with the FCA on the phone and three browser tabs open. The product has to work when the user is tired, interrupted, and unsure. If it doesn't work then, it doesn't work.