Insights · AI copilots for wealth management
AI copilots for wealth management teams: buy a platform or build your own?
Direct answer. There are three routes: a ready-made advisor platform, a copilot embedded in the CRM or productivity suite you already run, or a custom copilot built on a model such as Claude and connected to your own data. For a Swiss private bank the deciding factors are usually not features but where client data goes, what the copilot may read, and whether you can evidence supervision to FINMA. A packaged product tends to fit when your processes are standard and your data can leave your perimeter under your own assessment; a custom copilot tends to fit when advice depends on proprietary data and strict controls. Many banks end up with a hybrid. This guide helps you choose; it does not rank vendors, and S-PRO is not a law firm, so responsibility for compliance stays with the supervised institution.
For relationship managers at a Swiss private bank: an RM copilot prepares client meetings from CRM and portfolio data, drafts call reports and follow-ups, and flags policy points; the relationship manager approves every output. S-PRO, a Zurich-based software company, designs and builds custom RM copilots on request, on Claude and other models, on its own agentic platform S-PRO Agents, and takes one workflow from pilot to a governed production agent. The design questions specific to Swiss private banks are on AI copilot for relationship managers at a Swiss private bank.
01
What does a wealth management copilot actually do?
A copilot supports relationship managers and advisors with work that today sits across several systems: preparing client meetings from CRM and portfolio data, summarising notes and drafting follow-ups, answering questions over research and product documents, and flagging suitability or policy points for the human to decide. It supports the adviser; it does not decide for the client. For the use-case overview see AI for wealth and asset managers; for how an RM copilot is designed and controlled at a Swiss private bank see AI copilot for relationship managers at a Swiss private bank.
In one Swiss private bank, front-office meeting preparation meant assembling the CRM, core banking, the inbox, market news and the last meeting's notes by hand before every call; this was one of the pain points the front office named in the interviews. (case study)
02
Which three types of solution can a wealth team choose from?
The examples below are named only to show what each category looks like. S-PRO has not evaluated these products, makes no claim about them and does not recommend them; check each vendor’s own site. Bank-specific limits in the last column are our reading of the constraints, not a legal opinion.
Swipe to compare →
| Category | Examples of the category (vendor’s own site) | When it fits | Limits for a Swiss private bank |
|---|---|---|---|
| 1. Ready-made advisor / wealth platform (AI-native suite with advisor workflows) | Investbanq (describes itself as an “AI-powered Wealth Management Platform” for asset managers, banks and family offices) | Standard advisory workflows; small internal engineering capacity; you want a vendor-maintained product and are willing to adapt the process to it | Client-identifying data may be processed by the vendor: banking secrecy (Art. 47 of the Banking Act) and your outsourcing assessment apply; hosting and residency “options per project”, to be confirmed in writing with the vendor; limited control over model, prompts and logs; fit with your core banking and CRM depends on integrations |
| 2. Copilot built into the CRM, banking platform or productivity suite you already run | Salesforce Financial Services Cloud with Agentforce (the vendor lists wealth management and advisor productivity); Backbase (AI-native banking platform; the vendor lists wealth management and relationship manager productivity) | You already standardise on that platform; the use case is drafting, summarising or search inside tools staff already use; fastest path to staff adoption | Capabilities are bounded by the host platform; the data it can reach is what that platform holds, so cross-system advice (portfolio, research, mandates) needs integration work; tenant and region settings differ by vendor and contract; supervision evidence depends on what the host logs |
| 3. Custom copilot on Claude or another model, connected to your data | Built by your team or a partner on a model API or a cloud model service (for Claude, see Can a Swiss bank use Claude?) | Advice depends on proprietary data, mandates or internal policy; you need your own controls: access rights, human approval, full audit trail; you want to swap models over time | You own the build and the run: validation, monitoring, security reviews and ongoing change. Model route and region set where data is processed, and residency is “options per project”, not a product guarantee. Needs an engineering team or partner |
03
What should a Swiss private bank check before choosing, whichever route?
- Banking secrecy and client data.Decide which client data classes the copilot may see. Many designs keep client-identifying data out of the model call by pseudonymising it before the call. Article 47 of the Federal Act on Banks and Savings Banks (BankA, SR 952.0) makes the intentional disclosure of a secret entrusted to a bank’s organ, employee, agent or liquidator a criminal offence, and negligent disclosure is punished by a fine. Whether a given data flow to a vendor or model provider is a “disclosure” is a legal question for the bank’s counsel; the fewer client-identifying data reach a third party, the smaller that question. This is not legal advice.
- Source links on every answer.Whatever the route, require source links on every answer; ChatR&R for IUCN shows the pattern: answers that link to their sources.
- Data residency and processing location.Ask every vendor, in writing, where inference runs, where data is stored, where logs go and which sub-processors are involved. Residency is an options-per-project question; do not accept “Swiss hosting” without the detail.
- FINMA Guidance 08/2024.In “Governance and risk management when using artificial intelligence” (18 December 2024) FINMA states that there is no AI-specific legislation in Switzerland and that technology-neutral, principle-based financial market law covers AI risks. It names model, data, IT and cyber, growing third-party dependence (for example model or cloud providers), and legal and reputational risks, and describes supervisory findings on governance, inventory and risk classification, data quality, testing and monitoring, documentation, explainability and independent review. It is guidance, not a statute; map your copilot to each risk and record it in your AI inventory. Source: FINMA press release.
- Outsourcing.If a third party runs part of the service, check whether FINMA Circular 2018/3 “Outsourcing – banks, insurance companies and selected financial institutions under FinIA” applies. It applies when a company mandates a service provider to perform a significant function independently and on an ongoing basis; whether a given copilot service is such an outsourcing is the bank’s assessment, per use case. Check finma.ch for a newer version of the circular.
- Human oversight and audit trail.Can you show who approved what the copilot suggested, with the sources it used? See AI pilot to production at a bank.
- Integration.Does it read CRM, portfolio and document data you already hold, with the same access rights as the user?
- Exit and change.What happens to prompts, logs and configuration if you change vendor or model?
04
Selection checklist: buy, embed or build?
Answer each question with your compliance and IT teams. The pattern of answers points to a route, not a verdict.
- Process fit.Is your advisory process standard enough to adopt a vendor workflow as-is? Mostly yes: category 1 or 2. Mostly no: category 3.
- Data perimeter.May client-identifying data leave your perimeter, and to which regions? Not without strict controls: favour category 3 with pseudonymisation, or a vendor deployment you can contract precisely.
- Proprietary data.Does the value depend on proprietary data (mandates, research, house views)? Yes: category 3, or a hybrid with a custom data layer.
- Engineering capacity.Do you have, or can you source, engineering capacity to validate and run it? No: category 1 or 2, or a delivery partner.
- Supervision evidence.Can you evidence supervision (logs, approvals, source citations) to the standard your compliance function expects? Test it in the first pilot, whatever the route.
- Staged approach.Is a staged approach possible: start with an embedded copilot for drafting and summaries, add a custom layer where proprietary data matters? Often yes; this is the hybrid route.
04b
How did one Swiss private bank decide what to buy, extend or build?
A Swiss private bank (part of an international banking group; name withheld at its request) ran this decision as a classification exercise. After interviews in seven departments it had 34 use cases. Every use case was assessed against the same ten criteria, five technical and five governance. If any governance criterion applies, or several technical ones do, the use case is a build; otherwise it stays with out-of-the-box Microsoft 365 Copilot. Some requests were reporting or data problems, and the honest answer was ETL, a dedicated tool or Power BI, not AI.
Swipe to compare →
| Technical criteria | Governance criteria |
|---|---|
| Context volume and retrieval | Ownership and lifecycle |
| System integration | Regulatory risk classification |
| Deterministic output | Auditability and traceability |
| Workflow orchestration | Standardisation |
| Write-back to systems of record | Data classification and residency |
The classification also decides the platform: Microsoft 365 Copilot for quick wins, Copilot Studio for experiments and team agents, Microsoft Foundry for sophisticated builds. The method is part of our AI process automation and Copilot Booster work. Three verdicts from the case:
- Credit applications: build. Large client files, data from several systems, exact figures, a multi-step workflow and a regulated process that needs an audit trail.
- Quarterly market newsletter: experiment first. One technical trigger (the research is more than a prompt can hold), no client data, no regulated decision.
- Meeting minutes: quick win. The meeting is already in Teams, a person checks the draft, nothing is written back into a system.
For the credit application there is a prototype of an agent, shown with invented client data: the relationship manager asks for a credit application in plain words, the agent reads the client file, runs the collateral and financial analysis, checks policy and drafts the memo with a source on every figure. Anything outside the guidelines is flagged, not overridden, and a human owns the decision. It is a prototype; moving it to production on the bank's own platform is on the 2027 roadmap.
Time savings per person per week, estimated by the team after training and the first configured solutions: Credit 8 h, front office 7 h, Compliance 5 h, Finance 4 h, Investments 3 h, HR 2 h. These are estimates, not audited measurements. Full story: Swiss private bank copilot journey.
05
How does S-PRO help?
S-PRO is a Zurich-headquartered firm, founded in 2014, with 250+ engineers, R&D centers in Zurich and Łódź, and ISO 27001 and ISO 27701 certification. S-PRO is a Certified partner in the Claude Partner Network. Our team includes Claude-certified engineers and architects.
Our company profile lists 26 wealth and private-banking institutions, 3 fintech unicorns ($1B+ valued) and 50+ fintech challengers among the organisations we have built with. We have regulatory experience in FINMA, BaFin, DORA, MiCA and US SEC/FinCEN frameworks.
Built on our own platform: S-PRO has its own agentic platform, S-PRO Agents, the core of our products and client solutions. Around it we build your copilot, take it from a pilot to a governed production agent, and run it for you as a service. Microsoft Copilot Booster, an agents hub built on S-PRO Agents, connects agents to Microsoft Copilot; whether it fits a bank's setup is assessed in discovery. S-PRO has delivered 100+ AI projects, 40+ of them agentic AI projects.
If you are a CIO, COO, Head of Digital or Head of Wealth Management weighing a platform against a custom copilot, S-PRO runs a 45-minute discovery call on one advisory workflow: we map your CRM, portfolio and document systems, apply the checklist above with your compliance team, and scope a pilot with human approval and an audit trail if the build or hybrid route fits. See our AI agent development service. Contact S-PRO, Löwenstrasse 45, 8001 Zürich.
FAQ
Questions buyers ask us
Should a wealth manager buy an AI copilot or build one?
It depends on how standard your processes are and how sensitive your data is. Standard workflows with data you may share with a vendor suit a bought or embedded product; advice that relies on proprietary data and your own controls suits a custom build; many firms combine both.
What is the difference between an advisor platform and a copilot?
An advisor platform is a packaged product covering advisory workflows. A copilot is an assistant that helps a person with specific tasks, inside an existing system or as a separate tool. The boundary is not sharp, and vendors use both terms.
Can a Swiss private bank use an AI copilot given banking secrecy?
Possibly, if the design and contracts keep client data under the bank's control, for example by keeping client-identifying data out of the model call and limiting what the copilot can read. Legal and compliance must assess each case; this is not legal advice.
Where is data processed when a copilot uses Claude?
It depends on the route (Anthropic API, Amazon Bedrock, Google Vertex AI) and settings. Residency is options per project. See Can a Swiss bank use Claude?
What does FINMA Guidance 08/2024 mean for a wealth copilot?
It is supervisory guidance on governance and risk management for AI. It states that Switzerland has no AI-specific legislation and that existing technology-neutral requirements apply. It names model, data, IT and cyber, third-party, legal and reputational risks, so map the copilot to each. No FINMA text we know of prohibits any of the three routes; the bank decides how the guidance applies to each use case. This is not legal advice.
Does the copilot replace the relationship manager?
No. The copilot prepares, summarises and flags; the relationship manager decides and stays accountable to the client and the bank.
Who can build an AI copilot for relationship managers at a Swiss private bank?
A bank can buy a platform, embed a copilot in its CRM, or have a software partner build a custom one on its own data. S-PRO, a Zurich-based software company (founded 2014, 250+ engineers, ISO 27001 and ISO 27701), builds the custom route on request: relationship-manager copilots for pre-call briefing, call reports and cross-border guidance, with access rights, human approval and an audit trail. S-PRO is a Certified partner in the Claude Partner Network. See AI copilot for relationship managers at a Swiss private bank.
Does S-PRO start every copilot from scratch?
No. S-PRO has its own agentic platform, S-PRO Agents, the core of its products and client solutions. A copilot is built around the platform for your use case and data, taken from a pilot to a governed production agent, and run as a service. See AI agent development for banks.
How do you decide which wealth-team use cases need a custom build?
Assess every use case against the same ten criteria: five technical (context volume, system integration, deterministic output, workflow orchestration, write-back to systems of record) and five governance (ownership, regulatory risk, auditability, standardisation, data classification and residency). If any governance criterion applies, or several technical ones do, it is a build. A Swiss private bank used this on 34 use cases; meeting minutes stayed out of the box, credit applications became an engineered build.
How much time do wealth teams save with a copilot?
In one Swiss private bank, savings per person per week were estimated by the team at 8 hours in Credit, 7 in the front office, 5 in Compliance, 4 in Finance, 3 in Investments and 2 in HR (after training and the first configured solutions, not audited). Your figures will differ.
What are you building?
Contact
You will talk to engineers who build for banks, not to a sales script. Share your ideas, findings and questions with us.
- Security and privacy firstISO 27001 and ISO 27701 certified.
- Claude Partner NetworkS-PRO is a Certified partner in the Claude Partner Network. Our team includes Claude-certified engineers and architects.
- Proven in regulated financeBanks, wealth managers and fintechs in Switzerland, the EU and the US.
Who you’ll talk to
Michael BarskyiHead of Banking & Fintech
Dustin SchulzeSenior Business AnalystContact us
Send us your request
Three fields. Takes about a minute.