The advisor AI stack, audience by audience. Where the return actually shows up, why the data layer is a gate rather than a nice-to-have, what supervision and recordkeeping obligations attach the moment you switch a tool on, and a build-versus-buy framework for three sizes of firm. The short version: the efficiency is real, it is smaller than advertised, and the best firms in the industry have decided not to convert it into revenue at all.
Carson Group built an internal AI assistant and reported that it saves five minutes per search and roughly five thousand hours a year across the firm. Five thousand hours sounds like a new department. Divided across the advisor base and the working year, it is about twenty minutes per advisor per week.
Twenty minutes a week does not become a new client. It becomes a slightly less rushed Tuesday.
This is not a criticism of Carson, whose disclosure was more specific and more honest than most. It is a criticism of the unit. Efficiency claims in this category are almost always expressed as hours per firm per year, which is the presentation that makes them sound largest. The only unit that supports a decision is minutes per advisor per week — because that is the unit in which an advisor either does or does not have room for another conversation. Before evaluating any tool in this piece, convert its claim.
The most-cited industry figure for AI efficiency in wealth management comes from F2 Strategy's 2026 survey: 68% of firms reported gaining 25% more efficiency in targeted workflows. That number deserves three qualifications, all of which are in the survey itself and none of which survive into the way it gets quoted.
It is 68% of the subset of firms that measure their AI investments at all — a denominator selected on the dependent variable, since firms that bothered to measure are disproportionately firms that got a result. The sample is forty firms. And it is "targeted workflows," not firm-wide. F2's own co-founder is blunter than the headline: "We're seeing a very loose correlation in 2026 between firms' spend on both AI technology and its tokens and a meaningful measurable value in a classic sense to the business."
Then there is the deeper problem. A randomized controlled trial run in early 2025 gave sixteen experienced open-source developers AI tools on real issues in their own repositories — projects averaging over a million lines of code that they had contributed to for years. They were 19% slower. Asked afterward, they estimated the tools had made them about 20% faster. A thirty-nine point gap between measured and perceived productivity, under randomization, in a population unusually numerate about its own workflow.
That study has since been qualified by its own authors, and the qualification is arguably more useful than the headline. In February 2026 METR reported newer data: a −18% estimate for the original cohort with a confidence interval running from −38% to +9%, and −4% for newly recruited developers with an interval from −15% to +9%. Both cross zero. More importantly, they are redesigning the experiment because AI adoption has made clean measurement hard — developers now decline to participate if they might be assigned to the no-AI arm, and self-report steering away from the tasks where AI helps most. The people most helped are selecting themselves out of the study.
So the durable finding is not the point estimate. It is the gap between what was measured and what was believed, plus the fact that the best-designed experiment in the field has been destabilized by the very adoption it was trying to measure. Every efficiency statistic in wealth management — including F2's — is self-reported, and none of them has anything like this level of methodological scrutiny behind it.
The RIA Edge 100 — the largest and most sophisticated independent firms in the country — were asked in 2026 whether AI would change the number of clients an advisor can serve. They said no. Form ADV data puts the cohort at roughly seventy client accounts per advisor, and the ratio is roughly flat against prior years. WealthManagement.com's framing for the phenomenon was "shadow efficiencies" — real improvements that make an advisor more effective without changing coverage.
"I don't think you're going to find 25% efficiency, at least in our model."Carrie Delgott, president, COO and CCO, Wescott Financial Advisory Group — responding to precisely the figure quoted above. Her framing for the alternative: "deeper, not wider."
This is the finding that reorganizes the whole analysis. It is not that efficiency fails to materialize. It is that the firms achieving it have decided not to convert it into revenue — they are spending it on service depth, proactive planning, and advisor quality of life. Absorbed slack by choice, not by failure. One executive at a firm serving ultra-high-net-worth families keeps deliberately to ten to fifteen relationships per advisor so the team stays "one call away." No amount of meeting-note automation will change that number, because the number is a strategy, not a constraint.
F2 found the same thing from the buy side: firms are prioritizing "operational efficiency, advisor productivity, and headcount-neutral scale." Headcount-neutral scale means buying AI in order not to hire. That is a real and defensible return. It is simply not the return in the pitch deck, and it is calculated completely differently.
There is a natural experiment in the advisor-productivity literature, and it predates AI. Advisors who add a paraplanner cut their own hours per client from roughly fourteen to ten, while total team hours per client rise from fourteen to twenty-two. Client counts go from about seventy-three to a hundred and twenty. But the striking number is revenue per client: it nearly doubles, from roughly $1,531 to $2,850.
When back-office load was genuinely offloaded, the gain showed up as moving upmarket, not as serving more households at the same price. That is a specific, testable prediction for AI adoption, and it is the pathway the calculator below treats as most plausible.
Four numbers determine whether an advisor AI deployment returns anything: how much time it actually saves, how much of that survives your data environment, how much of what survives gets redeployed into revenue-generating work, and what an hour of that work is worth. Vendor ROI models set the middle two to 100% silently. This one exposes them.
Start with a firm size, then a scenario. The gap between "vendor claim" and "measured evidence" on identical firm inputs is the point of the exercise.
The best-designed study of AI and professional knowledge work gave 758 BCG consultants eighteen realistic tasks. On tasks inside what the authors called the "jagged technological frontier," the AI-assisted group completed 12.2% more tasks, 25.1% faster, at higher quality. On tasks outside it — tasks that looked similar and felt similar — they were nineteen percentage points less likely to reach the correct answer.
The frontier is jagged because its boundary does not track apparent difficulty. That is the governing fact for an advisory practice: summarizing a client meeting and judging whether a recommendation is suitable feel like adjacent tasks and are on opposite sides of the line. Advisors adopting these tools cannot see the boundary from the inside.
The market has, so far, located it correctly by instinct. Advisors report using AI for meeting summaries at 31%, CRM updates 28%, meeting prep 26%, routine client communications 25% — and AI-generated financial recommendations at 3%. Ninety-three percent insist on retaining control of decisions and advice. Forty-six percent lack confidence in AI outputs. The category has found its edge without anyone drawing it.
| Category | Frontier | What it does | Published price / seat / mo | The catch |
|---|---|---|---|---|
| Meeting capture | Inside | Transcript → structured summary → CRM write-back → extracted tasks → drafted follow-up. The clearest win in the stack: bounded, verifiable, immediately useful. | Jump $100 (+$50/+$50 modules) · Zocks $67–$184 annual-billed ($80–$220 monthly) · FinMate $95–150 · Wealthbox add-on $49 · Altruist Hazel ~$50 · generic $0–20 | Recording consent is a live legal exposure (§05). Price compression is severe — platform-native tools at ~$50 have made $120 hard to defend. |
| Document & statement parsing | Inside | Extracts structured data from brokerage statements, tax returns, estate documents, insurance policies. Feeds proposals and onboarding. | Powder unpublished · bundled free into Nitrogen, Morningstar, TradePMR | The most heavily absorbed function in the stack — three major platforms now give it away. Standalone economics here are the weakest in the category. |
| Planning assistance | Edge | Natural-language input, data validation, scenario narration. In every case the AI is a wrapper over an unchanged deterministic Monte Carlo engine. | RightCapital $150–$255 (AI agent gated to $210+ tiers) · Conquest, eMoney, MoneyGuide all unpublished | Sounds like the AI is doing the planning. It is doing the data entry and the narration. Verify which layer you are buying. |
| Proposal generation | Edge | Statement in, recommendation-shaped document out. Drafts talking points and income maps. | Nitrogen Nucleus $0 to existing users · Morningstar bundled · Robinhood Cortex $0 on TradePMR | A proposal is a communication and may be an advertisement. Marketing Rule and Rule 2210 attach to the output regardless of who drafted it. |
| Next-best-action | Edge | Scores and prioritizes clients and prospects on life events, asset signals, engagement. Recommends who to call. | Catchlight $2,500/yr (500 profiles) · Salesforce FSC Agentforce $750/user · TIFIN unpublished | Requires the unified data layer most firms do not have (§04) — this is the category that fails first without it. Also the least transparent: several vendors disclose no signals, no recommendation types, and no outcomes. |
| Investment recommendations | Outside | Security selection or allocation advice generated by a model. | — | 3% adoption, and correctly so. Fiduciary duty does not delegate. RIAs cannot deploy an agent to manage client money under current rules — the ceiling is regulatory, not technical. |
| Horizontal AI you may already own | Inside | Meeting summarization, drafting, document Q&A inside tools already licensed. | M365 Copilot $30 · Gemini now bundled into Workspace ($7–$22 base) · ChatGPT Business $25–30 | The most-ignored line in every build-vs-buy analysis. A firm on Google Workspace Business Standard has meeting AI at roughly $14/user/month. Any specialist tool has to beat that, not zero. |
FinanceBench asked a frontier model real questions against real SEC filings under different retrieval conditions. Handed the correct evidence, GPT-4-Turbo answered 85% correctly. Made to find the answer itself in one company's filings, 50%. Made to find it in a shared store containing every company's filings, 19%.
Retrieval scope alone — not model quality, not prompting, not reasoning — moved accuracy thirty-one points. And a wealth firm running fifteen to twenty-five disconnected systems is the shared-vector-store condition. It is the worst case in that experiment, by construction.
One nuance worth carrying, because it changes what the risk looks like in practice: in the shared-store condition the failures were dominated by refusal — 68% of questions declined, against 13% answered incorrectly. A model that cannot find the evidence mostly declines rather than fabricating. That is the better failure mode, and it means the operational symptom of a bad data layer is not a stream of confident errors but a tool that quietly stops being useful, which is much easier to tolerate and much harder to notice.
This is the mechanism underneath every adoption-versus-outcome gap in the survey data. EY: 95% of wealth and asset managers have scaled AI to multiple use cases, 27% report substantial impact. Schwab, from an independent 533-advisor study fielded by Logica: 63% using AI, roughly 10% integrating it into business strategy. Two different researchers, different samples, a year apart, converging on the same shape. F2 supplies the reason: 64% of wealth firms and 83% of bank and trust respondents lack a unified data layer.
Advisor360's advisors have named "bad data and lack of integrated tools" their top technology complaint for three consecutive years — before, during, and after the generative AI wave. The constraint is not new and AI did not create it. AI simply made it expensive.
Eight component systems, at minimum: CRM, portfolio accounting and performance, custodian feeds, financial planning, document management, billing, held-away aggregation, and market data. Connecting them is not primarily an API problem. It is an identity resolution problem — matching the same household across systems that disagree about what a household is, and mapping accounts to households to contacts to service tiers. That is the piece that gets under-budgeted, and it is the piece that determines whether retrieval lands in the 85% condition or the 19% one.
Published implementation timelines, all vendor-sourced and converging across two independent providers: a native CRM accelerator with two or three custodians, four to eight weeks; middleware, eight to sixteen weeks; custom API builds, three to six months; full custom engineering, six to eighteen months with a permanent team. Cost figures are thin and entirely vendor-published — one puts custom integration at $50,000 to $500,000 per system pair, which for a six-system stack is fifteen pairs if built point-to-point. No independent benchmark for total data-layer cost in wealth management appears to exist.
The most revealing datapoint is what Orion actually built when it built "AI." In its own description: an automated data pipeline drawing from CRMs, planning systems and client data lakes into Orion's lake. The AI is the interface. The pipeline is the product. A platform vendor spending at that scale concluded the same thing this section argues — and then sold it back as an AI story.
Five obligations activate when an advisor AI tool goes live. Two are well-defined, two are genuinely unanswered by any regulator, and one — the one nobody in the securities world is watching — is currently being litigated as a class action.
FINRA's position is that its rules are technology-neutral and apply unchanged. Under Rule 3110, a supervisory system's policies "should address technology governance, including model risk management, data privacy and integrity, reliability and accuracy of the AI model." The sleeper clause is scope: FINRA rules apply "whether member firms are directly developing Gen AI tools for their proprietary use or when leveraging the technology of a third party, including through embedded features in existing third-party products."
Embedded features means Copilot in Outlook, the AI summarizer your CRM shipped last quarter, Zoom's meeting assistant — capability nobody procured as "AI" and nobody put through a governance review. For most firms that is the largest uninventoried AI surface they have. FINRA's 2026 effective-practices list is concrete about the remedy: robust pre-deployment testing, ongoing monitoring of prompts and outputs, "storing prompt and output logs for accountability and troubleshooting," "tracking which model version was used and when," and human-in-the-loop validation.
For registered advisers, Rule 206(4)-7 requires written policies reasonably designed to prevent violations, reviewed annually. There is no SEC rule, release, or staff guidance prescribing AI-specific content for those policies. The only signal is enforcement: the March 2024 AI-washing orders charged the compliance rule alongside the Marketing Rule, so the Commission's theory is that making AI claims without policies to test them is itself a compliance failure. AI has now been an examination priority three years running.
Rule 2210 applies to AI output — FINRA's advertising FAQ, updated December 2025, says firms "are responsible for their communications, regardless of whether they are generated by a human or AI technology." A bespoke meeting summary sent to one client is correspondence, subject to risk-based review rather than principal pre-approval. A templated AI recap sent to more than twenty-five retail investors in thirty days is a retail communication requiring principal approval before use. The template is the communication, not the individual send — which is exactly the distinction an automated workflow is designed to blur.
FINRA has conceded the problem. Regulatory Notice 26-14, published 9 July 2026, proposes to dismantle blanket principal pre-approval, stating that applying it to AI-generated retail communications "can be challenging" and that the difficulty is "compounded by the potential speed and volume of AI-generated communications." The replacement would require firms to write their own procedures determining which categories need pre-approval. It also offers the sector's clearest statement of the standard: "Gen AI communication tools can be part of a reasonably designed system, provided they are vetted, tested and monitored."
Is the prompt a record? Is the output? There is no SEC or FINRA guidance. That silence is the finding, and the practitioner analysis has moved well ahead of the regulators.
The conventional test is transmission: AI-generated content that is never sent is probably not a written communication requiring retention; content transmitted by email or chat triggers retention if the subject matter fits. The better analysis notes that transmission answers the wrong question — "Transmission tells you whether you have a communications problem; it does not tell you whether you have a records problem elsewhere." An untransmitted transcript can still be a required record under provisions that have nothing to do with communications: order memoranda, code-of-ethics violations and responsive action, performance-calculation support, annual compliance review documentation. A notetaker running in an investment committee meeting or a compliance interview can manufacture a required record that would not otherwise exist.
Two practical consequences follow, and the second is counterintuitive. Decide at the category level which meeting types may be recorded, before deployment rather than case by case — and prohibit notetakers outright on certain call types, such as calls with counsel and compliance interviews. And recognize that retaining everything is not the conservative choice: surplus transcripts create examination and discovery exposure that would not otherwise exist.
The market is pricing prompts as records ahead of the regulators. Commercial capture products now exist that ingest prompts and responses from enterprise AI platforms into the same archive as email. The off-channel communications sweep — over 100 firms and more than $2 billion in penalties — is the cautionary backdrop, and "shadow AI" on personal devices is reported by one examiner-facing consultant to occur at virtually every RIA examined.
No SEC or FINRA guidance addresses meeting-recording consent. Neither the AI notice, nor the 2026 oversight report, nor the examination priorities mentions it. The exposure is private civil litigation and state law, which is precisely why compliance departments oriented toward securities regulators are missing it.
In re Otter.AI Privacy Litigation is consolidated in the Northern District of California, pleading the federal Wiretap Act, California's Invasion of Privacy Act, Illinois's Biometric Information Privacy Act and more. The core allegation is architectural rather than incidental: the notetaker "seeks permission only from meeting hosts... but not from all participants." That host-only consent model is the industry standard design. Speaker diarization — how a transcript labels who said what — arguably extracts a voiceprint, which creates biometric exposure independent of the wiretap claim.
Two points practitioners routinely get wrong. First, any list of "two-party consent states" you have seen is probably wrong. Roughly a dozen states impose an all-party or anti-secret-recording rule, but at least six are medium-dependent or judicially narrowed: Connecticut is all-party for telephone and one-party in person; Oregon is the inverse; Michigan reads all-party on its face but courts have recognized a participant exception since 1982; Nevada and Delaware are contested. Illinois — the state everyone cites — requires the recording to be surreptitious and the conversation to carry a reasonable expectation of privacy, so a disclosed, visible notetaker is likely fine there. Massachusetts is a secrecy statute rather than a consent statute, and is the harshest in practice.
Second, on a multi-state video call, the location of the advisor, the firm and the server is irrelevant. The controlling authority is a brokerage case: California's Supreme Court held that California law governed recordings made by a firm's Atlanta branch of calls with California-resident clients, because California's interest in resident privacy would otherwise be severely impaired. If any participant is physically in an all-party state, assume that state's law applies. California statutory damages run $5,000 per violation; Illinois biometric damages are $1,000 to $5,000 per violation and accrue per scan.
Vendor practice converges on disclosure in the calendar invite, a verbal announcement, capturing the affirmative response inside the transcript, and switching off on objection. Some wealth-specific vendors have moved to no-recording, text-only architectures explicitly citing the Otter litigation. None implements a true per-participant consent gate. That is an unremediated industry-wide exposure, and the firm — not the vendor — is the one with the client relationship.
The amended Regulation S-P requires written policies obliging service providers to notify the firm "as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred." Compliance dates were December 2025 for larger entities and June 2026 for smaller ones — both now passed.
This is the practical blocker in AI procurement, and it is asymmetric: large model providers' standard terms do not generally commit to 72-hour breach notice, and a mid-size RIA has no leverage to negotiate one. The firm must paper it or document an exception. Separately, disclosing client information to an AI vendor without an opt-out depends on the service-provider exception, which requires contractual confidentiality and purpose limitation. If the vendor trains on your data, the purpose-limitation prong is arguably broken. No regulator has confirmed or rejected that reading. Vendors that state plainly they do not train on client data — several wealth-specific ones do — are materially easier to diligence, and that single contractual term is worth more than any feature comparison.
Purpose-built advisor AI runs roughly $800 to $2,400 per seat per year at list price. A hundred-advisor firm buys the category for something between $80,000 and $240,000 annually. Savant Wealth Management, at 727 employees, has disclosed spending $15–20 million a year — roughly $50 million over three years — building its own data warehouse and internal AI. Its stated goal is to quadruple revenue while only doubling headcount.
Those two numbers are not close enough for cost to be the deciding factor. The build case cannot be about cost. It has to be about differentiation or data control, and a firm should be made to say which — out loud, in writing, before the first hire.
The model is the cheap part. In published enterprise retrieval-application costings, engineering and data preparation account for 50–60% of budget and model API calls for 5–15%. Most firms budget the inverse. The expensive work is connectors, identity resolution, document cleanup and evaluation — precisely the work in §04, which is why a build that skips the data layer produces the 19% condition at ten times the price.
Maintenance is what kills mid-size builds, not construction. The canonical case is Commonwealth Financial Network, which built its advisor platform, then spun it off as a separate company in 2019 because ongoing maintenance costs could not be carried without more scale. They built it, it worked, and they still could not keep it. Generic benchmarks put annual maintenance at 15–20% of initial build cost, permanently.
The famous builds are mostly not builds. Morgan Stanley did not build a model — it built retrieval, evaluations and workflow on a vendor model, growing an internal corpus from 7,000 to 100,000 documents and reaching 98% adoption among advisor teams. Bank of America's Meeting Journey ran on infrastructure it had already built for Erica since 2018; the marginal build cost was low because the platform existed. Both are correctly described as assembly, not construction. Neither has ever disclosed team size, budget, or timeline — so any mid-size firm modelling itself on them is modelling against numbers that do not exist publicly.
What is genuinely transferable from Morgan Stanley is not the architecture but the discipline: purpose-built evaluation sets graded by advisors and prompt engineers, and daily regression testing against a question suite. That is an operating cost, forever, and it is the line most build models omit entirely. It is also, as Part II found, the only published evaluation methodology anywhere in the sector — and it belongs to a build, not a purchase.
Build is not on the table and should not be discussed. The real risk is buying four overlapping subscriptions and a data problem.
Check what your CRM, custodian and productivity suite already include before buying anything — the horizontal tools in §03 may already cover meeting capture. Buy one thing, use it for two quarters, measure in minutes per week.
Notetaker adoption is highest among solos, and so is unmanaged consent risk — you have no compliance department to catch it. Get the consent script right before the tool goes on.
The only segment where the question is genuinely open — and the segment where the evidence most strongly says buy the applications and build the data layer.
Split the decision. Applications are commoditizing fast and are cheap; the data layer is durable, differentiating, and portable across whichever vendors survive. Spend on connectors and identity resolution, not on a proprietary assistant.
Maintenance, not construction, is what breaks builds at this size. Before approving one, write down the annual run-rate at 15–20% of build cost and ask whether it survives a bad revenue year.
Build is real, and the advantage is not the model — it is the corpus, the evaluation apparatus, and the ability to make adoption non-optional.
Assemble rather than construct: vendor models, internal retrieval, internal evals. Fund the evaluation function permanently. One large bank ties AI usage to performance review — an adoption lever no buyer of point solutions has.
Supervision scales worse than deployment. Rolling a tool to twenty thousand advisors means twenty thousand advisors generating communications that Rule 2210 attaches to — which is exactly why FINRA is now proposing to rewrite the pre-approval regime.
The standard advice on this category has been that standalone AI notetakers are doomed, because CRMs and custodians will absorb the feature and give it away. The absorption is real: Nitrogen bundled statement parsing and proposal drafting into existing subscriptions at no additional cost in February 2026, Morningstar embedded the same functions into its advisory suite in March, and Robinhood's Cortex for Advisors arrived free to advisors custodying on TradePMR in June.
But the prediction failed. CRM response was slow — one major CRM did not ship a notetaker until autumn 2025 and another still lacks one. The specialists won on speed, and the assessment by mid-2026 had inverted: it is now the CRMs that look threatened by the standalone tools rather than the other way around. Jump reached roughly 27,000 advisors and raised $80 million; Zocks raised $45 million; both are expanding into onboarding, account opening, analytics and client data — becoming systems of record.
So the real vendor risk is not the one everyone is watching. It is not your AI vendor gets absorbed. It is your AI vendor becomes your system of record and you never decided that it should. A tool bought for meeting notes at $100 a seat, two module upgrades later, is holding your client data model. That is a governance decision being made by procurement.
Where absorption has bitten is the proposal and statement-parsing category, where three major platforms now give away what standalone vendors charge for. Thinly capitalized point solutions in that lane are the ones to diligence hardest.
| Question | Why it separates vendors |
|---|---|
| Do you train any model on our client data? | Determines whether the service-provider exception under Reg S-P holds. Several wealth-specific vendors state plainly that they do not; most generic tools do not make the statement. This one contractual term outranks any feature comparison. |
| Will you commit contractually to 72-hour breach notification? | Required by amended Reg S-P. Large model providers generally will not. The answer tells you whether you are papering an exception on day one. |
| Do you record audio, or process text only? | Recording architecture drives the wiretap and biometric exposure in §05. No-recording, text-only designs materially reduce it. |
| Do you retain prompts and outputs, and can we export them? | FINRA's effective practices call for prompt and output logs and model-version tracking. If the vendor cannot produce them, you cannot either. |
| Which model, which version, and how are we told when it changes? | A foundation-model version bump is a model change. Almost no vendor commits to notifying you. |
| Show us your evaluation results. | No vendor in this category publishes evals, a model card, or governance documentation. Asking is still worth it — the quality of the non-answer is informative, and enough asking changes the norm. |
| What happens to our data if you are acquired? | The exit mode in this category so far is acquisition, not failure. Portability language matters more than survival odds. |
Two useful screens do not yet work. SOC 2 Type II is now table stakes across the notetaker category and therefore differentiates nothing. And no advisor-AI vendor we could find publishes ISO 42001 certification — the AI management-system standard has not penetrated this market, so buyers cannot use it as a filter yet.
Ordered so that each step produces the artifact the next step needs, and gated so that nothing is deployed into a data environment that cannot support it.
| Item | Status |
|---|---|
| Build cost, timeline or team size for any enterprise AI deployment | Never publicly disclosed — not by Morgan Stanley, JPMorgan, or Bank of America. Any mid-size firm benchmarking against them is benchmarking against numbers that do not exist. |
| Any wealth-specific total-cost-of-ownership comparison for internal LLM applications | Appears not to exist. The TCO figures cited here are generic enterprise, vendor-published, and used only for order of magnitude. |
| Independent benchmark for data-layer implementation cost in wealth | Appears not to exist. All cost and timeline figures in §04 are vendor-published. |
| Rigorous switching-cost or data-portability benchmarks in advisor technology | Appears not to exist — which means firms are making lock-in decisions with no reference point. |
| Any measured, independently verified productivity study of AI in an advisory practice | None found. The best available is a 28-day, 60-employee observation at one RIA, conducted jointly with the vendor. An independent 533-advisor study reported adoption but no productivity metrics at all. |
| Published pricing for roughly half the vendors in §03 | Contact-sales only. Where pricing is published it is unstable: three sources give figures for the same two products differing by 40–100%, and one vendor raised prices into a compressing market. List prices are also heavily discounted in practice, so the per-seat figures here are ceilings, not transaction prices. |
| Technology spend as a share of RIA revenue | The circulating 3–4% figure traces only to secondary commentary, not to any primary benchmarking study. Treated here as a rule of thumb, not a benchmark. |
| Ruling on the consolidated AI-notetaker privacy litigation | Motion to dismiss argued May 2026; no ruling confirmed as of publication. Check the docket before relying on §05's litigation analysis. |
| Whether prompts and outputs are books and records | Not a research failure — a confirmed regulatory silence. No SEC or FINRA guidance exists. |
Advisor time-allocation figures carry an additional caveat worth stating: the canonical study's activity detail sums to roughly 53 hours per week while the same advisors self-report 43. Every derived per-hour figure moves about 19% depending on which base you use.
Part IV takes up the question this piece keeps deferring: what happens when the model stops drafting and starts acting. The engineering problem is the one every firm meets at the edge of §03's frontier — how an investment policy statement becomes a machine-readable constraint set the agent cannot argue with: tracking-error budgets, VaR caps, concentration limits, drawdown triggers, and the position limits, rate limits and circuit breakers that Part II found missing from every published agentic retail product.
Part V is the validation playbook — evaluation design, backtest hygiene, champion–challenger promotion, shadow deployment, drift monitoring, and treating a foundation-model version bump as the model change FINRA already says you should be tracking.