The file takes a day. The decision takes ten minutes.
We read client onboarding and periodic review files inside your own environment: structure charts, ownership chains, source-of-wealth evidence. Your analysts get a cited answer instead of a stack of PDFs.
- Beneficial owner p. 14
- Natural person, 74%
- Ownership chain p. 3–22
- Four layers, two jurisdictions
- Source of wealth p. 31
- Matched to evidence
One branch unresolved · stated, not guessed
Software only. Your documents never leave the environment you choose, and nothing you process trains a model.
- Where it runs
- Your cloud, your servers, or air-gapped
- Data leaving your tenant
- None
- Acceptance criteria
- Scored on your own documents
- Pilot
- Four weeks, paid, contractual
A single onboarding file takes most of a day, and almost none of it is judgement.
The decision is not the hard part. The reading is.
- 01
Ownership charts arrive as scans. Someone redraws them by hand to work out who actually owns the entity.
- 02
A beneficial ownership chain runs through four jurisdictions and two languages. Tracing it is a spreadsheet, an email and a wait.
- 03
A source-of-wealth claim sits in one document. The evidence for it is spread across eleven others.
- 04
Something in the file expired months ago. Nobody notices until the inspection does.
- 05
Periodic review arrives and the whole exercise starts again, on a file that barely changed.
This is the work regulators inspect most closely, carried by the people with the least time to do it.
It reads the file. Then it shows you where it read it.
One workflow, done to an audit standard: client onboarding and periodic review. Not a platform you have to configure into existence first.
- In01
Ingest
Point it at the folder, the shared mailbox or the document system you already use. Scans, phone photographs and native PDFs all go in.
- Read02
Extract
Entities, ownership percentages, dates, jurisdictions and document types come out as fields you can query and export.
- Follow03
Trace ownership
Each holding layer is followed until it reaches a natural person, or until the evidence runs out. Where it runs out, it says so rather than guessing.
- Check04
Match the evidence
Every source-of-wealth claim is matched to the documents that support it. Claims with nothing behind them are named.
- Out05
Flag the gaps
Missing, expired and contradictory documents come back as a list, each one with a reason and a page reference.
- Applicant entityDIFCp. 3
- Holding companyCayman Islandsp. 11
- Nominee holdingJerseyp. 22
- Natural personBeneficial ownerp. 14 §3
- Second branchUnnamed holderEvidence runs out
Every field carries its source.
A page reference on every answer and an append-only log of every question asked. When an inspector wants to know how a conclusion was reached, the trail is already written.
Screening tools match names. They do not read documents.
You almost certainly own a screening stack already. It is not the thing costing you the week.
- Names checked against sanctions, PEP and adverse media lists
- Lists refreshed, alerts raised, cases queued
- Ongoing monitoring of existing relationships
- Case management and an audit trail for those alerts
- Reading corporate structure charts out of scanned documents
- Tracing ownership through holding layers to a natural person
- Matching source-of-wealth claims to the evidence behind them
- Checking whether a file is complete and still in date
- Repeating all of it at periodic review
We do not replace your screening provider, and we will say so in front of your procurement team. We take the reading off your analysts' desks.
Use your own numbers.
Four inputs, one hourly rate, the published price band. Every figure below is one you can reconstruct on paper, and nothing you type here is sent anywhere.
Onboarding and periodic review together
Reading, tracing and chasing documents, not the decision itself
Salary, benefits, desk and licences. One year, one analyst.
The only claim in this model. Pull it down if you think we are optimistic.
One analyst-year is taken as 1,700 productive hours, net of leave and everything that is not file work. The licence band follows document volume, exactly as published below.
$168,988
Against a year-one cost of $55,000, at your volume band.
- Analyst hours a year on reading
- 4,320hours
- What that reading costs you
- $241,412
- Hours returned a year
- 3,024hours
- Analyst capacity returned
- 1.8analysts
- Hours back on every file
- 4.2h / file
- Payback
- 3.9months
- Annual licence, your volume band
- $40,000
- Implementation, once
- $15,000
- Year one total
- $55,000
- Net in year one
- $113,988
- Net every year after
- $128,988
Indicative. At pilot close these estimates are replaced by measured figures from your own documents.
Three ways to deploy. All of them inside your perimeter.
You are not buying access to our environment. You are installing software in yours.
Your cloud tenant
Azure UAE North or AWS Middle East, inside your own subscription. Your keys, your logs, your invoice from the cloud provider.
Two weeks, typically.
Your own servers
Installed on hardware you already run, behind the firewall your auditors have already looked at.
No new supplier in your data centre.
Fully air-gapped
No outbound network at all. You buy the hardware directly from your distributor; we install, verify and hand over.
We do not resell hardware.
- 01
Your documents never leave the environment you chose.
- 02
Nothing you process trains a model, not ours and not anyone's.
- 03
Model weights are permissively licensed with documented provenance, and every component is named in writing.
Everyone else runs a demo. We hand you a score.
Before a pilot begins we build an evaluation set out of your own documents. It becomes a schedule to the contract, which means “good enough” is defined in writing before anyone starts building.
- 01
We build the set with your expert
During discovery we extract 100 to 200 question and answer pairs from your real files. Your subject-matter expert signs off on the answers, not us.
- 02
It becomes the acceptance criteria
The signed set is attached to the contract. There is no later argument about whether the system works, because the definition was agreed before the work started.
- 03
You get the report at pilot close
Accuracy against the signed set, median time per file, and the share of answers carrying a page-level source. Pass or fail, you see the same numbers we do.
- Accuracy against the signed set Your threshold, set by you
- Answers carrying a page-level source Reported per question type
- Median time per file Measured against your baseline
The security review, answered before you ask it.
Enterprise deals rarely die on product quality. They die in the security questionnaire, six weeks at a time. Ours is already written.
Anyone who has to prove they read the file.
It began with regulated firms in the DIFC, where the inspection is closest and the data rules are strictest. The workflow travels to any organisation whose evidence has to survive an audit.
Private banks and wealth managers
Onboarding files thick with cross-border structures and source-of-wealth narrative.
Family offices
Small teams carrying institutional obligations, with no capacity for a week of reading.
Asset and fund managers
Investor onboarding at volume, plus a periodic review that never quite gets scheduled.
Corporate service providers
Company formation and administration, where the structure chart is the product.
Insurance and reinsurance
Broker and cedant due diligence spread across documents nobody owns.
Banks and payment institutions
High-volume onboarding where the queue, not the decision, is the constraint.
Law firms and audit practices
Client due diligence assembled under professional obligation and time pressure.
Regulated firms across the Gulf and beyond
ADGM, Saudi Arabia and any jurisdiction whose regulator asks how you reached the conclusion.
- You have no compliance function and no inspection to prepare for.
- Your policy already allows client documents in public cloud and price is your only question.
- You want a general-purpose assistant rather than one workflow held to an audit standard.
Published, because you were going to ask.
Anchor it against one compliance analyst. The licence sits below the fully loaded cost of the person whose reading it takes over. That is the entire business case.
- Annual licence
- $40,000 – $80,000
- Per firm, three-year term. The band follows document volume and user count.
- Implementation
- $15,000 – $25,000
- Fixed fee, year one. Deployment, connectors, the evaluation set and handover.
- Paid pilot
- $12,000 – $15,000
- Four weeks with written acceptance criteria. Credited against year one if you proceed.
- Additional connectors
- Quoted per system
- Annual, per module. Priced once you name the system it has to reach.
- Connectors to your document store, mail and case system
- An evaluation set built from your documents and signed by your expert
- Audit log, single sign-on and role-based access wired to your directory
- Workflow and model updates, quarterly
- The assurance pack, kept current
- Support under the written SLA
There is no free pilot.
A pilot with no invoice has no owner, no sponsor and no closing date. Yours has all three, plus criteria you signed.
US dollars, excluding tax. Where you choose an air-gapped deployment the hardware is bought directly from your distributor. We do not resell it and we do not mark it up.
Four weeks from the first call to a scored report.
No procurement marathon to reach the point where you can actually judge it.
One conversation
How many hours does a single file take, where does it stall, and what did your last inspection flag. We listen. There is no demo in this meeting.
Evaluation set and target
We build the question set from your documents and your expert signs the answers. The deployment target and the acceptance threshold are agreed in writing.
Live in your environment
Deployed where you chose, connectors running, analysts using it on real files rather than on a sandbox we prepared.
The score and the evidence pack
The measured report against your signed set, plus the compliance evidence pack. You decide with numbers in front of you.
What procurement asks first.
Bring the file that takes longest. We will read it with you.
Thirty minutes with the engineer who builds it, not a salesperson. You will know inside that half hour whether it is worth a pilot.