Your company brain.
Built with you, owned by you.

use cases

Financial crime, judged on the whole relationship.

Every customer and supplier, on one current risk picture - each alert read against the whole relationship, the case assembled before the analyst arrives, and real risk lifted out of the queue rather than left waiting in it.

“Our analysts drown in alerts that go nowhere, and the real risk hides in the queue.”

§ 01 Is this you?

Is this you?

  • Most of the alerts your team works are closed as nothing, and each one takes as long to close as the last.
  • The same harmless pattern on the same account is cleared again and again, and every analyst starts from scratch.
  • Screening, monitoring and fraud each see their own slice of a customer, and nobody sees the whole relationship.
  • A new supplier, or a change of bank details on an invoice, is checked one payment at a time, if at all.
  • When something real turns up, the file is built by hand from four systems while the clock runs.

If two or more of these sound familiar, this is the use case to start with.

§ 02 Before and after

Before and after

today with a company brain
An alert fires It is judged on the transaction in front of it, by an analyst who has to go and find the rest. It is read against the account's own history and its past alerts, and arrives as a case with a recommendation and the evidence attached.
Weak signals arrive An adverse-media mention, a change in payment rhythm and new connected parties sit in three places, and none clears a threshold alone. They are put together on one record, and the case reaches the money laundering reporting officer with the file already built.
The same false alarm, again A cause cleared many times before is cleared once more, and the rule that raised it never changes. The pattern is spotted, and a change to the rule is proposed with its evidence, for a named owner to approve.
Who has the whole picture Every queue has an owner. The customer as a whole belongs to no one. One current risk picture for each customer and supplier, from onboarding to exit.
§ 03 What you would see

Illustrative: the shape of what you would receive, not a client's record.

What you would see

alert review

Alert: a large payment out of a long-standing business account

what it saw
A payment well above this account's usual size, raised by the size rule.
the history
The same payment to the same payee falls each quarter, and has been cleared each time with the cause recorded.
recommends
Close as a known, legitimate pattern for this account.
how sure
Sure of the pattern. The analyst confirms every close.
sources
The transaction, the account history and the earlier alert decisions, each linked.

recommend held for the analyst to confirm

case file

Three weak signals on one business customer

what it saw
An adverse-media mention, a change in the rhythm of payments, and new connected parties forming around one account.
why it matters
None clears a threshold alone. Together they are worth an investigation.
what it holds
The signals, the account history and how the parties connect, in the order an investigator reads them.
drafted
A suspicious activity report, ready for review.
how sure
Sure the signals connect. Whether they are suspicious is the reporting officer's call.

recommend held for the reporting officer's decision

tuning proposal

Detection rule: the same harmless cause, cleared again

what it saw
One rule keeps raising alerts on a cause that has been cleared every time it has been reviewed.
what it costs
A recurring share of the queue, each alert worked from scratch.
recommends
Tune the rule to recognise this cause, and keep a sample of it under review.
how sure
Sure of the pattern. The change is tested against past alerts before anyone approves it.
sources
Every alert the rule raised on this cause, and how each was closed.

recommend proposed to the rule owner as a recorded change

Every output says what it saw, why it matters, what it recommends and how sure it is, and links each fact to its source.

§ 04 How it works

How it works

  1. 01 it notices Alerts, screening hits, payment patterns, adverse media and changes to customer or supplier details, where they already arrive.
  2. 02 it connects Each one to the customer or supplier it concerns, their history, the parties around them and every past alert.
  3. 03 it judges Whether an alert is real risk or a cause already cleared, and when weak signals together are worth a case.
  4. 04 it checks Every action against your rules: who may see a case, and what needs a named person before it goes further.
  5. 05 it acts Within the permission you have granted: it recommends a close, builds the case, drafts the report, or proposes a tuning.

It reads from your screening, transaction monitoring, payments and case management systems. It does not replace them, and nothing is migrated.

§ 05 What it runs on

The parts of a company brain financial crime relies on, in the framework's own terms.

What it runs on

01The record
Every customer and supplier, their history, the parties around them and every past alert.
02Finding the answer
Each question answered with its sources, or a plain "I can't answer that well".
03The company manual
Your risk appetite, what each alert rule is for, and who decides an escalation.
04The way in for AI tools
How your people ask it from the AI assistant they already use, on the same permissions as everyone else.
05Connectors
Your screening, transaction monitoring, payments and case management systems.
06Who may see and do what
Who may see a case, checked before every answer. Cases stay with the people working them.
07Agents and actions
Building a case file or proposing a rule change, only through actions agreed in advance. Reports and freezes are never among them.
08Where people use it
Where the analyst confirms a close and the reporting officer decides on a report.
09Testing it on your own questions
Tested against your own past alerts and their outcomes before it is trusted.
the company brain keeping it trustworthy, under all of it your systems documents email, calendar business systems your ai tools your people namedsources checked,then kept checkedfirst read in your terms a question,and its answer approvals acting, througha second door 05 connectors 01 the record 06 who may see and do what 02 finding the answer 03 the company manual 04 the way in for ai tools 08 where people use it 07 agents and actions 09 testing on your questions 10 keeping it running 11 keeping every brain current 12 before anythingis built
The twelve parts of a company brain, with the ones financial crime runs on drawn in red. Read left to right: what comes in, what it knows, and who and what uses it.

what this shows about a company brain

It works through the AI tools you already use

Your people reach it from the assistant they already have, on the same permissions. They might ask:

“Has this payee been cleared before, and on what grounds?”

It compounds

It reads the same customer and supplier records as customer retention and supplier risk, so a risk signal is judged against the whole relationship, not a single queue.

It is yours

The record, the rules and the permissions it builds belong to you, not to a vendor: handed over to your team or run for you. The same company brain runs every use case you add.

§ 06 You stay in control

You stay in control

  1. observeIt reads silently and measures its own accuracy against what really happened.
  2. recommendIt puts the case and a proposed action to a named owner.
  3. draftIt prepares the action, and holds it for a person to sign.
  4. actIt acts within the bounds you set, and logs everything it does.

Each permission is granted or withheld, taken back as easily as it was given, and expires unless someone renews it. Everything starts at observe, and a permission is granted on the measured record, never on a promise. Every action is checked against your rules before anything goes out.

Suspicious activity reports, freezes, exits and every decision to escalate stay with a named person, permanently if that is your policy.

§ 07 Where it starts

Where it starts

first scope
One segment of the book, or one type of alert: the queue that costs you most to work.
how it proves itself
It runs at observe against your own past alerts and their outcomes first, so you see how it would have done before it is allowed to do anything.
what it connects to
The systems you already run: screening, transaction monitoring, payments, onboarding records and your case management tool. Connectors are built for you, as part of the work. How it connects.
what you own
You own the result: the risk record, the judgement rules and the permissions, handed over to your team or run for you.
§ 08 Questions

Questions

Does it replace our transaction monitoring or screening system?
No. It reads from them, and from the rest of the relationship they cannot see. Your detection stays where it is; the company brain gives each alert the context to judge it.
Which kinds of financial crime does it cover?
The ones you choose. It starts where the pain is: payment and invoice fraud, money laundering and customer checks, sanctions screening, or due diligence on the parties you deal with.
Who can see what?
Only what each person is allowed to see. Cases stay with the people working them, permissions are checked before every answer, and every question is recorded.
Will it file a report or freeze an account on its own?
No. Suspicious activity reports, freezes and exits wait for a named person to decide, and you can keep it that way for good.
Is this available today?
It is built for each company that runs it, on that company's own brain, not installed off a shelf. The question audit comes first and shows what it would and would not do for you before anything is built.
§ 09 Start

Start

try this on your own record

Take three past alerts: one that was real, one false alarm that cost a week, and one that surprised you late. What did your own records already know, and when did you find out?

Questions like this are what the question audit answers: about two hundred real questions from your business, each answered in writing, so you know what financial crime on a company brain would and would not do for you before anything is built. It is a small fixed fee, credited against the build or the service if you go ahead.

book a discovery call → take the diagnostic · 10 min (opens in a new tab)