Skip to content
Start free
All industries

Wealth management · Adviser context

Client context.
With the sources attached.

Connect client records, holdings, household relationships and research documents for the applications your advisers use to prepare and follow up.

Discuss your adviser workflow Explore the quickstart

Prepare the conversation from its records.

Scope the client, retrieve the relevant holdings and documents, and keep each source reference with the briefing your application assembles.

Client scope → source records → adviser briefingIllustrative preparation flow
Prepare a briefingClient CU-07Source references stay attached
01 / Client scope CU-07
Household reference
HH-04
Account reference
AC-12

The application selects the client and the records it is allowed to retrieve.

02 / Retrieve the working context

Mandate

M-09 · version 3

Recorded client instructions and their source document.

Linked client: CU-07

Holdings

Import H-14

Stored account and instrument rows, with the supplied as-of date.

Linked account: AC-12

Research

R-04 · version 2

Retrieved passages with document and instrument references.

Source passage: R-04 / 3
03 / Application assemblesBrief BR-05

Client context, source versions and questions for the adviser.

What should the adviser inspect?

Mandate sourceCheck the instruction document and the version referenced.

Holdings contextCheck the imported dataset and its supplied as-of date.

Research evidenceRead the source passage before using it in the conversation.

Illustrative records and workflow. The application assembles the briefing; source retrieval does not establish suitability or produce an investment recommendation.

5 use cases / Wealth management

The right modalities for your workflow.

Start with the combination that fits your question. These are recommended starting points; the best fit depends on your data and query patterns.

Wealth management: use cases, recommended query modalities and why each combination fits.
Use caseRecommended modalitiesWhy this combination fits
Portfolio servicing

Retrieve client positions, transactions and account activity.
SQL

SQL joins portfolio records, filters effective dates and aggregates the imported holdings and transaction data.
Household relationship view

Connect clients, households, accounts and advisers.
SQL Graph

SQL supplies account and client attributes. Graph follows household, ownership and adviser relationships.
Issuer research context

Trace portfolio exposure to issuers and their published documents.
SQL Graph FTS

SQL retrieves positions, Graph connects instruments and issuers, and FTS locates relevant terms in issuer research.
Adviser briefing retrieval

Find source material relevant to a client meeting.
SQL FTS Vector

SQL supplies client context. FTS and Vector retrieve research by named entities, exact wording and similarity of meaning.
Mandate document lookup

Find recorded client instructions and agreement wording.
SQL FTS

SQL identifies the client and agreement version. FTS searches the indexed document for the instructions being reviewed.

Combine query results in your application using shared record IDs. Keep text indexes and embeddings updated as the source data changes.

Choose the query by the question

Facts, relationships
and source passages.

SQL
Which records belong in this briefing?

Filter client and account rows, join stored holdings and inspect their source timestamps.

SQL reference
Graph
How are the entities connected?

Traverse declared household, account, instrument and issuer relationships.

Graph schema
Full-text
Where does the document say that?

Find exact phrases or rank matching passages in text you have indexed.

Full-text reference
Vector
Which passages discuss this topic?

Retrieve text using supplied embeddings and return its original source ID.

Vector schema

A focused first build

Start with one client briefing.

Use sample client records, a holdings import and a versioned mandate to test the full retrieval path.

Review the design with us
  1. 01

    Retain identity and provenance.

    Store client, household and account IDs alongside source IDs, document versions and the supplied holdings date.

    Schema reference
  2. 02

    Keep retrieval sources aligned.

    Index text and embeddings through their separate endpoints. Have your ingestion pipeline track revisions and resolve results back to source records.

    Text indexing
  3. 03

    Review the client boundary.

    Apply your application's access rules across every query path. Test restricted users, outdated documents and missing references before introducing client data.

    Authentication reference

The database retrieves context. Your application and advisers own interpretation, recommendations and client decisions.