Every relationship manager, held to the same standard.
Forty relationship managers means forty standards of client understanding and forty qualities of evidence. Luscent makes that variance visible before an audit or a resignation makes it visible for you.
The pilot, in four factsCheckable on this page
- Pilot90 days, free
- Seats3 to 5
- DataEU only
- MigrationNone
Regime divergence on household action
PROP-0113 spans both booking sleeves and cannot be split. EU MiFID II passes; Brazil CVM blocks the product class (CVM-30-A3). Most restrictive wins: block, with a path to comply.
Suitability review lapsed · advice restricted
The annual suitability review lapsed on 31 August. Advisory capability is restricted until it is refreshed: if the client calls today, no advice can be given.
The same book, ranked. Fifteen signals in four groups, each carrying what it is worth and which engine produced it.Synthetic data. Every name and figure is invented.
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 now hold an exclusive relationship with a single firm, down from 39 percent in 2019.
Capgemini World Wealth Report 2026 (6.510 HNW clients, 27 markets)
The variance is invisible until it is expensive.
Your strongest and weakest coverage produce the same CRM record. The difference surfaces at an audit and at a resignation.
The record shows activity, not understanding.
What happened and when is in the system. Whether anyone noticed the client's circumstances change is in the mailbox.
Evidence is reconstructed, not kept.
Suitability files get assembled after the fact, from memory, unevenly across the population.
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.
Does this change what my relationship managers do all day?
No. Luscent reads the mail and calendar they already produce and puts what needs attention at the top of one list. There is no daily form to fill in and no new record to keep.
What happens to the understanding when a relationship manager resigns?
It stays with the firm. Every Signal, Health Score and piece of evidence attaches to the client rather than to the person who happened to hold the relationship.
What do you write into my systems?
Into your CRM, nothing: Luscent reads it, and it stays the system of record. In Microsoft 365, only what the Relationship Manager sends or books from Luscent.
Can a model decide whether we were suitable?
No. Compliance outcomes come from a deterministic rules engine, so the same input produces the same result every time and the rule that fired is on the record with its source.
Is this scoring me?
It scores the relationship, not the person. A Health Score resolves to the movement behind it, which makes it a conversation about a client rather than a verdict about you.
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.
The last three exchanges were all opened by the client.
Microsoft 365 · 3 messages · 14 daysA fee question has gone unanswered for nine days.
Microsoft 365 · 1 message · 9 daysSignal
Signals arrive in order of what needs attention, each one opening onto the exchange it came from.
Rosendahl Holding · Health Score
Response time doubled; no meeting booked since April.
Health Score
Every Health Score resolves to the movement behind it, so it survives a supervision conversation.
Evidence
Compliance outcomes come from rules, never from a probability, and the rule that fired is on the record.
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
- Banks running Microsoft 365, with or without Salesforce
- Books where several relationship managers cover the same client type
- Firms whose compliance function already asks for suitability evidence
Not for
- Firms looking to replace core banking or CRM
- Firms wanting the system to make or approve an advice decision
- Books held entirely outside the systems we read from
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 private bank 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 FSC 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.