Choosing the process
Together we pick the process that repeats most often, has a clear definition of "done" and has its data in your systems. We define what the AI does on its own and what it does only after a person approves.
KYC documents after an Onfido or Sumsub check, customer enquiries, complaints and reports to the financial regulator: in a financial firm this is a daily flow with strict rules. We implement private AI that prepares, cross-checks and saves a draft in Dynamics 365 or Salesforce, while a person makes the decision. Everything is logged and data stays in the EU, in line with GDPR and DORA.
Built for ISO 27001NIS2 DORA
Payment institutions, e-money institutions, credit unions and consumer lenders get the same thing every day: the customer passes the identity check through Onfido or Sumsub, but a compliance officer still compares their business register extract, proof of income and beneficial owner declaration by eye and retypes them into the customer record in Dynamics 365 or Salesforce. Customer service answers questions about a payment status that the core system already knows. Complaints reach the register in SharePoint from a shared Outlook inbox on Monday, although the deadline started on Friday. At the end of the quarter, the finance team collects the report for the financial regulator from Sage and the core system into Excel. Every retyping costs an hour and leaves room for an error that an audit will find.
Here AI takes over the preparatory work: it extracts the fields from documents and cross-checks them against the Onfido or Sumsub result and the CRM record, answers customers' standard questions from core system data, classifies complaints and incidents against your register in SharePoint, finds the rule for an employee with its source, and assembles a draft of the report for the financial regulator from Sage and the core system. We implement with Claude, Microsoft 365 Copilot and ChatGPT, and for customer data we use private AI: models in the MDP CLOUD GPU cloud in Lithuania (EU) or Amazon Bedrock in an EU region. We connect to your systems through an API, a file export or an email flow, depending on the version. The first step is always the same: role-based access, data location in the EU, a log for audit and the regulator, and a clear boundary: the final decision about a customer, a loan or a complaint is made by a person.
The 5 solutions we implement most often in this industry. Each one starts with a single process, has a human approval step and is measured.
The customer passes the identity check through Onfido or Sumsub and sends a company register extract, proof of income and a beneficial owner declaration. A private model extracts the fields, cross-checks them against the check result and the customer record in Dynamics 365 or Salesforce, and flags expiry dates and mismatches. The compliance officer sees the prepared record with notes and makes the decision personally.
We implement: Private model in a Bedrock EU region + Onfido / Sumsub and Dynamics 365 or Salesforce integration
A customer asks by email or in the self-service portal where their payment is, what their limit is and how much a transfer costs. After the identity check, the assistant pulls the status from the core system with read-only access and answers according to your rules. A dispute, a suspicious transaction or a question about credit terms is passed straight to an employee as a ticket in Dynamics 365 or Salesforce with a conversation summary.
We implement: Claude agent via API + core system and Dynamics 365 or Salesforce integration
A complaint arrives in a shared Outlook inbox, and an ICT incident report arrives from monitoring overnight. A Power Automate flow passes them to the model, which assigns a category, severity and deadline according to your complaints procedure and the DORA criteria, checks for duplicates and creates a record in the SharePoint register marked "awaiting approval". A person approves the classification and decides whether to notify the financial regulator.
We implement: Claude via API + Power Automate flow into a SharePoint register
A relationship manager asks in Teams what the early termination fee is for a business customer or when enhanced due diligence applies, and gets a quote with a link to the current version of the document in a SharePoint library. The assistant sees only the documents the employee can see under their Entra ID permissions, and if a document does not exist, it says so instead of guessing.
We implement: Copilot Studio agent for SharePoint documents in your Microsoft 365 tenant
Before a report to the financial regulator, the finance team exports balances from Sage, payment volumes from the core system and the incident count from the register. AI puts the data into your report template, calculates the indicators using the documented formulas and flags fields where the systems disagree or data is missing. Finance and compliance managers review, correct and approve, and they submit to the financial regulator themselves.
We implement: Claude via API + read-only data from Sage and the core system
From the first conversation to a working solution, with measurement and ongoing support.
Together we pick the process that repeats most often, has a clear definition of "done" and has its data in your systems. We define what the AI does on its own and what it does only after a person approves.
We put access to files and systems in order, give the AI its own identity with the least privileges it needs, turn on an action log and choose where the model runs: your Microsoft 365, Amazon Bedrock in an EU region or our GPU cloud in Lithuania (EU).
We build the solution with Copilot, Claude or ChatGPT, whichever fits the task, connect it to your systems and test it on historical documents and enquiries until accuracy reaches the agreed threshold.
We launch with a person in the loop, review the logs and exceptions and adjust the rules. Once the first process runs reliably, we move on to the next one on the list.
These solutions are a starting point for a conversation, not a complete list. Tell us which processes repeat in your company, and in one conversation we will tell you what is worth handing to AI and what is not.
An AI solution is an ICT service, so we add it to your register of third-party providers with a contract, SLA, data location and exit plan, as DORA requires. The implementation documentation covers a risk assessment, access management and logs, so that you have something to show the supervisor.
Yes, but we choose the integration method after a check. We take the Onfido or Sumsub result through the API or from the reports they send, and we connect to Dynamics 365 and Salesforce through an API, a file export or an email flow, depending on your version and licences. Access to the core banking system is read-only and limited to agreed queries.
No. AI cross-checks documents, prepares a record with notes in Dynamics 365 or Salesforce and suggests a classification, but KYC approval and credit and complaint decisions are made by an employee, and their action is logged. This keeps the accountability and traceability that supervisors require.
Reception calls, record summaries from Cliniko or CGM and the national e-health system, insurer and health insurance billing documents, internal…
The value of AI depends not on the platform but on which processes in your industry repeat.
Market reviews from Bloomberg Terminal and LSEG Workspace, prospectuses, client reports built from Euroclear and Excel data, compliance documents…
Contracts are reviewed by hand in Word, case material is hunted down across Clio and SharePoint folders, and hours are entered from memory in the…
This service is delivered by specialists with valid international certifications. Their expertise is confirmed by independent organisations, not by us.
AI systems are deployed with protection against data leakage and model abuse.
The AI security programme and its controls are managed following the ISACA methodology.
AI risks are identified and managed like any other IT risk.
We reply within 1 business day