The value of a conference is almost never the conference. It is the conference follow-up, the message you send three or six weeks later, when the badge is in a drawer and everyone else has forgotten the hallway conversation you had. That is the window where a friendly chat becomes a real opportunity, and it is also the window where most people do nothing, because by then they cannot remember what was actually said. This is a guide to closing that window: when to reconnect, and how to do it so the other person remembers you and wants to reply.
If your problem is earlier in the funnel, keeping track of everyone you met in the first place, start with how to remember everyone you meet at a conference. This post is about what happens after: turning one of those conversations into something months later.
Why does conference follow-up fail?
Because the detail that would make your message land has already evaporated. A 2015 replication of Ebbinghaus's forgetting curve in PLOS ONE confirmed the steep early drop-off in memory: you lose the most right after the conversation, exactly the period between the event and the follow-up you keep meaning to send.
So people default to one of two failures. They fire off a generic "great to meet you" the same day, which reads like the eleven identical emails everyone else sent. Or they wait for the right moment, cannot recall a single specific thing, and never write at all. Both come from the same root cause: nothing was captured while it was fresh.
When should you follow up after a conference?
Sometimes right away, but the follow-up that changes things usually comes later, when you have a real reason. Speed is not the point for a relationship the way it is for a sales lead; relevance is. A message that references the exact thing they were working on, sent the week it becomes relevant to them, beats a same-day pleasantry every time.
That means you are waiting for a trigger, not a calendar reminder. The trigger is when your goal and their situation line up: you need design partners and they mentioned an onboarding problem, or they are hiring and you just met the right engineer. The whole game is being able to recall that overlap weeks after you would normally have forgotten it.
How do you turn a conference conversation into an opportunity?
Four steps, and only the first one is about the event itself:
- Capture the specific detail on the day. Not "met a VP of ops," but "frustrated with their onboarding tooling, building an internal wiki for it." The specific is what you will reconnect on.
- Wait for the overlap. Do not force it. Reconnect when you have something genuinely useful to them, or a reason that serves you both.
- Lead with their thing, not yours. Open on the wiki, the hire, the problem they described. It proves you listened, which almost nobody does.
- Make the ask small and easy to refuse. "No worries if the timing is off" gets more yeses than a hard push, because it does not corner them.
The reason a warm reconnection works at all is trust you already banked in the hallway. A cold outreach has to earn attention from zero. A follow-up that recalls a real conversation borrows the goodwill you built in person, which is why the specific detail matters more than the speed.
Here is how that can play out (an illustration)
The following is a hypothetical, not a real customer, meant to show the mechanics.
Imagine you meet a VP of ops at a side event during a big SaaS conference. You are not pitching. You just bond over a shared frustration with clunky onboarding tools, and she mentions her team is building an internal wiki to fix it. It is a good chat. Then you both fly home and get back to work.
Six weeks later, your own product is ready for design partners. The problem: without a note, that conversation is gone. You remember a face and a vague sense that someone, somewhere, cared about onboarding. With a note, you search "onboarding" in your logs, her name comes up, and there is the line about the internal wiki. Your email opens on the wiki, not a product deck. Because it is specific and clearly aimed at her, it reads as a real message from someone who listened, which is the kind of message people answer.
That is the difference a captured detail makes. It is not magic or a guaranteed deal, just a far better shot at a reply than the generic note you would otherwise have sent, if you sent one at all.
Why is a near-stranger worth the effort?
Because the people you meet once at a conference are precisely the ties research says pay off. In a 2022 study in Science spanning more than 20 million LinkedIn users, moderately weak ties drove more new job opportunities than close contacts did. Your close friends already share your information and your circle. The person you spoke to once, in a hallway, is the bridge to something you do not already have access to.
That is why the forgettable conversation is worth capturing. The weak tie is the valuable one, and the weak tie is exactly the one your memory drops first.
Where Ozzy fits
This only works if the detail is written down somewhere you can search. The fastest way to do that is to log the conversation by voice in the ninety seconds after it ends, while it is fresh, instead of trusting it to memory. Then, weeks later, Ozzy's Discover lets you search your own network for the overlap, so "who did I meet who cared about onboarding" returns a person and the reason, not a blank. If you want the mechanics of that reconnection, finding the right person for a warm intro covers it in detail, and the follow-up mistakes founders make covers what to avoid.
The honest caveat: Ozzy is newer than the incumbents and in private beta, and none of this works if you skip the capture step. The tool makes the detail searchable. You still have to write it down on the day.
FAQ
How soon should I follow up after a conference?
Send a short note quickly if it feels natural, but the follow-up that turns into something usually comes later, when you have a real reason to reconnect. For a relationship, a relevant message weeks out beats a generic one the same day.
What should a conference follow-up message say?
Open with something specific they told you, the project or problem they mentioned, to prove you listened. Then make a small, easy-to-refuse ask tied to a reason that helps them, not just you.
How do I remember what someone said at a conference weeks later?
Only if you captured it at the time. Log a quick note, by voice if that is fastest, right after the conversation, so the specific detail is searchable when the right moment finally arrives.
Why follow up with people I barely know?
Because weak ties, the people you met once, tend to open doors your close circle cannot, since they connect you to information and networks you do not already have. That is what makes the forgettable conference chat worth capturing.
Ozzy is in private beta. Request an invite at tryozzy.xyz.