I build compliance functions that don't stop the business.

From nothing, licensed across borders, with AI doing the gathering and people doing the judgement.

Farhad ChowdhuryLondon → Dubai · 20 yrs
Now

Head of Risk & Compliance

Cross-border payments across Africa, the UK and Canada. Building the risk and compliance function up from close to nothing, with a small team. Licensing included, which takes longer than anyone expects.

Dubai · 2025—
What I do · 01

Ground-up builds

A function where there isn't one. Framework, controls, operating model, people, while the product is already live and taking customers.

Four so far
What I do · 02

Global licences

Regulated in more than one place at once. Applications, supervisors, board attestation, and the awkward questions before the regulator asks them.

UK · EU · UAE · US · Africa · Canada
What I do · 03

AI that earns its place

Pointed at the gathering, never the judgement. Done properly it takes cost out and lifts quality at the same time.

40%+ efficiency gain
Why AI belongs in this function 80% gathering 20% judgement

AI is very good at the first part. Nowhere near the second.

Scale I've worked at
24mcustomers monitored 1m+alerts a month

Big teams did that, I was one part of it. I've also been the whole function alone at a startup. Most guidance is quietly written for the first case.

How I got here

I flagged a payment I couldn't explain

First job, payments officer. Something looked wrong and I had no idea why.

Where I've done it
2025—Head of Risk & Compliance
2023—25UK MLRO, Africa oversight
2021—23Head of Financial Crime, consulting
2019—20Deputy Head of Financial Crime
2017—18MLRO, board level
Build spec · free, no sign-up

Regulatory Horizon Scanner

Under two hours a week. If it takes longer, your scope is too wide.

The week's regulator output, one page. The model gathers, a human tiers. Full spec, copy it and change it.

Read the spec →
Also building

KYB Triage Assistant

Local · Oct

Fuzzy-Match Playground

Synthetic data · Nov

MLRO First 90 Days

Checklist · Nov
Free course · no sign-up · 5 modules

Learn KYC properly

Trading Co Holdco A Holdco B Person 1 Person 2 Person 3 60% 40% 30% 30% 65% = 18% = 18% = 26% Lesson 04 · only one of them crosses 25%, and it isn't the obvious one
Start with module 1 →
Modules 2–5

KYC in Practice

Document matrix, a worked file, a threshold sandbox, and what actually gets you promoted.

Open →
Interactive map

What a compliance and financial crime framework actually looks like

Thirty components across three lines, governance and the enablers underneath. Click any one for who owns it, day one against at scale, and how it fails. Twenty five you need from the start. Five can wait.

Open the map →
Watch first

Two short films, then the tools they are about

One on the whole operating model. One on the free KYC course. Both under forty seconds.

Film 01 · 37 seconds

What a compliance framework actually looks like

Governance on top, three lines holding it up, enablers underneath. Thirty components, and only five of them can wait until after day one.

Open the interactive map →
Film 02 · 34 seconds

The free KYC course, in 34 seconds

Thresholds you move yourself, a document hunt, an ownership chain you unpick. Five modules, no sign-up, no email.

Start module 1 → Modules 2–5
Follow along in Farhad Chowdhury

Three posts and one video a week. Where AI actually helps, rather than just sounding good.

Posts

Nobody missed the rule

Operating model

A risk-based approach is a testing schedule, not a policy

AML/CFT

Your fuzzy-match threshold is a business decision

Sanctions
Things I believe

Compliance should not be the reason nothing ships. A function that can only say no has failed at its job. The work is building one that can say yes quickly, for the right things, and evidence why.

Say hello
so what do you actually do?
I build the risk and compliance side of banks and fintechs. Usually from nothing.
like the people who say no?
like the people who work out how to say yes without breaking the law. and get you licensed while we're at it

Standing up a function, chasing a licence, or you think one of my specs is wrong. The useful messages tell me what broke.