Wealth firms already have plenty of data. Client facts live across CRM records, emails, meeting notes, custodial statements, financial plans, and spreadsheets, plus whatever an advisor happens to remember, and none of those systems share a model of the relationship.
A knowledge base gives the firm that model. It connects people, households, entities, accounts, goals, concerns, events, tasks, and source citations, so every workflow starts from the same understanding of the client. Ask a question about one household or about every household in the book, and the answer comes from the same place.
Ask across your whole book, not one client file.
Most tools answer a question about whatever client file happens to be open. Briefly checks every household in your book for the same question, then answers it the way it would answer about one client, with a name, a number, and the document behind it.
The same pattern holds for any cross-client question, whether it's about concentrated positions, upcoming distributions, or clients who mentioned selling a business. Briefly reads the statements, transcripts, and notes already filed for each household and answers from what's actually there, with the file it read linked under every claim.
This works because every document lands in a household's own record first, then gets checked across the whole book whenever a question calls for it. Filing an email into the Rivera file doesn't just help the next Rivera question. It also becomes one of the records checked the next time someone asks about concentrated positions, upcoming distributions, or anything else that spans the book. A CRM field or a folder of PDFs can't do this on its own, because nothing connects the file you're looking at to the dozens of others you'd need to check by hand.
Why this matters in wealth management.
- Households are becoming more complex as wealth transfers across generations.
- Advisors are responsible for more relationships without proportional support staff.
- What advisors know about a client often stays in individual memory instead of firm infrastructure.
- Generic AI summaries are risky unless they are traceable to source material.
Briefly is built to answer inside that reality without asking a firm to change how it works. It runs inside Claude, where many advisor teams are already working, and reads the files that are already there. If a firm runs the connector, those files stay on the advisor's own computer, and the only things that reach Briefly's servers are a sign-in, a check that the seat is active, a de-identified layer of firm preferences, and a short usage record for each tool call, never the client file itself. That's true whether the question comes up during meeting prep the morning of, or mid-call about a household nobody on the call remembers well. The advisor doesn't have to leave Claude, open a second app, or wait for someone else to pull the file.
Why CRMs are not enough.
CRMs are important systems of record, but they are not built to reconstruct a relationship across every source. The details that matter most often live in a note, a forwarded email, a PDF, a meeting transcript, a planning document, or the memory of a senior advisor.
Search helps when you already know what to look for. A knowledge base helps when you need the system to surface what matters before you ask.
A CRM also only knows what someone typed into it. It doesn't read the email you forwarded, the PDF you saved to a folder, or the transcript from last week's call, not unless someone copies the details in by hand. Briefly reads those files directly, so the knowledge base grows every time a document gets filed, not every time someone remembers to update a record.
Neither one learns from being corrected. If an advisor tells a CRM once that a client goes by a nickname, or that the firm calls it a planning conversation and never a sales meeting, someone has to remember to make the same fix again the next time it comes up. Briefly keeps a correction like that as a standing rule instead. One firm did exactly this with a single phrase, telling Briefly to say planning conversation instead of sales meeting, and every brief that firm has received since has followed it, for every advisor on the team.
What a knowledge base should include.
The concentrated-position example above pulled from one category, portfolio positions. A full client file covers more ground than that.
- Family and household relationships, including heirs and decision makers.
- Professional network, including CPAs, attorneys, trustees, and centers of influence.
- Planning themes such as liquidity, philanthropy, estate complexity, concentrated positions, and tax deadlines.
- Open loops, follow-ups, unresolved concerns, and promises made in prior meetings.
- Source citations so advisors can verify before using anything with a client.
None of this shows up on its own. A knowledge base only holds what gets filed into it, so the categories above are really a checklist for what to point Briefly at first, statements, planning documents, and the emails and notes an advisor already has sitting in a folder.
A meeting brief is one thing the knowledge base can do.
A meeting brief is useful because it gives the advisor an edge before the conversation starts, but the brief draws on the same knowledge base behind the whole-book questions above it. Open tasks, portfolio changes, client sentiment, life events, and the professional network around a client all come from files that were filed for other reasons first. The brief just pulls the relevant pieces together and cites where each one came from. See an actual brief, with names and firms changed.
Each meeting adds more source-backed memory to the knowledge base, and meeting prep gets faster with every cycle because there's less new material to review each time. The client file gets richer, and the firm becomes less dependent on any one person's memory.
What Briefly builds.
Briefly turns fragmented advisor files into a living knowledge base. It keeps every fact traceable to its source, keeps outputs reviewable, and gives each workflow what it needs without forcing a CRM migration.
Each new document, an email forwarded from a client, a statement uploaded after it arrives, a note typed up after a call, gets filed into the household it belongs to and read into the knowledge base right away. Nothing has to be reformatted or copied into a separate system first. The file just gets bigger and more accurate, and the next question about that household, or about the whole book, draws on it.
Briefly runs two ways, inside Claude with the connector or as a web app Briefly sets up for you. Either way it's the same knowledge base underneath, built from the same files, with the same citations on every answer.
The result is one base of firm memory. It gets better every time an advisor uses it, and it keeps working long after any single meeting ends.
Connor Florczyk
Founder of Briefly. Before Briefly, he worked as a private wealth analyst on a top-performing team at Morgan Stanley, where he saw firsthand how much advisor time gets lost hunting for a client's own files.
See it answer a question on your own files.
Start the connector and ask it something real about your book. Every answer comes back with the file it was pulled from, so you can check it before you use it with a client.
Start now Book a demo