Capability Overview · Investment Operations

One governed engine.
Every operations process.

The Digital Analyst reasons over the evidence like a person, on an exact and auditable code core, with your experts in control. We built that engine once — so onboarding a new process is configuration, not a rebuild.

6 processes live · one engine · zero core changes · every finding gate-scored
A new category

Not a tool. Not a hire. A new kind of analyst.

Until now there were two ways to get work done. This is the third — which is why capacity is no longer tied to headcount.

Tool · you operate it

Excel, OMS, RPA

Deterministic and exact — but no judgment, and capacity is fixed by licences. Rules break the moment a case needs interpretation.

Employee · you manage it

Analyst / ops team

Judgment and context — but capacity is bound to headcount, it doesn't scale, and consistency is hard to audit.

Digital Analyst · you govern it

Powered by agentic AI

Judgment on an exact, auditable core — managed like a person, scales like software. Onboarded in days, then cloned across every book.

The platform

Build once. Configure for any process.

We didn't build six tools — we built one governed engine and configured it six times. The engine is fixed and proven; a new process changes only the configuration layered around it, never the core.

Built once · reused

The engine

The same core powers every process — never re-engineered for a new one.

  • Deterministic core — the exact work: calculations, validations, lookups
  • Agentic reasoning — classification, diagnosis and judgment over the evidence
  • Human-in-the-loop — the system proposes; your expert signs off
  • Audit & evaluation — every run logged, every finding gate-scored
Configured per process

A pack

Everything specific to one process — supplied as configuration, on the unchanged engine.

  • Taxonomy — the data it reads, and how each feed is recognised
  • Rule library — the checks, and how each finding is judged
  • Escalation owners — who each finding is routed to
  • Pipeline — the deterministic + agent stages, declared not coded
  • Gate-scored test set — proof it catches what it should
Worked example · added with zero core changes

Client Onboarding & KYC went live as a pack: a watchlist + applicants taxonomy, a seven-rule library (sanctions, PEP, adverse-media, CDD completeness, beneficial ownership…), Compliance / MLRO and Onboarding Operations as escalation owners, a screen → adjudicate → report pipeline, and a gate-scored dataset — every planted issue caught, and a look-alike sanctions hit correctly cleared as a false positive. The core engine was not touched.

How it's governed

Judgment from AI, certainty from code, control from people

AI on its own isn't auditable; code on its own can't reason. Together — with oversight — they make a digital analyst you can actually trust.

1

Deterministic core

The exact, repeatable work — calculations, validations, lookups, thresholds — stays in code, so it is always correct and fully auditable.

2

Agentic reasoning

Everything that needs interpretation — classification, diagnosis, decisions, free text — is handled by AI agents that reason over the evidence.

3

Human in the loop

People review, approve and escalate. The system proposes; the expert decides. Nothing material clears without sign-off.

A way of working

The same five-step pattern, whatever the process

Every pack runs this same pattern on the same engine — only the configuration differs. That's why a new process is days of setup, not a build.

01

Ingest & validate

Pull data from source systems and confirm it is complete and well-formed.

02

Detect & analyse

Scan for anomalies, breaches and gaps — exact checks plus judgment.

03

Diagnose & decide

Group findings, reason to root cause, and propose the resolution.

04

Act & report

Produce the fix, the audit trail and the report — for human sign-off.

05

Monitor & learn

Track issues until resolved; carry context forward across the cycle.

Proven, not promised

Six processes live — each a configuration, not a rebuild

Every one of these was added to the same engine as a new pack, with zero changes to the core — and each ships with a gate-scored test set. Run any of them end-to-end.