[00] IntegrationsLive, in build, roadmap

What Luscent connects to, and what it does not yet.

Luscent reads the systems your firm already runs and writes nothing back. Two connections are live today. The rest are marked for what they are: in build, or on the roadmap with no date promised.

Connections8

  • Microsoft 365Live
  • SalesforceLive
  • Luscent CRMIn build
  • Core bankingRoadmap
  • Portfolio managementRoadmap
  • ConsolidationRoadmap
  • Custodian platformsRoadmap
  • Advisor platformsRoadmap
[01] Connections8
CommunicationsLive

Microsoft 365

Mail, calendar, Teams

Pilots start here.

CRMLive

Salesforce

Client records and activity, including Financial Services Cloud

Scoped separately for a pilot.

CRMIn build

Luscent CRM

Client records, activity history and relationship data

Built in-house for firms that do not run a CRM. Included at no extra cost.

Banking and custodyRoadmap

Core banking

Positions and balances

Not shipped. No date is promised.

Portfolio and platformsRoadmap

Portfolio management

Holdings and returns

Not shipped. No date is promised.

Portfolio and platformsRoadmap

Consolidation

Positions across custodians

Not shipped. No date is promised.

Banking and custodyRoadmap

Custodian platforms

Positions and statements

Not shipped. No date is promised.

Portfolio and platformsRoadmap

Advisor platforms

Holdings and valuations

Not shipped. No date is promised.

[02] How a connection worksThree facts

Your CRM stays the record

Luscent reads your CRM and does not write to it. In Microsoft 365 it sends an email or books a meeting only when the Relationship Manager does so from Luscent.

Authorised by the firm

Each connection runs through the provider's own consent flow and is scoped to what the firm chooses to share.

Stays in the EU

Client data is stored on Scaleway in Paris; Luscent's data and AI services run on Hetzner in Germany.

Sub-processors, data classes and access controls are in the Trust Center.

[03] Questions

Questions

  1. Which systems does Luscent connect to?

    Luscent integrates with Microsoft 365 and with Salesforce, and is building its own in-house CRM for firms that do not run one. Each connection is authorised by the firm through the provider's own consent flow and is scoped to what the firm chooses to share.

  2. Does Luscent require a firm to replace its existing CRM?

    No. Luscent is an intelligence layer over the systems a firm already runs. A firm with an existing CRM such as Salesforce keeps it, and Luscent integrates with it. A firm without one will be able to use the Luscent CRM, which is in build and included for Luscent clients at no extra cost. The system of record stays wherever the firm wants it.

  3. Do we have to move any data into Luscent?

    No. Luscent reads Microsoft 365 and Salesforce where the data already sits, through connections the firm authorises and scopes. Nothing is migrated.

  4. Does Luscent write anything back into our systems?

    Into your CRM, no: Luscent reads it, and it stays the system of record. In Microsoft 365, Luscent sends an email or books a meeting only when the Relationship Manager does so from Luscent.

  5. What does a pilot connect?

    Pilots start on Microsoft 365, with three to five relationship managers. A CRM connection is scoped separately with the firm.

Pilots start on Microsoft 365, with three to five relationship managers.

A CRM connection is scoped separately with the firm.