Your best conference follow-up gets written before you check in.

The cursor after "Great meeting you"

Tuesday morning, back at your desk. A few dozen contacts from the show are sitting in your phone, and you've opened a reply to the VP you talked with near the coffee line. You type "Great meeting you at the conference" and then you stop.

What did you talk about? Something about their team growing. Maybe a migration. You remember the lanyard color better than the conversation.

So the message goes out the way most of them do: a pleasantry, a link, a "would love to find time." It reads like every other email they got that week, because it is one of them.

The trouble with that email started weeks earlier, on the day you registered and didn't decide who you were going there to meet.

The anchor gap: follow-up quality is set before the event

Call it the anchor gap. A follow-up can only point back to something the conversation actually contained, and a conversation mostly contains what you walked in ready to ask.

Walk the floor with no list and you get pleasant, interchangeable talk. Flights, the keynote, the hotel, what do you do. Nothing in that exchange gives the email a hook, so the email reaches for the template.

Walk in with five to ten named people and a question for each, and the conversation has a spine. They answer the question. The answer becomes the anchor, and the follow-up has a real thing to say: you mentioned the vendor review next quarter, here's the comparison I said I'd send.

Specific follow-up is a preparation outcome. Most advice files it under post-event discipline, which is why most advice doesn't fix it.

Specific follow-up is a preparation outcome.

Why "follow up within 24 hours" doesn't fix it

The standard conference advice is about speed and volume. Scan every badge, send within a day, use a template so nothing slips.

Speed matters. We've made that case in The 72-Hour Memory Cliff, and context really does decay fast once you leave the venue. But speed only preserves what you captured. If the conversation had no anchor, a fast follow-up is a generic message that arrives sooner.

Templates make it worse in a quiet way. They let you send a stack of messages that feel finished while every one of them says the same nothing.

And the post-event sprint is where most people try to recover what's missing. They scroll photos, squint at card scans, try to rebuild who said what from memory. That's archaeology, and it's expensive. The cheaper fix sits upstream, before your badge is even printed.

What a badge scan captures, and what the email needs

Budget pressure is sharpening all of this. Marketers on forums like r/b2bmarketing keep asking how to choose the few conferences worth paying for, and the worry underneath is consistent: if you can only afford a handful of events, each one has to produce real pipeline instead of a pile of scans.

Fewer events means each conversation carries more weight. The capture tools most people rely on weren't built for that. Badge scanners, card-scanning apps and lead-retrieval systems across the category do one job well: they record who you met. Name, title, company, email.

What they can't record is why you talked. That reason only exists if you brought it with you.

Put the two side by side and the gap is plain.

How do you prepare for networking at a conference?

Keep it to three sources and one page.

Start with the speaker lineup. Speakers are the easiest people to find and the easiest to open with, because you can reference what they said on stage. Skim the agenda for sessions that touch your buyer's problem and pull the names.

Then the sponsor and exhibitor list. A company paying for floor space is telling you what it wants to be known for this year. Find the person there who matches your target role, usually on LinkedIn, and check whether they're speaking, staffing the booth or posting that they'll attend.

Then the attendee list, if the event publishes one or runs a networking app. Filter hard. You want five to ten names. Fifty is just a badge scanner with extra steps, and the questions get vague fast.

For each name, write one line on why them and one question only they can answer well. Then add what you're listening for, so you know a useful answer when you hear it. Here's the shape of that sheet for an account executive heading to a payments show.

The capture moment changes first, then the email

The bigger shift happens on the floor. When you know what you were listening for, you know what to write down.

The note you take after the conversation gets specific: "moving off current vendor after next quarter, wants a comparison, decides with the CFO." Compare that to "nice, fintech, follow up," which is what most of us type at 4pm on day two with sore feet. Those three specific lines are the follow-up. You just have to send them back in a sentence.

It helps with the unplanned conversations too. Serendipity still happens, and some of the best contacts at any event are people who were never on the list. But with a list in hand you notice them as exceptions, so you give them the same treatment and ask yourself what they said that you can point back to.

So the hours move upstream. You spend a little time before the event deciding what context to collect, and you get back the hours you'd otherwise lose trying to reconstruct it.

Keeping the answer attached to the person

Preparation only pays off if the answer survives the next few conversations. That's the narrow job Met is built for.

Event Mode keeps capture quick while you're still standing in the aisle, so the note about the vendor review lands on that contact before the next introduction pushes it out of your head. When you sit down to write, the follow-up draft has the anchor to work from, because you captured it.

Your contacts live in your own iCloud. There are no ads in your Live Activities pulling at your attention mid-show.

Met can't decide who you should meet. That part's yours, and it's the part that makes everything after it work. Build the list, walk in with the questions, and let the app hold on to the answers.