Client engagement · Wealth management
Meeting preparation,
scoped with the owner.
I worked directly with a Minneapolis wealth-management firm’s owner to scope and build a Claude API agent that turns CRM and document-store context into cited, two-page meeting briefs.
Agree on what the brief must get right
Before rollout, the firm owner signed pass/fail thresholds for whether the agent retrieved the right information and made unsupported claims. Those criteria gave the build a defined target.
Connect the existing sources
The work included a custom MCP and a Claude API meeting-prep agent connected to the firm’s CRM and document store. The agent produced a cited, two-page brief for an advisor to review.
Keep separate decisions separate
A separate assessment examined role-scoped AI access to portfolio systems. I compared two MCP-gateway vendors with a custom build and recommended a 90-day read-only pilot.
What happened in use
One advisor completed total meeting preparation in under five minutes in a single session, including reading the brief and checking questionable details. The time result is limited to that one session. The firm continued using the custom MCP and meeting-prep workflow after the contract ended.
Anonymized engagement · 2026-06 to 2026-08. References on request.
Inside an illustrative brief
For the advisor
A statement you can trace.
A question left open.
Discuss the client’s planned move. [1]
[1] Read the sample source
“Client asked to discuss a planned move at the next meeting. Date not provided.”
When is the move?
The source does not specify a date.Illustrative acceptance check
- Source attached
- Shown
- Missing date flagged
- Shown
- Advisor confirmation
- Still needed
Invented content and review checks. Not actual client output or evaluation results.