Following up after a conference: a working method

A conference is not over when the closing keynote ends. It is over about a week later, when every conversation you had has either turned into a next step or quietly expired. The follow-up is where the ticket price is won or lost — and it is the part almost nobody plans. Here is a method that works. It needs no particular tool: a notes app and an inbox are enough.

Why conference follow-up fails

The failure mode is nearly always the same, and it is not laziness. You leave the event with a pile of undifferentiated contacts — cards, badge-scan exports, half-remembered hallway chats — and you tell yourself you will “go through them properly” at the weekend. The pile makes every message equally hard to start, because before you can write any of them you have to reconstruct who the person was and what you talked about. Reconstruction is expensive, so the pile waits. Then your normal workload returns, the reconstruction gets harder by the day, and eventually sending anything at all would feel strange. The conversations were real; the follow-up simply never had a system.

Notice what actually failed there. Not the writing — the remembering. Follow-up fails at the moment context is lost, which is usually days before you open the laptop to write.

The window: about forty-eight hours

A working rule — offered as practice, not as research — is that the first follow-up should land within roughly forty-eight hours of the conversation. Inside that window, you are still a shared memory: the other person can place you, the topic, and the thing you said you would send, without effort. Your message completes a conversation that is still open in both heads.

After a week, the same message does a different job. Now it has to reintroduce you, justify itself, and ask the reader to do the reconstruction work you skipped. It can still succeed — relationships survive slow replies — but you have converted a warm continuation into a cold outreach, and cold outreach competes with everything else in their inbox. The window is not a deadline to panic about. It is simply the period in which following up is cheap, for both of you.

Follow-up starts at the event, not after it

The single highest-leverage change you can make has nothing to do with writing: capture the context of each conversation while it is still happening in your head. Thirty seconds on the walk to the next session, four lines per person: where you met, what you actually talked about, why this person matters to you, and what — if anything — was promised in either direction. That last line is the engine of the whole method, because a promise is a pre-written follow-up: you already know what the message says.

If you do nothing else from this article, do that. The mechanics of remembering at volume — why “I’ll remember” fails on a thirty-conversation day, and what to write instead — are the subject of the companion guide on how to remember people you meet.

Sort by intent before you write a word

Back home, resist the urge to start writing from the top of the pile. Sort first. Every person you met falls into one of three lanes:

Promised — you owe them something, or they owe you: a deck, an introduction, a date for a call. These go first, always, because a kept promise within the window is worth more than any clever message. Alive — no explicit promise, but a real reason to continue: a shared problem, an obvious collaboration, a person you plainly want to know in a year. These get a specific message inside the window. Polite — pleasant conversations with no next step. Let these go, guilt-free, or send nothing more than a genuine one-line note. Padding your follow-up queue with polite-lane messages is how the promised lane misses its window.

What to actually write

A good follow-up has four properties: it references the specific conversation, it delivers anything promised, it proposes exactly one next step, and it is short. In practice that looks like this:

“Hi Lena — good to talk at the logistics panel yesterday about your cross-border returns problem. Here’s the deck I mentioned. If it’s useful, I’d happily walk your ops lead through it — would a short call in the next two weeks work?”

Three sentences: the anchor (which conversation, which topic), the delivery (the promised deck), the single ask (one call, loosely time-boxed). No biography, no company pitch, no “synergies”. The anchor matters most — it is the proof that this message was written for one person, and it is only possible if you captured the context at the event.

The anti-pattern is equally recognizable: “Great to meet you at [Event]! Let’s stay in touch.” It references nothing, delivers nothing, and asks for nothing — a message that could have been sent to all thirty people, and reads that way. The same goes for silently adding people to a newsletter, or a connection request with no note. If you cannot write one specific sentence about the conversation, the honest move is the polite lane, not a generic blast.

The second follow-up

Most guides stop at the first message; most relationships are decided by the second. Silence after a good follow-up is rarely rejection — conference weeks are chaotic on both sides. Wait a week or so, then send one short, unresentful nudge that adds something: a link relevant to what you discussed, a concrete easier ask, or simply “bumping this in case it sank”. One nudge, not three. If the second message also lands in silence, park the relationship rather than deleting it — people resurface, and the context you captured keeps its value for the day they do. Which is exactly why the capture, not the message, is the asset.

Where Affinira fits

Everything above works with paper. Affinira for conferences takes the friction out: scan their card, keep the context attached to the person, and hold a dated follow-up for each one. The method costs nothing either way.