Luscent reads the communications your firm already has, shows every Relationship Manager the next right conversation, and generates the suitability evidence as work happens.
09:12A Client writes that the family business has been sold. About 9.200.000 EUR arrives next month.Luscent picks up two things: cash is coming, and the Client’s suitability file no longer matches their situation.Anne, the Relationship Manager, confirms what was read. Until she does, the Q4 proposal waits.Who read what, who decided and when, filed for compliance without anyone writing it up.Found at 09:14 the same morning, not at the annual review.
“The sale of the operating company is now closed and the proceeds, roughly 9.200.000 EUR, will land next month. Michael asks again for a liquidity figure before the Q4 committee.”
Nothing moves until Anne confirms. The Q4 proposal waits for her.
Call Charlotte, confirm the liquidity figure and the horizon of the 9.200.000 EUR proceeds.
Luscent generates the evidence. Your firm keeps its records.
Luscent reads the emails and meetings your firm already has and puts first the Clients who need you, with the reason. It sends an email or books a meeting only when you do so from Luscent.
Above · step 03, Anne confirmsSuitability checks run on fixed rules, not a model. Every Signal, decision and confirmation goes into the Audit Trail with who, what and when.
Above · step 04, the Audit TrailEvery Client has a Health Score from 0 to 100, with the reason behind each change, across every RM. Gaps in coverage show up before the annual review.
Above · Klein Family Office, 76Start here
Tell us where you work and what you need, and we point you to the one page that answers it.
Shown in our demo environment
A system of record answers one client at a time. In our demo environment, Luscent Analyst reads the whole book, for the RM, compliance and leadership, and nothing runs until a person confirms.
Try itPick an ask, or type your own. Each answer shows what it read.
Klein Family Office is cooling, and the reason is in writing: two fee questions unanswered and a house purchase that changes the plan.
Last three interactions
“Before we get to fees: you mentioned the house. Let’s make sure the portfolio is ready for it.”
What your firm knows about a client lives in emails, call notes and meeting summaries your CRM never reads.
Your System of Record answers any question you know to ask. It cannot tell you which relationship cooled three months ago, or prove what the firm knew, and when, to an auditor.
Fig. 02.3 · Sound familiar?
The auditor is asking when we knew the Kleins’ plans had changed.
Charlotte mentioned a house in an email. September, I think.
And the profile still says ten years or more?
It is on the list for the periodic review.
So we cannot show what we knew, or when.
You knew on 03.09. Charlotte Klein wrote, “We will need liquidity for the house next year.” The profile of 03.07.2025 said ten years or more. The Signal was raised, the review was drafted, and a named RM approved it.
Your firm already holds the answer. Luscent reads it, says what changed, and keeps the proof. Nothing reaches a Client until a person approves it.
Run it on your own bookDemo environment · fictional Client · 90-day pilot, free
Fig. 02.4 · The old way
“Has anything changed for the Klein family since the last review?”Demo environment · fictional Client
“We will need liquidity for the house next year.”
The profile on file says ten years or more. A suitability review is proposed as a Task, and the RM decides.
01 · Observe
Mail, calendar, Teams and CRM records, read from the systems your firm already runs. Nothing new to type.
02 · Understand
Language models, hosted in the EU by EU providers, read the communications. Deterministic rules produce every compliance outcome.
03 · Act and prove
Tasks route the next right conversation to the right Relationship Manager. The audit trail writes itself, retained seven years.
On every Client
Every pass leaves a record
Examples from our demo environment, fictional Clients
Anne, we signed on Friday. The sale of the operating company is now closed[1] and the proceeds, roughly 9.200.000 EUR[2], will land next month. Michael asks again for a liquidity figure[3] before the Q4 committee, a number rather than a range.
[1]Material change
Liquidity event
Signal raised, 92% confidence. A suitability reassessment opens.
[2]Amount
9.200.000 EUR, next month
Capacity and goals have moved, so the pending rebalance waits.
[3]Repeat request
A second ask for the same figure
Health Score 78 → 64. This line is the reason.
Health Score · Klein Family Office
CoolingEach change carries the line that caused it. Fictional Client, shown in our demo environment.
Suitability evidence · MiFID II Art. 25(2)
AI draft, approvedAnne Keller, RM · 09:14
Reassessment after material change
Reassessment opened, the email attached. The pending rebalance waits until suitability is checked again.
Point at a phrase or a note to follow it
Four jobs stand between a Relationship Manager and the Client. Luscent takes the reading and the drafting. The judgement stays where it belongs.
Noticing what changed
A sale, a house, a second request for the same figure, somewhere in 46 messages.
Knowing who to call first
Every relationship ranked by its Health Score, with the line that moved it.
Writing the suitability evidence
Drafted as the advice happens, the exchanges attached. The RM approves it.
Preparing the review meeting
The last three interactions, the open Signals and one opening line.
The conversation with the Client
The judgement, the relationship, the call. The part only you can do.
Luscent does not manage your obligations or decide anything on your behalf. Compliance Signals come from an explicit rules engine, not a probability: a rule either fired or it did not, and you can read it. No client-facing output leaves without a named person approving it, which is a design decision, and it shapes how the EU AI Act applies to Luscent.
Mail, calendar, Teams and CRM records. The exchanges your firm already produces, read where they already sit.
A deterministic rules engine, not a probability. A rule either fired or it did not, and you can read which one and why.
The suitability record, written as advice happens, with the exchanges it was drawn from attached to it.
A named person signs before anything reaches a Client. That is a design decision, and it shapes how the EU AI Act applies to Luscent.
The rule that ran, the message it ran on, and the person who approved, in one entry your auditor can read.
Fig. 04.2 · Who sends
Some AI tools earn autonomy: they ask at first, then start sending on their own. Luscent does not offer that switch for anything that reaches a Client. A named person approves it, and the approval goes on the record with their name and the time.
Draft · to Charlotte KleinDemo environment
How should replies like this go out?
Send them on its own from now onThe switch other tools offer once they have learned.
Not offeredAsk a named person, every timeThe only option for anything client-facing.
AlwaysApproved by Anne Keller, RM09:14On the record
Luscent is a System of Intelligence for private banks, family offices, external asset managers and independent advisors.
The book is the same problem in all four: what the firm knows sits in communications nobody reads back, and the evidence has to exist whether or not anyone wrote it down. Luscent sits above the systems each of them already runs, and replaces none of them.
A prioritised view of client Signals for every relationship management team, with suitability evidence generated as advice happens and compliance in control at every step.
See the private bank viewThe Signals buried in your client communications, and succession context kept in the firm rather than in one person's memory.
See the family office viewThe evidence discipline of a full-service institution: Signal detection, MiFID II suitability support and an exportable audit trail, without building any of it.
See the asset manager viewGrowth opportunities identified and the documentation your obligations require generated, so the practice scales without the administration scaling with it.
See the advisor viewFive commitments a compliance officer asks about first, each linked to the Trust Center section that backs it, then the standards and where each one stands.
It stays in the EU, layer by layer.
Client data is stored, processed and run through models inside the European Union, by European providers. No US hyperscaler and no non-EU model API in the client-data path.
Your CRM stays the record.
Luscent reads your CRM and does not write to it. In Microsoft 365 it acts only when the Relationship Manager does.
MiFID II suitability, evidenced at the point of advice. CVM and ANBIMA in the same rules engine; Swiss, German and UK rules on the roadmap.
MiFID II · LiveA person decides.
No client-facing output leaves Luscent without a person approving it.
US model APIs in the client-data path. Client data trains nothing.
AI27001Controls aligned to ISO/IEC 27001:2022. The certificate is not held.
Aligned, not certifiedYours to delete on exit.
Deleted or returned on termination, as the data processing agreement sets out.
A data processing agreement with every client. Template on request before any commitment.
GDPR Art. 28 · AvailableArt. 50Transparency position documented, available on request.
EU AI Act Art. 50 · DocumentedLuscent is a member of the LHoFT, the Luxembourg House of Financial Technology, and showed its first release at the LHoFT AI Experience Centre on 13.04.2026.Member · LHoFT · LuxembourgNo. A CRM records what happened. Luscent reads the same substrate and tells you what it means and what has been missed. A native CRM exists as a separate Luscent product for firms that do not have one. It is in build, and it is included for Luscent clients at no extra cost; firms on Salesforce keep Salesforce.
Copilot is a general assistant across Microsoft 365: it drafts, summarises and searches for any employee. Luscent does one job for wealth managers. It reads the Client communications your firm already records, keeps a Health Score for each Client, raises Signals, and assembles MiFID II suitability evidence that a named Relationship Manager approves. The two can run side by side.
No, and it is built so that it cannot. No client-facing output leaves Luscent without a person approving it. Every Signal is a recommendation, and the relationship manager decides.
No. The pilot starts on synthetic data, and you decide if and when real correspondence enters it.
No. Luscent drafts, and a named person approves. Nothing reaches a Client until that person confirms it, and the approval is recorded with their name and the time. It is a design decision, not a setting.
Every Signal shows the rule that fired or the line it was drawn from, so a wrong one can be traced and corrected. In a pilot, wrong Signals are triaged weekly with your compliance function; the false-positive rate is one of the agreed metrics, and the one we expect to look worst early.
The pilot starts on synthetic data, so in its first weeks there is nothing of yours to lose. Under an agreement, Client data is kept for its term and deleted or returned on termination, as the data processing agreement sets out, and backups age out of a 30-day recovery window. Data exports are standard and source-code escrow is available, and because your CRM stays the system of record, your own systems stay complete without it.
No. Luscent supervises Client files and the firm's obligations, never the Relationship Manager. There is no RM-level score, ranking or rate anywhere in the product. The Health Score belongs to the Client relationship.