AI for Wealth Management Firms: A 90-Day Rollout Plan for Small Firms

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI for Wealth Management Firms: A 90-Day Rollout Plan for Small Firms.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI for Wealth Management Firms: A 90-Day Rollout Plan for Small Firms.

A small wealth management firm should write a one-page AI policy in weeks 1 and 2, vet vendors in weeks 3 and 4, pilot one use, meeting notes, with two advisers in weeks 5 to 10, then decide in weeks 11 to 13 from measured hours saved and errors found before adding a second use.

This plan assumes three to ten advisers, a part-time or outsourced compliance lead, one operations person and no IT department. It is not compliance advice. Your regulator's rules on recordkeeping, supervision and client consent decide what you may do, so have your compliance lead sign off the policy and the pilot design before anyone records a client meeting. Meeting notes go first because the volume is high, an adviser reads every note before it is filed, and nothing the tool writes reaches a client unreviewed.

Follow me on Instagram@sagnikteaches

Weeks 1 to 2: find out what staff already use, then write one page

Begin with a fifteen-minute survey, with no blame attached for honest answers. Assume somebody already pastes client notes into a free chatbot, and find out who, before a policy tells them to stop. Ask five questions: which AI tools do you use, for what jobs, with what kind of data, on a personal or firm account, and what would you use if you were allowed? Then sort the answers into an inventory. This one is invented, to show the shape:

Connect on LinkedInSagnik Bhattacharya
Tool in useWhoWhat goes inAccountDecision
A free chatbotTwo advisersMeeting summaries with client first names; email draftsPersonalStop for anything about clients; allow for non-client drafts until a business plan is approved
A free transcription appOne adviserRecorded client callsPersonalStop at once; delete the recordings and note it in the log
The assistant bundled with the office suiteFour staffInternal drafts, no client dataFirmApprove for non-client work
AI features inside the CRMNobody yetNoneFirmReview in the vendor checks in weeks 3 and 4

The decision column matters more than the list. For every tool you either approve it, restrict it to named uses, or stop it. A tool that is neither approved nor stopped is how a policy fails in its first month.

Subscribe on YouTube@sagnikteaches

Now write the policy itself on one page. A long document is not read, and a one-page version can be taught in a single session. This is a starting draft with placeholders, to be adapted and signed off by your compliance lead:

AI USE POLICY - [Firm name] - version 1.0 - owner: [compliance lead] - [date]

1. Approved tools: only those on the approved list kept by [owner]. Anything
   else is not to be used with client or firm information.
2. Never enter into an unapproved tool: client names, account or policy
   numbers, addresses, dates of birth, tax identifiers, portfolio details,
   or notes of client meetings.
3. AI does not make or draft investment recommendations, suitability
   conclusions or risk ratings. Advisers remain responsible for all advice.
4. Anything a client will read is reviewed and edited by a named person
   before it is sent. The reviewer is accountable for it.
5. Recording or transcribing a client meeting needs the client's consent at
   the start of that meeting, recorded in the client file. If the client
   declines, take notes by hand.
6. AI-generated notes and transcripts are firm records and follow the firm's
   retention schedule. They are stored only in [CRM / approved system].
7. New AI tools or new uses need approval from [owner] after the vendor
   checks in section [x] of this plan.
8. Report immediately: wrong information sent to a client, client data
   entered into an unapproved tool, or an AI output you cannot explain.
9. Everyone completes the AI training and signs this policy. The training
   log is kept by [operations].
10. Review this policy every quarter, and after any incident.

Rule 3 is the one most firms get questions about, so say plainly why it is there: the pilot is about admin, and the line between admin and advice is easier to hold if it is written down before the first tool arrives. The tutorial on what compliance allows when advisers use ChatGPT covers that boundary in more depth. Finish week 2 by having every member of staff read and sign, and put the signed copies and the inventory in one folder that the compliance lead owns.

The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Weeks 3 to 4: vendor checks sized for a firm with no IT department

A 200-question security questionnaire is built for a firm with a procurement team. A five-adviser firm needs two or three candidates, twelve questions and written evidence. For a meeting-notes pilot the candidates usually include a dedicated adviser notetaker, such as Jump or Zocks, and the notetaker your CRM sells, if it has one. Wealthbox, for example, sells an AI Notetaker as an add-on. Here is what each vendor's pages said on 1 November 2026, and, just as useful, what they did not say.

ToolPrice I readWhat its pages say about recording, consent and dataNot on the pages I read
JumpMeet is $100 per adviser a month; Onboard and Grow add-ons are $50 each; annual payment saves up to 20 percentRecording is optional (transcript-only, summary-only or full audio and video), configurable to your supervision and record-keeping policies; says it runs on SOC 2-certified infrastructure and that client data never trains its models; every output is reviewable before it goes anywhereRetention periods and archiving mechanics; CRM names on the pricing page, though Redtail and Wealthbox logos appear on the home page
ZocksEssentials $67, Professional $117, Ultimate $184 per user a month on annual billing ($80, $140, $220 monthly); Enterprise by quoteConsent tracking on all three plans; its comparison table lists firm-level consent controls, audit logs, PII redaction and transcript archiving from Professional upwards (check the live page); says it never records client conversations and that no LLMs hold or train on your dataRetention periods in days; its pricing FAQ does say it is SOC 2 Type II certified and offers a 14-day trial with a card
Wealthbox AI Notetaker$49 per user a month on top of Basic $59, Pro $75 or Premier $99Preps you before the call, captures it, and writes the summary and follow-up to the contact recordRecording, retention and training details on the pricing page

Do not compare these prices as if they were the same unit: Jump prices per adviser, Zocks per user, and Wealthbox adds to the CRM seat you hold. The tutorials on Jump against Zocks on compliance set-up and the Wealthbox notetaker against standalone tools do the head-to-head. For the vendor checks, ask each candidate these twelve questions in writing:

QuestionWhy it mattersA good answer
1. Do you hold a current SOC 2 Type II report, and will you share it?Evidence beats a badge on a web pageYes, with the date of the latest report
2. Where is client data stored, and which sub-processors touch it?You must be able to say where client data goesA list with locations and notice of changes
3. Is any client data or transcript used to train models?Training use turns a notetaker into a leakNo, stated in the contract, not only on the website
4. How long are audio, transcripts and summaries kept, and can we set it?Notes are records; spare audio is a liabilityConfigurable, with proof of deletion
5. Can recording be off and still produce notes?Some clients will decline recordingYes, through a transcript-only or notes-only mode
6. How is consent captured and logged?Consent must be provableA logged field per meeting that can be exported
7. Can we archive transcripts and summaries to our recordkeeping system?The notes are firm recordsAn export or integration you have seen work
8. What can an administrator see and control?Supervision depends on itAudit logs by user and action; MFA enforced
9. Which CRM integrations are two-way, and what do they write back?Notes belong in the client record, not a separate portalA named CRM and the fields shown in a demo
10. What happens to our data if we cancel, and how fast?Exit terms are set before the pilot, not afterAn export in a standard format and a stated deletion date
11. What are the term, notice period and price-change rules?A year's lock-in before the pilot ends defeats itMonthly, or a 30-day exit for the pilot
12. Which AI models and providers does the product use, and will you tell us when they change?Behaviour shifts when models doA named list and notice of material changes

Treat questions 3, 4, 6 and 10 as knock-outs. A vendor that cannot answer them in writing does not reach the pilot, however good its demo looks. Then test candidates with a mock meeting in which a colleague plays a client and mentions two numbers, a name and an action item, so you can see what the tool does with each. Ask for a pilot on monthly terms and confirm the trial length: Zocks's pricing page says 14 days with a card required, while Jump's and Wealthbox's pricing pages did not state one.

Weeks 3 to 6: set the baseline, then design a pilot that can fail

Pick two advisers, one keen and one doubtful, plus the operations person who files the notes. Between them they should run at least 60 client meetings during the pilot, because below that the error rate is noise. Then spend weeks 3 and 4 measuring how things work today, since without a baseline any improvement is a guess. For each meeting, the two advisers record the minutes spent writing the note, the minutes spent filing it in the CRM, and how long after the meeting it was filed (same day, next day or later). The operations person also samples 20 manual notes and classifies the errors in them, because human notes contain errors too and the AI should be compared with that, not with perfection.

Agree the error scale before anything is counted:

  • Serious. Anything that changes what the firm believes the client said, decided or owes: a wrong amount or date, a missed decision, an action assigned to the wrong person, or any item that was never discussed. An invented follow-up belongs here, and it is the type of error AI notetakers are most likely to add and humans least likely to.
  • Minor. Wording, order or detail that does not change the record.

Report serious errors per ten notes, and separately count how many reached the client record uncaught. Next, write the consent line the advisers will say, and decide what happens when a client declines. Here is wording to adapt:

"I use an AI notetaker to write up our meetings. It records or transcribes our conversation, and I check the notes myself before they go into your file. Are you comfortable with that? You can say no at any time, and I'll take notes by hand."

If a client says no, switch the tool off, take notes by hand and flag the client record so it is not asked again by the next adviser. Log every consent answer in the CRM, with the date, so the record shows consent for each recorded meeting. Recording and consent rules differ by place, so your compliance lead should approve this wording and the exceptions.

Set the pilot rules in writing and keep them tight:

  • Pilot advisers read and correct every note before it is filed. Nothing is filed automatically.
  • Notes only. No follow-up emails go to clients from the tool during the pilot.
  • Exclude complaint meetings, any discussion of a client's health or vulnerability, and any meeting the client would rather not have recorded.
  • The tool is used only on the firm's approved account, never on a personal login.

Decide the stop conditions now, not in the middle of a bad week: any serious error reaching a client record uncaught, any recorded meeting without logged consent, or a data incident at the vendor. A pilot with no way to fail is a rollout wearing a pilot's name. Keep a simple log with one row per meeting:

DateAdviserMeeting typeConsent loggedMinutes to review and fileSerious errorsMinor errors
12 JanAAnnual reviewYes1101
12 JanBNew enquiryYes810
13 JanARetirement planningNo: client declinedManual, 24Not applicableNot applicable

The third row is a success, not a gap. It shows the consent rule working and gives you a manual timing for the baseline.

Weeks 5 to 10: run the pilot on a fixed review cycle

The pilot runs six weeks, and the review effort tapers as trust is earned, never before. In weeks 5 and 6, each adviser reviews every note, and the compliance lead reads five notes per adviser per week against the transcript, looking for what the adviser missed. In weeks 7 and 8 the sample drops to three per adviser. In weeks 9 and 10 it stays at three, and the two advisers swap one note each, so a second pair of eyes tests the first. Hold a 20-minute stand-up every Friday to read the log, discuss patterns and change one thing, such as a template or a setting, so you can see what that change did. Changing three things at once teaches you nothing.

Know the patterns to look for, because reviewers find what they expect. Check numbers and dates first, then who said or owns what, then action items, then hedges. Hedged statements are a classic place for a note to go wrong: a client who says "I might consider topping up" can end up recorded as "agreed to top up", and in a regulated record that one-word change is a serious error. These are patterns to watch, not claims about any product, so keep your own tally and let the log show which apply.

Here is how a ten-week result might look in an illustrative firm of five advisers where two took part. The figures are invented to show the sums.

MeasureBaselinePilot
Meetings heldNot applicable82, of which 78 recorded with consent and 4 declined
Minutes per meeting to write and file the note229, including review and correction
Notes filed the same day55 percent91 percent
Errors per note0.30 (6 in 20 sampled manual notes)0.29 (23 in 78 notes)
Serious errors1 in the 20 sampled notes3, all caught by the adviser before filing
Serious errors that reached the record uncaughtNot measured0
Errors the advisers missed but compliance foundNot applicable2 minor, in 44 sampled notes

Read it the way a sceptical partner would. The 13 minutes saved per meeting is 1,014 minutes, or 16.9 hours, across the 78 recorded meetings. The error rate matches the manual baseline, 0.29 against 0.30 per note, but the kinds differ. The three serious errors in AI notes were a transposed contribution figure, an action item given to the client instead of the adviser, and an invented follow-up that said the client had agreed to review life cover. All three were caught because the advisers read every note. The one serious error in the manual sample was a missed decision. The lesson is that the review step is carrying the safety, which is why it must not be dropped when the firm scales up.

Now extrapolate cautiously. Five advisers at ten meetings a week for 46 weeks is 2,300 meetings a year. At 13 minutes saved each, that is 29,900 minutes, about 498 hours. At Jump's listed $100 per adviser a month, five advisers cost $6,000 a year, which is roughly $12 per hour saved. If only half the time saving appears, because meetings run longer or reviews slow down, it is about $24 per hour saved. The cost per hour saved is the figure to compare with what an hour of adviser time is worth, and with the other uses you could try next.

Weeks 9 to 11: staff training in three 45-minute sessions

Run training while the pilot is still going, so the rollout can start the week the decision is made. Three short sessions beat one long one. If you have clients or operations in the EU, the EU AI Act's AI-literacy duty has applied since 2 February 2025. Its wording was softened by the Digital Omnibus on AI, in force from 27 July 2026, so providers and deployers must take measures to support staff AI literacy without having to guarantee a specific level. Either way, a dated training log is cheap evidence that you took the duty seriously.

  • Session 1, everyone: the policy and its red lines. Spend 15 minutes on the policy, 15 on a quiz of realistic cases, and 15 on how to report an incident. Use cases such as: "Paste a client's name and portfolio into a free chatbot to tidy an email" (no); "Ask the approved assistant to reword a market commentary paragraph that contains no client data" (yes, then compliance review before it is published); "Switch on the notetaker for a client who said they would rather not be recorded" (no).
  • Session 2, advisers and operations: the tool and the review habit. Run a mock meeting and review the notes together in a fixed order: numbers and dates, then who said or owns what, then action items, then hedged statements. Practise the consent line aloud, and show how to switch recording off mid-meeting.
  • Session 3, everyone who will use it: spot the error. Show six anonymised errors from the pilot log, give people two minutes to find them, and discuss why reviewers miss them. This session is the one that changes habits, because people believe their own pilot's examples in a way they never believe a vendor's.

Keep a log with the date, the attendees and the version of the policy. Schedule a 20-minute refresh each quarter, because the policy review is a natural moment to retrain, and a firm that trains once finds the old habits back within a season. The tutorial on setting up Jump for a three-adviser firm goes into templates and consent in detail if Jump is your pilot choice.

Weeks 11 to 13: decide with numbers, then plan the second use

Write the pass marks before the pilot starts and hold to them. Here is an example, scored with the illustrative results above:

MeasureGo ifIllustrative result
Serious errors reaching the record uncaught, last four weeksNone0: pass
Minor and serious errors per noteNo worse than the manual baseline0.29 against 0.30: pass
Recorded meetings with logged consent100 percent78 of 78: pass
Net minutes saved per meeting, review includedAt least 813: pass
Cost per hour saved, assuming half the saving appearsUnder $25About $24: narrow pass
Pilot advisersBoth would keep using itYes from both: pass

There are four possible outcomes. Go: roll out to the other three advisers in two waves, with the same review rule for the first four weeks of each wave. Extend: run four more weeks with named fixes, such as a better template, when one measure narrowly fails. Switch: repeat the pilot with the second-choice vendor, keeping the policy and baseline. Stop: a legitimate result, and one that still leaves you with a policy, an inventory and a baseline for the next idea.

Choose the second use from the inventory by three tests: how often the job happens, whether a person reviews the output before a client sees it, and whether you can measure it. Follow-up emails drafted from the pilot notes, annual-review preparation packs and onboarding document checks all pass. The tutorials on five admin jobs worth trying and preparing annual client reviews with AI describe those candidates. Give the second use the same short pilot, the same review cycle and the same pass marks.

What the 90 days cost in cash and in hours

The cash is small and the hours are not. For the pilot, two advisers on a notetaker for three months costs about $600 on Jump at its listed $100 per adviser a month, $840 on Zocks Professional at the $140 monthly rate, or $294 on Wealthbox's AI Notetaker add-on at $49 a user. That is a few hundred dollars. The hours are the real budget:

WhoWhatHours over 13 weeks
Compliance leadSurvey, policy, vendor checks, weekly samples, decision26 (about 2 a week)
OperationsInventory, log, baseline sampling, training log13 (about 1 a week)
EveryoneThree 45-minute training sessions, eight people18
PartnersSign-off on the policy and the decision2
Total59

So the first 90 days cost under $1,000 in software and about 60 hours of senior and operations time. The pilot advisers' own review time is already inside the measured minutes. If the decision is to roll out to all five advisers, the year-one list price is $6,000 for Jump at $100 each ($4,800 if its annual payment discount of up to 20 percent applies in full), $4,020 for Zocks Essentials or $7,020 for Professional on annual billing, or $2,940 for the Wealthbox AI Notetaker on top of your existing CRM seats. These are list prices read on 1 November 2026. Put the one you choose against the cost-per-hour figure from your own pilot, not against anyone else's.

Where small-firm rollouts go wrong, and how each shows up

  1. The tool arrives before the policy. Staff start using it on day one, and the first rule you write is a reaction to something that has already happened.
  2. The pilot is all enthusiasts. Results look wonderful, and the rollout stalls the moment it reaches the advisers who were never convinced.
  3. No baseline. A partner asks whether it actually saves time, and the only answer is that it feels faster.
  4. Counting the tool's minutes, not the editing minutes. The vendor says the note takes two minutes; the adviser spends nine reviewing and correcting it. The nine is the number that matters.
  5. Notes living in the vendor's portal. The CRM and the portal drift apart, and nobody knows which holds the record.
  6. Review dropped after week four because the notes look good. An invented follow-up reaches a client file, and nobody notices until a client mentions it.
  7. No owner. The policy is one year old, three tools have been added, and nobody has read it since signing.
  8. Training once. Within a season the old habits are back, and personal-account use reappears.

None of these needs a bigger budget to fix. Each needs a named person, a written rule or a number on a page, and a Friday stand-up that keeps all three alive.

Questions small wealth firms ask about a first AI rollout

Do we need a separate AI policy or can it sit in the compliance manual?

A short standalone policy is easier to train on and to update, and the compliance manual can point to it. Keep it to one page that names the approved tools, the data that must never leave them, the review rule and the owner. A long document nobody reads protects nobody.

How many advisers should be in the pilot?

Two or three, ideally one enthusiast and one sceptic, running at least 60 client meetings between them over four to six weeks. Fewer meetings make the error rate meaningless, and a pilot of enthusiasts alone tells you nothing about how the rest of the firm will cope.

Do clients need to be told about an AI notetaker?

Tell them and ask at the start of every meeting that is recorded or transcribed, and record the answer in the client file. Recording and consent rules differ by place and by regulator, so have your compliance lead confirm the wording and what to do when a client says no.

What should come second after meeting notes?

Choose a job that is frequent, measurable and reviewed before a client sees it. Follow-up emails drafted from the pilot notes, annual review preparation packs and onboarding document checks are common candidates. Give each its own short pilot with the same measures, rather than switching everything on together.

How do we count errors fairly?

Compare against a manual baseline, not against perfection, because human notes contain errors too. Sample 20 manual notes before the pilot, classify errors by severity, then apply the same scale to AI notes. The figure that matters most is serious errors that reached a client record uncaught.

Further reads

Sources: Jump, Zocks and Wealthbox pricing pages and Jump and Zocks home pages, read 1 November 2026; EU AI Act Article 4 and the Digital Omnibus on AI. The firm, meeting counts, minutes and error figures are illustrative.

Want a 90-day plan sized to your firm?

On a 1:1 call we can list what your advisers already use, choose the one pilot worth running first, and set the measures and review cycle your compliance lead will accept.

Book a 1:1 call with me