Why Remy
4 min read
Every advisor already carries a memory of their clients - in their head, their inbox, their notes. It is incomplete, it goes stale the moment they are on holiday, and it leaves when they do. Remy makes that memory complete, current and owned by the bank, and puts an AI teammate on top of it that does the preparation overnight so the advisor only has to review and decide.
Advisor throughout this page means the relationship manager or financial advisor who owns a book of client relationships, reviews what Remy prepares, and decides what to send.
Memory, not sourcing
What separates Remy from a chat assistant with connectors:
Sourcing - a value taken from one system and shown in one place. You can point to the field it came from.
Memory - a conclusion that exists only because two or more sources were joined. Nobody typed it anywhere, and it is kept for the next time it matters.
Remy produces memory on its own:
Across sources. On a call in May the client said they were expanding into Asia. This week the news reports a Singapore office, and the policy on file covers one jurisdiction. Remy flags the gap and drafts the proposal.
Learned, then used. In March the client mentions the children start school in autumn. In September the renewal brief and the prepared email include them in the household cover.
Across the whole book. The CIO office brings forward its rate-cut forecast. The dashboard opens with every client it affects, from idle cash to the one waiting to buy property, each with a prepared note.
What the advisor stops doing
Assembling a picture from Outlook, the client record and the KYC system before every meeting.
Remembering which promise was made to whom.
Noticing that a document expires next month.
Writing routine client letters from scratch.
Most of the preparation is done by the time the morning page opens - and nothing has been sent, decided or written to a system of record on the advisor's behalf.
What the bank gets
Concern | How Remy answers it |
|---|---|
Client-sensitive data in an AI tool | Remy runs inside the bank's own deployment, under the user's own permissions, on the bank's knowledge base. No new database. Governance, retention, versioning and audit are inherited rather than bolted on. |
The memory follows the client, not the advisor | Client memories are knowledge-base assets of the institution, not personal files. The governed record of the relationship - compliance, mandate, commitments, matters in flight and the change log - sits in the organisation-level memory, and that is what a successor inherits on day one. What is promoted there, by whom and under which rule is agreed in the design phase; see Client memory - how it works. |
Regulatory exposure | Remy is never a system of record. KYC and custody fields are mirrored or blank, never inferred. Screening hits and suitability observations stay pending until a human dispositions them. No skill sends mail or writes to a core system. |
Encoded domain knowledge | Connectors, chat, an agent harness and a knowledge base are all available in the market. The knowledge of how advisors work is not: which facts matter, how they are organised, what a brief must contain, which alerts fire when, what a client letter may say. That is what the package encodes, and what the bank tunes to its own processes. |
Lock-in to one vendor's data model | The memory is plain markdown in the bank's knowledge base. Further systems connect as MCP servers without changing it, and the bank authors its own skills against the same contracts. |
One document through the system
A client returns a signed mandate form by email. The advisor files it in the client's document folder - the single copy. On the next run Remy records the type, issue and expiry date and a link in the documentation register, clears the open "not on file" action together with its prepared letter, and updates the dashboard and the next brief. The advisor sees the change; if they reply to the client, that mail is read on the following run and the loop closes.
Why it matters: the document lives once, under the bank's existing permissions and retention. The memory answers "is it on file, since when, where" with the original one click away. The audit trail is the register row plus the change log, not a manual tick. Nothing was sent by a machine.
What ships
Remy is delivered complete as a versioned package after contracting. The design phase decides which connectors are wired, which pages are in scope and how each monitor is tuned; nothing in the package needs redevelopment to activate. See Before you begin for what depends on your own environment.
Package A · Advisor UI
Installer, dashboard, client 360, meeting brief side panel, record pages, drafts, questions, approvals and evidence, accessibility, brand pack.
Package B · Client Memory
14 topic pages, live registers, change log, prepared letters, provenance on every fact, identity controls, conflicts register, three scope levels, the mining pipeline, and connectors to every source.
Package C · Skills
Mining and curation, monitoring, daily brief and dashboard, lifecycle, communication and actions, orchestration and setup, plus the scheduled task set. The bank can add its own skills on the same memory and actions register.