Schwab's Q4 connector turns AI access into a custody term

Anthropic's advisor assistant will reach the wealth management desktop in the fourth quarter through exactly one custody platform, and the eleven integration partners signed on to build around it all sit behind a single connector owned by Schwab.

That turns the assistant into a custody term rather than a software license a practice can evaluate on features and price, because whoever owns the pipe through which Claude reaches an advisor's book also owns the default for client data, workflow, and the assets behind them.

The license fee is the smallest part of what a practice is being asked to buy: the visible price may be trivial, but the leverage Schwab gains over integration decisions is the actual cost, and it never appears on an invoice.

Custodians compete for assets, but assets sit on top of workflow, and if an advisor's morning starts inside an assistant that can pull clean, permissioned data from only one custodian, the workflow itself becomes a reason to consolidate accounts there.

Schwab does not need to pay a recruiting bonus to get the next dollar; it just needs the assistant to work best on its own platform, and the eleven integration partners sharpen that point.

Each has a reason to build into Anthropic's assistant, but none of them controls the connection to the underlying account data, so they are building on Schwab's pipe, which means Schwab can see which tools are being used and in what combination even if it never reads a single prompt.

The assistant's route to the advisor runs through a single point of control, and the cost is the data and workflow advantage Schwab accumulates every time an advisor runs a client meeting through its connector.

What Schwab can observe is likely the pattern of use—which advisors adopt the assistant, which workflows they automate, and which third-party tools they combine it with—enough to know which practices are becoming dependent on the Schwab pipe without reading every prompt.

A practice that uses two custodians now faces a forced choice: the assistant can access Schwab-held accounts directly, but it cannot do the same for accounts at the other custodian until that custodian builds its own connector and Anthropic certifies it.

So the advisor must either run two workflows, one AI-enabled and one not, or begin moving accounts to Schwab to make the tool work across the book.

At that fork, the practice is deciding whether to restructure its custody relationships to make the software useful, and the license fee remains the smallest line item in that decision.

Advisors who negotiate software routinely compare per-seat prices, a category error when the license fee for the assistant is likely a rounding error against a single client relationship; the real negotiation is over the custody agreement, where one clause about data portability can be worth more than a decade of seat fees.

Advisors should treat the connector's arrival as a trigger to audit their custody agreements, many of which were drafted before AI data flows existed and may be silent on whether client data used by the assistant stays portable, whether integration rights are exclusive, and what happens to the tool if the practice leaves Schwab.

Before the connector goes live, a practice needs written answers to whether the assistant can run against any custodian it chooses or only Schwab, who owns the prompts and outputs generated from client data, and whether the custody agreement grants Schwab any right to use that data to improve its own products.

If the answers are not in writing, the practice is giving away leverage it does not yet know it has.

Multi-custody firms should ask the hardest question first: if the assistant only works fully at Schwab, what is the cost of not consolidating? The cost is the lost productivity advantage competitors will gain by moving first.

The window to act is short: Schwab's connector is scheduled for the fourth quarter, and once it is live, the default terms will already be set, so advisors who wait until the assistant is on their desktop will find themselves negotiating from the weaker side of an installed workflow.

The right move is to amend the custody agreement now, adding language that preserves data portability, prevents exclusive integration rights, and requires Schwab to support equivalent connectors for any other custodian the practice uses. If Schwab refuses, that refusal is information about what the connector is really for.