Fashion.
Clienteling and customer intimacy, personalised without a leak.
In fashion and luxury, growth is intimacy at scale: knowing each client, personalising the relationship, and earning the next purchase through clienteling, not discounting. That runs on the client's most personal data and the house's creative IP, neither of which should ever become another model's training data.
- R01Clienteling data (CRM, advisor notes, in-store) leaking through marketing platforms
- R02Personalisation on client data without eroding the human relationship
- R03Creative-direction IP exposure through prompt logging
What's actually
reshaping the sector.
The shifts our research is tracking, named, current, cited.
BCG's 2025 True-Luxury study finds 65% of top clients feel overwhelmed by impersonal over-communication; the way forward is human clienteling enhanced by GenAI, personalisation that deepens rather than dilutes the relationship.
BCG (True-Luxury / Altagamma) →Burberry's in-house generative-AI clienteling platform 'Penguin', used by 100+ consultants worldwide, delivered a 24% uplift in average transaction value. Clienteling AI is a proven growth lever, not a demo.
DataIQ Awards 2025 →The EU Digital Product Passport (under the ESPR) makes a structured, residency-compliant record a precondition to sell a garment, every SKU needs clean product data, with obligations landing around 2027–2028.
European Commission (ESPR) →McKinsey/BoF's State of Fashion 2026 finds 35%+ of executives already use generative AI daily and rank AI as the industry's single biggest opportunity, with maisons augmenting discovery and clienteling without ceding brand meaning.
McKinsey / BoF →In fashion, the client relationship is the asset AI should deepen, never absorb, and the clienteling data that powers it stays sovereign.
Deepen the client relationship, without handing it over.
In luxury, growth is clienteling: knowing each client and personalising the relationship so the next purchase is earned, not discounted. That runs on the client's most personal data, held by advisors who are the brand. It is also the last data a house should let become somebody else's training set.
Personalise clienteling and acquisition on sovereign, first-party client data and you lift average order value and loyalty while the human relationship, the whole point of luxury, stays intact. Let the frontier run free on general creative and content, where no client identity or unreleased design is exposed.
We keep the two crown jewels, the client relationship and creative IP, sovereign, and let the frontier accelerate everything else. Taste and intimacy are the differentiators; AI should expand them, never absorb them.
Where each AI workload
should live.
| Workload | Placement | Rationale |
|---|---|---|
| Clienteling & personalisation | Sovereign | Advisor-client trust is the brand; data stays sovereign. |
| Client acquisition & CRM enrichment | Sovereign | First-party client data, never shared. |
| Campaign & content creative | Frontier | Non-personal; pre-release IP excluded. |
| Visual search & discovery | Hybrid | On-device plus sovereign back-end. |
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.
- →House codes: silhouette, proportion, palette, and the things the brand never does
- →The archive, described well enough that a machine can search it the way a designer does
- →Materials, construction, and care standards
- →Styling and clienteling rules for the boutique floor
- →Merchandising and drop logic
An image model adapted on the house archive gives you generative work in your own aesthetic, on your own hardware, with the archive never leaving the atelier.
- +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 house archive,
as a private model.
The same four layers we ship in legal, instantiated for a fashion house, where the archive and the hand are the whole business and both are trivially easy to give away.
A creative studio that generates against your own archive and lookbooks, a clienteling copilot for the boutique and the personal shopper, and a product and atelier assistant that knows your materials, suppliers, and construction.
Brand voice, silhouette and styling rules, materials and care standards, and merchandising logic compiled into skills, so what the system produces reads as the house rather than as a generic model doing an impression of it.
Unreleased collections, archive imagery, and client books are pinned to local inference. Nothing about a season in development is uploaded anywhere, which is the difference between using AI and licensing your aesthetic to a stranger.
A box in the studio for creative work, a managed instance for clienteling and commerce, or a single perimeter covering both when the house prefers one estate.
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.
For a fashion house the appliance is what makes generative work safe at all: the archive is the asset, and it never leaves the atelier.
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
fashion
placement map.
We send a sector-specific brief with workload-by-workload placement guidance and a reference architecture for sovereign deployment.