The understanding should outlast the person holding it.
A family office runs on relationships measured in decades and knowledge held by very few people. Luscent keeps that understanding with the office, not with whoever happened to be in the room.
The pilot, in four factsCheckable on this page
- Pilot90 days, free
- Seats3 to 5
- DataEU only
- MigrationNone
The record of who was in the room, and what the rules found while they were.Synthetic client. Rebuilt in the product's own idiom, not a screenshot.
The Q4 council committee entry names Michael, Charlotte and Thomas Klein. The record holds the attendance, not one person's memory of it.
CVM Res. 30 and MiFID II Art. 25(2) sit in the same timeline as the meetings, each labelled with the engine that produced it.
The deterministic rule carries no probability. The model-derived signal carries 92 per cent, and says so on its face.
What this book looks like from here.
Three patterns that hold across firms like yours, and one number from outside that frames them.
of high-net-worth clients describe their advisory experience as seamless and personalised.
Capgemini World Wealth Report 2026 (6.510 HNW clients, 27 markets)
The knowledge is in three people.
Offices run lean by design. That works until the person who has held a family for eleven years takes a role somewhere else.
A generation changing is a discontinuity.
What the next generation inherits from your systems is a transaction history, which says nothing about the conversations behind it.
Governance asks for evidence the file cannot produce.
A trustee or a family council asks why a decision was taken. Answering from memory is normal, and it is the weak part.
The figure is somebody else's number about the market, with its source. It is not a Luscent result.
Who asks what.
The seats that have to be satisfied, and the concern each one carries. Every question below is the first thing that seat asks, with the answer that holds today.
Who else can see what is written about the family?
Only the people your office authorises. Access is scoped to your organisation, staff at Luscent do not read client data as a matter of course, and every access is logged.
What happens when the person who knows the family leaves?
The understanding stays with the office. It accumulates against the relationship rather than in one person's memory and mailbox.
Do we have to move anything?
No. Luscent reads from the systems you already run. There is no migration and no new system of record.
Where does the data physically sit?
In the European Union: stored on Scaleway in Paris, with the data and AI services on Hetzner in Germany. The full sub-processor list is published.
Does it replace my judgement?
No. It surfaces what changed and what it came from. Every consequential decision is taken by a named person.
What it looks like on the day.
Three pieces of the product, in the order a relationship manager meets them: a Signal, the Health Score it moves, and the evidence a rule writes. Every name and figure is invented.
Two members of the next generation joined the last two reviews.
Microsoft 365 · calendar and 4 messages · 21 daysTwo documents were requested and have not been sent.
Microsoft 365 · 2 messages · 12 daysSignal
Signals are drawn from the office's own communications, and each one opens onto its source.
Klein Family Office · Health Score
Contact narrowed to one family member over the quarter.
Health Score
A Health Score per relationship, with the movement that produced it, for a team that cannot watch everything.
Evidence
The evidence a committee asks for exists before it is asked for, and shows which rule produced it.
Every trade checked before the advice leaves.
Before a relationship manager sends a rebalance, Luscent checks each trade against the mandate and the strictest jurisdiction, and names the smallest fix.
Read the use case →Use case 02 · Comms to ComplianceAn email changes the client. The advice waits.
When a client email says their circumstances changed, Luscent reads the change, holds the advice that relied on the old picture, and opens a reassessment.
Read the use case →Use case 03 · Cross-BorderTwo rulebooks. One household. One defensible answer.
A household booked in Luxembourg and São Paulo sits under MiFID II and CVM at once. Luscent evaluates one action under both and shows a path to proceed.
Read the use case →Use case 04 · Relationship DriftRelationships rarely end loudly. They drift.
When a client relationship slips, Luscent shows it in the Health Score, links the messages behind it and lists the next conversation for the relationship manager.
Read the use case →Where this sits against the rules.
Each row names its article, its method and what it puts on the record. A row that is not shipped says so, and is drawn that way.
This describes what Luscent does, not what your firm is obliged to do. It is not legal or compliance advice. The platform generates evidence and surfaces Signals; decisions remain with the firm and its professionals at all times.
Whether this is a fit.
Said plainly, both ways, so nobody spends ninety days finding out what one page could have told them.
Built for
- Single and multi-family offices running Microsoft 365
- Offices where a handful of people hold long relationships
- Offices facing a generational transition or a coverage change
Not for
- Offices looking for portfolio consolidation or performance reporting
- Offices wanting the system to make an allocation decision
- Offices whose client contact happens mostly outside written channels
The same for every firm.
Five things that do not change with the kind of firm you are. Each one opens in place.
06.1Where Luscent sits in your operating model.
A family office runs its Clients across front, middle and back office on systems it already owns, and Luscent replaces none of them. The numbers mark the three places relationships are most often lost. Select a tile.
Luscent today
Health Score for every Client, 0 to 100
Every Client carries a Health Score from 0 to 100, updated from the conversations Luscent reads. A falling score is the early sign that a relationship is cooling, before it shows in the assets.
See it on the day, section 03 →- 1A relationship cools between reviews, and the first sign anyone sees is the transfer request.
- 2Advice is given on a call and written up later, from memory.
- 3Supervision reads a sample of files, weeks after the conversation.
Luscent reads only the systems it is connected to, listed under What is connected below. In build means designed and in development; no date is promised on this page.
06.2Two engines, and a rules core that never guesses.
The three things you saw in section 03, and where each of them comes from.
A Signal carries a confidence because a model produced it. A compliance outcome carries the rule that fired and no confidence at all, because a regulatory result is not a guess.
Inference is EU-hosted, by EU providers only, with no US model API in the client-data path. Tabular models are on the roadmap and are drawn that way.
06.3What is connected, and what is not.
2 of 4 live
Microsoft 365 and Salesforce are live today. The two drawn dashed are on the roadmap and not shipped. We would rather tell you that than let you assume otherwise. Luscent reads them and replaces none of them.
06.4Where this gets it wrong.
Every firm evaluating this has been shown a confident wrong answer by something before. So the limits are on the page rather than in the room, and each one names the control that catches it.
Confidence is a number, not a feeling.
Every probabilistic Signal carries a numeric confidence on its face. Deterministic outcomes carry none, because they have none to state: the same input produces the same result every time.
It reads what it is connected to, and nothing else.
A relationship conducted by telephone, in person, or on a channel Luscent does not read is invisible to it. The systems drawing above is the whole of what it can see.
It surfaces, it does not decide.
No Signal approves advice and no score authorises an action. Every consequential decision is taken by a named person, and the record says who.
It will be wrong, and the pilot counts it.
False positives are reviewed weekly with your compliance function during the pilot, and the rate is one of the success metrics agreed before day one rather than something discovered at the end.
A thin month is a thin month.
The representation of a relationship accumulates from your own communications. Month six is worth considerably more than month one, and no amount of capital shortens that for anyone.
06.5What your outsourcing officer needs.
Whether a deployment is a critical or important function is your firm's classification to make, and your outsourcing officer owns it. What we can do is put the facts that classification turns on in one place.
Luscent reads it and does not write to it.
Every consequential decision is taken by a named person.
Stored on Scaleway, Paris; services on Hetzner, Germany.
Fact means true today and checkable, here or in the Trust Center. Position means the stance Luscent takes into a negotiation; it binds nobody until it is in a signed agreement.