Before you hire for it, automate it.
For trust companies, family offices and funds in Europe.
Pick a job that today needs a person, a spreadsheet and an inbox. See it run as an automated flow, and where a human still approves. Fictional firms, example data — no prices, no real clients.
Alarifa · We build the flows around the systems you already use. No new platform to buy.
Example · a fund administrator’s COO
A week before. A week after.
Harbour Lane Fund Services is a fictional firm. This is an illustration of what changes, not a client story or a measured result.
Pick a scenario · examples
Four jobs that usually mean another hire.
Scenario 01 · Inbound request handling · Example
Harbour Lane Fund Services
Fictional firm. What this job looks like before and after it becomes an automated flow.
- One person reads the shared inbox all day
- Requests forwarded by hand, chased by hand
- Open items tracked in a spreadsheet
- Nobody sees what is late until a client asks
- Every request lands in one queue with an owner and a status
- AI sorts, summarises and routes each request
- Replies are drafted from approved sources
- A person approves every reply before it goes out
The flow, step by step
Click a step: what runs by itself, what a person approves.
Views
What the team sees.
Inbound requests — Harbour Lane (example)
| Request | Type | Owner | Status |
|---|---|---|---|
| Copy of quarterly statement | Statement | Client service | Draft ready |
| New bank details | Change of details | Operations | Human check |
| Capital call question | Question | Fund accounting | With owner |
| Complaint about a delay | Complaint | Head of client service | Must stay human |
Draft reply (example)
Dear Ms Example, please find attached the statement for the last quarter, as requested.
Sources: statement archive · approved template “statement request”
What stays human — and why
| Activity | Keep human? | Reason |
|---|---|---|
| Sending any reply | Yes | A named person approves |
| Changing bank details | Yes | Fraud risk; call-back check |
| Answering complaints | Yes | Judgment and tone |
| Labelling and routing | Automate | No decision on the client |
Want this flow in your firm?
Start with one process. Then we run and extend it with your team.
Scenario 02 · Client and partner reporting · Example
Calder Wealth Partners
Fictional firm. What this job looks like before and after it becomes an automated flow.
- Each period someone copies figures from portals into a spreadsheet
- The pack is rebuilt by hand every time
- Different versions of the same number
- The path from source to report lives in one person’s head
- Figures are pulled from named source systems on a schedule
- Each figure shows where it came from
- Mismatches are flagged for a person, not guessed
- The pack goes out only after a person approves it
The flow, step by step
Click a step: what runs by itself, what a person approves.
Views
What the team sees.
Source map — Calder (example)
| Figure | Source system | Pulled | Status |
|---|---|---|---|
| Positions | Custodian portal | Scheduled | Matched |
| Cash balances | Accounting system | Scheduled | Exception |
| New accounts | CRM | Scheduled | Matched |
| Fees | Billing spreadsheet | Manual | To automate |
Exceptions to resolve (example)
- 01Cash differs between two sourcesOpenCustodian vs accounting · reviewer decides
- 02Account missing from CRMResolvedAdded by operations, re-run
Partner report — draft (example)
Positions custodian portal
Cash exception open
Commentary drafted for the analyst to edit.
Want this flow in your firm?
Start with one process. Then we run and extend it with your team.
Scenario 03 · Client onboarding with KYC · Example
Meridian Trust & Corporate Services
Fictional firm. What this job looks like before and after it becomes an automated flow.
- Analysts chase ID documents by email
- Entities and UBOs drawn by hand for every structure
- Risk rating lives in a spreadsheet
- Approvals happen in email threads
- Missing documents are chased with drafted reminders
- The structure and its UBOs are mapped from the documents for review
- Every step has an owner, a system and a log
- Client acceptance stays a human decision
The flow, step by step
Click a step: what runs by itself, what a person approves.
Views
What the team sees.
Client onboarding — Meridian (example)
| Step | System | Owner | Note |
|---|---|---|---|
| KYC pack request | Email + shared drive | KYC analyst | Manual chase |
| Sanctions / PEP | Vendor A | KYC analyst | Tool |
| Risk rating | Spreadsheet | Head of KYC | Human decision |
| Approval | Email thread | Compliance | Must stay human |
Structure chart — draft (example)
| Entity | Role | Source document | Status |
|---|---|---|---|
| Example Holding S.à r.l. | Client | Register extract | Confirmed |
| Example Family Trust | Shareholder | Trust deed | Analyst check |
| Ms A. Example | UBO | Passport + register | Confirmed |
| Mr B. Example | Controller | Board minutes | Missing document |
What not to automate — and why
| Activity | Keep human? | Reason |
|---|---|---|
| Final client acceptance | Yes | Supervisory sign-off; audit trail |
| Override of risk rating | Yes | Second-line judgment |
| Chasing missing ID documents | Candidate | Reminders only; no decision |
| Packaging the KYC file | Candidate | Draft for analyst review |
| Exporting logs for audit | Automate assist | Read-only pull; human requests |
KYC file — Meridian (example)
Why now · for trust and company service providers
AMLR applies from 10 July 2027.
The EU anti-money-laundering regulation sets one rulebook for obliged entities. This is background, not legal advice.
A fixed start date
Regulation (EU) 2024/1624 applies from 10 July 2027 for most obliged entities, including trust and company service providers.
Art. 90, Regulation (EU) 2024/1624 · EUR-LexTrust and company service providers are in scope
They are listed as obliged entities.
Art. 3, point (3)(c), Regulation (EU) 2024/1624 · EUR-LexA regulation, not a directive
It is directly applicable in all Member States, so the same rules apply across the EU.
Art. 90, Regulation (EU) 2024/1624 · EUR-LexWant this flow in your firm?
Start with one process. Then we run and extend it with your team.
Scenario 04 · Client-facing mobile app · Example
Northbank Trust
Fictional firm. What this job looks like before and after it becomes an automated flow.
- Clients email to ask where things stand
- Staff answer status questions by phone
- Documents arrive as attachments in personal inboxes
- Someone retypes what the client sent
- Clients see status and next steps in an app
- Documents are uploaded once and checked for completeness
- Requests from the app join the same queue
- Staff approve; the app never decides for them
The flow, step by step
Click a step: what runs by itself, what a person approves.
Views
What the team sees.
Your file
Next: staff check your proof of address
The one on file has expired.
App requests — Northbank (example)
| Request | From app | Owner | Status |
|---|---|---|---|
| Proof of address | Upload | Onboarding | Complete |
| Passport (expired) | Upload | Onboarding | Reminder drafted |
| Statement request | Request | Client service | With owner |
What the app never does
| Activity | In the app? | Reason |
|---|---|---|
| Accepting a client | No | Human decision, recorded |
| Changing payment details | No | Call-back check by staff |
| Showing status and next step | Yes | Same data staff see |
| Uploading documents | Yes | Checked, then reviewed |
Want this flow in your firm?
Start with one process. Then we run and extend it with your team.
Hire vs automate
Before you hire for it.
| Hire for it | Automate it first | |
|---|---|---|
| Who does the work | A new person, trained on your way of working | A flow that runs on your systems; your team approves |
| When someone is away | The work waits or someone covers | The flow keeps running; approvals go to a named deputy |
| Seeing what is late | Ask the person, check the spreadsheet | Every item has an owner and a status |
| What your regulator sees | Emails and personal notes | A log of every step and every approval |
| When volume grows | Hire again | Extend the flow; people keep the decisions |
No numbers here on purpose: what fits depends on your process. That is what the first call is for.
What to expect
Here’s what better looks like.
A clear scope
One process at a time, agreed before work starts, with each step and its owner marked from the first call.
Full transparency
Every step of every flow is logged, and every finding shows its source.
One accountable person
You work directly with Evgeny Goncharov, who signs every report.
A human always makes the decision
Flows prepare, sort, check and draft. They end in “submit for approval”, never in a decision.
Who it is for
For the professionals who sign off.
You run the work. We find what runs by itself.
A map of which jobs can become automated flows, and a plan with owners.
See the scenariosYou sign the numbers. We make every figure traceable.
Reports built from named source systems, with exceptions flagged for a person.
Client reportingYou answer to the regulator. We write down what stays human.
A register of what not to automate and why, reviewed with you before anything is built.
Onboarding and KYCYou answer the clients. We take the inbox off your desk.
One queue for every request, drafted replies, and a person approving each one.
Inbound requestsBefore you hire for it, check what can be automated.
One process first, then a flow your team runs and extends with us.
How we workYou back the company. We check its technology.
Pre-deal technology due diligence on one target company.
Due diligenceAI in your operations, without losing control.
For trust companies, family offices and funds in Europe. The first step is a 20-minute call.