Find out before you move a single client record.
Ninety 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.
Join the pilot programmeBest for a sponsor in compliance or private banking leadership who is ready to scope three to five Relationship Managers.
Talk to Armin firstBest for testing the idea in 15 or 30 minutes, before compliance is involved.
Not ready for either? Take the eight-question readiness check first.
At a glanceCohort open
- Applications
- Open
- Length
- 90 days
- Cost
- Nothing
- Seats
- 3 to 5 relationship managers
- Data
- Synthetic first
- Migration
- None
Ninety days, free, and nothing moves until you have seen it work.
The trade is legible in both directions. You get ninety days and a written review against criteria you set. We get the first look at what this does in front of a real book, which is the thing no amount of synthetic data will tell us.
What the firm gets
- Ninety days at no cost
- No fee, no commitment to buy, no auto-conversion to a paid contract at the end.
- Success metrics agreed before day one
- Written down before anything is connected, so the review at day ninety is against your criteria and not ours.
- Synthetic data first
- The first four weeks run on invented clients. Your compliance function approves a pilot that touches no client record.
- A named person, weekly
- One person on our side for the whole ninety days, on a scheduled call, not a shared inbox.
- Nothing migrated
- Luscent reads where the data already sits, and your CRM stays the system of record.
- Your data leaves when you say
- Deletion or return on termination, on terms set out in the data processing agreement rather than asserted on a marketing page.
What Luscent gets
- What a real book looks like
- Every design decision so far has been made against synthetic data. We need to be wrong in front of someone.
- Rule coverage tested against your jurisdictions
- The rules core covers MiFID II, GDPR, the EU AI Act and the Brazilian resolutions. FinSA and FinIA are on the roadmap, not in the product today. Your booking centres will find the gaps.
- A false-positive rate we did not choose
- Triaged weekly with your compliance function. It is one of the agreed metrics, and it is the one we expect to look worst early.
- A reference, if it worked
- Only if it worked, only with your review of the wording, and never as a condition of the pilot.
A pilot where only one side's benefit is stated is a pilot the other side has not thought about. Ours is on the right of this section, in the same type as yours.
#the-tradeFive stages, each with something true at the end of it.
A plan with no stated end state per stage is a list of activities. Each of these finishes with a sentence you can check, and the last one is a decision rather than an impression.
The ninety days, in five stages
Signature
Scope, seats and success metrics, in writing
The SOW names the three to five relationship managers, the booking centres in scope, and the metrics the pilot is judged on. Signature is gated on Luscent S.à r.l. existing and holding its business permit.
The test is defined before it starts.
Connect
Through your own consent flow
Microsoft 365 and Salesforce, authorised by the firm, scoped to what the firm chooses to share. Running on synthetic clients throughout, so nothing yet depends on a real record.
The system can see a book.
First look
The book, ranked, and you say whether it is right
Every relationship carries a Health Score and a reason. The first conversation is whether the ranking matches what the desk already believes. Disagreement here is the useful outcome, not the failure.
You know whether it agrees with you.
First Signal acted on
A recommendation a person acted on
One Signal, one decision, one record, with the rule that fired and the messages it was drawn from attached. False positives are triaged weekly with the compliance function, and the stage closes with a mid-point read-out to your sponsor against the day-zero metrics.
There is something to judge.
Review
The metrics agreed on day zero, answered
A written review against the day-zero criteria, including what did not work. If the answer is no, the answer is no, and the deletion procedure runs.
You have a decision, not an impression.
Five things from you, and nothing to build.
Procurement in this industry stalls on the questions nobody wrote down: who signs, what IT has to do, and whose time it takes. This is the whole list, on both sides.
What the firm provides
- A sponsor who can sign
- From compliance or private banking leadership. The firm signs the SOW, and the sponsor takes the mid-point read-out at week eight and the review at the end.
- Three to five named relationship managers
- The seats on the SOW. They use it on their own book and say, at the first look in week four, whether the ranking is right.
- Your compliance function, weekly
- A scoping call before the SOW, then the weekly false-positive triage. It is part of the design, not an escalation path.
- An administrator for the consent step
- Microsoft 365, and Salesforce if you run it, authorised through your own consent flow and scoped to what you choose to share. Nothing to build.
- Half an hour a week
- One scheduled call with the named person on our side, for the ninety days.
What Luscent provides
- The environment and the models
- Luscent runs both. You do not need an AI team, and nothing is hosted on your side.
- Invented clients first
- The first four weeks run on synthetic data, so the first approval your compliance function gives is for a pilot that touches no client record.
- A named person, weekly
- The same person for the whole ninety days, on a scheduled call, not a shared inbox.
- The triage and the record
- Each week's false positives, brought to the triage. Every Signal acted on is recorded with the rule that fired and the messages behind it.
- The written review, and the exit
- A written review against the day-zero metrics, including what did not work. If the answer is no, the deletion procedure in the data processing agreement runs.
If this list and your SOW ever differ, the SOW is the one that counts.
#who-does-whatBecause the short approval buys you the long evaluation.
Starting on invented clients is not caution. A pilot that touches no client record is a different approval from one that does, and it is a much shorter one. The two paths end at the same vendor assessment. Only one of them lets a firm find out whether the product is worth assessing before it spends the assessment.
Two approval paths, drawn to the same scale
A pilot that starts on synthetic data needs roughly one week of compliance approval before it can run, leaving thirteen weeks to evaluate the product. A pilot that starts on live client data needs a full vendor assessment first, which commonly runs to nine weeks, leaving five. Both paths end at the same vendor assessment; only one of them lets a firm find out whether the product is worth assessing.
Solid is approval. Outlined is the time left to evaluate. Both paths end at the same vendor assessment; only one lets you find out whether the product is worth assessing first. Nine weeks is a common figure for a full assessment, not a measured one.
Nine weeks is a figure commonly quoted for a full vendor assessment in this industry. It is not measured, and it is drawn as an outline for that reason.
#approvalIt reads. A person decides.
The first question in every one of these conversations is what happens to the firm's systems. Luscent reads what the firm already produces and generates its output inside Luscent. The CRM stays the system of record, and nothing reaches a Client until a Relationship Manager confirms it.
What Luscent reads, produces and leaves as it is
Luscent reads Microsoft 365 mail and calendar, Salesforce if the firm runs it, and meeting notes the firm already writes. It produces Signals, Health Scores and suitability evidence inside Luscent. The firm's CRM stays the system of record, nothing is migrated, and no message goes out without a Relationship Manager.
- Microsoft 365 mail and calendar
- Salesforce, if you run it
- Meeting notes you already write
- Signals, with the rule attached
- A Health Score per relationship
- Suitability evidence, as it happens
- No data migration
- No new system of record
- No message without the RM
The right-hand frame is what the pilot does not change: your CRM stays the system of record, and no message goes out without a Relationship Manager.
Nothing is migrated during the pilot, and the CRM stays the system of record throughout.
#boundaryNo pilot has completed, so there is nothing to report.
This page used to carry four numbers under a heading about value: a retention increase, assets recovered per hundred million, a compliance saving and a first-mover window. None of them came from a pilot, because there has not been one. They are gone, and what they were is written here rather than quietly deleted.
A retention number
No pilot has completed. Any retention figure would be modelled, and a modelled figure on a page headed Results is a result.
Recovered assets per relationship manager
The same problem, with a currency symbol in front of it.
A compliance time saving
Plausible, unmeasured. Ask us again in ninety days with a cohort behind it.
A first-mover window
Nobody can date the closing of a market. It was on this page and it should not have been.
Everything below is either a commitment, which you can hold us to, or somebody else's figure with the source on the page. When a cohort produces a number, it will appear here with the cohort size and the date attached.
Kept in step with the FAQ and the Trust Center. Where any two differ, the Trust Center is the one that counts.
#not-claimedFour things that have to be true.
Seats are limited by our capacity to support them properly, not by scarcity as a technique.
#fitFour firms this will not work for.
A ninety-day pilot costs you time whether or not it costs you money. These are the cases where we would rather say so now.
Every other page on this site carries one of these. This page did not, which is how it ended up the least honest page on the site.
#wrongSix questions, answered before you have to ask them.
The gate on a pilot in this industry is not the budget and it is not the relationship managers. It is the person who has to sign off on a vendor reading client correspondence. These are the six they open with.
Does any client record leave our systems?
Not in the first four weeks: the pilot runs on synthetic clients. When live data is connected, it is authorised through your own consent flow and processed in the European Union.
Where does inference run?
In the EU, with EU providers only. No OpenAI, Anthropic or Google API sits in the path of client data.
Is our data used to train anything?
Luscent does not use client data to train or fine-tune models, as stated in the Trust Center.
Who are the sub-processors?
Six, named in the Trust Center with their jurisdictions. Three run the EU infrastructure: Scaleway in Paris, Hetzner for the data and AI services in Germany, and Mistral AI (France) as the primary inference provider, through its EU regional endpoint. Two are in the United States: Tailscale receives network metadata only and Mailgun sends outbound email. Luscent states that rather than leaving it to be found in a questionnaire.
What certifications do you hold?
None today. Controls are aligned to ISO/IEC 27001:2022 and certification is planned. The Trust Center lists the controls in place, and the full register is in the security pack.
What happens to the data at the end?
Data is deleted or returned on termination, on the terms set out in the data processing agreement. Luscent does not publish a timescale it has not agreed with you, so that number is in the DPA and not on this page.
The full versions of all six, with the sub-processor names and jurisdictions, are in the Trust Center.
#complianceA written reply within 48 hours, whether or not it is a yes.
Luscent is a technology provider, not a regulated financial institution, and nothing here is legal or compliance advice. The platform generates evidence and surfaces Signals; decisions remain with the firm and its professionals at all times.
Pilot agreements are signed with Luscent S.à r.l. in Luxembourg.
#afterApplications are open. If the answer is no, you will have spent forty-five minutes and learned what a system of intelligence does. If it is yes, you will know inside ninety days whether it is worth having.
Before you apply
Talk to Armin first.
15 or 30 minutes with Armin Prior, CEO and co-founder. Ask about the pilot, the rules engine or where the data lives.
Comparing vendors first? Take the ten questions to ask any vendor into every conversation, including this one.
The calendar loads from Cal.com only when you pick a length. What you enter there goes to Cal.com and to Armin; see the privacy policy.
Luscent S.à r.l. is a société à responsabilité limitée in formation in Luxembourg, at House of Startups, 9 Rue du Laboratoire, L-1911 Luxembourg. Luscent stores and processes client data in the European Union only: storage on Scaleway in Paris, and the data and AI services on Hetzner in Germany. Sub-processors, certifications and security controls are documented in the Trust Center.