Your CRM logged the stage and lost the sentence that mattered.
Applicant tracking systems and advisor CRMs record where a person sits in a process. The relocation, the kid starting college, the reason to call: no field holds it.
Six months later, the call sounds like a cold call
A recruiter reopens a candidate record in March. The applicant tracking system shows exactly what it was built to show: applied in September, phone screen passed, final round with the hiring manager, role filled internally. Disposition: silver medalist. Every field is complete.
So the recruiter dials and opens with 'I came across your profile again.' The candidate hears a stranger.
Back in that September screen, the candidate had mentioned moving to Austin in the spring. A new Austin opening should have made this the warmest call of the week. That detail never made it into a field, because no field asked for it.
Swap the desk and the story repeats. A financial advisor pulls up a household before an annual review: assets, allocation, risk profile, last rebalance, all current. What the screen doesn't hold is the remark from last year's meeting that the client's daughter starts college next fall. The advisor opens with market commentary. The client came in wanting to talk about tuition.
The status-story gap
Professional tools are very good at recording where a person sits in a process. They're close to useless at recording what made the conversation with that person matter. Call it the status-story gap.
Status is structured: a stage, a date, an account value, a dropdown. Story is the sentence someone said in passing that changes how you should talk to them next time. The relocation. The kid starting college. The boss retiring in June.
Applicant tracking systems and advisor CRMs were designed around status, and for defensible reasons. Status is what managers report on, what forecasts roll up from, and what compliance reviews. But the detail that makes a follow-up land has nowhere structured to live, so it lives in someone's memory until it doesn't.
Moving to Austin in the spring; only open to hybrid after the move
Financial advisory (CRM)
Assets, allocation, risk profile, last review date
Daughter starts college next fall; tuition timing is on the client's mind
Illustrative records. The middle column is what the category's tools are built to capture; the right column is what made the follow-up matter.
Why 'just use the notes field' doesn't fix it
The standard advice is discipline. Log every call. Use the notes field. Write it down before you forget. Managers say it, trainers say it, and the people doing the job mostly agree and then don't do it.
That's a predictable result of the design. In most of these systems the notes field is free text at the bottom of the record, filled in after the conversation, when the details have already started to fade. (We've written about how fast that fade runs in [the 72-hour memory cliff](/articles/72-hour-memory-cliff/).) It also fills up with logistics: left voicemail, sent job description, rescheduled. The one line that mattered ends up buried among them.
And the system never brings it back. Reminders, tasks and dashboards key off structured fields: stage changes, review dates, account values. A free-text mention of Austin triggers nothing when an Austin requisition opens. Telling people to type more into a field the system ignores is asking them to compensate for the schema.
How do financial advisors keep clients? The research points to the person
Advisory is the cleanest test of whether the relationship or the firm owns the client, because advisors change firms and you can watch where the assets go. Researchers have studied exactly that, and the pattern they point to is that clients tend to follow the advisor.
If that holds, the firm's real asset sits with the person across the table, and the platform holds a ledger of what that relationship produced.
Recruiting runs on the same logic. Teams call the runners-up from past searches silver medalists, and re-engaging them is one of the oldest moves in the trade. The candidate already knows you. Whether the second call lands depends almost entirely on whether you remember what they told you the first time.
What the research does and doesn't show
The paper measures client movement when advisors switch firms. It says nothing about CRMs or note-taking. The step from clients follow the person to tools should store the person is our argument, built on that finding.
Where the Austin line gets lost: capture, attachment, recall
Walk the recruiter's example back and the detail fails at three separate points. Each one is a design decision, and each one shows up in advisory too.
First, capture. The candidate says it twenty minutes into a phone screen. There's no slot for it in the moment, so it lives in the recruiter's head until the next free gap, which might come after four more screens. By then it's 'relocating, maybe?' or it's gone.
Second, attachment. If the note gets written at all, it can end up hanging off the application to that one role. When the role closes, the note gets archived with it. In advisory, the college remark lands in a meeting log tied to a review date, several clicks away from the household summary the advisor actually opens.
Third, recall. Six months on, nothing surfaces the line when it becomes relevant. The recruiter would have to remember that a note exists in order to go find the thing they forgot.
Fix capture alone and you still lose it at attachment. Fix attachment and recall still depends on memory. The gap closes only when the detail is captured in the moment, stored against the human, and visible the next time you reach for them.
What changes if the gap is structural
Stop grading relationship work by activity counts. Logged calls measure effort against the pipeline, and a team can hit every activity target while every follow-up opens like a cold call.
Run a different audit instead. Take your twenty most important relationships, open each record, and try to find one thing the person told you that has nothing to do with the deal: a move, a kid, a boss leaving. If you can't find one for most of them, the system stopped helping a long time ago.
Keep the pipeline tool. It's good at what it was designed for, and forecasting, reporting and compliance depend on it. What it needs is a person layer alongside it, one built for the sentence instead of the stage.
For recruiting leads and branch managers, that moves follow-up quality off the training budget and onto the tooling list.
The pipeline tells you when to call. The story tells you what to say.
Where Met fits
Met was built around the first failure point. You meet someone, scan the card or add the contact, and save the line that mattered while you're still standing there, so it's tied to the person from the first minute. Follow-ups start from what they actually said.
Keep your ATS or advisor CRM running the pipeline. Met holds what those tools were never designed to hold, and it stores your contacts in your own iCloud, with no ads and nothing sold.
For a recruiter screening dozens of people a month, or an advisor who sees a household once a year, that one line is usually the whole difference between a call that sounds remembered and one that sounds scripted.
Save the line that matters while they're still talking. Get Met.
Recruiters and advisors already have a system for the pipeline. What they're missing is a place for the sentence someone said in passing: the move, the kid, the reason the next call should be warm. Met captures that line at the moment you meet someone, keeps it attached to the person, and stores everything in your own iCloud with no ads and no data sold.