01The systems in the way
Core banking hands you overnight batch files. Company registries answer to a browser and challenge automated access. Regulator portals publish no interface at all. The CRM has a clean REST API, which is exactly the one system that was never the bottleneck. The result is an onboarding process where analysts spend most of their time re-keying between windows.
| System | What it gives you |
|---|---|
| Core banking | batch files |
| KYC portal | web only |
| Registry | CAPTCHA |
| Regulator portal | no API |
| CRM | REST API |
| Statements |
02Why the usual approaches stall
Vendors sell "AI onboarding" that assumes every source has an API. When one does not, the work quietly returns to a human, and the promised cycle-time saving never materialises. Meanwhile anything that automates a regulated check without an evidence trail is unusable the moment an auditor asks how a decision was reached.
If a human can do it in a browser or a terminal, an agent can do it — at volume, with an audit trail. That is the whole basis of how we approach financial services: we treat the systems you already run as the integration surface, rather than waiting for an API that is never going to ship.
03What an agent actually does here
Worked example
An onboarding agent gathers documents, cross-checks company registries and sanctions lists, drafts the KYC file, and routes only genuine exceptions to a compliance officer — with the source evidence for every field attached to the decision.
This is a reference design drawn from the problems we are asked about most often in financial services — not a case study of delivered client work. Where we have shipped a build, we say so plainly and put you in touch with the client.
04Constraints we design to
- Every extracted field carries a pointer to the document and page it came from
- Decisions are reversible and replayable; dry-run mode performs no writes
- Deployable inside your own tenant or on-premise where data cannot leave the institution
- Access is under your credentials, scoped to systems you are authorised to use, with written authorisation
Tell us which system is the problem
Describe the workflow that is done by hand today and the system that blocks it. We will come back within one working day with an initial read on feasibility — including if the honest answer is that an agent is the wrong tool.
Scope your agent →