Relationship manager
- A verdict and the smallest fix before the client sees anything
- No second round on advice that has already gone out
OutcomeAdvice leaves once, cleared.
Before a relationship manager sends a proposed rebalance, Luscent checks each trade against the client's mandate and the strictest jurisdiction that applies, and returns a verdict, a plain reason and, where it blocks, the smallest change that would clear it.
A rebalance is drafted and sent, then checked against a mandate that sits in another system. A breach found after the fact is a remediation, not a correction.
Before anything is sent, every trade meets the mandate and the strictest rule that applies. Same inputs, same answer, every time.
The fix is named, the escalation routed and the whole decision written down before the client reads a word of the advice.
| Leg · instrument | Verdict |
|---|---|
| T1European equities fund | Queued |
| T2US equities fund | Queued |
| T3Capital-protected note | Queued |
| T4EM sovereign bond fund | Queued |
| T5EUR money market fund | Queued |
REB-2041, drafted by Anne Keller. Equities at 52,0 % against a 45,0 % target. Five trades, checked against Mandate v3.2 and the strictest jurisdiction that applies. Nothing has been sent.
Demo environmentSynthetic data. Klein Family Office and everyone named here are fictional.
OutcomeAdvice leaves once, cleared.
OutcomeReview moves from after the fact to before it.
OutcomeConsistency without another review layer.
OutcomeA defensible record by design.
The Suitability Gate works on the compliance effort around advice: checking before, documenting after. This is the part of the homepage estimate it addresses.
12 relationship managers × 10 h a week × 48 weeks × 85 EUR an hour × 40 % of the effort addressed. The same model and assumptions as the estimate on the homepage. Modelled from time-and-motion assumptions, not measured client results.
“When providing investment advice or portfolio management the investment firm shall obtain the necessary information ... so as to enable the investment firm to recommend to the client or potential client the investment services and financial instruments that are suitable for him ...”
Suitability is decided per recommendation, against what the firm knows about the client. A gate on the draft, before it is sent, is where that obligation is cheapest to meet and easiest to prove.
Our reading, not legal advice. The rules engine applies the firm's own configuration of these rules, and the relationship manager decides.
No. It evaluates a draft recommendation before it is sent. There is no order routing and no connection to a custodian; what leaves is advice, signed by the relationship manager.
Yes. A block is a workflow hold, not a system veto. The relationship manager can clear it with the suggested fix or override it with a reason, and the override is written to the Audit Trail. A knowledge and experience gap is different: that leg waits for the second person's sign-off.
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.
See it run 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.
See it run Use case 04 · Relationship DriftRelationships rarely end loudly. They drift.When a client relationship starts to slip, Luscent shows it in the Health Score, links the messages behind it, and puts the next conversation on the relationship manager's list.
See it runNinety days, at no cost, with three to five relationship managers, starting on invented clients. Success metrics are agreed in writing before anything is connected, so at the end there is a decision rather than an impression.
The terms