One book, several rulebooks, one standard of evidence.
An external asset manager carries a book across custodians and borders, and answers to more than one supervisor for the same client. Luscent generates the evidence once, as the work happens, with the jurisdiction attached.
Luscent is a relationship intelligence platform for external asset managers: client Signal detection, MiFID II suitability evidence, and an exportable audit trail, across every custodian the book sits on.
What this book looks like from here.
The book sits on platforms you do not control.
Positions live in someone else's format on someone else's schedule. What you control is the relationship, and nobody reads it back.
Two supervisors, one client, two standards of proof.
Keeping one set of evidence and hoping it satisfies both frameworks is the common approach and the fragile one.
Small teams carry large books.
More clients per person than a bank, and no supervision layer to catch what gets missed.
What it looks like on the day.
Three pieces of the product, at the sizes they render at. Synthetic data throughout: every name and figure below is invented.
Mandate scope questioned in two separate custodian threads.
A custodian statement query is still open.
Suitability recorded as the advice happens
Two engines, and a rules core that never guesses.
The three things you just saw, 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. Tabular models are on the roadmap and are drawn that way.
What is connected, and what is not.
Microsoft 365 and Salesforce are live today. The two drawn dashed are on the roadmap and are not shipped. We would rather tell you that than let you assume otherwise. Nothing is written back into any of them: Luscent reads, and your systems of record stay exactly as they are.
Where this sits against the rules.
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.
Who asks what.
Where 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.
What 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, before you have to ask for them.
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. The clause set behind the second group is Article 30 of Regulation (EU) 2022/2554.
Read the full Trust Center→Whether this is a fit.
The pilot is ninety days, free, with three to five relationship managers, starting on synthetic data. Success metrics are agreed before day one, so at the end there is something to judge rather than an impression.
One book, several rulebooks, one standard of evidence.
An external asset manager carries a book across custodians and borders, and answers to more than one supervisor for the same client. Luscent generates the evidence once, as the work happens, with the jurisdiction attached.
Luscent is a relationship intelligence platform for external asset managers: client Signal detection, MiFID II suitability evidence, and an exportable audit trail, across every custodian the book sits on.
What this book looks like from here.
The book sits on platforms you do not control.
Positions live in someone else's format on someone else's schedule. What you control is the relationship, and nobody reads it back.
Two supervisors, one client, two standards of proof.
Keeping one set of evidence and hoping it satisfies both frameworks is the common approach and the fragile one.
Small teams carry large books.
More clients per person than a bank, and no supervision layer to catch what gets missed.
What it looks like on the day.
Three pieces of the product, at the sizes they render at. Synthetic data throughout: every name and figure below is invented.
Mandate scope questioned in two separate custodian threads.
A custodian statement query is still open.
Suitability recorded as the advice happens
Two engines, and a rules core that never guesses.
The three things you just saw, 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. Tabular models are on the roadmap and are drawn that way.
What is connected, and what is not.
Microsoft 365 and Salesforce are live today. The two drawn dashed are on the roadmap and are not shipped. We would rather tell you that than let you assume otherwise. Nothing is written back into any of them: Luscent reads, and your systems of record stay exactly as they are.
Where this sits against the rules.
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.
Who asks what.
Where 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.
What 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, before you have to ask for them.
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. The clause set behind the second group is Article 30 of Regulation (EU) 2022/2554.
Read the full Trust Center→Whether this is a fit.
The pilot is ninety days, free, with three to five relationship managers, starting on synthetic data. Success metrics are agreed before day one, so at the end there is something to judge rather than an impression.