Every advisor carried a book of clients across scattered notes, tasks, transcripts, and a CRM, and lost real time to the admin between meetings. I built the cockpit, the client portal, and the overnight pipeline that turns each meeting into a review-and-approve step by morning, without ever sending a word the advisor did not approve.
At an independent capital-markets advisory firm, each advisor runs a book of clients through a structured, multi-month program, meeting each of them on a recurring cadence. The record of every one of those relationships was spread across spreadsheets, a shared drive, call transcripts, email, and the CRM that is supposed to be the system of record.
The cost was the admin around each meeting. Before a call, an advisor reloaded the client's whole situation by hand across those systems. After it, they wrote the notes, split out who owed what, and sent the follow-ups. Every week, the open tasks were copied by hand into the next week's tab, one of the biggest time sinks in the whole workflow. The firm's own stated goal for the project was simple and specific: give the advisors their hours back.
Six systems, reconciled by hand, around every meeting.
Two surfaces sit on top of one engine. The advisor gets a cockpit that holds the whole book in one place. The client gets a clean portal. Between them runs an overnight pipeline: it takes each meeting's transcript and, by morning, has drafted everything the advisor used to write by hand, queued behind a single approval gate.
The advisor walks in, opens the queue, and reviews. Approve, edit, or reject. The work that used to take a block of admin after every call is now a few minutes of reviewing drafts that already exist.
An AI that drafts client-facing messages in a regulated relationship has to be safe by construction, not by good intentions. Five invariants held across the entire build, and every design decision was checked against them.
The integrations, Zoom, the CRM, the drive, calendar, and email, are all flagged adapters with mock implementations behind them. That let the whole product run on a deterministic seeded demo of twenty-five clients, so it could be shown and tested top to bottom without reaching into anyone's real data. The riskiest real-world join, matching a recorded meeting back to the right client, was named as the top build risk and designed around from the start.
The notes, the tasks, and the client drafts that an advisor used to produce by hand after every meeting are waiting for them in the morning, already drafted, gated on their approval. The firm's stated success metric for the engagement was advisor hours saved, and the per-meeting admin is where those hours were.
The admin around each meeting collapses to reviewing pre-drafted work. Across a book of clients and a weekly cadence, that is where the advisor's time was going.