Skip to Content
The Adoption PathWhat AI Is For

Decide What AI Is For

This is the first step in The Adoption Path. Before you choose a tool, you decide — in writing, in your own words — what AI is for in your practice and what it is not for yet. That use-case list is not a formality. It is the input every later step works from: which data is even allowed to leave the firm, which tools are worth spending time vetting, and what a written policy actually has to cover. Skip this step and the decision does not go away; it just gets made informally, by whoever on the team first tries a chat assistant on a real client matter, with no one else aware it happened.

Why it matters

Without a defined list, use tends to start by accident. Someone drafts an email with a chat assistant because it was faster, does it again the next week, and within a couple of months it is a habit nobody chose, documented nowhere, reviewed by no one. Your firm already has a compliance program, however thin; an unrecorded, ad hoc use of AI does not fit inside any of its policies, which is exactly the gap this step exists to close.

Everything after this step depends on what you decide here. Sort Your Data only works if you already know which tasks you are sorting data for. Vet and Choose Tools only has something concrete to evaluate against if you know what job the tool needs to do. Write the AI Policy is grounded in real, named uses, or it is a generic document that does not match what is actually happening in the firm.

What actually happens

Inventory the recurring work

List the tasks that come up on a weekly or quarterly basis — not the aspirational uses you have read about, the actual repeated work of the practice. Drafting client emails, summarizing a document before a meeting, pulling together the first pass of a quarterly letter, searching old notes for a fact. If it is not something the firm already does regularly, leave it off the list for now; you are inventorying real work, not brainstorming a wish list.

Sort each task into three buckets

Not every use of AI carries the same weight, so sort each item on your list into one of three buckets. This is the guide’s own plain-language framing, not an official category from any regulator. Assist covers drafting, summarizing, and first-pass research, where you review everything before it goes anywhere. Analyze covers numbers, plan inputs, and comparisons, where the output has to be independently checked before it ever reaches a client. Decide covers recommendations to clients — and AI does not make these, full stop. That is not just caution; it follows from the duty of care and loyalty you already owe every client, a fiduciary duty that is yours alone, however a recommendation was drafted.

Name what is off limits — for now

Write down what you are not using AI for yet, as clearly as what you are using it for. “For now” is the honest phrasing, not a hedge: a use off the table today because a tool has not been vetted, or a rule has not been mapped, may move onto the list once step two and step four are done. Naming it now, instead of leaving it an unstated assumption, means a use case does not sneak in before it has actually been evaluated.

Write down the expected benefit

For each use on the list, write a short, honest estimate of what it actually saves — time, mostly, sometimes the quality of a first draft. You are about to take on some ongoing oversight cost for every use you approve, and the only way to judge whether that cost was worth it is to have written down, at the start, what you expected to get. What you decide in this step is itself something the firm should be able to show, not just something it did.

Decide who may use AI at all

Name who in the firm is covered by this — not just advisers, but anyone with access to firm or client information, including an assistant. A use case is not controlled if one person is deciding on their own, separately, what counts as acceptable. This is also where informal use gets pulled into the open: if someone is already using a chat assistant for part of their job, that use belongs on the inventory, not left as something nobody asked about.

Questions to ask yourself

  • What does the practice do every week or every quarter that this list should include?
  • For each candidate use, which bucket does it belong in — assist, analyze, or decide — and does everyone doing that work agree?
  • What are you deliberately not doing yet, and what would have to be true before that changed?
  • If a use case saves less time than expected, would anyone notice?
  • Is there a use already happening informally that this list needs to catch up to?

Common mistakes

  • Starting with a tool instead of a task — evaluating something because it looks capable, rather than naming the job first.
  • Treating “AI” as one thing, when it is really a set of different tools with different data handling, different accuracy, and different appropriate uses.
  • Letting an assistant’s private use of a tool go unrecorded, because “AI policy” quietly gets read as “policy for advisers.”
  • Assuming an advisor-specific platform settles this question, when the question is about the task, not the vendor.
  • Writing use cases so broad — “AI for client communication,” full stop — that no one could supervise them.

Which Firm Functions apply

  • Advice and Planning Work: The assist/analyze/decide split in this step comes directly from where advice work can and cannot use AI.
  • Operations and Back Office: Many of the safest, most obvious entries on the inventory live in back-office work rather than advice itself.
  • Compliance and Supervision: Once a use case is named, someone has to be responsible for supervising it — that ownership question starts here.
  • Prompting and Review Skills: Estimating what a use case would actually save depends on realistic expectations of what these tools do well.

At a larger firm, this list usually already exists in some form, or is imposed from outside the immediate practice — by compliance, by IT, by a decision made above the adviser’s level. The job at a larger firm is not to start from a blank page. It is to find the list that already exists, find who owns it, and get your own uses onto it, reviewed the same way everyone else’s are, before using anything on your own.

Next step

Map the Rules That Apply: Take the list from this step and work out which obligations — state, SEC, and, for dual registrants, FINRA — actually apply to each use on it.