Before you begin
4 min read
This page sets out what must be contracted, decided and provisioned before Remy is installed, and which features are limited when a dependency is missing on your side.
Read it before you start any procedure in the For administrators, For IT operators or For developers tracks. Every one of those procedures assumes the conditions below are already met.
Remy is not self-service. Nothing in this documentation enables an install of Remy on a platform where it has not been contracted. The skill package, the installer and the administration tool are delivered as part of the engagement.
Readiness checklist
Remy is a contracted, productised package — Advisor UI, Client Memory and Skill Packages — delivered complete and then adopted in a joint design phase with the delivery team. Confirm all three statements below before the first install:
Contracted and scoped. Remy is contracted for your organisation and the pilot group — advisors and their clients — is agreed.
Design phase closed. Process fit, connected systems, memory shape, scope and entitlements, thresholds, routing and language are all decided.
Prerequisites provisioned. Every item in the next section is in place on your side.
If the design phase is still open, see Design phase, branding, language and audit.
Prerequisites
The prerequisites highly depend on the deployment model and differrent
Provision each item before the first install. The Owner column names the function that normally supplies and signs off the item.
Item | Requirement | Owner |
|---|---|---|
Platform | The bank's own deployment of the AI platform - public cloud, private cloud or on premises - with knowledge base, agent runtime, MCP hub, side panel and scheduled tasks enabled | IT |
Space | A dedicated agent space for the advisor team; Skills tool enabled and pointed at the Remy skills folder; side panel pointed at the dashboard | Administrator |
Model and Harness | A frontier model with tool use and subagent support available in the space. Current minimum requirement Models inferior to GPT-5.5 or Claude Sonnet 5.5 may lead to significantly reduced accuracy and must support vision capabilities when document generation is required. | IT |
Connectors | Outlook mail and calendar as the minimum; Teams recommended; CRM, portfolio, web search and further MCP servers as approved - all with delegated, on-behalf-of permissions | IT · Security |
Identity | Identity federation with group sync- user to client book, team, deputy, handover - available for automated synchronisation | IT · IAM |
Technical user | An API token for the administration tool that pushes skills and configures the space | IT |
Owners | A named business owner per source system; compliance, privacy and records owners for retention classes, the legal basis for public-source research and the excluded categories | Business · Compliance |
Limitations that depend on your environment
A missing dependency limits a feature, not the product. The affected conclusions are restricted, and an explicit question or a blocked section is produced rather than the preparation being abandoned. The tables below list what is limited, and by what.
Connected systems and data
Area | Depends on | Without it |
|---|---|---|
Meetings card and meeting briefs | Outlook calendar access (mail alone is not enough) | Meetings must be stated by the advisor in chat ("I'm at meeting X on Thursday, prepare me"); no proactive briefs |
Teams content | Which Teams mode is licensed: chat only, or recordings and transcripts | Chat-only mode gives no call or meeting transcripts; interaction history is thinner |
Master client list and master client ID | A readable CRM / client record connector | The book is derived from document folders and mailbox correspondents; generated client IDs are used until a system ID arrives |
Portfolio drift monitor, portfolio blocks on the client 360 and brief | A portfolio / core-banking connector | Drift runs on the last mirrored figures and says so; portfolio and performance blocks show as placeholders |
Screening, market radar, referrals, live web intelligence in briefs | Web search approved by the bank's security and compliance functions | These skills stay in the package but inactive; briefs are produced from memory and connected systems alone |
Prepared drafts in the mailbox | The mail connector's draft-creation capability | Drafts are still written into the client memory; the advisor copies them into a mail |
Scope and memory shape
Area | Depends on | Without it |
|---|---|---|
Team and organisation scope, deputy cover, handover | IdP group synchronisation and role mirroring | Per-user scope only; team and organisation views follow once federation is in place |
Client 360 completeness | Which topic pages are in scope at launch and which systems feed them | Out-of-scope pages are absent; unknown fields show as unknown, never guessed |
Output and presentation
Area | Depends on | Without it |
|---|---|---|
PDF briefs | An HTML-to-PDF renderer in the deployment | HTML briefs in the side panel only |
Corporate identity on briefs | A brand pack supplied by the bank | The standard design system is used |
Client-communication languages | Languages agreed in the design phase | English drafts |
Platform, operations and governance
Area | Depends on | Without it |
|---|---|---|
Overnight readiness by 07:00 | Scheduled tasks enabled; book size; connector throughput | Larger books push the pipeline start earlier; a missed night is signalled on the dashboard |
Anything written back to CRM, KYC or portfolio systems | Not part of the package | Core systems are read-only; write-back is a separately governed decision |
Data residency and retention | The bank's platform deployment and knowledge-base policies | Remy inherits them; it cannot offer retention or residency the platform does not |
On-premises or air-gapped deployments | Model availability and outbound network policy | Web-dependent skills unavailable; model choice constrained to what is hosted |
Where a component has been delivered but cannot be used because of a dependency on your side — system or data access, connector or permission provisioning, internal approvals — it is activated once the dependency is resolved, without redevelopment.
Plan the first run
The first install mines every client once. The memory build is the slow step and scales with the number of clients and the volume of documents and mail per client; identity resolution and mining run five clients in parallel.
Schedule the first run outside working hours for a large book. From then on the nightly pipeline is incremental — see Schedules.