See the next right conversation.Prove every past one.
Luscent reads the communications your firm already has, so every Relationship Manager can grow the book, protect the relationships at risk and prove each recommendation was suitable, with the evidence written as the 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: 9.200.000 EUR to plan for, and a suitability file that no longer matches the Client’s 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.”
Confirm what was read
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.
Each row says who did it: the model, a fixed rule or a person. Luscent generates the evidence. Your firm keeps its records.
Same book.A different morning.
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.
Planned at the next review, if someone rereads the thread.
Nobody is told. Nothing is recorded.Products are matched to what she said and held until the suitability check passes.
Open the review TaskWe have received a proposal from another bank.
Found when the transfer request arrives.
Nobody is told. Nothing is recorded.The score drops with the line that moved it, and a call Task reaches the RM the same day.
Assign the callWhy was the pending rebalance held on 12.10?
Someone rebuilds it from emails and the CRM.
Assembled after the fact, with gaps.The answer is already written: who read the message, which rule ran, who confirmed, and when.
Open the Audit TrailNo times or percentages here until a pilot has measured them. Confidence shown is the Signal’s own.
Join the pilot programme90 days, free, 3 to 5 RMs→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.
The warning before assets leave, and the news before new money arrives, are often already in writing, in messages nobody reads back.
Your CRM records the contact, an AI assistant answers once, the archive keeps every message. Luscent reads all three and replaces none.
System of Record
Stores what happened.
Reports when asked.
Treats every client as equally urgent.
Waits for someone to notice.
System of Intelligence
Observes what is happening.
Explains what changed and why it matters.
Ranks the book by what needs attention today.
Proves the decision afterwards.
Fig. 01.3 · Sound familiar?
The question every firm gets. Usually after the person who knew has left.
- Head of Compliance
The auditor is asking when we knew the Kleins’ plans had changed.
- Relationship Manager
Charlotte mentioned a house in an email. September, I think.
- Head of Private Banking
And the profile still says ten years or more?
- Relationship Manager
It is on the list for the periodic review.
- Head of Compliance
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. 01.4 · The old way
One question. Five places to look.
“Has anything changed for the Klein family since the last review?”Demo environment · fictional Client
- Mail46 messages since the last review. Nobody has read them back.Dead end
- CRMThe last call note was logged in June. The trail stops there.Dead end
- Portfolio systemPositions, not reasons. It cannot say what changed.Dead end
- Suitability fileProfile confirmed 03.07.2025: ten years or more.Dead end
- The RM's memoryOn leave until Monday.Dead end
“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.
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.
The warning before assets leave, and the news before new money arrives, are often already in writing, in messages nobody reads back.
Your CRM records the contact, an AI assistant answers once, the archive keeps every message. Luscent reads all three and replaces none.
System of Record
System of Intelligence
Fig. 01.3 · Sound familiar?
The question every firm gets. Usually after the person who knew has left.
- Head of Compliance
The auditor is asking when we knew the Kleins’ plans had changed.
- Relationship Manager
Charlotte mentioned a house in an email. September, I think.
- Head of Private Banking
And the profile still says ten years or more?
- Relationship Manager
It is on the list for the periodic review.
- Head of Compliance
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. 01.4 · The old way
One question. Five places to look.
“Has anything changed for the Klein family since the last review?”Demo environment · fictional Client
- Mail46 messages since the last review. Nobody has read them back.Dead end
- CRMThe last call note was logged in June. The trail stops there.Dead end
- Portfolio systemPositions, not reasons. It cannot say what changed.Dead end
- Suitability fileProfile confirmed 03.07.2025: ten years or more.Dead end
- The RM's memoryOn leave until Monday.Dead end
“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.
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.
The warning before assets leave, and the news before new money arrives, are often already in writing, in messages nobody reads back.
Your CRM records the contact, an AI assistant answers once, the archive keeps every message. Luscent reads all three and replaces none.
System of Record
System of Intelligence
Fig. 01.3 · Sound familiar?
The question every firm gets. Usually after the person who knew has left.
- Head of Compliance
The auditor is asking when we knew the Kleins’ plans had changed.
- Relationship Manager
Charlotte mentioned a house in an email. September, I think.
- Head of Private Banking
And the profile still says ten years or more?
- Relationship Manager
It is on the list for the periodic review.
- Head of Compliance
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. 01.4 · The old way
One question. Five places to look.
“Has anything changed for the Klein family since the last review?”Demo environment · fictional Client
- Mail46 messages since the last review. Nobody has read them back.Dead end
- CRMThe last call note was logged in June. The trail stops there.Dead end
- Portfolio systemPositions, not reasons. It cannot say what changed.Dead end
- Suitability fileProfile confirmed 03.07.2025: ten years or more.Dead end
- The RM's memoryOn leave until Monday.Dead end
“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.
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.
The warning before assets leave, and the news before new money arrives, are often already in writing, in messages nobody reads back.
Your CRM records the contact, an AI assistant answers once, the archive keeps every message. Luscent reads all three and replaces none.
System of Record
System of Intelligence
Fig. 01.3 · Sound familiar?
The question every firm gets. Usually after the person who knew has left.
- Head of Compliance
The auditor is asking when we knew the Kleins’ plans had changed.
- Relationship Manager
Charlotte mentioned a house in an email. September, I think.
- Head of Private Banking
And the profile still says ten years or more?
- Relationship Manager
It is on the list for the periodic review.
- Head of Compliance
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. 01.4 · The old way
One question. Five places to look.
“Has anything changed for the Klein family since the last review?”Demo environment · fictional Client
- Mail46 messages since the last review. Nobody has read them back.Dead end
- CRMThe last call note was logged in June. The trail stops there.Dead end
- Portfolio systemPositions, not reasons. It cannot say what changed.Dead end
- Suitability fileProfile confirmed 03.07.2025: ten years or more.Dead end
- The RM's memoryOn leave until Monday.Dead end
“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.
From the record to the evidence.
01 · Observe
The record comes in.
Mail, calendar, Teams and CRM records, read from the systems your firm already runs. Nothing new to type.
02 · Understand
Two engines read it.
Language models, hosted in the EU by EU providers, read the communications. Deterministic rules produce every compliance outcome.
03 · Act and prove
Evidence as work happens.
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
From the record to the evidence.
01 · Observe
The record comes in.
Mail, calendar, Teams and CRM records, read from the systems your firm already runs. Nothing new to type.
02 · Understand
Two engines read it.
Language models, hosted in the EU by EU providers, read the communications. Deterministic rules produce every compliance outcome.
03 · Act and prove
Evidence as work happens.
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
From the record to the evidence.
01 · Observe
The record comes in.
Mail, calendar, Teams and CRM records, read from the systems your firm already runs. Nothing new to type.
02 · Understand
Two engines read it.
Language models, hosted in the EU by EU providers, read the communications. Deterministic rules produce every compliance outcome.
03 · Act and prove
Evidence as work happens.
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
From the record to the evidence.
01 · Observe
The record comes in.
Mail, calendar, Teams and CRM records, read from the systems your firm already runs. Nothing new to type.
02 · Understand
Two engines read it.
Language models, hosted in the EU by EU providers, read the communications. Deterministic rules produce every compliance outcome.
03 · Act and prove
Evidence as work happens.
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
From the record to the evidence.
01 · Observe
The record comes in.
Mail, calendar, Teams and CRM records, read from the systems your firm already runs. Nothing new to type.
02 · Understand
Two engines read it.
Language models, hosted in the EU by EU providers, read the communications. Deterministic rules produce every compliance outcome.
03 · Act and prove
Evidence as work happens.
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
Compliance is a constraint we designed around, not a module we added.
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.
Illustration with an invented Client. See the full example
Observe
Mail, calendar, Teams and CRM records. The exchanges your firm already produces, read where they already sit.
Detect
A deterministic rules engine, not a probability. A rule either fired or it did not, and you can read which one and why.
Assemble
The suitability record, written as advice happens, with the exchanges it was drawn from attached to it.
Approve
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.
Fig. 03.1 · Who sends
It asks first.Every time.
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
Compliance is a constraint we designed around, not a module we added.
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.
Illustration with an invented Client. See the full example
- 01 The record
Observe
Mail, calendar, Teams and CRM records. The exchanges your firm already produces, read where they already sit.
- 02 The rules
Detect
A deterministic rules engine, not a probability. A rule either fired or it did not, and you can read which one and why.
- 03 The evidence
Assemble
The suitability record, written as advice happens, with the exchanges it was drawn from attached to it.
- 04 The approval
Approve
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.
Fig. 03.1 · Who sends
It asks first.Every time.
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
Compliance is a constraint we designed around, not a module we added.
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.
Illustration with an invented Client. See the full example
- 01 The record
Observe
Mail, calendar, Teams and CRM records. The exchanges your firm already produces, read where they already sit.
- 02 The rules
Detect
A deterministic rules engine, not a probability. A rule either fired or it did not, and you can read which one and why.
- 03 The evidence
Assemble
The suitability record, written as advice happens, with the exchanges it was drawn from attached to it.
- 04 The approval
Approve
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.
Fig. 03.1 · Who sends
It asks first.Every time.
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
Compliance is a constraint we designed around, not a module we added.
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.
Illustration with an invented Client. See the full example
- 01 The record
Observe
Mail, calendar, Teams and CRM records. The exchanges your firm already produces, read where they already sit.
- 02 The rules
Detect
A deterministic rules engine, not a probability. A rule either fired or it did not, and you can read which one and why.
- 03 The evidence
Assemble
The suitability record, written as advice happens, with the exchanges it was drawn from attached to it.
- 04 The approval
Approve
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.
Fig. 03.1 · Who sends
It asks first.Every time.
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
Compliance is a constraint we designed around, not a module we added.
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.
Illustration with an invented Client. See the full example
- 01 The record
Observe
Mail, calendar, Teams and CRM records. The exchanges your firm already produces, read where they already sit.
- 02 The rules
Detect
A deterministic rules engine, not a probability. A rule either fired or it did not, and you can read which one and why.
- 03 The evidence
Assemble
The suitability record, written as advice happens, with the exchanges it was drawn from attached to it.
- 04 The approval
Approve
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.
Fig. 03.1 · Who sends
It asks first.Every time.
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
Shown in our demo environment
Ask one client.Or ask the whole book.
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.
- Reading 46 messages and 5 meeting notes for Klein Family Office
- Checking the Health Score and the open Signals
- Brief ready: three points and an opening line
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
- “We will need liquidity for the house next year.”Mail · 03.09
- Quarterly review cancelled by the client.Calendar · 02.09
- “Could you send the fee schedule we discussed?” UnansweredMail · 29.08
“Before we get to fees: you mentioned the house. Let’s make sure the portfolio is ready for it.”
Answer: Prepare me for my 14:00 with Klein Family Office
Runs on the stack you already have
- Microsoft 365Mail and calendar. Luscent acts there only when the relationship manager does.
- SalesforceLuscent reads the CRM record and does not write to it. Your CRM stays the record.
- Luscent CRMFor firms without a CRM, the native one is built in.
Four kinds of firm.One intelligence layer.
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.
Private banks
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.
Family offices
The Signals buried in your client communications, and succession context kept in the firm rather than in one person's memory.
External asset managers
The evidence discipline of a full-service institution: Signal detection, MiFID II suitability support and an exportable audit trail, without building any of it.
Independent advisors
Growth opportunities identified and the documentation your obligations require generated, so the practice scales without the administration scaling with it.
Four kinds of firm.One intelligence layer.
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.
Private banks
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.
Family offices
The Signals buried in your client communications, and succession context kept in the firm rather than in one person's memory.
External asset managers
The evidence discipline of a full-service institution: Signal detection, MiFID II suitability support and an exportable audit trail, without building any of it.
Independent advisors
Growth opportunities identified and the documentation your obligations require generated, so the practice scales without the administration scaling with it.
Four kinds of firm.One intelligence layer.
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.
Private banks
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.
Family offices
The Signals buried in your client communications, and succession context kept in the firm rather than in one person's memory.
External asset managers
The evidence discipline of a full-service institution: Signal detection, MiFID II suitability support and an exportable audit trail, without building any of it.
Independent advisors
Growth opportunities identified and the documentation your obligations require generated, so the practice scales without the administration scaling with it.
Trust you can check. Not taken on faith.
Five 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.
- Storage and database
- Scaleway
- FR
- Data and AI services
- Hetzner
- DE
- Model inference
- Mistral AI, EU endpoint
- FR
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 · LuxembourgTwo founders, one problem from both ends.
Armin Prior advised wealth managers for years, then worked inside a bank. Dr. Frano Milos builds the models that read what a firm already holds. Founded in Luxembourg.
Is this a CRM?
No. 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.
How is Luscent different from Microsoft 365 Copilot?
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.
Does it replace the relationship manager?
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.
Do we have to give you production data to evaluate it?
No. The pilot starts on synthetic data, and you decide if and when real correspondence enters it.
Does Luscent help us grow assets, or only stay compliant?
Both, from the same reading. Luscent shows where new money is coming and which products fit what the Client said, and flags relationships that are cooling before the assets move. Every proposal passes the suitability rules first, and a named person approves anything that reaches a Client.
What happens when a Signal is wrong?
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.
You are an early-stage company. What happens to our data if you stop?
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.
Does it score our Relationship Managers?
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.