The warm book is a memory system that breaks at 150 clients
When an advisor leaves, the firm keeps the account and loses the relationship, because the CRM logged assets and addresses, never the context that made the client stay.
The handoff that hands over nothing
An advisor retires after twenty years, and the firm keeps all 140 households. Then the successor sits down to read the files, and the handoff hands over almost nothing. Assets under management: current. Address: current. Birthday: logged. Risk tolerance: a dropdown set to 'moderate.' What isn't anywhere in the system is why any of it looks the way it does. That the Hendersons went conservative in 2022 because his company ran layoffs and the pension he was counting on stopped feeling safe. That the widow in the coastal account will not hear the word annuity, because her late husband was sold one and regretted it. That the business owner's whole plan rests on a sale he brings up every spring and never closes. None of that made it into a field. It lived in one person's memory, and that person just walked out the door.
The warm book is a memory system wearing a contact list's clothes
Call it the warm book: the advisor's running mental model of every client, updated across a hundred small conversations. It's the most valuable asset most practices own, and it sits almost entirely off the books. The warm book works beautifully at forty clients. It strains at a hundred and fifty. That number isn't arbitrary. It's roughly where the anthropologist Robin Dunbar put the ceiling on stable relationships a person can actively carry, and an advisory book is exactly that kind of load: not names on a list, but live context on real people whose situations keep moving. Past that line, the advisor is still the system of record. They're just quietly running out of room to be one.
The most valuable asset most advisory practices own sits almost entirely off the books.
Why the CRM-versus-spreadsheet debate misses it
Most of the conversation about advisor tooling argues about containers. Spreadsheet or CRM, this platform or that one, more integrations or fewer. All of it skips the question that decides whether the tool matters: do the fields you capture let someone rebuild the relationship six months from now? A CRM full of clean, current, well-integrated data can still be useless the day the advisor leaves, because the fields it enforces are the ones that are easy to structure, not the ones that carry the relationship. Address is easy. 'What he's actually afraid of' has no dropdown. So it never gets typed, and the tidiest CRM in the firm inherits a book of strangers.
How financial advisors keep track of client details
Ask around, and the honest answer is: in their heads, with the CRM as a billing and compliance backstop. The structured fields get filled because the firm requires them and the custodian needs them. The context gets remembered because the advisor cares, not because anything prompts it. That split holds fine until capacity does. Practitioner research on advisor workload has long argued that effective capacity per advisor runs well below the client counts many books carry, The sweet spot for many advisors falls between 40 and 100 client households, per Kitces' 2025 Advisor Wellbeing Study. ([source](https://www.advisorhub.com/whats-the-right-number-of-clients-consultants-say-fewer-is-often-better/)), which means a large share of books are already operating past the point where memory alone is a safe system of record. The relationship isn't documented anywhere it can survive a departure. It's rehearsed, nightly, by one person.
What makes a relationship recoverable six months later
Recoverable is the word that matters. Not stored, recoverable: could a competent successor read the record and pick up the relationship without the client feeling handed off to a stranger? That test sorts client data into two piles, and most systems only capture one of them. The recoverable pile is conversation-shaped: what the client is worried about, what they said no to and why, the life event driving this year's decisions, the priority they repeat every review. It's softer to log and it decays fast, which is exactly why it has to be captured in the moment it's said, not reconstructed from memory at year-end.
What most systems log
What makes it recoverable
Assets under management
What the client is actually worried about
Address, phone, birthday
The life event driving this year's decisions
Risk tolerance dropdown
What they said no to, and why
Account balances
The priority they repeat every review
Last contact date
The context you'd need to not sound like a stranger
The left column is what a CRM enforces. The right column is what survives a departure.
The liability nobody files under retention
There's a version of this that isn't about retention at all. FINRA's suitability rule and the SEC's Regulation Best Interest both start from a premise the firm rarely documents: that the advisor knows the client well enough to recommend in their interest. When the reasoning behind a recommendation lives only in one person's memory, the firm can't demonstrate the basis for it after that person leaves, or if a regulator asks. Undocumented relationship context is a suitability record the firm can't produce on demand, not only a retention gap. Most practices treat the warm book as a soft asset. It's also a compliance exposure, sitting quietly until the year it isn't quiet.
Undocumented context is a suitability record you can't produce
FINRA's suitability rule and Reg BI assume the advisor knows the client. If the basis for a recommendation lives only in memory, the firm can't demonstrate it once that advisor leaves. That's a compliance exposure, not just a retention risk.
Capture the context at the moment it's said
The fix isn't a bigger CRM. It's capturing the recoverable fields when they surface, which is almost always mid-conversation, when there's no time to open a laptop and type into the right tab. Met is built for that moment: capture a card and the context around it fast, in the room, so what the client actually said gets attached to who they are before it fades. It's the same memory cliff we've written about in other settings, sharpened by a book that keeps growing and a regulator that assumes you remember. Your contacts stay yours too, held in iCloud, not sold and not sitting on someone else's server. The advisor still carries the relationship. The record just stops depending on their memory to survive them.
Get Met and stop keeping your book in your head.
Met is built for the moment context actually surfaces: in the room, mid-conversation, before it fades. Capture the card and what was said, keep it on the client's record, and keep the whole thing in iCloud rather than on a vendor's server.