Skip to main content
Research preview · Not a product yet

Advisors see their book. Nobody sees the whole client.

The accounts that decide a client’s real risk, the 401(k), the HSA, the outside brokerage, sit where an advisor’s software cannot reach. The standard fix is emailed statements. The contested fix, credential sharing, is being banned custodian by custodian. We are researching the third way with practicing advisors, and there is nothing to buy on this page.

One book · Custody markedDesign concept · Illustrative data
Taxable · SchwabIn custody
Household A$412,800
401(k) · FidelityHeld away
Household A$688,200

NVDA 31% of household across all three accounts

RSU · ShareworksHeld away
Household A$194,500
IRA · SchwabIn custody
Household B$897,400

Drifted 6.4 pts from the household target since March

403(b) · EmpowerHeld away
Household B$241,900
Brokerage · VanguardHeld away
Household C$156,300

Holds MU · filing last week contradicts the stated reason

Household A’s flag only appears because the 401(k) and the RSU account are in the view · account by account, nothing looks wrong · the held-away rows are what your stack cannot show you today
The research

Six things we are testing with practicing advisors.

01

The whole book, by name

Every client holding a given security across every account, custodied or not. The list-holders lookup wirehouse desks have and independents lack.

02

Reasons, monitored

A reason on file for each position, read daily against filings, with verbatim citations when something contradicts it. No reason on file is itself a flag.

03

What changed overnight

Concentration that crossed a line, drift past tolerance, evidence against a held reason. Not a news feed. What moved in your book.

04

The pre-meeting brief

Before the 2pm: what changed in this household since you last met, across all of their accounts, with the receipts attached.

05

MCP for your AI tools

A read-only, audit-logged layer so the notetaker and CRM assistant you already pay for can answer questions about actual portfolios.

06

Read-only by construction

Client-permissioned, token-based connections. No credentials stored, no trading capability anywhere in the design, revocable by the client.

Access

The client grants sight. Nothing else exists.

The client authorizes each account through their institution’s own login. The institution issues a revocable token. Here is the entire scope we are designing to, enforced at the protocol level, not promised in a policy.

Connection scope · client-permissioned · revocable
Granted · read-only
  • Balances and holdings
  • Transactions and history
  • Ongoing visibility, in-custody and held-away alike
  • Audit-logged queries from your AI tools
Never granted
  • Stored credentials
  • Trading capability
  • Money movement
  • Model training on client data
No credential sharing anywhere in the design · the client can cut any link at any time · a categorically different posture from the one custodians are banning
The ask

Twenty minutes. No pitch.

We want advisors who feel the outside-account blind spot weekly: fee-only planners, RIA owner-operators, and advisors at larger firms who are candid about what their tools do not show them. Your workflow, your morning, what you would actually use.

Interviews shape what gets built and whether it gets built.

The interview starts here20 min · no pitch
Read by the founder, not a funnel.