Practitioner resource
Meeting prep and AI notetakers: what each one needs before it can help
Preparation is the part of a client meeting with no fixed length. It expands to fill whatever evening is available, and it is the first thing cut when the week runs short. Software aimed at that problem all reads alike in a feature list: summarise the meeting, draft the follow up, produce a briefing. The more useful question is what each tool needs before it can produce anything at all, because that is what decides whether it can help you with the meeting on your calendar at nine tomorrow.
01
Two jobs, split by the meeting itself
The meeting is the dividing line. One group of tools runs before it and tries to answer what you should walk in knowing. The other group runs during and after it, and tries to answer what was said and what happens next.
Most products in this category now do some of both, which is why their feature grids blur together, and why you could reasonably conclude the two jobs have merged. In the marketing they largely have. The underlying jobs still draw on completely different material, and that difference is what you feel on a morning when one of them has nothing to work with.
02
The question that separates them
Ask what a tool requires before it can generate its first useful sentence.
Notetaking needs the meeting to have happened. The tool listens, or reads a transcript, and what it produces is downstream of something that was said out loud. Ahead of the meeting it has nothing to work from.
Prep that assembles itself from your systems needs those systems to hold the client already. It reads CRM notes, portfolio positions, financial plans, tax records, email threads and past meeting history, and stitches them into a briefing with each claim traced back to where it came from. That is a strong brief when those systems hold the client. It is an empty brief when they do not.
That gives you a more useful axis than the feature list: whether the material a tool draws on already exists.
03
Side by side
| AI notetaker | Integrated prep | Standalone prep | |
|---|---|---|---|
| Runs | During and after the meeting | Before the meeting, on a schedule | Before the meeting, when you ask |
| Needs first | A meeting to capture | Connected CRM, custodian or planning data about this person | What you already know, typed in |
| Produces | Notes, action items, CRM updates, follow up drafts | An agenda and briefing assembled from your systems | A structured document built from the context you supply |
| Quiet when | Nothing has been recorded yet | The person is not in your systems, or the record is thin | You want the meeting itself captured and filed |
| Setup | Calendar and conferencing access | Integrations across your stack | None |
Categories, not products. Plenty of tools span two columns. The rows describe what each approach needs before it can produce its first useful output, which is the thing feature lists leave out.
04
When a notetaker is the right answer
If the work you lose time to happens after the meeting, buy a notetaker. Writing up what was said, updating fields, and drafting the follow up are exactly the jobs this category was built for, and a preparation tool will not do any of them for you.
Recording and consent handling differ meaningfully between products in this category. Some capture the conversation without retaining audio at all, some keep the recording, some keep only a transcript. If your firm has a position on retention, that difference matters more than any feature list, and it is the first question worth putting to a vendor rather than the last.
05
When integrated prep is the right answer
If your CRM and planning software genuinely hold your book, and the friction is that the information is scattered rather than missing, this is the approach that fits. It reads systems you already maintain, and it can run without being asked.
The precondition is real, though, and it is easy to read past in a feature list. A tool that reads your systems is worth exactly what your systems contain. Integration counts in this category run from the dozens into the low hundreds, and that number is a strength and a requirement at the same time: each connection is something you have to hold, and keep current, before the briefing is worth opening.
06
The meetings neither one covers
Three situations sit outside both of those requirements.
- The prospect. Someone referred to you last week has no CRM history, no portfolio positions and no recorded meeting. There is little for either kind of tool to draw on, and the preparation still has to happen.
- The first real conversation with an existing name. A contact has sat in the CRM for two years as a name and an email address. The record exists and holds nothing.
- The practice without the stack. Independent and boutique practices often run a CRM that is a calendar and a spreadsheet. Integration depth cannot help where there is nothing to integrate with.
In all three the material sits in your head, in an intake call, in a referral conversation, in something the client's accountant mentioned. Little of it is in a system to be read, which is why the work tends to land on you the night before.
07
Where AdvisorBrief sits
AdvisorBrief is standalone preparation. You supply the context and it returns a structured document: no CRM connection, no recording, no prior meeting required. That last part is what lets it run on a prospect the day after a referral, and it is the reason the tool exists.
Five tools, matched to the document you need: Prospect Intelligence, Client Onboarding, Meeting Prep, Portfolio Review and Estate Planning. Each returns named sections rather than an open ended answer, so a meeting brief arrives with a situation read, a timed agenda, the key figures, objection responses in language you would actually use, and a next step. You are reading a document, not a chat reply.
The part that matters if you have to stand behind what you carry into the room: every figure states its basis, whether it was provided, calculated, estimated or left unconfirmed, and names who should verify it. Nothing is presented as established because it read plausibly. Briefs are not saved to your account.
It does not capture the meeting or write anything back to your CRM. If that is the half of the problem you need solved, this is the wrong tool for it.
08
Canadian context
Two things are worth separating when you evaluate anything in this category, wherever it was built. Privacy and residency is one question. Whether the analysis understands Canadian planning is a different question, and it is the one that shows up in the document. A brief that does not know an RRSP must be converted by December 31 of the year the client turns 71, or that alter ego trusts require the settlor to be 65 or older, will read as generic to anyone who has run those conversations. The Canada Revenue Agency and CIRO publish the underlying rules directly, and both are linked below.
AdvisorBrief encodes Canadian planning facts as its primary regime, with US and cross border handling underneath. That is a statement about what the analysis knows, not a compliance claim, and it does not remove your obligation to verify every figure in any document before it informs advice.
09
Sources
- Canada Revenue Agency, registered retirement income fund guidance. canada.ca
- CIRO, know your client and suitability guidance. ciro.ca
The software categories described here move quickly. Confirm what any specific product does with its vendor directly before you buy it.
Nothing on this page is investment, tax, legal or compliance advice, and it does not state what any regulator requires of your firm.