·
13 minute read
·
By
If you want a wealth management CRM with automated meeting capture, you have two routes: keep your current CRM and add an AI meeting assistant, or move to an Un-CRM, where your client records and the AI share one platform.
An AI meeting assistant can document your client conversations, prepare the meeting notes and send them into your existing CRM. Depending on the integration, it can add new information without seeing the client history, documents and records already stored in the CRM. An Un-CRM takes a different approach: client management and AI sit in one platform, designed so the information you already have helps with the whole relationship, not just the latest meeting.
Put simply, an AI meeting assistant doesn't replace a CRM: it works alongside it, and the CRM stays the system of record.
In short
Legacy CRM: The traditional system of record for client information, meeting notes, tasks and follow-ups. Depending on the system, you or your assistant still do many of the admin steps by hand.
Legacy CRM + AI meeting assistant: Adds AI to your existing CRM, to capture meetings, prepare notes and automate some tasks. How much it helps depends on how deeply the assistant integrates with the CRM.
Un-CRM: Combines CRM functions and AI in one platform, designed so the AI can work with the client information already in the system and carry it into the work that follows.
Which one should you choose? Keep your CRM and add an AI meeting assistant if your CRM meets your needs and the assistant can read your existing client records, not only write new notes. Consider an Un-CRM if your team still searches across tools for client history, documents and follow-ups after every meeting.
Why are advisors looking for AI meeting assistants?
Advisors look for AI meeting assistants because keeping a CRM up to date takes work, and much of it lands after the meeting. The CRM has long been the foundation of many financial advisory practices: one place for client profiles, meeting notes, tasks, documents and follow-ups. After a client meeting, someone usually has to write the summary, update the profile, create the tasks, prepare the follow-up and file the documents. Some CRMs automate parts of this, but you and your team still do much of what keeps the system useful.
An AI meeting assistant can reduce that work without changing the system you already use. Depending on the product, it processes the meeting, writes the summary, picks out action items, drafts the follow-up email and sends the meeting information into your CRM. It's also one more product to evaluate, pay for and manage. Its value beyond the meeting comes down to one thing: what it can actually read from your CRM, not simply whether an integration exists.
Option A: Can AI add-ons make your existing CRM less painful?
Yes, to a point. AI add-ons can document meetings, draft follow-ups and create tasks in your CRM. Where they fall short is when the add-on can write into the CRM but can't read what's already there.
Keeping your existing CRM makes sense if you're happy with it, if your workflows depend on it, or if your dealer or network requires it. In that setup, the CRM stays the system of record, and other tools handle specific jobs: meeting notes, email drafts, scheduling and other admin work. An AI meeting assistant can reduce how much information you and your assistant have to enter by hand.
Every month, I talk with a hundred financial and insurance advisors on average, in meetings with their teams and at industry events, about their practice, their technology and how they use AI. One frustration keeps coming up: the assistant writes into the CRM, but it can't see what's already there. Recently, an advisor on a three-person team walked me through their setup: a dealer-supported CRM, a general AI assistant with custom agents, and a dictation app. Each tool helps. They still copy and paste between them, because the CRM lets other tools push information in but doesn't open up what's already stored there. For a team that size, moving to a new CRM wasn't realistic, so the friction stays.
Some CRM integrations only go one way, or cover only part of the record. An AI meeting assistant may push meeting notes into the CRM while having little or no access to what's already stored there: past client records, existing documents, the full client profile. The level of access varies by product and integration.
An AI meeting assistant may know what was said in the last meeting without the client history it would need to spot what matters or help with the next steps. The tools are connected, but the intelligence available to each one can still be fragmented.
For some practices, that's a fair trade-off. Others may be better served by a system where client records, documents, meeting history and AI work together.
We started using Bloks for compliant notes, and quickly realized it flipped how we think about our CRM.
Brendan Gordon, Managing Partner, GBF Insurance and Investment Planning, Inc.
What happens after the meeting?
After a client meeting, someone has to document the discussion, update the right records, work out the next steps and prepare for the next conversation. Take an annual review. Your client mentions a change in their family situation, asks about an existing policy and agrees to send you an updated document. The conversation is only the start of the work.

Here's how the three approaches handle it.
After the meeting | Legacy CRM alone | Legacy CRM + AI meeting assistant | Un-CRM |
|---|---|---|---|
Meeting notes | The advisor or assistant writes and records the notes, unless the CRM automates it. | The assistant prepares notes and syncs them to the CRM. | Meeting notes are connected to the client profile in the same platform. |
Client history and documents | The advisor or assistant retrieves information from different sections of the CRM or other systems. | The assistant adds the new meeting. Whether it can read the existing history and documents depends on the integration. | AI uses the client records, documents and meeting history in the platform, within your permissions. |
A change involving an existing policy | The team locates the relevant records and determines which documents or actions are needed. | AI can flag the change. Using existing policy information or preparing the next steps depends on its access. | Client information and documents inform the next steps, and support form preparation where the product supports it. |
Follow-up email | The advisor writes the email or adapts an existing template. | The assistant drafts an email from the meeting, with only the context the integration gives it. | AI drafts a follow-up from the client information and the commitments made in the meeting. |
Tasks and reminders | The advisor or assistant creates the required tasks, unless the CRM automates them. | The assistant creates some tasks. Other steps still need separate systems or manual work. | Meeting outcomes and client information feed connected tasks and follow-ups. |
Preparation for the next review | The advisor or assistant retrieves previous notes, documents and outstanding items. | Meeting history is easier to find, but the assistant may not see the complete client record. | Client information, documents and meeting history come together to prepare the next meeting. |
The difference isn't simply whether an AI assistant can write to the CRM. It's whether it can also read what it needs to understand the client and help finish the work.
Option B: What is an Un-CRM, a CRM alternative designed to automate notes and follow-up?
An Un-CRM is a client management platform where client records and AI work in the same system. Because the AI sits inside the client record, it's designed to prepare meeting notes, follow-ups and tasks from the client's full history, not only the latest meeting.
A traditional CRM is mainly a place to store and organize client records. An Un-CRM is meant to connect those records to the work that follows a client interaction: documentation, follow-ups, tasks and preparing the next meeting. That doesn't mean every data source is automatically available, or that every task gets done on its own. Access still depends on permissions, integrations and what the product can do.
How Bloks approaches the Un-CRM
Bloks is building an Un-CRM that brings client management and its AI companion together in one platform for Canadian financial advisors. To be transparent, I work at Bloks.
You can keep using Bloks Companion AI alongside your current CRM, where the integration is supported. Today, Bloks Companion AI sends information into supported CRMs. Reading and using the full client record is what the Bloks Un-CRM is being built to do. The Bloks Un-CRM is a separate option, still in development, that combines CRM functions with the AI companion.
The planned CRM capabilities include household management, client notes, follow-ups, assets, insurance policies and document management. The idea is that the client record keeps itself up to date, so you and your team can focus on using what's in it.
Wealth management CRM with automated meeting capture: which setup fits your practice?
A wealth management CRM with automated meeting capture usually means one of two setups: your current CRM plus an AI meeting assistant that sends notes into it, or an Un-CRM, where the client record and the AI share one platform. The first keeps your CRM. The second is designed so the AI reads the full record, not just writes to it.
No setup is right for every financial advisor. The best one depends on your existing CRM, how your practice works and how deep the available integrations go.
Consideration | Legacy CRM | Legacy CRM + AI meeting assistant | Un-CRM |
|---|---|---|---|
Primary purpose | Store and organize client records. | Add AI capabilities to an existing CRM. | Combine client management and AI in one platform. |
Client information | Stored in the CRM. Advisors retrieve it by hand for each task. | New meeting information syncs to the CRM. Access to existing client data depends on the integration. | AI works with the records, documents and meeting history in the platform. |
Meeting documentation | Manual, unless the CRM has built-in automation. | AI prepares meeting notes and transfers them to the CRM. | Meeting documentation goes straight into the client record. |
Insights and context | Advisors review records and documents themselves. | Insights are limited to the information the integration lets the AI access. | AI draws on client information across the platform. |
Administrative work | Manual steps and separate tools remain. | Automates some tasks, and stops where the integration stops reading. | Shared client information feeds connected workflows. |
Number of systems | The existing CRM, plus the tools already in use. | Adds another product and integration to manage. | CRM and AI in one platform. Some external systems remain. |
Best suited for | Practices satisfied with their existing CRM and workflows. | Practices that want AI assistance without replacing their current CRM. | Practices looking for a more integrated approach to client management and AI. |
Whichever you choose, test what the integration actually does. Don't assume that because two products are connected, the AI can see everything in your CRM.
What should Canadian advisors check before adding automated meeting capture?
Before adding automated meeting capture, Canadian advisors should check five things: compliance and recordkeeping, privacy, integration depth, team workflows and access controls, and migration. The right setup meets your compliance and privacy obligations, gives the AI access to the client information it needs and fits your dealer or network policies. For some practices, that's the current CRM plus an AI meeting assistant. For others, it's an Un-CRM.
1. Compliance and recordkeeping
Which rules apply depends on your registration and business model: CIRO rules, securities regulations, insurance-sector obligations and your dealer's or network's internal policies. For investment dealers and registered individuals, start with CIRO's Client Focused Reforms resources and National Instrument 31-103, which covers books and records.
AI-generated notes or summaries don't guarantee compliance on their own. Check the tool against how your firm actually handles documentation, supervision, retention and recordkeeping.
2. Privacy and client information
Client conversations and records can hold sensitive personal and financial information. In Canada, that brings in PIPEDA and, for clients in Quebec, Law 25. If you're an insurance advisor, also check what the AMF or your provincial insurance regulator expects. Ask:
What client information is sent to the AI service, and where is it stored?
How is it protected and retained, and who can access it?
What permissions do integrations require, and can the firm control access to records and documents?
Does the provider use client information to train models, and under what terms?
The Office of the Privacy Commissioner of Canada's principles for responsible AI are a good reference. Before you bring in a new tool, go over your firm's internal policies with your compliance or privacy team.
3. Integration with existing systems
"Integration" doesn't mean the same thing from one product to the next. One tool may send information to another without being able to read anything back. Another may offer broader data access or two-way sync. Confirm:
Can the AI read existing client records, or only create new ones?
Can it access historical meeting notes and relevant documents?
Which fields and record types can be synchronized?
How are updates, duplicates and conflicting information handled?
What happens when an integration fails or permissions change?
4. Team workflows and access controls
A CRM is often used by more than one person. Check that the platform supports the roles, permissions and workflows your practice needs. A system that saves the advisor work but adds steps for the assistant may not be an improvement overall.
5. Migration and operational requirements
Changing CRMs touches client records, documents, workflows and team habits. Before you migrate, find out which data can move, how it will be checked and whether the new setup works with your dealer or network requirements.
For more detail, see Bloks' guide to AI note-takers and compliance for Canadian financial advisors.
How do you choose between a Legacy CRM setup and an Un-CRM?
Start with where your workflow has the most friction. If it's documenting meetings, an AI meeting assistant that integrates well with your CRM may be enough. If it goes beyond the notes, look at whether the AI can reach the client history and documents, and whether your team still digs through the CRM and juggles separate products to get the work done.
Choose a Legacy CRM with an AI meeting assistant when:
Your existing CRM meets your core requirements.
You want less manual meeting documentation without replacing your current system.
The integration supports the workflows and data access you need.
The setup meets your firm's compliance, privacy and operational requirements.
Consider an Un-CRM when:
You want client management and AI in the same platform.
Your team spends a lot of time jumping between systems to find client information.
You want the AI to work with the client records, documents and meeting history in the platform.
You're able to evaluate migration, compatibility and organizational requirements.
An Un-CRM isn't automatically the right choice for every practice, especially where existing systems or dealer requirements dictate how client records are managed. Before you decide, compare complete workflows, not individual features. A tool that writes excellent meeting notes can still leave your team with plenty of work afterward. For more, see How to eliminate manual CRM updates for financial advisors and Why Canadian financial advisors hate their CRM.
From managing client records to getting the work done
A Legacy CRM is still the foundation of many financial advisory practices, and third-party AI meeting assistants can fill some of its gaps. But when the integration gives limited access to what's already in the CRM, the AI may not have the context it needs to help with the next steps. An Un-CRM is designed to put client information, documents and meeting history to work across more of the relationship.
With a Legacy CRM, AI can help you update the system you already have. With an Un-CRM, AI can work with the client intelligence available within the system itself.
Frequently asked questions
Yes, in two ways. You can add an AI meeting assistant to your CRM, which documents meetings and sends the notes into it, or move to an Un-CRM, where the CRM and the AI share one platform. Before you choose, check whether the assistant can only write into your CRM or can also read what's already there.
A Legacy CRM is a traditional system used to store and organize client information, notes, documents, tasks and follow-ups. An Un-CRM combines client management and AI in the same platform. The main difference isn't simply the presence of AI. It's how client information is accessed and used across the system.
No. An AI meeting assistant documents meetings and sends information to your CRM, which stays the system of record for client records, documents and history. It can reduce the manual work around meetings, but it works alongside the CRM, not instead of it. An Un-CRM is designed to combine both in one platform.
Yes, if the assistant supports your CRM and the integration meets your requirements. It can write meeting notes, pick out action items and send information into client records. How deep the integration goes varies, though: before you pick a product, confirm which records and fields the assistant can read and write.
No. How much it can automate depends on what the product can do, the data available, permissions and integrations. You and your team are still responsible for reviewing the information, making the professional judgment calls and meeting your firm's requirements.
Bloks Companion AI can be used alongside a supported existing CRM. Bloks is also building the Bloks Un-CRM, which combines CRM functions and the AI companion in one platform. Availability and compatibility depend on your current setup, so confirm them with Bloks.
Keep reading
Every client, your only client.
The person across from you won’t know why. They’ll just feel it.
No setup, no training, and a dedicated team walking you through it if you want one. Encrypted at rest and in transit. You own your data.
