Held-Away Account Detection With Plaid + Claude — The Build

RIAs lose rollover business they could have won because they don't know what the client holds elsewhere. The held-away 401(k) doesn't move until something triggers it. The firm that sees the trigger first wins the rollover.

Plaid plus Claude is the system that surfaces the triggers in time.

What Plaid can do here

Plaid's Investments product gives you read access to a client's investment accounts at thousands of institutions. Holdings, transactions, balances. Updated automatically.

You don't get trade execution. You don't get write access. You get visibility.

That visibility is the missing piece for most firms. Without it, you're asking the client to fill out a form every quarter that they ignore.

What to detect

The four triggers worth detecting:

1. Job change signals. A held-away 401(k) at Fidelity for Acme Corp suddenly stops getting contributions. Plaid sees contribution patterns. When they stop, the client likely left Acme.

1. Inheritance signals. A new beneficiary IRA appears in the client's connected accounts. Plaid surfaces the new account.

1. Large deposit signals. A jump in a connected savings account beyond normal patterns. Could be a bonus, a property sale, an inheritance.

1. Asset drift signals. A held-away account's allocation drifts significantly from where it was. Time for a conversation.

The build

Layer 1: Plaid Link integration. Standard onboarding. Each client connects their held-away accounts. Re-prompt annually to add new accounts.

Layer 2: Webhook ingestion. Plaid fires webhooks on transactions and holding changes. Your system stores these in Postgres (Supabase works well).

Layer 3: Pattern detection. A scheduled job (Inngest cron) runs daily across all clients:

• For each held-away employer plan, check whether contributions have stopped (no contribution in last 30 days when prior 6 months had monthly contributions).
• For each connected account, check for new accounts that appeared in the last 14 days.
• For each connected savings/checking, check for unusual deposit patterns (Z-score > 2.5 against rolling 90-day average).
• For each held-away account, check whether the allocation has drifted >10% from last quarter.

Layer 4: Claude prioritization. Raw signals go to Claude with the client's relationship context:

Client: {name}, age {age}, total AUM with us: {amount}.
Recent signal: {signal_description}
Last advisor conversation: {summary, last_date}

Score this signal:
- Likelihood of an actionable opportunity (0-10)
- Suggested action for the advisor
- Why this is worth a touch (one sentence)
- Best framing for the outreach

Only signals scored 7+ get surfaced to the advisor.

Layer 5: Advisor notification. A Slack message or a daily digest email. Each signal includes the client name, the trigger, the suggested action, and a draft outreach.

How to measure it

For each trigger type, count the signals the system raised, how many became conversations, and how many changed something for the client. Review those counts with compliance every quarter. A trigger that rarely leads to a useful conversation is noise, and it should be tuned or dropped.

What tends to break

False positives. A contribution-stop detector can mistake year-end timing for a job change. Require a longer gap and an established pattern before flagging, for example no contribution in 45 days after at least four monthly contributions in a row.

Plaid's connection breakage. Plaid connections expire. Re-auth flows have to be in the client portal. Without ongoing re-auth, your data goes stale.

Disclosure. An outreach draft that says "we noticed your contributions stopped" tells the client exactly what the firm is watching. Make sure the client's consent clearly covers that use of their data, and have compliance approve the outreach wording before anything goes out.

What this isn't

Not a robo-advisor. Not auto-trading. Not auto-rolling-over.

Just: better awareness, faster outreach, more conversations at the right time.

What to build first

If you're a wealth firm:

One, Plaid Investments integration with a clean client opt-in flow. The opt-in is the harder cultural piece than the technical piece.

Two, the simplest job-change detector. It catches the highest-dollar opportunity (rollover). Build this before anything else.

Three, the advisor notification path. Don't build the dashboard first. Build the Slack message first.

Budget time for the compliance review and the re-authorization flow, not only the build. Those two pieces decide whether the system is still running a year later.