Proven in Private Lease. Reusable across every financial product. And on a five-year horizon: the kernel of an autonomous sales company built around cars.
Walk through the full private lease lifecycle — from orientation to end of contract. Each step shows what agents handle autonomously and what a human sees when a case is escalated.
Configuration and ordering still happen on a normal screen — a marketplace or a dealer system. What changes is everything after checkout: no back-office screens, an AI agent mesh performs the operational work across the full lifecycle — orientation, onboarding, contract activation, servicing, billing & accounting, and end of contract. Each stage below also shows what a human sees when a case is escalated.
Example — human exception in this step
Back-office screens
0
Elapsed time
0:00
Human interventions
0×
Applicant & product
The order was placed on a normal screen. From here, no back-office screens — agents take over.
Agent mesh
Agent activity
Example — human exception in this step
Back-office screens
0
Elapsed time
0:00
Human interventions
0×
Approved application
Vehicle ordering runs through Leaslink — the dealer/factory ordering platform — with no manual re-entry.
Agent mesh
Agent activity
Example — human exception in this step
What the customer sees — My VWPFS portal
Volkswagen ID.4 Pro
Deep black · Advanced 20" wheels
€589 /month
Contract — · 36 months · 15,000 km/year
My details
| Name | J. de Vries |
| Address | Kalverstraat 12, 1012 PS Amsterdam |
| j.devries@example.com | |
| IBAN | NL91 ABNA 0417 1643 00 |
| Contract holder since | 2026-07-10 |
Or choose any other request
Behind the scenes — internal agent operations console
Example — human exception in this step
Ledger status — system overview
Example — human exception in this step
Example — human exception in this step
Every AI transformation deck shows a wall of named agents. That picture quietly recreates the problem it set out to solve: twenty systems to build, version, monitor and keep aligned — a monolith, shattered into pieces.
Pricing Agent, Billing Agent, Fraud Agent… each a long-running service with its own logic, its own drift, its own maintenance burden.
A single model-neutral runtime spawns short-lived agents on demand. Everything durable lives outside the agent — in skills, memory and the event log.
The strategic question is not "which agents do we build?" It is "what must remain when every agent — and every model — is replaced?"
This is the full inventory of what AI-Native Lease OS actually builds and owns. Each one answers a question the current deck leaves open.
One execution environment that wakes an agent when an event demands it, injects the right skills and memory, enforces its autonomy budget, and tears it down when the loop completes. No standing services, no per-agent infrastructure.
"How to calculate a buy-out price." "How to file a BKR notification." "What to do when a contract holder passes away." Each is a reviewable artifact — instructions, policy boundaries, tool access — written with the best business SMEs and released like software.
Three layers: what we know about this customer (history, behaviour, preferences), what we learned from similar cases (every resolved exception is training data), and why every decision was taken (a searchable rationale ledger).
Agents don't execute a script; they iterate toward an outcome within a budget — max actions, max financial exposure, max blast radius. A human exception is not a dead end but a mid-loop instruction: the person redirects, the agent finishes the work.
The existing Connect / compliance data model forms a strong starting point for the AI-Native Lease OS data model. Fields are formally defined with business definitions, data types, domain values, relationships, scope, primary-key indicators and data quality rules — covering core lease concepts such as contract, vehicle, residual value, mileage, exposure and realisation.
Important gap to close: the model does not yet cover the full commercial pricing structure — lease services, discount frameworks and price components from Miles. Connect is a strong foundation, but not the complete target data model.
The event log is more than plumbing. It is the audit trail, the replay mechanism for testing new skills against history, and — in horizon three — the sensor network an autonomous sales company acts on. The financial core stays behind it as a controlled system of record: agents propose postings, the core validates and books them.
"Credit Agent 80%" suggests autonomy belongs to an agent. It doesn't. An address change and a bereavement case may touch the same agent, but they deserve completely different levels of machine independence. Every case type climbs this ladder on evidence.
Some case types are capped by design. Bereavement stays at L1 forever — not because the machine can't, but because we decide it shouldn't. Writing that ceiling into policy is itself a governance feature the board can point to.
This is the engine of the whole vision. Exceptions are not operating cost — they are the R&D pipeline. Every human touch is converted into less need for the next one.
An agent hits its confidence floor or autonomy budget mid-loop and pauses with full context attached.
A specialist picks an option or types a free-text instruction. The agent resumes and completes the case.
The resolution lands in case memory. Recurring patterns become skill-update proposals, reviewed by the SME owner.
With the updated skill, the case type's evidence improves — and it climbs a level when it clears the gate.
Model neutrality is not just procurement hygiene — it defines where five years of investment must land. Everything on the left appreciates. Everything on the right gets cheaper and better without our help.
Hundreds of codified processes, policies and exception playbooks — the operational knowledge of the company in executable, auditable form. Grows with every SME session and every flywheel cycle.
Years of customer context, resolved cases and decision rationales. The dataset that calibrates confidence, personalises service and answers every future audit — impossible to purchase.
A replayable record of the business. New skills are tested against real history before touching a live case — the safety mechanism that makes fast iteration acceptable in a regulated company.
The per-case-type track record that justifies each level on the ladder. This is what turns "trust us" into a supervisory-grade argument for more automation.
In 2031 the models will be unrecognisable. The skills library, the memory and the evidence base will be exactly what we spent five years building — and they transfer to every new model on day one.
The same kernel, aimed at progressively larger loops. Nothing built in horizon one is thrown away in horizon three — that is the point of building the kernel first.
Private Lease runs on the kernel. Case types climb the ladder; the flywheel starts turning.
Same kernel, new skills. Financing, insurance and fleet products onboard as skill packages — not as new systems.
The loops grow from cases to commerce. Agents don't just service contracts — they run the trading motion around the car itself.
Max actions, max financial exposure, max data scope per case type and level. Exceeding the envelope is not an error state — it is the designed trigger for a human step.
Versioned, reviewed, signed off by an accountable owner. For any decision, we can reproduce the exact skill version, memory snapshot and rationale — the answer to EU AI Act and supervisory scrutiny by construction.
They propose; the core validates and books. Ledger integrity is enforced by architecture, not by agent discipline.
Bereavement, hardship, reputational edge cases: capped at L1 by policy. And every case type can be dialled down a level in minutes, with the event log ensuring nothing is lost in the transition.
Approve the kernel — runtime, skills, memory, loops — and every euro spent from here on lands in an asset that appreciates: a company that gets measurably more autonomous every quarter, on evidence a regulator can inspect.
Five owned components, event-driven, model-neutral — the permanent layer under every horizon.
Board-visible levels per case type, evidence-gated promotion, designed ceilings and kill-switch drills.
Exception rate per case type, quarter over quarter — the one number that proves the system is learning.