Every new conference buries the contacts from the last one.

The name you can't place in October

It's October, day two of your seventh conference this year. Someone walks up to the booth, smiles like you're old friends, and says they've been meaning to get back to you since February. You met at the first event of the year. You had a real conversation, and you promised them an intro.

You never sent it. And you can't remember their company.

The February conversation went fine. You captured the card, sent the first follow-up that week and meant to circle back. Then March brought a new event and forty new names, and May brought another. Each batch got your full attention for a week or two. The February batch never got a second look.

The cohort squeeze

Call it the cohort squeeze. With one event, follow-up is a discipline problem, and discipline fixes it. Across a circuit of six to ten conferences a year, it becomes a structural problem that discipline alone can't touch.

The mechanism is simple. Your attention resets to whoever you met most recently. Each new event drops a fresh batch of warm contacts on top of the last batch's unfinished relationships. The new batch always wins because it's louder: newer names, fresher context, more obvious next steps. The older cohort just stops getting looked at.

So your Q1 contacts go cold while you're busy building Q3 relationships. You never decided to let them go. The calendar made that call for you.

You never decided to let the February batch go. The calendar made that call for you.

Why better follow-up habits don't fix it

Most follow-up advice, including ours, treats each conference as a standalone problem with its own clock. [The 72-Hour Memory Cliff](/articles/72-hour-memory-cliff/) covers the first few days after a single event, and that advice holds. But it assumes the event is the only thing going on.

On the circuit, it never is. The tools make it worse, too. Most personal CRMs and contact apps organize by person: an alphabetical list, a search bar, a sort by recent activity. Each of those views hides what you need to see. Alphabetical order scatters a cohort across the whole list. Search only finds people you already remember. Sorting by recency is the worst of the three, because it pushes the oldest cohort to the bottom just when it most needs attention.

None of those views answers the question a circuit operator actually has: how is the February batch doing, as a batch?

How many conference contacts can you keep warm in a year?

Here's the math on a plausible circuit: eight events, roughly six weeks apart, forty meaningful contacts each. Those numbers are only an example, so swap in your own. The pattern holds at almost any size.

By the last event of the year, the circuit alone has left you with 320 relationships you haven't closed out. Robin Dunbar's research puts the number of stable relationships a person can maintain at around 150, and that budget also has to cover colleagues, clients, friends and family. The circuit on its own is more than double that.

Now look at the Q1 cohort. Suppose you split your follow-up attention perfectly evenly across every open contact (nobody does). The February and March people still drop from all of your attention to a quarter of it by November. Recency bias pushes the real number lower.

The circuit in practice

Picture a BD lead working that eight-event calendar. February goes well: a tight follow-up week, a few calls booked, and three people who said "let's talk again after your Q2 planning."

Those three are the most valuable contacts of the year, because they asked for a second touch on a specific timeline. They're also the ones who disappear. By the time Q2 planning wraps, the BD lead has two more events' worth of contacts in the queue, each with a fresh first follow-up due. The "talk again in Q2" notes sit on cards from an event that now feels like it happened last year.

In September, one of the three posts on LinkedIn about a partnership with someone else. No single week was to blame. The relationship just never got picked back up.

The same thing plays out in investor relations, government relations and conference-heavy sales. In a 2026 r/marketing thread, a practitioner running more than ten events a year asked for a dashboard that tracks ROI across the whole calendar. That request is a symptom. The tools report on one event at a time, and the decay happens in the gaps between events.

What a circuit-aware capture system has to do

If the cohort squeeze is real, the fix has to be structural. Four things change.

The event becomes the unit. Every contact carries the event it came from, so you can pull up a cohort as a batch instead of rebuilding it from memory.

Cohort health becomes visible. You should be able to see at a glance how many of February's people have had a second touch, and how many haven't heard from you since the first week.

Old cohorts come back up before new ones arrive. The right time to revisit Q1 is the week before your next event, while you can still act on it. The week after is too late, because forty new names will drown it out.

And triage happens per cohort. You can't keep 320 relationships warm. You can decide, batch by batch, which few from each event get the second and third touch, and let the rest stay friendly acquaintances on purpose.

Where Met fits

Met was built around the moment of capture at an event, and that's where a cohort has to start. Event Mode keeps the room captured while you keep talking, so each contact is tied to the event where you met Yes. In Event Mode, every card captured is saved already linked to the active event, so the event name fills in as where you met without extra typing. You can browse contacts by event: the Events view groups them into per-event lists (with a roster and follow-up counts for each event) and an event's contacts can be exported. A contact can also be unlinked from an event without being deleted.. Contacts live in your iCloud, on your devices, with no ads and nothing sold.

That event tag is the raw material for everything in the previous section. You can't triage a cohort you never recorded as one.

If you're heading into your sixth or seventh event of the year, start small. Capture the next one as a batch. Then, before you fly out, open the last batch and see who's still waiting to hear from you.