Banking.
Acquire, personalise, and retain, on customer data that stays sovereign.
In retail and wealth banking, the contest is for the customer relationship: acquiring the right clients, personalising every interaction, and keeping them from switching. That runs on transaction and behavioural data, the most revealing signal a person emits, so the marketing and personalisation stack is exactly the one that cannot cross an extraterritorial border.
- R01Personalisation drifting into automated decisions under GDPR Art. 22 and consumer-duty rules
- R02First-party consent and lawful basis for cross-sell on transaction data
- R03Customer and behavioural data crossing extraterritorial jurisdictions (DORA third-party risk)
What's actually
reshaping the sector.
The shifts our research is tracking, named, current, cited.
DBS runs hyper-personalised nudges to customers and relationship managers as an always-on system, not a campaign, and the nudges to relationship managers alone drove a 16% lift in client engagement. That is the bar your customers are being taught to expect.
DBS Bank →McKinsey finds banks that centralise customer-value-based personalisation earn 5 to 15% higher revenue from campaigns, and shift the metric from products sold to retention and advocacy.
McKinsey →BBVA completed the global rollout of its ADA data-and-AI platform specifically to power generative-AI personalised customer services. The lesson: the personalisation is only as good, and as sovereign, as the data foundation beneath it.
BBVA →DORA (live since Jan 2025) + EU AI Act high-risk (2 Aug 2026) + FiDA make where your customer AI runs a board-level decision. Europe's largest banks have read it that way: they are already funding sovereign, CLOUD-Act-free alternatives for themselves.
Retail Banker Int’l →In banking, the customer relationship, not the core ledger, is where AI and sovereignty compound: personalisation runs on data too revealing to hand to a third-country model.
Win the customer on data a competitor can never see.
Retail and wealth banking growth is a personalisation problem now: acquiring the right customers, guiding the next best action, and keeping them from switching. Every one of those runs on transaction and behavioural data, the most revealing signal a person emits. A bank that lets that signal leave its perimeter has given away the one edge a rival cannot buy.
Personalise onboarding, cross-sell, and relationship management on sovereign, first-party data and you lift revenue and retention on the campaigns where a few points compound, without a transfer or consumer-duty problem. Run them on an opaque US API and you have handed a competitor the one signal that was yours alone.
We build the sovereign customer-data and personalisation stack: first-party acquisition, next-best-action, and RM copilots decisioned on EU compute, with frontier speed reserved for non-personal creative. In banking, the relationship is the franchise; sovereignty is how you keep it growing.
Where each AI workload
should live.
| Workload | Placement | Rationale |
|---|---|---|
| Acquisition & onboarding personalisation | Sovereign | Built on first-party customer data; belongs on EU compute. |
| Next-best-action & cross-sell | Sovereign | Decisioned on transaction history that must not leave the perimeter. |
| Relationship-manager copilots | Sovereign | Client PII and portfolio context; long retention. |
| Marketing creative & campaign copy | Frontier | Non-personal, fast iteration. |
What is yours to encode,
and what you are renting by accident.
Before any platform decision, one question settles the rest: how much of what your organisation knows can be written down precisely enough for a machine to act on it, and who ends up owning that writing. We run a short engagement to answer it, and it produces working artefacts rather than a report.
Two artefacts come out of this. An operating ontology, the nouns: the entities, relationships, and states your business actually runs on, described once and precisely. And agentic skills, the verbs: the procedures, thresholds, and judgments your best people apply, written down, versioned, and testable instead of retold.
A placement map addressed to the CTO or CIO office: what runs on your compute, what is bought, what is rented, who holds the keys, and what each costs. One test cuts through most of the debate. If a supplier vanished on a Friday, what stops working on Monday, and how long would it take you to replace it?
Where an open-weight model fine-tuned or adapted on your own corpus beats a frontier call, where a small purpose-built model for one narrow task beats both, and where the frontier still earns its fee. Geographic sovereignty falls out of that answer rather than having to be argued for on its own.
- →Credit and eligibility policy: the criteria, the exceptions, and who may grant them
- →Suitability and consumer-duty language, with the reasoning a regulator would ask for
- →Complaint handling: what counts as detriment, and the remedy ladder that follows
- →The relationship manager's playbook: which signal triggers which conversation
- →Fraud and financial-crime triage rules that today live in analysts' instincts
Transaction narratives are a corpus nobody else holds. A small open-weight model fine-tuned on your own decisioned cases beats a frontier call on classification, at a fraction of the cost, and never leaves the perimeter.
- +A register of encodable know-how, ranked by value and by how fast it decays
- +A draft operating ontology in an open format, not inside a vendor's platform
- +Two or three working skills, built and evaluated on your real work, not demonstrated on a slide
- +A bring-it-in-house plan the CTO or CIO office can actually staff
- +A model strategy: open weights, fine-tuning, purpose-built small models, and where the frontier stays
- +An evaluation harness that shows it works, and keeps showing it after we leave
This is a CTO and CIO office engagement, not a procurement exercise. Your own people have to end up running it, because the moment the encoding is delegated, the thing being encoded quietly stops being yours.
Palantir calls this layer an ontology, and the idea is right: a governed model of your objects, links, and actions that agents can act on. It lives inside their platform. 8090 will design, build, host, and maintain the software around it for you. Both are serious, and both leave the same question open. At the end of it, who owns the layer that holds your judgment? We build the same artefacts in open formats, on compute you control, and hand your CTO the keys.
The customer stack,
inside the bank.
The same four layers we ship in legal, instantiated for a bank. Here the application layer is built with you rather than bought off a shelf, and it belongs to you when the engagement ends.
A first-party identity and consent spine, a next-best-action console the marketing team can operate without a data scientist in the room, and a relationship-manager workspace grounded in the client's own portfolio and correspondence.
Eligibility criteria, suitability and consumer-duty language, complaint handling, and tone of voice, written once as versioned skills the agents load, reviewable by compliance, rather than buried in prompts nobody can audit.
Routing by sensitivity: anything decisioned on transaction or behavioural data stays on sovereign compute by architecture, non-personal creative work goes to the frontier under zero-retention terms, and every call is logged against the customer record.
In your own data centre, on an isolated instance we operate on sovereign infrastructure, or on dedicated AI hardware inside the bank's perimeter for the models that score transaction data.
The application layer here is built for you, not bought. The pattern is the one we already ship, as a product, in legal.
Four postures.
One codebase.
The same software in every posture, so a team can start hosted and end up air-gapped without a migration project. You move along the ladder when you decide to, not when a contract renews.
Your stack stood up on our infrastructure in days and pointed at real work, so it is judged on your matters rather than on a demo. The pilot fee credits against the hardware when you migrate.
Teams that want proof before capital expenditure.
The open-source cores installed on a machine you own, by a script anyone can read first. No account with us, no telemetry, no phone-home. Code flows one way, from us to you, and only when you ask for it.
Small teams, and anyone who wants to inspect the source before trusting it.
An isolated instance per client on sovereign infrastructure, European by default, run, patched, and monitored by us, with the security and backup credentials in your hands rather than ours.
Organisations without an infrastructure team to spare.
Dedicated AI hardware inside your building, with the applications and the open-weight models you choose installed and tested before it ships. It runs with the network unplugged, and it keeps working whatever happens to us.
In banking the appliance usually sits beside the analytics estate, scoring the data that is too revealing to send anywhere.
Work that cannot leave the building, ever.
- +Deployment and hardening, on your machines or ours
- +Knowledge encoding: your playbooks and positions compiled into installable skills
- +Model selection, tuning, and an evaluation harness built on your own work
- +Remote maintenance and monitoring at a published monthly rate
- +Updates as ordered, readable migrations, always after an encrypted backup
- +Backup, restore, and continuity drills you can actually rehearse
- +Enablement for the people who use it daily, not only for IT
- +Governance evidence: routing logs, audit trail, and an attestation pack
- Reach into your instance or see your work
- Revoke your software or disable a licence remotely
- Force an update on you
Not promises. Consequences of the architecture: your keys and your data are generated on your machine and stay there, and nothing calls home.
Get the full
banking
placement map.
We send a sector-specific brief with workload-by-workload placement guidance and a reference architecture for sovereign deployment.